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
@@ -81,7 +81,7 @@ The rules that get proposals bounced fastest:
|
||||
- **Do not claim post-quantum consensus without its limits.** On chain 2800
|
||||
anchor blocks carry a post-quantum certificate under their hash since block
|
||||
13,014,000, and since block 24,300,000 (AIP-22 stage 4) a consensus vote
|
||||
counts only with the verified post-quantum seal of its author (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); that arrangement has 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. Aere's post-quantum work is also at the signature, account and application layers. A proposal that names fewer of these limits, or blurs them, will be sent back (this
|
||||
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) (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); that arrangement has 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. Aere's post-quantum work is also at the signature, account and application layers. A proposal that names fewer of these limits, or blurs them, will be sent back (this
|
||||
rule corrected on 2026-10-26: until that date it said that Aere consensus is
|
||||
classical secp256k1 ECDSA QBFT).
|
||||
|
||||
|
||||
Reference in new issue
Block a user