AIPs: AIP-20 and AIP-21 status rows carry the chain-2800 deployment of 2026-09-22 (AIP-21 live on all ten validators, AIP-20 armed for block 19,900,000); AIP-22 (post-quantum-only finality) added as a design-only Draft; the index no longer describes the pre-September world (seven validators, one client, no AIP above 19) and states which post-quantum layers are live with their heights
This commit is contained in:
1 parent
a2fe6c46ba
commit
c94b3f5c06
4 files changed
+857
-9
No files matched your search
+24
-9
@@ -44,10 +44,13 @@ document is current.
|
||||
| [17](./AIP-17.md) | One-Gwei EIP-1559 Base-Fee Floor | Standards Track / Core | Final | |
|
||||
| [18](./AIP-18.md) | EIP-2935 on Chain 2800: Deviation from the Written Activation Schedule | Standards Track / Core | Final | |
|
||||
| [19](./AIP-19.md) | AIP Process Hardening | Meta | **Review, not ratified** | |
|
||||
| [20](./AIP-20.md) | Native Post-Quantum Transactions (Type 0x50, ML-DSA Authorization) | Standards Track / Core | **Draft, not ratified; implemented in both clients and proven conformant on shared vectors (2026-09-17); live on testnet 28001 from block 2,212,000 (first type-0x50 transaction at 2,212,032, both clients); on chain 2800 the implementation runs on every node since 2026-09-22 and is armed, uniformly, for block 19,900,000 (per-node property, not a genesis change); no type-0x50 transaction on chain 2800 before that height** | |
|
||||
| [21](./AIP-21.md) | Verifiable Post-Quantum Finality per Block (Side Store, Proof RPC, Anchor as Permanent Record) | Standards Track / Interface (non-consensus) | **Draft, not ratified; first half (retention window + `aere_getPqFinality`) implemented in the Besu-derived client with 7 tests and deployed on testnet 28001 (5 nodes, public door `testnet-rpc.aere.network/finality`) on 2026-09-18; Nethermind port the same day (10 tests) and deployed on the testnet Nethermind validator with its own public door; two-client conformance proven live (`aip21-conformitate/DOVEDESTE.sh`, CONFORM on block 2,250,809); second half (the window on disk, same journal format in both clients) deployed on all six testnet nodes the same day: the window survives a restart in both (1,284 and 1,255 seals re-verified, 0 failed), and a round-1 block is `post-quantum` in both on the same hash (CONFORM 08:49Z, block 2,285,481 and round-1 block 2,285,333); on chain 2800 since 2026-09-22 on all ten validators and both clients (`aere_getPqFinality` answers `post-quantum` with 10 of 10 seals re-verified; dated record at the end of AIP-21)** | |
|
||||
| [22](./AIP-22.md) | Post-Quantum-Only Finality (Chained Quorum Certificates, PQ Validator Identity, ECDSA Demoted to Compatibility) | Standards Track / Core | **Draft, design only (2026-09-23): nothing implemented or deployed; every quantity carries its provenance or is marked not measured** | |
|
||||
|
||||
Numbers are permanent and are never reused, including for withdrawn proposals
|
||||
(AIP-1 section 2). Numbering is contiguous from 1 to 19 with no gaps. No AIP
|
||||
numbered 20 or higher exists in any Aere repository.
|
||||
(AIP-1 section 2). Numbering is contiguous from 1 to 22 with no gaps. No AIP
|
||||
numbered 23 or higher exists in any Aere repository.
|
||||
|
||||
## Which of these are live on chain 2800
|
||||
|
||||
@@ -59,17 +62,29 @@ AIP-3 (500 ms target, 516.4 ms measured), AIP-4, AIP-5, AIP-6, AIP-7
|
||||
block 10,141,734), AIP-18 (EIP-2935 from block 9,189,161). AIP-9 through AIP-14
|
||||
describe the decisions behind the live system.
|
||||
|
||||
**Not live:** AIP-8 (needs a hard fork), AIP-15 (isolated testnet only), AIP-16
|
||||
(a skeleton that verifies nothing), AIP-19 (a process change under review).
|
||||
**Post-quantum layers live on top of QBFT (see `SPEC.md` of the public node
|
||||
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; hybrid
|
||||
Falcon-512 + SLH-DSA since 17,047,600; at least six valid seals per scheme of the ten
|
||||
validators since 14,961,456), 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.
|
||||
|
||||
**Never claimed:** post-quantum consensus. Aere consensus is classical secp256k1
|
||||
ECDSA QBFT at N = 7. Post-quantum applies to signatures, accounts and
|
||||
applications only. The precompiles `0x0AE6` and `0x0AE7` are testnet-only.
|
||||
**Not live:** AIP-8 (needs a hard fork), AIP-15 as written (its testnet R&D form;
|
||||
what is live is the dated list above), AIP-16 (a skeleton that verifies nothing),
|
||||
AIP-19 (a process change under review), AIP-22 (design only).
|
||||
|
||||
**Not claimed:** consensus whose safety does not depend on ECDSA. Aere consensus is
|
||||
QBFT in which classical secp256k1 ECDSA is still a validity criterion on every block
|
||||
and every message, with the post-quantum layers above added to it (hybrid, never
|
||||
"post-quantum only"); AIP-22 is the design for removing that dependence and nothing
|
||||
in it is implemented. The precompiles `0x0AE6` and `0x0AE7` are testnet-only.
|
||||
|
||||
## Governance, stated plainly
|
||||
|
||||
Aere is not yet trustlessly governed. Seven validators, all Foundation-operated,
|
||||
one live client, no external security audit, thin real usage. In that reality an
|
||||
Aere is not yet trustlessly governed. Ten validators (since 2026-09-11), all
|
||||
Foundation-operated, two client implementations (one of each since 2026-09-11) but
|
||||
one operator, no external security audit, thin real usage. In that reality an
|
||||
AIP is not ratified by a vote of independent stakeholders. **The founder decides**,
|
||||
acting through the Foundation account
|
||||
`0x0243A4f47D44b40b65D33f20329dE20D00c6f3C3`, which is a single-key account and
|
||||
|
||||
Reference in new issue
Block a user