AERE Testnet

Chain 28001. The same node software that runs mainnet, with hybrid post-quantum consensus (every 32nd block carries a Falcon-512 validator certificate under its hash) and the enforcement of those seals switched on, and free test tokens so you can build and break things without spending real AERE.

What this is, and what it is not. The testnet is run by the Aere Foundation with five validators, four Hyperledger Besu and one Nethermind, on two hosts, so it is a place to test contracts, tooling and the post-quantum rules, not a demonstration of decentralisation. It may be reset with notice, its tokens (tAERE) have no value, and there is no block explorer for it yet. Everything below is measured against the live testnet when the page loads; if a service is down the page says so.

Connect

Chain ID28001 (0x6d61)
CurrencytAERE (18 decimals)
RPC (HTTPS)https://testnet-rpc.aere.network
RPC (WebSocket)wss://testnet-rpc.aere.network/ws
Block timemeasuring…
Head
Explorernone yet (use the RPC)

Get test tokens

Drip
Cooldown
Faucet balance
Claims so far

Test dollar and x402 payments

tUSD is an ERC-20 with EIP-3009 (transferWithAuthorization) at 0x8215bA247a3574af8EBC36606eB437811E318FBd, 6 decimals, no value: call faucet() from any funded address for 100 tUSD per hour. An x402 v2 facilitator for this chain answers at https://testnet-rpc.aere.network/x402/ (GET /supported, POST /verify, POST /settle) and settles the "exact" scheme on tUSD, sponsoring the gas. A real payment is pushed through it every six hours; the latest result is public at x402-proba.json, next to the load-bench result. Live since 2026-09-02. Mainnet has neither yet: it needs a real EIP-3009 asset first.

Want AERE on your own machine instead? docker run --rm -p 8545:8545 git.aere.network/aere-network/devnet:latest starts the validators' own binary as a local one-validator chain (id 28002) with DEBUG and TRACE open.

What is switched on here

The testnet runs the exact consensus code of mainnet, so what you observe here is what mainnet does or will do. The differences are heights and the number of validators.

Testnet 28001Mainnet 2800
Validators / quorum5 / 4 (Besu 4, Nethermind 1)9 / 6
Block period500 ms from block 1500 ms
Post-quantum precompiles (Falcon, ML-DSA, SLH-DSA)from genesislive
Post-quantum certificate under the block hash (every 32nd block)from block 64; three of four Falcon-512 seals required from block 128live; six seals required (of nine then; ten validators since 2026-09-11)
Post-quantum seals on every consensus messageemitted from block 200; enforced from block 1000emitted on all four message types; enforcement pending activation
Beacon-root and history system contracts (EIP-4788, EIP-2935)deployed in genesisnot deployed

Verify it yourself: fetch any block whose number is a multiple of 32 above 64 and look at extraData; it carries the Falcon-512 certificate (about 2,900 bytes) where ordinary blocks carry about 330. The mainnet verifier at tools/verify-anchor.mjs (with falcon512.mjs next to it) runs unchanged against the testnet, checking the binding under the block hash, every Falcon-512 seal, and the published key manifests:

RPC=https://testnet-rpc.aere.network MANIFESTS=https://testnet-rpc.aere.network/pq/manifests CHAIN_ID=28001 node verify-anchor.mjs

Genesis and peering

The testnet genesis, including the anchored Falcon-512 key registry, is served at /testnet-genesis.json so anyone can check what the chain was born with. The public interface of the testnet is the RPC above; node-to-node peering for outside operators is not open yet. If you want to run a testnet node, ask us and we will peer you.