aere-network/aere-node
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

SPEC 3.5: the seal-window journal domain AERE-PQ-SEALWINDOW-1 of AIP-21 (patch 0007) documented by dated note; nothing removed

Browse Source
This commit is contained in:
Aere Network 2026-10-07 15:50:25 +03:00
parent e05efd57f2
commit 97542b5f1e
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
SPEC.md
View File

@ -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 - `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 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`). 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-<height / 64>.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 ### 3.6 The canonical registry hash