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

+4
View File
@@ -200,6 +200,8 @@ From `H_hdr` (at or above `H_fin`), `extraData` gains element 6, `proposerSeal =
**Note added 2026-10-27 (to the correction above).** The correction says that one consensus message still carries ECDSA. Every consensus message still carries the ECDSA envelope of the upstream wire format, and both clients judge its form, though not its author: the Besu-derived client requires a low s (`SignedData`), and the Nethermind-derived client refuses a message whose envelope does not recover (`BesuQbftWire.Recover`). The D-454 quotas also classify a message by the key that signed its envelope. What the correction says of the commit seal is unchanged. The correction is kept as it was written.
**Note added 2026-10-28 (to the note above).** "The D-454 quotas" in the note above, and in the Errata entry of 2026-10-27, is an internal name. It means the per-author quotas that a client keeps on consensus messages it holds before it can judge them; in the Besu-derived client these are the commits heard before the proposal of their round, kept within a quota per claimed author and per class of the envelope (signed by the same ECDSA key as the commit seal, or by another), in `AereD454PendingCommits` (patches 0009 and 0010 of the aere-node recipe).
### 6. Equivocation evidence and consequences without stake
**Evidence object.** `PqEquivocation = [type, height, round, payloadA, sealA, payloadB, sealB, registryProof]` where `type` is one of the four message domains, the two payloads are the upstream RLP payloads of two messages of that type at the same height and round with different digests (for round-change, different `prepared digest` at the same target round), the seals are the two Falcon-512 seals of the same index over the respective pre-images of SPEC 2.6, and `registryProof` is the v3 Merkle path of that index's row in the epoch bound at `height`. The object is valid iff both seals verify under the row's Falcon key, the index is the same, and the digests differ. A second form, `PqConflictingAnchors = [anchorHeaderA, anchorHeaderB, registryProofs]`, two anchor headers at the same height with different parent hashes and each with a valid certificate of at least Q seals: by the quorum-intersection bound proved for all N in `formal-consensus/qbft_safety_smt.py` (L1: `2Q - N >= f + 1`), the two certificates share at least f + 1 = 4 indexes at N = 10, each of which double-signed. This is accountable safety: a finality violation names its authors by their post-quantum seals, and it needs `K = Q` (section 2), which is one more reason for that step.
@@ -414,6 +416,8 @@ Two refinements to the text above, recorded rather than silently applied: the Me
- 2026-10-27, section 3.3, section 5 and Security Considerations: three dated notes. The row "message authorship" of table 3.3 required the envelope's recovered address to equal `row.ecdsa.addr` while that field exists; from `H_fin` the envelope is not examined for authorship. The correction of 2026-10-25 to section 5 named the commit seal as the one classical element of consensus messages; every message still carries the ECDSA envelope, whose form both clients judge and by whose signer the D-454 quotas classify. "Denial of service by seals" said that the per-peer limits of the clients apply and that a refusal costs 0.068 ms; neither client's consensus layer bounds one peer, and a forged proposal can cost about 1,025 Falcon-512 verifications. Found by an adversarial review of the draft that removes ECDSA from consensus messages.
- 2026-10-28, the note of 2026-10-27 under section 5 and the Errata entry of that date: both named per-author message quotas by an identifier of an internal register ("the D-454 quotas"), defined nowhere in this AIP; a dated note under section 5 now says what they are and where they are in the source.
## Post-Acceptance Outcome Record
Not accepted; nothing to record.