AIP-20, AIP-22, index and execution-kernel contract: AIP-22 stage 4 in force on chain 2800 since block 24,300,000 (2026-10-25), dated notes
This commit is contained in:
1 parent
200f4338f0
commit
7932becfb4
4 files changed
+10
-16
No files matched your search
+4
-2
@@ -27,6 +27,8 @@
|
||||
> chain 2800. See the Errata entry of that date; the Preamble (Requires), the Motivation and Security Considerations carry
|
||||
> dated notes.
|
||||
|
||||
> **Note added 2026-10-25.** Stage 4 is active on chain 2800 since block 24,300,000: from it every validator, on both clients, takes the author of a consensus message from its verified post-quantum seal, and the second client's proposal, prepare and round-change layers, named in the notes above as taking effect at stage 4, are in force. Rule 4 of section 4 (the provisional tail and its rollback) is not part of the stage-4 binaries on chain 2800: neither client implements it at this date, a block is final on import as before, and its post-quantum proof is the anchor that covers it; the bound of rule 1 holds because every anchor height must carry a valid certificate. Headers keep their ECDSA commit seals until stage 5.
|
||||
|
||||
## Preamble
|
||||
|
||||
| Field | Value |
|
||||
@@ -38,7 +40,7 @@
|
||||
| Category | Core |
|
||||
| Status | Draft (design only; nothing described here is implemented or deployed at the Created date) |
|
||||
| Created | 2026-09-23 |
|
||||
| Requires | AIP-15 (anchor certificate under the block hash), AIP-21 (per-block seal record), the per-message post-quantum enforcement of SPEC section 2.6 (on chain 2800: commits at every validator; all four message types at the nine validators that run the primary, Besu-derived client, since block 17,700,000; at the second, Nethermind-derived client, commits since block 18,131,633 and the other three types from stage 4 of this AIP, whose height is not yet set on chain 2800; corrected 2026-10-09, see Errata), AIP-19 (the acceptance process) |
|
||||
| Requires | AIP-15 (anchor certificate under the block hash), AIP-21 (per-block seal record), the per-message post-quantum enforcement of SPEC section 2.6 (on chain 2800: commits at every validator; all four message types at the nine validators that run the primary, Besu-derived client, since block 17,700,000; at the second, Nethermind-derived client, commits since block 18,131,633 and the other three types from stage 4 of this AIP, active on chain 2800 since block 24,300,000 (2026-10-25); corrected 2026-10-09, see Errata), AIP-19 (the acceptance process) |
|
||||
| Supersedes | None |
|
||||
| Superseded-By | None |
|
||||
| Ratification | Not ratified; testnet-gated (chain 28001 first, both clients), second-client-gated (both clients accept and refuse the same headers), founder-gated per activation height (AIP-19), external-audit gated before the canonical rule (section 4 of the Specification) is armed on chain 2800 (the gate AIP-15 already names) |
|
||||
@@ -49,7 +51,7 @@ This AIP makes the finality of every block of an Aere QBFT chain a post-quantum
|
||||
|
||||
## Motivation
|
||||
|
||||
Chain 2800 today has the following measured shape (sources in the Specification): every validator refuses a commit unless it carries a valid Falcon-512 seal bound to its author, and the nine validators that run the primary client refuse every QBFT message on the hot path (proposal, prepare, commit, round-change) without one, since block 17,700,000; the second client, which runs the tenth validator, refuses any commit without one since block 18,131,633, while its proposal, prepare and round-change layers take effect at stage 4 below (`H_fin`, whose height is not yet set on chain 2800); every 32nd block carries a Falcon-512 certificate over its parent under the block hash and every 128th block a hybrid Falcon-512 + SLH-DSA-SHA2-128s one, with at least seven valid seals per scheme of the ten validators (stages 1 and 2 below, active from blocks 20,715,632 and 20,746,736; before them every 128th block, with at least six); and `aere_getPqFinality` returns, on every validator, the Falcon seals it heard for a recent block, re-verified (ten of ten on 2026-09-22). A validator that is online therefore finalizes nothing without post-quantum seals. (Corrected 2026-10-09: until that date this paragraph said that the four message types are refused without a seal "since block 17,700,000 on both clients"; on chain 2800 the second client enforces its commit layer only, and its other three layers take effect at stage 4. See the Errata entry of that date.) (Corrected 2026-10-12: the 2026-10-09 version of this paragraph gave, as today's, the certificate grid and threshold of before stages 1 and 2.)
|
||||
Chain 2800 today has the following measured shape (sources in the Specification): every validator refuses a commit unless it carries a valid Falcon-512 seal bound to its author, and the nine validators that run the primary client refuse every QBFT message on the hot path (proposal, prepare, commit, round-change) without one, since block 17,700,000; the second client, which runs the tenth validator, refuses any commit without one since block 18,131,633, while its proposal, prepare and round-change layers have been in effect since stage 4 below (`H_fin`, block 24,300,000 on chain 2800, 2026-10-25); every 32nd block carries a Falcon-512 certificate over its parent under the block hash and every 128th block a hybrid Falcon-512 + SLH-DSA-SHA2-128s one, with at least seven valid seals per scheme of the ten validators (stages 1 and 2 below, active from blocks 20,715,632 and 20,746,736; before them every 128th block, with at least six); and `aere_getPqFinality` returns, on every validator, the Falcon seals it heard for a recent block, re-verified (ten of ten on 2026-09-22). A validator that is online therefore finalizes nothing without post-quantum seals. (Corrected 2026-10-09: until that date this paragraph said that the four message types are refused without a seal "since block 17,700,000 on both clients"; on chain 2800 the second client enforces its commit layer only, and its other three layers take effect at stage 4. See the Errata entry of that date.) (Corrected 2026-10-12: the 2026-10-09 version of this paragraph gave, as today's, the certificate grid and threshold of before stages 1 and 2.)
|
||||
|
||||
What remains classical is exactly what a node that is NOT online, one that syncs the history, is asked to believe:
|
||||
|
||||
|
||||
Reference in new issue
Block a user