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

AIP-22 stage 4 in force on chain 2800 since block 24,300,000 (2026-10-25): READMEs, SPEC and RUN-A-NODE say so, dated

Browse Source
This commit is contained in:
Aere Network 2026-10-25 08:14:30 +02:00
parent 89d557000a
commit c4771b6b32
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
anchor/README.md
View File

@ -72,7 +72,7 @@ without a seal. (*Clarified 2026-10-09:* the words "by the Besu-derived validato
that date. On chain 2800 these four heights are those of the nine validators that run this, the that date. On chain 2800 these four heights are those of the nine validators that run this, the
Besu-derived client, the whole set in September; the tenth validator, admitted at block 18,083,404, Besu-derived client, the whole set in September; the tenth validator, admitted at block 18,083,404,
runs the second, Nethermind-derived client, which refuses an unsealed commit since block 18,131,633 runs the second, Nethermind-derived client, which refuses an unsealed commit since block 18,131,633
and applies the rule to proposal, prepare and round-change messages from AIP-22 stage 4, at block 24,300,000 on chain 2800, a height announced on 2026-10-22.) What a quantum and applies the rule to proposal, prepare and round-change messages since block 24,300,000 (AIP-22 stage 4, 2026-10-25).) What a quantum
adversary cannot do at any height is rewrite history past the last anchor without also forging adversary cannot do at any height is rewrite history past the last anchor without also forging
Falcon-512 and SLH-DSA-SHA2-128s signatures (added 2026-10-01, AIP-22 erratum of that date: except the Falcon-512 and SLH-DSA-SHA2-128s signatures (added 2026-10-01, AIP-22 erratum of that date: except the
last anchor's parent while headers carry ECDSA seals, before stage 5 of AIP-22, since an anchor can be last anchor's parent while headers carry ECDSA seals, before stage 5 of AIP-22, since an anchor can be
@ -196,7 +196,7 @@ This matters more than the file list, so it is stated before it.
| Post-quantum validator identity and the v3 key registry (AIP-22 stage 3, `aere.pq.identityBlock`, `aere.pq.registryV3`) | yes (added 2026-09-23) | **yes**, since block 20,836,228 (2026-09-30) | | Post-quantum validator identity and the v3 key registry (AIP-22 stage 3, `aere.pq.identityBlock`, `aere.pq.registryV3`) | yes (added 2026-09-23) | **yes**, since block 20,836,228 (2026-09-30) |
| Sealing keys read from the v3 epochs, key rotation under an id (AIP-22 stage 3b, `aere.pq.registryV3.keysFrom`, `aere.falcon.keys.next`) | yes (added 2026-09-23) | **keys read from the v3 epoch since block 20,836,228**; no key rotated on chain 2800 | | Sealing keys read from the v3 epochs, key rotation under an id (AIP-22 stage 3b, `aere.pq.registryV3.keysFrom`, `aere.falcon.keys.next`) | yes (added 2026-09-23) | **keys read from the v3 epoch since block 20,836,228**; no key rotated on chain 2800 |
| The post-quantum commit seal bound to the consensus round (COMMIT-2) and the v3 anchor certificate (AIP-22 stage R, `aere.pq.commitRoundBlock`, patch 0010) | yes (added 2026-10-14) | **yes**, since block 24,148,752 (2026-10-24); on testnet 28001 since block 6,157,024 | | The post-quantum commit seal bound to the consensus round (COMMIT-2) and the v3 anchor certificate (AIP-22 stage R, `aere.pq.commitRoundBlock`, patch 0010) | yes (added 2026-10-14) | **yes**, since block 24,148,752 (2026-10-24); on testnet 28001 since block 6,157,024 |
| Message authorship from VERIFIED post-quantum seals, with the startup guards AERE-PQC-FIN-01/02/03 (AIP-22 stage 4, `aere.pq.finalityBlock`) | yes (added 2026-09-23) | **no**; proven on testnet 28001 only (H_fin 3,117,000) | | Message authorship from VERIFIED post-quantum seals, with the startup guards AERE-PQC-FIN-01/02/03 (AIP-22 stage 4, `aere.pq.finalityBlock`) | yes (added 2026-09-23) | **yes**, since block 24,300,000 (2026-10-25); on testnet 28001 since block 3,117,000 |
| Checkpoint option, a header rule that refuses another hash at a checkpoint height (AIP-22 stage 4, `aere.pq.checkpoint`) | yes (added 2026-09-23) | **no**; not configured anywhere | | Checkpoint option, a header rule that refuses another hash at a checkpoint height (AIP-22 stage 4, `aere.pq.checkpoint`) | yes (added 2026-09-23) | **no**; not configured anywhere |
| Headers without ECDSA committed seals, sealed by the proposer's post-quantum seal as extraData element 6 (AIP-22 stage 5, `aere.pq.headerBlock`, guards AERE-PQC-HDR-01/02) | yes (added 2026-09-23) | **no**; proven on testnet 28001 only (H_hdr 3,131,000) | | Headers without ECDSA committed seals, sealed by the proposer's post-quantum seal as extraData element 6 (AIP-22 stage 5, `aere.pq.headerBlock`, guards AERE-PQC-HDR-01/02) | yes (added 2026-09-23) | **no**; proven on testnet 28001 only (H_hdr 3,131,000) |
| The hybrid (SLH-DSA) seal of a commit judged, from the v3 key height, with the key of the v3 epoch in force (a rotated row signs with its new key) | yes (corrected 2026-09-23) | **yes**, since block 20,836,228 (the v3 epoch of chain 2800); on testnet 28001 since 2026-09-23 22:51Z | | The hybrid (SLH-DSA) seal of a commit judged, from the v3 key height, with the key of the v3 epoch in force (a rotated row signs with its new key) | yes (corrected 2026-09-23) | **yes**, since block 20,836,228 (the v3 epoch of chain 2800); on testnet 28001 since 2026-09-23 22:51Z |

4
validator/README.md
View File

@ -512,7 +512,7 @@ Falcon-512 seal of its author, each under its own domain. On chain 2800 the nine
validators refuse a message without a valid seal: COMMIT from block 17,250,000, PROPOSAL from validators refuse a message without a valid seal: COMMIT from block 17,250,000, PROPOSAL from
17,400,000, ROUND-CHANGE from 17,550,000 and PREPARE from 17,700,000. The tenth validator, which runs 17,400,000, ROUND-CHANGE from 17,550,000 and PREPARE from 17,700,000. The tenth validator, which runs
the second client, refuses a COMMIT without one from block 18,131,633 and applies the other three the second client, refuses a COMMIT without one from block 18,131,633 and applies the other three
types from AIP-22 stage 4, at block 24,300,000 on chain 2800, a height announced on 2026-10-22. Each message has two switches, passed like types since block 24,300,000 (AIP-22 stage 4, 2026-10-25). Each message has two switches, passed like
the anchor properties: the anchor properties:
| property | what it does | | property | what it does |
@ -539,7 +539,7 @@ admits you, and the same emission and enforcement heights as the fleet, which th
A validator whose seals are refused does not fork and does not accept anything wrong: it loses its A validator whose seals are refused does not fork and does not accept anything wrong: it loses its
turn as proposer, and the chain continues without it as long as a quorum of the others can seal. turn as proposer, and the chain continues without it as long as a quorum of the others can seal.
**What we do not claim.** Per-block finality on chain 2800 still rests on classical ECDSA, so AERE is **What we do not claim.** Since block 24,300,000 (AIP-22 stage 4) every validator attributes a consensus vote only through its verified post-quantum seal, but headers still carry ECDSA commit seals until AIP-22 stage 5, so AERE is
not a "fully post-quantum consensus" and we do not describe it as one. What you can verify yourself, not a "fully post-quantum consensus" and we do not describe it as one. What you can verify yourself,
without taking our word for it, is the anchor certificate at every 32nd block, with the public without taking our word for it, is the anchor certificate at every 32nd block, with the public
verifier. verifier.