AIP-22 stage 5 live on chain 2800 since block 25,080,000 (2026-10-30): prose, AIPs and dated notes
This commit is contained in:
1 parent
7dcad651ca
commit
412fc73285
11 files changed
+25
-15
No files matched your search
@@ -248,6 +248,8 @@ is byte-for-byte agreement with the NIST KAT and ACVP vectors in both directions
|
||||
recorded in `AERE-NIST-VALIDATION-STATUS.md` section 3.4. Nothing normative in this
|
||||
AIP changed: the precompiles, addresses, encodings and gas constants are untouched.
|
||||
|
||||
**Erratum 2 (2026-10-30).** The Abstract describes AERE consensus as classical secp256k1 ECDSA QBFT and not post-quantum, and the Specification describes blocks as committed by validators signing classical secp256k1 ECDSA committed seals. For when that description held, see the notes of 2026-10-27 and 2026-10-28 at the top of this document, which date it (the second dates the post-quantum layers added to consensus before block 24,300,000). Since block 25,080,000 (AIP-22 stage 5) headers no longer carry ECDSA commit seals, each carrying the Falcon-512 seal of its proposer instead, and, since block 24,300,000 (AIP-22 stage 4), every vote counts only with the verified post-quantum seal of its author, and a commit still carries the ECDSA commit seal of its validator as an additional check, which Aere calls post-quantum consensus, with three limits: the transport between nodes is still authenticated by secp256k1, the ten validators are run by one operator, and no third party has audited it yet. What the note of 2026-10-27 says about the headers, and that Aere does not claim post-quantum consensus, describes chain 2800 below block 25,080,000. What this AIP records, a fork that changed the execution layer only, remains true. The original text is left exactly as published, per AIP-1 section 5.
|
||||
|
||||
The clarification below remains an outcome record rather than an erratum,
|
||||
because this AIP specified five precompiles and five is what is live. The record
|
||||
exists to close off a misreading that arose elsewhere, not to correct this text.
|
||||
|
||||
Reference in new issue
Block a user