aere-network/aere-research
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

AIPs: dated notes for AIP-20, AIP-21 and AIP-22 on chain 2800; AIP-22 stages 1 to 3 active

Browse Source 
AIP-22 described chain 2800 "today" as the chain before stages 1 to 3. A note dated 2026-09-30 says which
stages are active from which block; the index row and the README summary carry the same heights.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Aere Network 2026-10-01 13:27:18 +03:00
parent 3117a33107
commit 856c5df2f8
5 changed files with 28 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -16,8 +16,11 @@ have been live as precompiles since block 9,189,161. You can call them yourself
**Consensus on chain 2800 is classical secp256k1 ECDSA QBFT on every block, with a post-quantum
checkpoint every 32 blocks.** Since block 13,014,000 anchor blocks carry, under the block hash, a
certificate of validator Falcon-512 seals, and since 2026-08-14 a node rejects an anchor block with
fewer than three valid seals (f+1 of nine, not a quorum; eight or nine are carried in practice). That
certificate of validator post-quantum seals (Falcon-512, with SLH-DSA-SHA2-128s as well since
2026-09-04, at every 128th block since 2026-09-29; every anchor was 128 blocks apart from block
17,225,968 to block 20,746,736). Since block 20,715,632 (2026-09-29) a node rejects an anchor block
with fewer than seven valid seals per scheme, the full quorum of the ten validators; the minimum was
three (f+1 of nine, not a quorum) from 2026-08-14 and six from 2026-08-21. That
checkpoint lives in the aere-node repository (patch 0003 and `anchor/`), not in this one: nothing in
this repository makes consensus post-quantum, and the chain is not "post-quantum consensus" without
that qualification (the per-block quorum claim published on 2026-08-15 was withdrawn on 2026-08-19).

5
aips/AIP-20.md
View File

@ -1,5 +1,10 @@
# AIP-20: Native Post-Quantum Transactions (Type 0x50, ML-DSA Authorization)
> **Note added 2026-09-30.** Where this document says that consensus binds every 128th block under a hybrid
> certificate, it describes chain 2800 from 2026-09-05 to 2026-09-29. Since block 20,746,736 (AIP-22 stage 2) a
> Falcon-512 certificate is carried every 32nd block and SLH-DSA seals every 128th, with at least seven of ten seals
> per scheme since block 20,715,632 (AIP-22 stage 1).
## Preamble
| Field | Value |

5
aips/AIP-21.md
View File

@ -1,5 +1,10 @@
# AIP-21: Verifiable Post-Quantum Finality per Block (Side Store, Proof RPC, Anchor as Permanent Record)
> **Note added 2026-09-30.** Where this document says that only every 128th block carries a certificate, it describes
> chain 2800 from block 17,225,968 to block 20,746,736 (2026-09-05 to 2026-09-29). Since block 20,746,736 (AIP-22
> stage 2) a Falcon-512 certificate is carried every 32nd block and SLH-DSA seals every 128th, with at least seven of
> ten seals per scheme since block 20,715,632 (AIP-22 stage 1).
## Preamble
| Field | Value |

7
aips/AIP-22.md
View File

@ -1,5 +1,12 @@
# AIP-22: Post-Quantum-Only Finality (Chained Quorum Certificates, PQ Validator Identity, ECDSA Demoted to Compatibility)
> **Note added 2026-09-30.** Where this document describes chain 2800 "today" (a certificate of at least six of ten seals
> per scheme every 128th block, validators named by ECDSA addresses), it describes the chain before stages 1 to 3 of this
> AIP. On chain 2800 stage 1 (at least seven of ten seals per scheme, the full quorum) is active from block 20,715,632,
> stage 2 (Falcon-512 every 32nd block, SLH-DSA every 128th) from block 20,746,736, both on 2026-09-29, and stage 3
> (post-quantum validator ids in the header and in `qbft_getValidatorsByBlockNumber`) from block 20,836,228, on
> 2026-09-30. Stages 4 and 5 (per-block post-quantum finality, the header without ECDSA) are not active on chain 2800.
## Preamble
| Field | Value |

10
aips/README.md
View File

@ -46,7 +46,7 @@ document is current.
| [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, not ratified; a design only on 2026-09-23; stages 1 to 6 then proven on testnet 28001 in both clients (2026-09-23 to 2026-09-25, stage records in the AIP); conformance corpus of all nine kinds published 2026-09-27 (`aip22-conformance/`); not armed on chain 2800 (activation heights are the founder's)** | |
| [22](./AIP-22.md) | Post-Quantum-Only Finality (Chained Quorum Certificates, PQ Validator Identity, ECDSA Demoted to Compatibility) | Standards Track / Core | **Draft, not ratified; a design only on 2026-09-23; stages 1 to 6 then proven on testnet 28001 in both clients (2026-09-23 to 2026-09-25, stage records in the AIP); conformance corpus of all nine kinds published 2026-09-27 (`aip22-conformance/`); on chain 2800 stages 1 to 3 active from blocks 20,715,632, 20,746,736 and 20,836,228 (2026-09-29 and 2026-09-30), stages 4 and 5 not armed (their activation heights are the founder's)** | |
| [23](./AIP-23.md) | AERE Proof Protocol (Portable Verifiable-Statement Envelope with Optional Post-Quantum On-Chain Finality) | Standards Track / Interface | **Draft, not ratified (2026-09-26); reference verifier and conformance vectors published 2026-09-27; finality proven end to end on testnet 28001** | |
Numbers are permanent and are never reused, including for withdrawn proposals
@ -65,9 +65,11 @@ describe the decisions behind the live system.
**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
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
(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.