AIP-20: key reuse with the empty ML-DSA context, and a dated correction on consensus enforcement; AIP-22 and README: seals stated as many as the quorum, proving signing, not decision (erratum of 2026-10-01)
This commit is contained in:
1 parent
c9ba6d4bec
commit
4739d4206b
4 files changed
+24
-7
No files matched your search
+1
-2
@@ -67,8 +67,7 @@ describe the decisions behind the live system.
|
||||
package for the exact rules and heights):** the anchor certificate under the block
|
||||
hash (every 32nd block from 13,014,000, every 128th from 17,225,968 to 20,746,736, every
|
||||
32nd again since, with SLH-DSA every 128th; hybrid Falcon-512 + SLH-DSA since 17,047,600;
|
||||
at least seven valid seals per scheme of the ten validators, the full quorum, since
|
||||
20,715,632, six from 14,961,456), post-quantum validator ids in consensus since 20,836,228
|
||||
at least seven valid seals per scheme of the ten validators, as many as the quorum, since 20,715,632 (the seals prove those validators signed the block, not that it was decided, per the AIP-22 erratum of 2026-10-01), six from 14,961,456), post-quantum validator ids in consensus since 20,836,228
|
||||
(AIP-22 stages 1 to 3, 2026-09-29 and 2026-09-30), and the per-message Falcon-512 enforcement on every QBFT
|
||||
message (heights 17,250,000 to 17,700,000, September 2026). AIP-21's record is live
|
||||
on chain 2800 since 2026-09-22; AIP-20 is deployed and armed for 19,900,000.
|
||||
|
||||
Reference in new issue
Block a user