AERE NETWORK · CHAIN 2800

Architecture, live versus planned

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 is not delivered, and it is drawn separately so that it cannot be mistaken for running architecture. 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 is currently idle. Measured 2026-08-05 at head 12,469,045: 120 headers sampled across the most recent 3,000 blocks carried zero transactions in total, while txpool_status reported 200 pending transactions that are not draining into blocks. The half-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. The cause of the stalled backlog is not yet measured, and is recorded as an open item in verifiable-claims.json.

Aere Network live architecture, chain 2800, with a separate plane for undelivered roadmap items Six delivered layers of chain 2800 on the left, each with a read-only call that verifies it, and each labelled with what it does not prove. On the right, a visually separated plane of four items that are NOT delivered on mainnet: the certificate anchor, Block-STM parallel execution, Adaptive QBFT, and the 273,000 TPS ceiling. A banner across the top of the left plane records that the chain is idle, so the block interval measures a timer rather than throughput. Aere Network · Architecture, live versus planned Every box on the left resolves to a read-only call you can run. The right plane is not delivered, by design. MEASURED 2026-08-05 · HEAD BLOCK 12,469,045 CHAIN ID 2800 (0xaf0) · 11 PEERS METHOD FOR EVERY FIGURE: /verifiable-claims.json LIVE ON MAINNET, VERIFIABLE NOW PLANNED, NOT DELIVERED THE CHAIN IS IDLE. Sampled 2026-08-05: 120 headers across the most recent 3,000 blocks, 0 transactions in total, while 200 transactions sit pending. Nothing below is a throughput figure. 1 Public read surface Two independent public endpoints. No wallet and no account is needed to check anything below. rpc.aere.network · rpc2.aere.network · besu/openjdk-java-25 · 11 peers · eth_syncing false LIVE 2 Application layer · post-quantum verifiers as ordinary contracts Each has runtime bytecode you can hash, and a real transaction receipt on this chain with block and status. Falcon-512 0x4E8e…8fFC · Falcon-1024 · ML-DSA-44 · XMSS RFC 8391 · zkML Groth16 · ZKScreen SP1 LIVE 3 EVM execution, strictly sequential Standard Besu execution, one transaction after another. We say so plainly because the opposite claim is common and cheap to make. Parallel execution exists in the rollup sequencer only, drawn on the right. LIVE 4 Native post-quantum precompile band 0x0AE1 to 0x0AE5 SHAKE256, Falcon-512, Falcon-1024, ML-DSA-44, SLH-DSA-128s, live since block 9,189,161. Proven by cost above a codeless control, calibrated on two costs the EVM specification fixes, not Aere: 0x04 and 0x02. LIVE 5 Consensus: QBFT signed with classical secp256k1 ECDSA 7 validators, quorum 5, f=2, all operated by the Foundation. Mean header interval 0.5236 s over 100,000 blocks, on EMPTY blocks. Block signing is NOT post-quantum, and no chain here claims otherwise. LIVE 6 Fee rule and burn path · deployed, and not flowing today Base fee floor of 1 Gwei from block 10,141,734. The splitter stores a 37.5% rate under a 50% code ceiling, but the vault balance has not moved. The VAULT has no owner; the SPLITTER rate is settable by one key. LIVE Roadmap, drawn separately so it can never be read as running architecture. PROVEN ON A TEST NETWORK Certificate anchor V2 Makes the block hash cover the Falcon certificate. K=3 at N=7 keeps full quorum margin. Not armed on mainnet. This is the single largest open gap in the system. L2 ONLY, NOT ON L1 Block-STM parallel execution The executor is real and benchmarked, and it runs in the rollup sequencer. The Besu base layer stays sequential. See box 3, which says the same thing from the other side. NO SUCH COMPONENT “Adaptive QBFT” A name on a slide. No code, no configuration flag and no measurement anywhere in the system. It is listed here so that nobody can mistake it for a layer that exists. WITHDRAWN, DERIVATION FAILS 273,000 TPS ceiling Described as arithmetic from gas limit over block time. The live gasLimit is 2^53-1, a JavaScript artifact, so that arithmetic gives ~8e11, not 273,000. Never measured, and the stated derivation does not reach the number. VERIFY THIS DIAGRAM WITHOUT TRUSTING US eth_chainIdproves box 10xaf0chain 2800 eth_call 0x…0AE5 data 0x00…20proves box 40x46b9dd2b0ba88d13…646ed5762fthe NIST SHAKE256 answer eth_getBalance 0x696afDF4… at latest and latest-400identicalbox 6, the burn is not flowing Every figure above carries its method, its block, and what it does NOT prove, in aere.network/verifiable-claims.json. Run them all at once with aere.network/verifiable-claims-check.py.
Figure 1. Chain 2800 as it runs on 2026-08-05. The left plane is measured; the right plane is not delivered. Nothing on the right has a deployed address, and the diagram says so on each card rather than leaving it to the reader.

Why the roadmap is on a separate plane

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 does exist and is benchmarked, but it runs in the rollup sequencer; the Besu base layer executes strictly sequentially, which is why box 3 states that in the first line rather than burying it.

Run the diagram yourself

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

What each box does not prove

BoxProvesDoes not prove
1. Read surfaceAn EVM endpoint exists, self-reports chain 2800 and is not syncing.Nothing about decentralization or control. One machine can answer all of it.
2. VerifiersContracts have runtime bytecode and successful historical receipts.A successful receipt means execution did not revert, not that the cryptographic content was meaningful.
3. Sequential EVMStandard Besu execution semantics.Nothing about capacity. The chain is idle, so nothing here is stressed.
4. PrecompilesCode 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. Consensus7 validators and 5 committed 65-byte seals, readable out of every signed header.That the 7 keys are held by independent parties. They are not. The effective Nakamoto coefficient is 1.
6. Burn pathThe 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.

Sources

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.