EVM Compatibility
Chain 2800 runs the standard EVM: Ethereum contracts and tooling work unchanged; post-quantum additions live in precompiles and the header, not the EVM.
EVM compatibility means a chain runs the same execution environment as Ethereum: the same bytecode, the same account and transaction model, and the same JSON-RPC interface. A contract compiled for Ethereum deploys unchanged. Wallets, libraries, and developer tools connect without modification, because the surface they depend on is identical: opcodes, state layout, and RPC methods such as eth_call and eth_getStorageAt.
AERE Network is a public EVM L1 with chain id 2800. Blocks are produced roughly every 500 ms under QBFT consensus among nine validators, with a quorum of six. Any standard Ethereum client library can point at the public RPC, https://rpc.aere.network, and a second public read endpoint exists. A second, independently implemented client validates the chain alongside the producing client, which is what client diversity means in practice.
Where chain 2800 extends the EVM, it uses the EVM's own extension mechanism: the precompile. Five post-quantum precompiles have been live since block 9,189,161 at addresses 0x0AE1 through 0x0AE5, covering the Falcon-512, ML-DSA, and SLH-DSA families, validated against NIST test vectors on-chain. The post-quantum anchor lives in the block header, outside the execution layer, so contracts and tooling see an ordinary EVM chain. Consensus signatures for finality remain classical ECDSA secp256k1 today; the post-quantum work adds to the EVM rather than forking away from it.
Verify it yourself
Verify it yourself: POST {"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1} to https://rpc.aere.network; the result is 0xaf0, which is 2800 in hex.