Dated correction 2026-11-04 (third pass) to vote attribution since block 24,300,000: README, anchor/README and validator/README (QBFT whose votes every validator attributes only through post-quantum seals; the second client's other three message types), one path of the second client until 2026-10-31 12:27Z (AIP-22 rule 3, correction of 2026-11-01)

README.md

@@ -26,7 +26,7 @@ seals at first (f+1 of nine), six of nine, as many as the QBFT quorum of nine (c
 validators on 2026-09-05) the anchor fell on every 128th block instead of every 32nd, with both
 schemes at every anchor; since block 20,746,736 (AIP-22 stage 2) Falcon-512 is required at every
 32nd block again and SLH-DSA-SHA2-128s at every 128th. Since block 20,836,228 (AIP-22 stage 3) the
-header and `qbft_getValidatorsByBlockNumber` name the validators by post-quantum ids. QBFT finalizes every block, whose votes every validator attributes, since block 24,300,000 (AIP-22 stage 4), only through their verified post-quantum seals (since block 25,080,000, AIP-22 stage 5, headers no longer carry ECDSA commit seals and are admitted on the Falcon-512 seal of their proposer alone; a commit still carries the ECDSA commit seal of its validator as an additional check), and node identity and transport (RLPx) remain classical, as does the ECDSA envelope that every consensus message still carries on the wire, whose form both clients judge and which no longer names its author on the Besu-derived validators; the QBFT
+header and `qbft_getValidatorsByBlockNumber` name the validators by post-quantum ids. QBFT finalizes every block, whose votes every validator attributes, since block 24,300,000 (AIP-22 stage 4), only through their verified post-quantum seals (corrected 2026-11-04: from block 24,300,000 until 2026-10-31 12:27Z one path of the second client took the author of a proposal that named a height below 24,300,000 from its ECDSA envelope, as the correction of 2026-11-01 to rule 3 of AIP-22 says) (since block 25,080,000, AIP-22 stage 5, headers no longer carry ECDSA commit seals and are admitted on the Falcon-512 seal of their proposer alone; a commit still carries the ECDSA commit seal of its validator as an additional check), and node identity and transport (RLPx) remain classical, as does the ECDSA envelope that every consensus message still carries on the wire, whose form both clients judge and which no longer names its author on the Besu-derived validators; the QBFT
 messages themselves carry post-quantum seals of their authors on the live fleet (emission since
 blocks 16,620,000 to 16,690,000), with refusal of unsealed messages armed for blocks 17,250,000 to
 17,700,000 (set 2026-09-05; see `anchor/README.md`, the arming table). Correction 2026-08-19: the

anchor/README.md

@@ -31,7 +31,7 @@ should not be confused:
    The schedule is `aere.pq.anchorMinSeals=13014000:0,13034000:3,14961456:6,17102384:0,17102416:6,20715632:7`,
    uniform on all ten validators; the
    startup guard refuses any threshold above N - f = 7, the highest count reachable with the fault
-   budget down. Blocks between anchors carry no certificate of their own (since block 25,080,000, AIP-22 stage 5, headers no longer carry ECDSA commit seals and are admitted on the Falcon-512 seal of their proposer alone; a commit still carries the ECDSA commit seal of its validator as an additional check), and since block 24,300,000 (AIP-22 stage 4) every validator attributes their votes only through verified post-quantum seals, so the post-quantum certificate is a checkpoint about every 20 seconds (32 blocks since block 20,746,736;
+   budget down. Blocks between anchors carry no certificate of their own (since block 25,080,000, AIP-22 stage 5, headers no longer carry ECDSA commit seals and are admitted on the Falcon-512 seal of their proposer alone; a commit still carries the ECDSA commit seal of its validator as an additional check), and since block 24,300,000 (AIP-22 stage 4) every validator attributes their votes only through verified post-quantum seals (corrected 2026-11-04: from block 24,300,000 until 2026-10-31 12:27Z one path of the second client took the author of a proposal that named a height below 24,300,000 from its ECDSA envelope, as the correction of 2026-11-01 to rule 3 of AIP-22 says), so the post-quantum certificate is a checkpoint about every 20 seconds (32 blocks since block 20,746,736;
    128 blocks, about 75 seconds, from block 17,225,968 to block 20,746,736; 32 blocks, about 16 seconds,
    before that), not a per-block quorum.
 3. **The hybrid certificate.** Since block 17,047,600 (2026-09-04) the certificate is the v2, scheme-tagged
@@ -73,7 +73,7 @@ without a seal. (*Clarified 2026-10-09:* the words "by the Besu-derived validato
 that date. On chain 2800 these four heights are those of the nine validators that run this, the
 Besu-derived client, the whole set in September; the tenth validator, admitted at block 18,083,404,
 runs the second, Nethermind-derived client, which refuses an unsealed commit since block 18,131,633
-and applies the rule to proposal, prepare and round-change messages since block 24,300,000 (AIP-22 stage 4, 2026-10-25).) What a quantum
+and applies the rule to proposal, prepare and round-change messages since block 24,300,000 (AIP-22 stage 4, 2026-10-25) (corrected 2026-11-04: from block 24,300,000 until 2026-10-31 12:27Z one path of the second client took the author of a proposal that named a height below 24,300,000 from its ECDSA envelope, as the correction of 2026-11-01 to rule 3 of AIP-22 says).) What a quantum
 adversary cannot do at any height is rewrite history past the last anchor without also forging
 Falcon-512 and SLH-DSA-SHA2-128s signatures (Added 2026-10-01, AIP-22 erratum of that date: except the
 last anchor's parent while headers carry ECDSA seals, before stage 5 of AIP-22, since an anchor can be

validator/README.md

@@ -510,7 +510,7 @@ Falcon-512 seal of its author, each under its own domain. On chain 2800 the nine
 validators refuse a message without a valid seal: COMMIT from block 17,250,000, PROPOSAL from
 17,400,000, ROUND-CHANGE from 17,550,000 and PREPARE from 17,700,000. The tenth validator, which runs
 the second client, refuses a COMMIT without one from block 18,131,633 and applies the other three
-types since block 24,300,000 (AIP-22 stage 4, 2026-10-25). Each message has two switches, passed like
+types since block 24,300,000 (AIP-22 stage 4, 2026-10-25) (corrected 2026-11-04: from block 24,300,000 until 2026-10-31 12:27Z one path of the second client took the author of a proposal that named a height below 24,300,000 from its ECDSA envelope, as the correction of 2026-11-01 to rule 3 of AIP-22 says). Each message has two switches, passed like
 the anchor properties:
 
 | property | what it does |