AIP-20, AIP-22, index and execution-kernel contract: AIP-22 stage 4 in force on chain 2800 since block 24,300,000 (2026-10-25), dated notes
This commit is contained in:
1 parent
200f4338f0
commit
7932becfb4
4 files changed
+10
-16
No files matched your search
+1
-1
@@ -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
|
||||
from AIP-22 stage 4, whose height is not yet set on chain 2800. Consensus also binds every 128th
|
||||
since block 24,300,000 (AIP-22 stage 4, 2026-10-25). 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.)
|
||||
|
||||
Reference in new issue
Block a user