From 97542b5f1e8563bce1b88dd0b56590e36fd3409c Mon Sep 17 00:00:00 2001 From: Aere Network Date: Wed, 7 Oct 2026 15:50:25 +0300 Subject: [PATCH] SPEC 3.5: the seal-window journal domain AERE-PQ-SEALWINDOW-1 of AIP-21 (patch 0007) documented by dated note; nothing removed --- SPEC.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/SPEC.md b/SPEC.md index 7e41466..b6af89e 100644 --- a/SPEC.md +++ b/SPEC.md @@ -772,6 +772,14 @@ Falcon key to a validator address with two signatures over two distinct pre-imag - `AERE-PQ-SEALSTORE-1` is the label of the node-local file in which a node persists the seals it has heard for its chain head across restarts (`aere-pq-seals.rlp`); it is not consensus data and a client is free to implement it differently or not at all (source: `PqSealStore.java`). +- Note added 2026-10-07: `AERE-PQ-SEALWINDOW-1` is the domain of the node-local seal-window journal + of AIP-21 (patch 0007, `PqSealWindowStore.java`): segment files of 64 heights (`w-.rlp`), + each a sequence of frames `length(4, big endian) || payload || crc32(payload)(4, big endian)`, the + payload being the RLP list `["AERE-PQ-SEALWINDOW-1", chainId, blockNumber, blockHash, [[index, + signature], ...]]`. Like `AERE-PQ-SEALSTORE-1` it is not consensus data: nothing read back is believed, + every seal is verified again at startup against the registry epoch bound at its height, and a client + is free to implement the journal differently or not at all (the second client writes the same + format; source: AIP-21, "The window on disk"). ### 3.6 The canonical registry hash