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

README: nine validators (seven until 2026-08-09); consensus is classical ECDSA on every block with a post-quantum checkpoint every 32 blocks (>=3 of 9 seals since 2026-08-14); live height dated

Browse Source
This commit is contained in:
Aere Network 2026-08-19 15:50:46 +03:00
parent 76db482aff
commit 53f1b81117
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@ -21,11 +21,13 @@ transactions, because a fork activation is a configuration change and not a tran
not the place to look for evidence. The proof that the precompiles are running is a gas measurement
at `latest`, set out in `DOVADA-PQC-VERIFICABILA-2026-07-20.md`.
**Consensus on chain 2800 is classical secp256k1 ECDSA QBFT.** The post-quantum work lives at the
signature, precompile, account and transport layers. Nothing in this repository makes the consensus
post-quantum, and nothing in it should be read as claiming so. Where you see post-quantum consensus
discussed, it is research about what a future activation could look like, not a description of the
running chain.
**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
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).
Two further limits worth knowing before you judge anything else here:
@ -34,8 +36,8 @@ Two further limits worth knowing before you judge anything else here:
- The on-chain zero-knowledge verifiers are classical BN254. They are broken by Shor's algorithm
like any other elliptic-curve construction, and we do not describe them as quantum-safe.
The network is operated by seven Foundation-run validators, so its Nakamoto coefficient is
effectively one today. That is a real limitation, it is on the roadmap, and it is not fixed by any
The network is operated by nine Foundation-run validators (f=2, commit quorum 6 of 9; seven until
2026-08-09), so its Nakamoto coefficient is effectively one today. That is a real limitation, it is on the roadmap, and it is not fixed by any
code in this repository.
## Which citations you can follow, and which you cannot