AIP-21, AIP-22: note added 2026-10-24: stage R (the round-bound post-quantum commit seal, COMMIT-2, and the v3 anchor certificate) is in force on chain 2800 since block 24,148,752; from that block a v3 certificate carrying the quorum of a single round proves the anchor's parent decided; stage 4 takes effect at block 24,300,000 (announced 2026-10-22)

aips/AIP-21.md

@@ -1,5 +1,11 @@
 # AIP-21: Verifiable Post-Quantum Finality per Block (Side Store, Proof RPC, Anchor as Permanent Record)
 
+> **Note added 2026-10-24.** Since block 24,148,752 (2026-10-24; AIP-22 stage R) the post-quantum commit seal this record counts carries
+> the consensus round (COMMIT-2), the record names that round (`decidedRound`, `sealForm` = `anchor-round`), and the anchor certificate
+> is v3: a v3 certificate carrying the quorum of a single round proves that the anchor's parent was decided. The correction of
+> 2026-10-01 below stands for blocks below 24,148,752. The certificate grid on chain 2800 is unchanged (Falcon-512 every 32nd block,
+> SLH-DSA every 128th, at least seven of ten seals per scheme).
+>
 > **Note added 2026-09-30.** Where this document says that only every 128th block carries a certificate, it describes
 > chain 2800 from block 17,225,968 to block 20,746,736 (2026-09-05 to 2026-09-29). Since block 20,746,736 (AIP-22
 > stage 2) a Falcon-512 certificate is carried every 32nd block and SLH-DSA seals every 128th, with at least seven of

aips/AIP-22.md

@@ -1,5 +1,13 @@
 # AIP-22: Post-Quantum-Only Finality (Chained Quorum Certificates, PQ Validator Identity, ECDSA Demoted to Compatibility)
 
+> **Note added 2026-10-24.** Stage R of this AIP (the post-quantum commit seal bound to the consensus round, COMMIT-2, and the v3 anchor
+> certificate that carries the round; `aere.pq.commitRoundBlock`) is in force on chain 2800 since block 24,148,752 (2026-10-24; carried
+> by every validator since 2026-10-21). From that block, an anchor certificate v3 carrying the quorum of a single round proves that the
+> anchor's parent was decided (the withdrawal in the correction of 2026-10-01 is lifted from that block on; below it the correction
+> stands). Stage 4 (per-block post-quantum finality) takes effect at block 24,300,000, a height announced on 2026-10-22. Where this
+> document describes chain 2800 "today", it describes the chain at the date of the note the sentence sits in; the live values are
+> measured on https://aere.network/capabilities.
+>
 > **Note added 2026-09-30.** Where this document describes chain 2800 "today" (a certificate of at least six of ten seals
 > per scheme every 128th block, validators named by ECDSA addresses), it describes the chain before stages 1 to 3 of this
 > AIP. On chain 2800 stage 1 (at least seven of ten seals per scheme, as many as the quorum) is active from block 20,715,632,

execution-kernel/MACHINE-INTERFACE-CONTRACT.md

@@ -316,8 +316,7 @@ The harness prints a NOT MEASURED block naming these on every run, and its JSON
 them in the `honesty` field, so the non-claims travel with every result rather than living only
 in this document:
 
-- **That consensus is post-quantum.** It is not. Consensus finality is classical secp256k1 ECDSA
+- **That consensus is post-quantum.** It is not. Consensus finality is QBFT whose votes every validator attributes only through their verified post-quantum seals since block 24,300,000 (AIP-22 stage 4), with classical secp256k1 ECDSA commit seals in the header until AIP-22 stage 5 and a Falcon certificate at every anchor. MI is an execution seam and says nothing about consensus.
-  QBFT plus a Falcon certificate. MI is an execution seam and says nothing about consensus.
 - **That equal header roots prove independent execution by themselves.** See the honesty boundary
   in section 5. The load-bearing fact is Nethermind's reject-on-disagreement behaviour, not the
   served bytes.