Every value on this page is readable from a public endpoint. Where a value is surprising, the surprise is explained rather than smoothed over.
Identity
| Parameter | Value |
|---|---|
| Chain ID | 2800 (0xaf0) |
| Network ID | 2800 |
| Consensus | QBFT, Hyperledger Besu implementation |
| Native token | AERE, 18 decimals |
| Genesis supply | 2,800,000,000 AERE, fixed, no minting |
| Genesis file sha256 | 361709dccec4e9fc85be5aec33b30b58a55dc53424087d84c1ad11bd1d944c24 |
| Block 0 hash | 0xd86d57a899cbfa580669f0e1c7cd4ae5f525247c3c823f8f75df176a0c5d7f1a |
The block 0 hash covers every consensus-relevant genesis field including the state root of the allocations, so matching it is the complete identity check. A node that reports that hash is on this chain.
EVM fork schedule
| Fork | Activation |
|---|---|
| Homestead through Shanghai | block 0 / time 0 |
| Cancun | timestamp 1780189051 |
| Prague | timestamp 1780189051, the same instant as Cancun |
| Osaka | timestamp 1780220351 |
| The AERE milestone | timestamp 1783820272, first block 9,189,161 |
The AERE milestone is not upstream Besu's futureEips. Upstream bases that on the unreleased Amsterdam definition, which commits state differently. Chain 2800 isolates it on the Osaka definition and adds, in that same fork, the five post-quantum precompiles and EIP-2935 historical block hashes, which performs one system state write per block into the ring buffer at 0x0000F90827F1C53a10cb7A02335B175320002935.
A client carrying Osaka rules plus those two additions computes the same state roots as the fleet. A client carrying upstream's Amsterdam-based futureEips does not: it stops at block 9,189,161 with a state root mismatch. That is not a hypothetical, it is how the height was measured.
Block period
Configured at 0.5 seconds. Measured 0.57 seconds under normal load.
The transition to sub-second blocks happened at block 2,137,652, where the rate moves from 1.050 to 0.544 seconds per block, a factor of 1.93.
The genesis file every node runs carries 2,138,451 for that transition, not 2,137,652. The two differ by 799 blocks. The value in the running configuration is the one clients must use; the measured value is the answer to "when did the chain speed up". Do not "fix" the genesis: a node with a corrected file computes a different chain. An archive node has resynchronised through that window to 13.4 million without stopping, so the value does not impede sync.
Supply
2,800,000,000 AERE allocated at genesis across six accounts, summing to exactly 2.8e27 wei. There is no minting. The comment strings inside those allocations are not consensus data, are read by no client, and two of them are textually wrong; the file is published byte for byte as the fleet holds it rather than tidied.