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:
Aere Network committed 2026-10-31 14:55:18 +02:00
1 parent 7dcad651ca
commit 412fc73285
11 files changed
+25 -15

No files matched your search

+4 -5
View File
@@ -46,7 +46,7 @@ document is current.
| [19](./AIP-19.md) | AIP Process Hardening | Meta | **Review, not ratified** | |
| [20](./AIP-20.md) | Native Post-Quantum Transactions (Type 0x50, ML-DSA Authorization) | Standards Track / Core | **Draft, not ratified; implemented in both clients and proven conformant on shared vectors (2026-09-17); live on testnet 28001 from block 2,212,000 (first type-0x50 transaction at 2,212,032, both clients); on chain 2800 the implementation runs on every node since 2026-09-22 and is armed, uniformly, for block 19,900,000 (per-node property, not a genesis change); no type-0x50 transaction on chain 2800 before that height** | |
| [21](./AIP-21.md) | Verifiable Post-Quantum Finality per Block (Side Store, Proof RPC, Anchor as Permanent Record) | Standards Track / Interface (non-consensus) | **Draft, not ratified; first half (retention window + `aere_getPqFinality`) implemented in the Besu-derived client with 7 tests and deployed on testnet 28001 (5 nodes, public door `testnet-rpc.aere.network/finality`) on 2026-09-18; Nethermind port the same day (10 tests) and deployed on the testnet Nethermind validator with its own public door; two-client conformance proven live (`aip21-conformitate/DOVEDESTE.sh`, CONFORM on block 2,250,809); second half (the window on disk, same journal format in both clients) deployed on all six testnet nodes the same day: the window survives a restart in both (1,284 and 1,255 seals re-verified, 0 failed), and a round-1 block is `post-quantum` in both on the same hash (CONFORM 08:49Z, block 2,285,481 and round-1 block 2,285,333); on chain 2800 since 2026-09-22 on all ten validators and both clients (`aere_getPqFinality` answers `post-quantum` with 10 of 10 seals re-verified; dated record at the end of AIP-21)** | |
| [22](./AIP-22.md) | Post-Quantum-Only Finality (Chained Quorum Certificates, PQ Validator Identity, ECDSA Demoted to Compatibility) | Standards Track / Core | **Draft, not ratified; a design only on 2026-09-23; stages 1 to 6 then proven on testnet 28001 in both clients (from 2026-09-23, stage 5 in its corrected form since 2026-09-26 and stage 6 in its repaired form since 2026-10-16; stage records in the AIP); conformance corpus of all nine kinds published 2026-09-27 (`aip22-conformance/`); on chain 2800 stages 1 to 3 active from blocks 20,715,632, 20,746,736 and 20,836,228 (2026-09-29 and 2026-09-30), stage R active since block 24,148,752 (2026-10-24), stage 4 active since block 24,300,000 (2026-10-25), stage 5 not armed (its activation height is the founder's)** | |
| [22](./AIP-22.md) | Post-Quantum-Only Finality (Chained Quorum Certificates, PQ Validator Identity, ECDSA Demoted to Compatibility) | Standards Track / Core | **Draft, not ratified; a design only on 2026-09-23; stages 1 to 6 then proven on testnet 28001 in both clients (from 2026-09-23, stage 5 in its corrected form since 2026-09-26 and stage 6 in its repaired form since 2026-10-16; stage records in the AIP); conformance corpus of all nine kinds published 2026-09-27 (`aip22-conformance/`); on chain 2800 stages 1 to 3 active from blocks 20,715,632, 20,746,736 and 20,836,228 (2026-09-29 and 2026-09-30), stage R active since block 24,148,752 (2026-10-24), stage 4 active since block 24,300,000 (2026-10-25), stage 5 active since block 25,080,000 (2026-10-30)** | |
| [23](./AIP-23.md) | AERE Proof Protocol (Portable Verifiable-Statement Envelope with Optional Post-Quantum On-Chain Finality) | Standards Track / Interface | **Draft, not ratified (2026-09-26); reference verifier and conformance vectors published 2026-09-27; finality proven end to end on testnet 28001** | |
Numbers are permanent and are never reused, including for withdrawn proposals
@@ -72,16 +72,15 @@ at least seven valid seals per scheme of the ten validators, as many as the quor
(AIP-22 stages 1 to 3, 2026-09-29 and 2026-09-30), and the per-message Falcon-512 enforcement: every validator
refuses a commit without a seal, and the nine validators that run the primary, Besu-derived client refuse every
QBFT message without one (heights 17,250,000 to 17,700,000, September 2026); the second, Nethermind-derived
client enforces commits since 18,131,633 and the other three message types since block 24,300,000 (AIP-22 stage 4, 2026-10-25). (Corrected 2026-10-09: until that date this line named the enforcement on every QBFT
client enforces commits since 18,131,633 and the other three message types since block 24,300,000 (AIP-22 stage 4, 2026-10-25). Since block 24,148,752 (AIP-22 stage R, 2026-10-24) every post-quantum commit seal is bound to its consensus round and every anchor certificate is v3, carrying that round; since block 25,080,000 (AIP-22 stage 5, 2026-10-30) headers no longer carry ECDSA commit seals, and each carries the Falcon-512 seal of its proposer. (Corrected 2026-10-09: until that date this line named the enforcement on every QBFT
message without the second client's exception.) AIP-21's record is live
on chain 2800 since 2026-09-22; AIP-20 is deployed and armed for 19,900,000.
**Not live:** AIP-8 (needs a hard fork), AIP-15 as written (its testnet R&D form;
what is live is the dated list above), AIP-16 (a skeleton that verifies nothing),
AIP-19 (a process change under review), AIP-22 from stage 5 (its stages 1 to 4 and stage R are live, above, stage R since block 24,148,752, 2026-10-24, and stage 4 since block 24,300,000, 2026-10-25; stage 5 runs on the public testnet 28001, and its height is not yet set on chain 2800; rule 4 of section 4, the provisional tail, is implemented in neither client).
AIP-19 (a process change under review), rule 4 of section 4 and stage 6 of AIP-22 (the provisional tail and its rollback, implemented in neither client, and the equivocation evidence of section 6, proven on the public testnet 28001 only; stages 1 to 5 and stage R are live, above, stage R since block 24,148,752, 2026-10-24, stage 4 since block 24,300,000, 2026-10-25, and stage 5 since block 25,080,000, 2026-10-30).
**Not claimed:** consensus whose safety does not depend on ECDSA. Aere consensus is
QBFT in which classical secp256k1 ECDSA is still a validity criterion on every block header (its commit seals), with the post-quantum layers above added to it (hybrid, never "post-quantum only"), and since block 24,300,000 (stage 4) a consensus message counts only through its verified post-quantum seal; AIP-22 is the design for removing that dependence: its stages 1 to 4 and stage R are live (above); rule 4 of section 4 and stages 5 and 6 are not. (Corrected 2026-10-09: until that date these two paragraphs said that AIP-22
**Not claimed:** a post-quantum transport. Since block 25,080,000 (AIP-22 stage 5) headers on chain 2800 no longer carry ECDSA commit seals, and since block 24,300,000 (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 we call post-quantum consensus; the transport between nodes (RLPx) is still authenticated by secp256k1, the ten validators are run by one operator, and no third party has audited it yet. Stages 1 to 5 and stage R of AIP-22 are live on chain 2800 (above); stage 6 and rule 4 of section 4 are not. (Corrected 2026-10-09: until that date these two paragraphs said that AIP-22
is design only and that nothing in it is implemented; its stages 1 to 3 have been
live on chain 2800 since 2026-09-29 and 2026-09-30.) The precompiles `0x0AE6` and
`0x0AE7` are testnet-only.