AERE Network · Whitepaper
Version history
Every version of the whitepaper, the date its content changed, the SHA-256 hash you can recompute yourself, and what changed. Back to the whitepaper.
The rule this list follows. The version changes only when the content changes. It is not a date stamp and is never incremented on a schedule. A number that moves every day whether or not anything was written tells you nothing; a number that moves only on substance, and that you can check by hashing the document, tells you everything.
Refreshing a measured on-chain figure does not create a new version. It changes the document hash, because the bytes changed, and it changes the block height the figures were read at. It leaves the version number alone, because the argument did not change. That is why two hashes are published per entry.
The two hashes
| Hash | What it answers | When it moves |
|---|
| Document | Am I reading the exact bytes AERE published? | Whenever anything changes, including a refreshed on-chain figure. |
| Editorial | Has the argument, structure or claims changed? | Only on a written change. Generated figures are blanked before hashing, so chain movement cannot move it. This is the hash tied to the version number. |
Recompute the document hash of the live page. The command removes the version block first, so the hash cannot depend on itself:
curl -sL https://aere.network/whitepaper | sed '/<!--WP-VERSION-BLOCK-START-->/,/<!--WP-VERSION-BLOCK-END-->/d' | tr -d '\r' | sha256sum
Machine-readable figures, each with its provenance and the block height it was read at: whitepaper-figures.json.
History before 2026-07-20 was not tracked, and this page does not pretend otherwise. Hash-based versioning began on 2026-07-20. Before that date the whitepaper was not under version control in this repository: public/whitepaper.html was an untracked file, so no commit history exists to reconstruct from. The entries below dated earlier than 2026-07-20 are recorded from evidence that survives, namely the version and status strings the document carried in its own cover metadata and the modification dates of archived files. They carry no hash, because no hash was recorded at the time and computing one now from a file that has since been edited would prove nothing. Those entries are marked Not hash-tracked. An honest gap is worth more than a fabricated record.
Entries
2.1.0
2026-07-20
Hash-tracked
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.
Document hashsee /whitepaper-figures.json
Editorial hashsee /whitepaper-figures.json
Figures measured at blocksee /whitepaper-figures.json
2.0
2026-07-11
Not hash-tracked
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.
1.x
date unknown
Not hash-tracked
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.
How an entry gets added
A new entry is added when, and only when, the editorial hash changes. That happens when someone edits the writing, the structure or a claim. It does not happen when a measured figure is refreshed from the chain, and it does not happen because a day passed.
The figures are regenerated on a schedule and checked for drift against the live chain continuously. That is what keeps the document current. The version number is deliberately not part of that loop, because a version that tracks the clock rather than the content is a signal with no information in it.