AERE Network, system status

Live health of the services this page can actually measure. Every number on this page is read from the chain or from the service itself when the page loads. Nothing here is written down in advance.

Post-quantum finality checkpoints

Last anchor block
Certificate in its header
Certificate form
Anchor interval (blocks)
Message layers enforced
Next enforcement height
Reading the last anchor header…

Every 32nd block (every 128th from block 17,225,968) carries, under its block hash, a certificate of validator post-quantum seals; since block 17,047,600 the certificate is hybrid, Falcon-512 and SLH-DSA-SHA2-128s, at least six validators per scheme (six of the nine of that time; ten validators since 2026-09-11). The four QBFT message types are refused without a post-quantum seal from blocks 17,250,000 (commit), 17,400,000 (proposal), 17,550,000 (round change) and 17,700,000 (prepare); which of those are in force is computed here from the latest block, not written down in advance. The certificate itself is verified from raw header bytes by verify-anchor.mjs; this card only reads whether the header carries one.

Chain liveness

Latest block
Age (s)
Validator set
Proposed a block recently
Faults tolerated / quorum
Gas price (gwei)

"Proposed a block recently" counts how many validators actually produced a block inside the node's recent signing window, read from qbft_getSignerMetrics. It is a separate measurement from the set size, so it can disagree with it, and it will say so when it does.

Network parameters

2800
Chain ID
QBFT
Consensus
Pectra + Fusaka
EVM ruleset
0.5 s
Block time
SP1 + R0
2,106,597
Fusaka fork block
AERE
Native token
Hyperlane-compat
Cross-chain messaging
ERC-4337
Account abstraction
ERC-7683
Intent-based bridging
Across-v3
Solver-based deposits
Pyth IPyth
Pull oracle
drand Quicknet
Verifiable randomness
37.5%
Validator-reward burn share
CoW-batch
MEV-resistant DEX
20% / 5%
Dev share / Treasury

Burn tracker

Held in the burn vault
Splitter counter (independent read)
Forwarded to address(0)
Cross-check not run yet.

The burn share is a cut of the validator reward, not of the base fee, and on an idle chain it is close to nothing. AereFeeBurnVault has no withdraw function and no admin, so native AERE that arrives there is out of circulation whether or not the optional sweepToZero() step has been called. The first two cards read two different contracts and should agree; the line above says whether they do. FeeBurnVault contract · CoinbaseSplitter contract

Public services

Checking…

A browser cannot always tell a service being down from a service refusing to answer this page. When it cannot tell, the light reads NOT MEASURED. It never reads UP on a guess.

dApp pages

A 200 on an HTML file proves the file is served, not that the application behind it works, so this page no longer carries a reachability grid for the dApp pages. Open any dApp from the dApps directory to see its own live state.

Smart contracts

Contracts in the site's known map
Of those, carrying code on chain
On-chain check not run yet.

The first number is the length of the list this page carries, so it cannot drift away from it. The second is measured with eth_getCode against the live chain, which is the check that catches a contract address that points at nothing. Browse the full set in the block explorer.