Version history

A sweep of factual corrections after a measured audit of the document against the live chain. Every item below was re-read from a public node before it was written, and the corrections run in both directions.

• Corrected both hard-fork activation heights. The document gave Pectra at block 2,075,363 and Fusaka at 2,106,606. Both forks are gated by timestamp, so the height must be read off the chain, and both published figures were too high, by 22 and 9 blocks. The measured heights are 2,075,341 and 2,106,597, re-derived twice over: 2,075,341 is the first block carrying a requestsHash header field and also the first whose timestamp reaches pragueTime, and 2,106,597 is the first whose timestamp reaches osakaTime.
• Withdrew "every Ownable contract is Foundation-owned". Of the 191 addresses in the canonical registry, 71 answer owner(); 57 return the Foundation account and 14 return an operational deployment account awaiting transfer. The word "every" was false and the count is now published in its place.
• Withdrew "the route owner cannot forge a verification". Each concrete verifier is immutable, but the route owner chooses which contract a selector resolves to, and the routes in use are not frozen, so the guarantee holds against the verifier a route already points at rather than against the owner of the route.
• Corrections that run in our favour, stated as plainly as the ones that do not. The canonical RISC Zero route is live rather than awaiting a signature; the over-18 program is registered on chain with a non-zero authorized root rather than pending; the Governor and Timelock are deployed, with the 48-hour minimum delay reading back from the chain, so what is missing is the ownership transfer and not the code.
• Deprecated addresses now travel with their replacements. The passkey factory, the intent pair, the storage-proof verifier, the aggregator and the Ethereum light client were each cited as current while our own registry marks them superseded. Each now carries what is wrong with it and the live replacement.
• Published the supply position instead of only the allocation. The six genesis wallets hold 2,239,999,990.70 AERE against the 2,800,000,000 cap, and the difference is accounted for rather than left as a gap a reader discovers by adding up the table.
• The same re-stamp failure as last time, caught and closed again. The corrections of 2026-08-01 were applied to the page without re-running the version block, so for a period the published verification command again did not reproduce the published hash. It has been re-stamped and both reader commands were replayed against the exact bytes on disk before this entry was written.

A factual correction, and a repair to the verification scheme itself, recorded together with the failure that prompted it.

• Corrected the sub-second transition height. The document said the transition to sub-second blocks activated at block 2,138,451. The measured height is 2,137,652: the mean block interval over the 200 blocks before it is 1.100 s and over the 200 blocks after it is 0.575 s, which anyone can recompute from public block bodies. All five occurrences were corrected.
• The failure, stated plainly. That correction was applied to the page on 2026-07-20 after the version block had been generated, and the re-stamp was missed. From then until this version was published, the published verification command did not reproduce the published hash, so a reader who followed our own instructions was in effect told the page had been tampered with. It had not been; it had been corrected without being re-stamped. The distinction matters and the process now enforces it.
• Added the content hash as the primary verification: it covers a delimited region holding the measured figures, the table of contents and the nine chapters, so an edit to the surrounding page cannot invalidate it, while any edit to the claims still does. The exact-bytes document hash remains published alongside it.
• Publishing now refuses a mismatched hash. The publish pipeline replays both reader commands over the exact bytes about to be shipped and refuses to publish unless each reproduces, so this class of failure can no longer reach the site.
• Rewrote the block-interval note so it stays true in degraded periods: the measured mean is published against the 500 ms target even when an outage pushes it well above the target, and the note now says exactly that instead of assuming the gap is small.

First version published under provable versioning. The document gained machinery rather than argument: its chain-derived figures stopped being typed by hand and started being generated.

• Added a version block carrying the semantic version, the date content last changed, both hashes, and the block height the measured figures were read at.
• Added a Measured on chain panel whose values are generated from a read-only RPC at a single pinned block height, so the figure set is internally consistent rather than assembled from readings taken minutes apart.
• Precompile liveness is now proved by measurement instead of asserted. Presence is established by gas differential against a control address holding no code. This proves the five mainnet precompiles are live and independently proves 0x0AE6 and 0x0AE7 are not on mainnet, matching their testnet-only status.
• Burn rate and burn cap are now read from the live splitter contract rather than quoted from a design document, and are cross-checked against the burn vault balance.
• Stated plainly, from measurement, that AERE is not deflationary today: lifetime burn is a rounding error against the 2.8 billion supply because validator coinbase revenue is effectively zero.
• Corrected the stated scale of the burn. While building the generator, the share of supply burned was computed in parts per billion and labelled as a percentage, which overstated it by a factor of ten million. The correct figures are published: 0.049 parts per billion of supply, which is 0.0000000049 percent. The error was caught before publication and is recorded here rather than quietly fixed, because a correction nobody can see is not a correction.
• Published the measured block interval next to the configured 500 ms target rather than in place of it. The long-run measured mean runs a few percent above the target, and the document now says so instead of quoting the target as though it were an observation.
• Labelled the 273,000 TPS figure as an architectural ceiling wherever it is generated, never as a measured rate.
• Restated that consensus is classical secp256k1 ECDSA QBFT, and that post-quantum cryptography on this chain is at the account and application layer.

The version 2 whitepaper. Date and version taken from the status line the document carried in its own cover metadata, which is self-reported and was not independently recorded at the time.

• What specifically changed between version 1 and version 2 is unknown. No changelog was kept and the file was not under version control, so any list here would be reconstruction presented as record.
• An archived copy of the version 1 document is retained at whitepaper-v1-archive.html.
• No hash is published for this entry. None was recorded at the time, and the file has been edited since.

An earlier revision, retained at whitepaper-v1-archive.html.

• Publication date unknown. The archived file's modification timestamp records when it was last touched on disk, not when it was published, so it is not quoted here as a publication date.
• Revision history within version 1 is unknown.