AERE NETWORK · CHAIN 2800
Every box on the left of the diagram resolves to a read-only call you can run against a public endpoint, with no wallet and no account. The right-hand plane holds two components that are live but were once shown as roadmap (each card carries its activation date) and two items that are not delivered; it is drawn separately so that nothing on it can be mistaken for the measured layers on the left. Where a figure is a specification rather than a measurement, it says so on the diagram itself.
Read this before you read the diagram. Chain 2800 carries almost no transactions. Re-measured 2026-09-10 at head 17,965,012: 120 headers sampled across the most recent 3,000 blocks carried one transaction in total, and txpool_status reported 0 pending and 0 queued. (First measured 2026-08-05 at head 12,469,045: zero transactions in the same kind of sample and 200 pending transactions that were not draining; that backlog is gone.) The sub-second block interval below is therefore a measurement of a timer, not of a system under load, and no throughput figure can be inferred from it; see verifiable-claims.json.
An architecture diagram that shows an undelivered component next to a running one is a false statement in visual form, and it is the kind an engineer disassembles in under a minute. Two items in particular have appeared in Aere material as if they were layers. Adaptive QBFT does not exist: there is no code, no configuration flag and no measurement of it anywhere in the system. Block-STM parallel execution exists in two places: a Rust executor benchmarked in isolation and used by the rollup sequencer, and, since 2026-09-05, our own multi-version block processor inside the Besu fork, switched on on all nine Besu mainnet validators and proven on real chain-2800 blocks with a recorded negative control. It stays on this plane because it buys nothing measurable while blocks carry at most one transaction, which is why box 3 says so in its first line rather than burying it.
These are the exact calls. They are read-only, they need no wallet, and they return the same answer from any node. If you script them, set a User-Agent header: the CDN in front of these endpoints answers HTTP 403 to the default Python urllib agent, which has nothing to do with the chain and has fooled people before.
$ curl -s -X POST https://rpc.aere.network -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_chainId","id":1}'
{"jsonrpc":"2.0","id":1,"result":"0xaf0"}
$ curl -s -X POST https://rpc.aere.network -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_call","params":[{"to":"0x0000000000000000000000000000000000000AE5",
"data":"0x0000000000000000000000000000000000000000000000000000000000000020"},"latest"],"id":1}'
{"jsonrpc":"2.0","id":1,"result":"0x46b9dd2b0ba88d13233b3feb743eeb243fcd52ea62b81b82b50c27646ed5762f"}
# compare against a value we cannot choose:
$ python3 -c "import hashlib; print(hashlib.shake_256(b'').hexdigest(32))"
46b9dd2b0ba88d13233b3feb743eeb243fcd52ea62b81b82b50c27646ed5762f
$ curl -s https://aere.network/verifiable-claims-check.py -o check.py && python3 check.py
PASS 74 FAIL 0| Box | Proves | Does not prove |
|---|---|---|
| 1. Read surface | An EVM endpoint exists, self-reports chain 2800 and is not syncing. | Nothing about decentralization or control. One machine can answer all of it. |
| 2. Verifiers | Contracts have runtime bytecode and successful historical receipts. | A successful receipt means execution did not revert, not that the cryptographic content was meaningful. |
| 3. Sequential EVM | Standard Besu execution semantics. | Nothing about capacity. The chain is idle, so nothing here is stressed. |
| 4. Precompiles | Code executes at 0x0AE1 to 0x0AE5 at costs that are constants in the client source. | Execution, not correctness. And the zero cost at 0x0AE6 and 0x0AE7 is consistent with absence, not proof of it; absence is asserted from the node's own eth_config enumeration. |
| 5. Consensus | 10 validators and 7 committed 65-byte seals (since 2026-09-11; 9 and 6 before), readable out of every signed header. | That the 10 keys are held by independent parties. They are not. The effective Nakamoto coefficient is 1. |
| 6. Burn path | The contracts are deployed, the rate is on-chain, and the vault has no owner and no withdrawal path. | That anything is being burned. The vault balance is unchanged, and the splitter's rate is settable by a single externally owned key. |
Machine-readable claim layer, with the verification call, the limits and the refusals: /verifiable-claims.json. Runnable checker, standard library only: /verifiable-claims-check.py. Capability to on-chain evidence map: /claim-evidence.json. Grounding document for machines: /llms.txt.
Measured 2026-08-05 against the public endpoints at head 12,469,045. Every number on this page was executed before it was written. Where a link in the chain of reasoning was not measured, the page says NOT MEASURED rather than filling the gap.