Dated corrections (2026-10-28) from the tenth review round: AIP-7, AIP-10, AIP-13, AIP-15, AIP-16, AIP-20 and AIP-22 and seven research documents; each change states its date in the text (what the anchor certificate is bound by, the consensus note after AIP-22 stage 4, and the denial-of-service paragraph of AIP-20, which no longer claims per-peer limits on pool admission)

This commit is contained in:
Aere Network committed 2026-10-28 12:47:00 +02:00
1 parent ac3d299e3f
commit 78cc137b7d
14 files changed
+43 -2

No files matched your search

+2
View File
@@ -1,5 +1,7 @@
# pq-finality-circuit
> **Note added 2026-09-24 (consensus).** Where this document says that consensus is classical secp256k1 ECDSA and not post-quantum, read it as the per-block finality statement it was until block 24,300,000 (AIP-22 stage 4, 2026-10-25). Since that block every validator attributes a consensus vote only through its verified post-quantum seal, and a block is post-quantum final once the next anchor, at most 32 blocks later, carries the certificate that covers it; headers still carry classical ECDSA commit seals until AIP-22 stage 5 (this sentence corrected on 2026-10-25). It no longer describes all of consensus on chain 2800: since 2026-08-14 every anchor block must carry a certificate of validator post-quantum seals under its hash (Falcon-512, with SLH-DSA as well since 2026-09-04), and since 2026-09-05 the nine AERE-client validators (nine of the ten) refuse any QBFT consensus message without a valid Falcon-512 seal of its author, while the tenth, the second client, enforced that seal only on commit messages until block 24,300,000 and attributes every consensus message only through it since (this clause corrected on 2026-10-12 and 2026-10-25). (Note applied to this document on 2026-10-28.)
The off-chain research core of the Aere Network Post-Quantum Finality Certificate
(research item #4).