Every AERE rule change, by block number. Standard Ethereum forks are on Chain parameters; this page is the AERE-specific ones.
The list
| Block | Change |
|---|---|
| 2,137,652 | Block period drops from 1.050 to 0.544 seconds, measured on timestamps. See the note on this height in Chain parameters. |
| 9,189,161 | The AERE EVM milestone: five post-quantum precompiles and EIP-2935 historical block hashes become active. |
| 10,141,734 | Base fee floor: the EIP-1559 base fee cannot fall below 1 Gwei. |
| 13,014,000 | Post-quantum anchor rules armed, minimum seals 0 (warm-up). |
| 13,034,000 | Anchor minimum 3 of 9 valid Falcon-512 seals, f+1. |
| 14,050,000 | Nothing changed. See the correction below. |
| 14,961,456 | Anchor minimum 6 of 9, a full 2f+1 quorum. |
| 17,047,600 | Anchor certificate format v2: hybrid Falcon-512 and SLH-DSA-SHA2-128s. |
| 17,225,968 | Anchor interval moves from 32 to 128, on a grid offset from that height. |
| 17,250,000 | QBFT commit messages require a post-quantum seal. |
| 17,400,000 | QBFT proposal messages require a post-quantum seal. |
| 17,550,000 | QBFT round-change messages require a post-quantum seal. |
| 17,700,000 | QBFT prepare messages require a post-quantum seal. |
The last three are armed and take effect when the chain reaches them. Compare against the current height rather than trusting this table to be fresh.
The correction at 14,050,000
Until 2026-08-19, this project's website, whitepaper and press releases in seven languages stated that from block 14,050,000 no block finalises without a six-of-nine post-quantum quorum.
That was false. The property armed at that height is a per-block rule which the shipped code retires when the anchor rules activate. Reading the source and the deployed bytecode, and then the chain itself, settles it: between anchors, blocks carry zero Falcon seals, and a per-block rule would have rejected all of them.
Nothing changed at 14,050,000. The correction was published the same day, dated, in every language the original claim appeared in. The row is kept in this table rather than deleted, because a fork history that quietly loses a retracted entry is not a history.
How AERE rules activate
By block number, through per-node system properties, not through genesis. The consequences of that choice, including the one that bites, are on Enforcement heights.