AERE Network is a public Layer 1 blockchain that runs the Ethereum Virtual Machine. Chain ID 2800. It produces a block roughly every half second with deterministic finality, and it verifies NIST-standardised post-quantum signatures natively, on mainnet, from inside the EVM.
What you can rely on
| Property | Value |
|---|---|
| Chain ID | 2800 (0xaf0) |
| Consensus | QBFT, nine validators, quorum six of nine, f=2 |
| Finality | Deterministic. A committed block does not reorganise. |
| Block period | 0.5 s configured; measured 0.57 s under normal load |
| Native token | AERE, 18 decimals, 2,800,000,000 fixed at genesis, no minting |
| EVM | Homestead through Osaka, plus one AERE milestone |
| Genesis block 0 hash | 0xd86d57a899cbfa580669f0e1c7cd4ae5f525247c3c823f8f75df176a0c5d7f1a |
Every one of those is checkable from a public endpoint. The genesis hash is the complete chain identity check: it covers every consensus-relevant field including the state root of the genesis allocations, so if your node reports that hash you are on this chain and no other.
What makes it different, stated exactly
Two things, and both are narrower than the marketing version of them.
Five post-quantum verifiers live in the EVM. Falcon-512, Falcon-1024, ML-DSA-44 (FIPS 204), SLH-DSA-SHA2-128s (FIPS 205) and SHAKE256 (FIPS 202) are precompiled contracts at fixed addresses, active on mainnet since block 9,189,161. Any contract can call them. All five pass the official NIST Known-Answer Tests on chain. See The five precompiles.
A post-quantum certificate under the block hash. Every 128th block on chain 2800 is an anchor block, and an anchor block does not finalise without a certificate of at least six of nine valid Falcon-512 validator seals bound under its block hash. See The certificate anchor.
What is not true
We would rather write this than have you discover it.
- **A post-quantum verifier called from an ECDSA-authenticated transaction gives no post-quantum
security.** The adversary does not attack the verifier, they forge the outer transaction. Having the precompiles is not the same as having protected accounts.
- Ordinary blocks are secured by classical ECDSA. The post-quantum certificate binds anchor
blocks. It is not the case that no block finalises without post-quantum signatures.
- The AERE Foundation operates the validator set today. What that means for a check you run,
and where the path from here is published, is on Network operations.
- There is no third-party security audit of the post-quantum anchor layer yet. Everything we
publish about it is our own work, offered so that you can re-run it rather than believe it.
Where to go next
- Connect to the network, which takes about a minute.
- Your first transaction.
- If you came for the cryptography, go straight to
Verify an anchor yourself. It is three commands and it does not trust us.