Dated correction 2026-11-04 (third pass) to vote attribution since block 24,300,000: the second client's proposal, prepare and round-change layers in AIP-20, AIP-22 and the AIP index carry the correction (one path of the second client until 2026-10-31 12:27Z; AIP-22 rule 3, correction of 2026-11-01); a dated note to the note of 2026-09-24 in seven documents outside aips/
This commit is contained in:
1 parent
9b5476a3e4
commit
65d0890c3a
10 files changed
+19
-5
No files matched your search
+2
-2
@@ -40,7 +40,7 @@ consensus already requires a post-quantum seal beside the classical signature on
|
||||
every validator (at the tenth since block 18,131,633), and on every QBFT message at the nine
|
||||
validators that run the primary, Besu-derived client (SPEC section 2.6, since block 17,700,000); the
|
||||
second, Nethermind-derived client applies the rule to proposal, prepare and round-change messages
|
||||
since block 24,300,000 (AIP-22 stage 4, 2026-10-25). Consensus also binds every 128th
|
||||
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). Consensus also binds every 128th
|
||||
block under a hybrid Falcon-512 + SLH-DSA-SHA2-128s certificate; the accounts of users are the
|
||||
remaining classical layer. (Corrected 2026-10-09: until that date this paragraph said that consensus
|
||||
requires "post-quantum seals on every QBFT message", without naming the second client.)
|
||||
@@ -241,7 +241,7 @@ early is safe.
|
||||
criterion of a consensus message. The seal is already required beside the classical signature: the
|
||||
validators that run the primary client count a commit only with a valid Falcon-512 seal of its author
|
||||
since block 17,250,000, and all four QBFT message types since block 17,700,000; the second client
|
||||
requires the seal on commits and applies the rule to the other three types from AIP-22 stage 4. The
|
||||
requires the seal on commits and applies the rule to the other three types from AIP-22 stage 4 (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). The
|
||||
decision recorded in each header remains the classical commit quorum.
|
||||
- **Key reuse and the empty context.** The signature covers the 32-byte `signing_hash` with the
|
||||
empty FIPS 204 context. A key that authorizes a type-`0x50` account MUST NOT be used by a signer
|
||||
|
||||
Reference in new issue
Block a user