Public EVM Layer 1 · Chain ID 2800 · Live
What it is. AERE is a public blockchain that runs ordinary Ethereum applications, and it is the first one where an account or a contract can require a NIST post-quantum signature, verified by the network itself. Five native PQC precompiles (Falcon-512, Falcon-1024, ML-DSA-44, SLH-DSA) have been active on chain 2800 since block 9,189,161, proven by a real Falcon-1024 signature recorded on-chain.
Why it matters. The signatures guarding almost every coin and contract in existence rest on mathematics that a large enough quantum computer undoes. Anything recorded today can be captured today and opened later. On AERE the defence is not a promise of a future upgrade, it is a signature the live network already verifies. What we do not claim: AERE consensus is classical ECDSA QBFT, not post-quantum; the post-quantum verification lives at the account and contract layer, and every claim below points to a block, a contract, or a command you can run yourself. Loading the full interactive experience.
AERE runs Hyperledger Besu with QBFT consensus and 0.5-second deterministic finality, no re-orgs by construction. Its monetary policy is anchored in immutable code: 37.5% of the validator reward is burned (a Foundation-set rate, hard-capped at 50%) into a burn vault with no admin and no withdrawal path and the owner-less AereSink flywheel, and supply is fixed at 2,800,000,000 AERE with zero mint. Nobody holds a key that can print more, and nobody holds a key that can empty the vault, because no such key was ever written. Throughput scales toward a 273,000 TPS testnet benchmark as the multi-layer roadmap lands; today the network delivers 0.5s finality and sub-cent fees. This is the chain no one can rug.
0x696afDF4f814e6Fd6aa45CE14C498ed9375fB2c6), a stateless sink with no admin and no withdraw.0x69734E4044B1C5943B9256A73De41B101BFA2633): t-of-n ERC-4337 accounts where every signer is verified by the live PQC precompiles, no single key and no admin path.0x79735c31F289F7A4d6Be3E02aaB70B544796D41d).0x3A097A459FD26aC79573aCB5adB51430e473C2f1).# chain identity
curl -s https://rpc.aere.network -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'
Expect "0xaf0", which is 2800.# the validator set, counted rather than described
curl -s https://rpc.aere.network -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"qbft_getValidatorsByBlockNumber","params":["latest"]}'
Returns the validator addresses at the current head. Today that array has 7 entries. Count them, and believe the chain rather than this sentence.# the contracts named above carry code
curl -s https://rpc.aere.network -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_getCode","params":["0x696afDF4f814e6Fd6aa45CE14C498ed9375fB2c6","latest"]}'
Repeat with 0x79735c31F289F7A4d6Be3E02aaB70B544796D41d, 0x3A097A459FD26aC79573aCB5adB51430e473C2f1 and 0x69734E4044B1C5943B9256A73De41B101BFA2633. Each returns deployed bytecode, not 0x.
Method note. A precompile is not a contract and has no bytecode, so
eth_getCode on a precompile address returns 0x either way. Absence of
code is not absence of capability. The real test is a call with a known-good NIST vector and a
second call with a corrupted one, so that a pass can be distinguished from a verifier that
always says yes. Vectors, addresses and encodings are in the whitepaper and the documentation.
Every item on the roadmap is asked one question: does it make the network singular, or only faster? Anyone with money and engineers can buy faster. Singular has to be built. When the two compete for the same people, singular wins. We publish no dates, we finish one thing before starting the next, and nothing counts as finished without a measurement whose test was shown able to fail.
Where the effort goes first.
Real value, none of it changes the category. It follows the column on the left.
The network runs on 7 Foundation validators today. You can read that number straight off the chain with the second command above, and we would rather you did. Full decentralization of the validator set is the declared direction of this network, written here so it can be held against us.
One honest detail, of the kind usually left out. Seven is not a ceiling on ambition, it is a measured engineering choice for this stage: at seven, the fault margin protecting the network is the same margin a larger set would give. Choosing the simpler configuration at equal safety is not a retreat from decentralization, it is how the work that gets us there stays affordable.
We publish no date. A date we have not earned is not a commitment, it is a slogan. What we publish instead is each step, when it is proven, with the measurement attached, and the call above will show a change before any copy on this page does.
The whitepaper (2026 edition) is the full technical specification, published as a web document and as a downloadable PDF. The PDF is re-rendered from the same source as the web edition whenever that source changes, so the copy you download matches the edition on the site.
RPC endpoint: https://rpc.aere.network (Chain ID 2800).