Dated corrections (2026-10-27): AIP-7 and AIP-13 carry a note that their statements that AERE consensus is classical describe chain 2800 before AIP-22 stage 4 (block 24,300,000); AIP-22 gains three dated notes (section 3.3, the clause on the envelope's recovered address no longer applies from stage 4; the correction of 2026-10-25 to section 5, every consensus message still carries the ECDSA envelope, whose form both clients judge; Security Considerations, 'Denial of service by seals': no per-peer bound in the consensus layer of either client, and a forged proposal can cost about 1,025 Falcon-512 verifications) and an Errata entry; execution-kernel/MACHINE-INTERFACE-CONTRACT.md no longer says it was written the day a consensus milestone went live at block 14,050,000 (withdrawn 2026-08-19) and names what the block hash covers; formal-consensus/RULEAZA-TOT.md dated.
This commit is contained in:
1 parent
6d24576357
commit
ac3d299e3f
5 files changed
+22
-5
No files matched your search
@@ -1,5 +1,7 @@
|
||||
# AIP-13: Post-Quantum Signatures: Falcon and ML-DSA Together, not a Single Lattice Family
|
||||
|
||||
> **Note added 2026-10-27 (consensus).** Where this document says that consensus remains classical (validators sign secp256k1 QBFT), read it as the statement it was until block 24,300,000 (AIP-22 stage 4, 2026-10-25). Since that block every validator attributes a consensus vote only through its verified post-quantum seal, and a commit still carries the ECDSA commit seal of its validator as an additional check; headers are still admitted on their ECDSA commit seals until AIP-22 stage 5, and Aere does not claim post-quantum consensus. The decision this document records, two lattice families plus hash-based schemes, is unchanged.
|
||||
|
||||
## Preamble
|
||||
|
||||
| Field | Value |
|
||||
|
||||
Reference in new issue
Block a user