AIP-21 erratum and AIP-23 note (2026-10-01), formal models annotated: the post-quantum commit seal carries no round

AIP-21: a record that reaches `post-quantum` shows that the commit quorum of distinct validators sealed the block
post-quantum in some round; it does not by itself prove that the block was decided (follows the AIP-22 erratum of the same
day). AIP-23: dated note on what the finality level rests on; level names unchanged. Three formal models carry a dated note
where they treated certificate uniqueness as a property of the code rather than of the model.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
Aere NetworkandClaude Opus 5.5 committed 2026-10-01 17:10:21 +03:00
1 parent 51d63e4c17
commit c9ba6d4bec
6 files changed
+46 -2

No files matched your search

+24 -1
View File
@@ -4,6 +4,12 @@
> 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
> ten seals per scheme since block 20,715,632 (AIP-22 stage 1).
>
> **Correction added 2026-10-01.** The commit seal this record counts carries no round, and the store keeps seals by block
> hash across rounds. A record that reaches `post-quantum` shows that at least the commit quorum of distinct validators
> sealed the block post-quantum, in some round; it does not by itself prove that the block was decided. See the Errata entry
> of that date, which follows the AIP-22 erratum of the same day. Chain 2800 today, below AIP-22 stage 5, is not affected:
> a node imports a block only with the ECDSA commit quorum of a single round.
## Preamble
@@ -254,7 +260,24 @@ local, so the record is read on the validator, or through Aere Cloud when that r
## Errata
None.
- 2026-10-01, Abstract, Motivation, "The record" (the verdict `post-quantum`) and "The permanent record": the record counts
Falcon-512 seals over `M(B) = keccak256(RLP["AERE-PQ-COMMIT-1", chainId, number(B), hash(B)])`, kept by the block's on-chain
hash; neither the seal nor the key carries the round. In QBFT an honest validator can commit a block in one round while a
different block is decided in a later round, and seals over `M(B)` made in different rounds cannot be told apart (AIP-22,
Errata, 2026-10-01). Measured on 2026-10-01 in the reference client: seven valid Falcon-512 seals over `M(p)` from rounds 0
and 2 on a block `p` that no round decided (test class `AereRoundFreeCertificateTest`), and a quorum of one round assembled
from the post-quantum seals of rounds 0 and 2 in the decision collector, which counts the same seals, under the adversary of
AIP-22 who forges ECDSA (`AereRoundFreeCommitTest`, case RF2-Q1). For `aere_getPqFinality` itself this is derived from the
code (the same seal store, kept by hash), not run against the method. Withdrawn as written, until the commit seal binds the
round: (1) "the immediate post-quantum finality of a block has been true" (Abstract) and the reading of the record as the
answer to "is this block final under post-quantum assumptions" (Motivation); (2) the verdict `post-quantum` as finality: the
field and its values stay (clients read them) and mean that at least the commit quorum of distinct validators' seals over
`M(B)` verify now, which is evidence of participation, not of the decision; (3) "The permanent record": the anchor
certificate is the permanent record of the same participation, and the AIP-22 erratum says what it proves. Not affected:
chain 2800 below AIP-22 stage 5, where a node imports a block only with the ECDSA commit quorum of one round, so the block of
a record is final there against an adversary who cannot forge ECDSA; the record as evidence of which validators sealed the
block; and the agreement of the two clients on the same record. The remedy is the one the AIP-22 erratum proposes: a commit
seal that binds the round, with a quorum of one round; it is a coordinated fork and is not scheduled.
## Post-Acceptance Outcome Record