Dated correction 2026-11-04 to 'since block 24,300,000 (AIP-22 stage 4) every vote counts only with the verified post-quantum seal of its author' and its variants: one path of the second client until 2026-10-31 12:27Z (AIP-22 rule 3, correction of 2026-11-01); dated notes at the top of AIP-4, 7, 9, 13, 22
This commit is contained in:
1 parent
f0e476dac3
commit
89ed8ca22d
11 files changed
+18
-6
No files matched your search
@@ -317,7 +317,7 @@ The harness prints a NOT MEASURED block naming these on every run, and its JSON
|
||||
them in the `honesty` field, so the non-claims travel with every result rather than living only
|
||||
in this document:
|
||||
|
||||
- **That consensus is post-quantum.** The contract does not make that claim: MI is an execution seam and says nothing about consensus. What the chain states is that since block 25,080,000 (AIP-22 stage 5) headers no longer carry ECDSA commit seals and, since block 24,300,000 (AIP-22 stage 4), every vote counts only with the verified post-quantum seal of its author, and a commit still carries the ECDSA commit seal of its validator as an additional check, which it calls post-quantum consensus, with three limits: the transport between nodes is still authenticated by secp256k1, the ten validators are run by one operator, and no third party has audited it yet; a Falcon certificate sits at every anchor.
|
||||
- **That consensus is post-quantum.** The contract does not make that claim: MI is an execution seam and says nothing about consensus. What the chain states is that since block 25,080,000 (AIP-22 stage 5) headers no longer carry ECDSA commit seals and, since block 24,300,000 (AIP-22 stage 4), every vote counts only with the verified post-quantum seal of its author (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), and a commit still carries the ECDSA commit seal of its validator as an additional check, which it calls post-quantum consensus, with three limits: the transport between nodes is still authenticated by secp256k1, the ten validators are run by one operator, and no third party has audited it yet; a Falcon certificate sits at every anchor.
|
||||
- **That equal header roots prove independent execution by themselves.** See the honesty boundary
|
||||
in section 5. The load-bearing fact is Nethermind's reject-on-disagreement behaviour, not the
|
||||
served bytes.
|
||||
|
||||
Reference in new issue
Block a user