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

This commit is contained in:
Aere Network 2026-08-19 15:50:49 +03:00
parent cde69bd25f
commit 0164207076

View File

@ -14,11 +14,13 @@ Falcon-1024 (`0x0AE2`), ML-DSA-44 (`0x0AE3`), SLH-DSA-128s (`0x0AE4`) and SHAKE2
have been live as precompiles since block 9,189,161. You can call them yourself against have been live as precompiles since block 9,189,161. You can call them yourself against
`https://rpc.aere.network` without asking us for anything. `https://rpc.aere.network` without asking us for anything.
**Consensus on chain 2800 is classical secp256k1 ECDSA QBFT.** The post-quantum work lives at the **Consensus on chain 2800 is classical secp256k1 ECDSA QBFT on every block, with a post-quantum
signature, precompile, account and transport layers. Nothing in this repository makes the consensus checkpoint every 32 blocks.** Since block 13,014,000 anchor blocks carry, under the block hash, a
post-quantum, and nothing in it should be read as claiming so. Where you see post-quantum consensus certificate of validator Falcon-512 seals, and since 2026-08-14 a node rejects an anchor block with
discussed, it is research about what a future activation could look like, not a description of the fewer than three valid seals (f+1 of nine, not a quorum; eight or nine are carried in practice). That
running chain. 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: Two further limits worth knowing before you judge anything else here:
@ -27,8 +29,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 - 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. 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 The network is operated by nine Foundation-run validators (f=2, commit quorum 6 of 9; seven until
effectively one today. That is a real limitation, it is on the roadmap, and it is not fixed by any 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. code in this repository.
Two more limits, both of which cut against claims made in this repository: Two more limits, both of which cut against claims made in this repository: