Monaco, October 2, 2026. Aere Network today confirmed that its public mainnet, chain 2800, now runs the full post-quantum validator stack it set out to build this year. Since block 20,836,228 (September 30, 2026) the ten validators are named in every block header, and in the chain’s own validator-set API, by post-quantum identities derived from their post-quantum keys rather than by classical elliptic-curve addresses. Native post-quantum transactions, signed with the NIST standard ML-DSA, have been accepted on mainnet since block 19,900,000 (September 23). Every node serves a post-quantum finality signal computed from the validators’ post-quantum seals. And since block 18,083,404 (September 11) the tenth validator runs an independent, second implementation of the consensus client, proposing its full share of blocks. All of it is live on a network that has produced more than 21 million blocks, and all of it can be verified by anyone with the open-source tools published at aere.network.
No other public blockchain names its validators by post-quantum identities in the block header, accepts natively post-quantum-signed transactions, and certifies its blocks with post-quantum validator seals under the block hash that an outsider can verify independently. Each of those three things is checkable today, from a laptop, against the live chain.
aere_getPqFinality, a finality signal computed from the post-quantum seals the validators have placed, independent of the classical signatures.0x50 is signed with ML-DSA-87 and carries no classical signature at all; the signing library is open source.qbft_getValidatorsByBlockNumber API.Each stage was activated by block height, rehearsed first on the public testnet (chain 28001), and left verifiable afterwards. The classical transaction path remains available for compatibility, and per-block finality still rests on the classical signatures of the validators: the post-quantum layer seals every consensus message, certifies every anchor and now names every validator. The remaining stages of AIP-22, a block header without any classical signature, are proven on the public testnet and are not deployed on mainnet; their activation is a Foundation decision, announced when taken.
Ask the chain for its validators at any height after 20,836,228 and it answers with ten post-quantum ids; ask at a height before it and it answers with ten classical addresses. The public verifier recomputes the post-quantum certificate under the hash of the latest anchors, seal by seal, against the published key manifests, from any machine and with no account:
curl -O https://aere.network/tools/verify-anchor.mjs -O https://aere.network/tools/mpt.mjs \
-O https://aere.network/tools/falcon512.mjs -O https://aere.network/tools/registry-v3.mjs \
-O https://aere.network/tools/package.json && npm install && node verify-anchor.mjs
The machine-checkable claims behind this release are listed in verifiable-claims.json, which ships with a checker that prints PASS or FAIL; the full fork history, by block number, is at aere.network/docs/network/forks; and the direction of the project, with what is live, what is being built and what is not yet, is published and dated at aere.network/vision.
In keeping with the project’s practice of publishing capabilities and limits together: all ten validators are operated by the Aere Foundation today, so the chain is not yet decentralized and a single organisation could stop it; no completed third-party security audit of the client modifications or the contracts exists yet, and the daily security score at aere.network/security-score.html says so; nine of the ten validators run the same primary implementation, so the second client adds agreement, not yet fault tolerance; per-block finality remains classical; and usage of the network is low, with every throughput figure published as measured, not designed.
Aere Network is cryptographic infrastructure built on a public, EVM-compatible Layer 1 (Chain ID 2800): a settlement layer with half-second finality and a fixed supply of 2.8 billion AERE set at genesis, native post-quantum signature verification, post-quantum validator certificates under the block hash, post-quantum validator identities, native post-quantum transactions, and a verification layer, Aere Cloud, for organisations. Its rule is that nothing is called live until it runs on the real network and a stranger can check it with published tools. Documentation, research and source code: aere.network/papers.html.
Chain ID 2800. Heights named in this release: 17,047,600; 17,250,000 to 17,700,000; 18,083,404; 19,900,000; 20,715,632; 20,746,736; 20,836,228. Specifications: AIP-20 (native post-quantum transactions), AIP-21 (post-quantum finality), AIP-22 (post-quantum identity and header). Verifier and tools: aere.network/tools. Media: [email protected]. Full media kit at the Press and Media Center.
###