AIP-20, AIP-22, README: message-layer enforcement stated per client (corrected 2026-10-09): every validator refuses a commit without a post-quantum seal, the nine primary-client validators any consensus message since block 17,700,000; the second client enforces commits since 18,131,633 and the other three types from AIP-22 stage 4, whose height is not yet set on chain 2800; dated notes and an Errata entry, nothing removed
This commit is contained in:
1 parent
39ec3c684a
commit
3b62b2c757
3 files changed
+55
-11
No files matched your search
+15
-5
@@ -68,19 +68,29 @@ package for the exact rules and heights):** the anchor certificate under the blo
|
||||
hash (every 32nd block from 13,014,000, every 128th from 17,225,968 to 20,746,736, every
|
||||
32nd again since, with SLH-DSA every 128th; hybrid Falcon-512 + SLH-DSA since 17,047,600;
|
||||
at least seven valid seals per scheme of the ten validators, as many as the quorum, since 20,715,632 (the seals prove those validators signed the block, not that it was decided, per the AIP-22 erratum of 2026-10-01), six from 14,961,456), post-quantum validator ids in consensus since 20,836,228
|
||||
(AIP-22 stages 1 to 3, 2026-09-29 and 2026-09-30), and the per-message Falcon-512 enforcement on every QBFT
|
||||
message (heights 17,250,000 to 17,700,000, September 2026). AIP-21's record is live
|
||||
(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 from AIP-22 stage 4, whose height is
|
||||
not yet set on chain 2800. (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 (design only).
|
||||
AIP-19 (a process change under review), AIP-22 from stage 4 (its stages 1 to 3 are
|
||||
live, above; stages 4 and 5 run on the public testnet 28001, and their heights are
|
||||
not yet set on chain 2800).
|
||||
|
||||
**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
|
||||
and every message, with the post-quantum layers above added to it (hybrid, never
|
||||
"post-quantum only"); AIP-22 is the design for removing that dependence and nothing
|
||||
in it is implemented. The precompiles `0x0AE6` and `0x0AE7` are testnet-only.
|
||||
"post-quantum only"); AIP-22 is the design for removing that dependence: its stages
|
||||
1 to 3 are live (above), and its later stages, from stage 4, are not set on chain
|
||||
2800. (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.
|
||||
|
||||
## Governance, stated plainly
|
||||
|
||||
|
||||
Reference in new issue
Block a user