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.
Every 32nd block (every 128th from block 17,225,968 to block 20,746,736) carries, under its block hash, a certificate of validator post-quantum seals, with at least seven validators per scheme since block 20,715,632, as many as the quorum of the ten (six from 2026-08-21, six of the nine of that time; the seals prove those validators signed the block, not that it was decided, per the AIP-22 erratum of 2026-10-01); the certificate carries SLH-DSA-SHA2-128s seals next to Falcon-512 at every 128th block (at every anchor from block 17,047,600 to block 20,746,736). Every validator refuses a commit without a post-quantum seal, and nine of the ten refuse any QBFT message without one. On the nine validators that run the primary, Besu-derived client the four message types are refused without a seal from blocks 17,250,000 (commit), 17,400,000 (proposal), 17,550,000 (round change) and 17,700,000 (prepare); the tenth validator, which runs the independent second, Nethermind-derived client, refuses an unsealed commit from block 18,131,633 and the other three types from AIP-22 stage 4, whose height is not yet set on chain 2800. Which of those are in force, client by client, is computed here from the latest block, not written down in advance. (Corrected 2026-10-09: until that date this paragraph gave the four heights without naming the client, and the two cards above counted the primary client's layers alone, so they read "4 of 4" and "all four in force" for every validator.) The certificate itself is verified from raw header bytes by verify-anchor.mjs; this card only reads whether the header carries one.
"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.
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
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.
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.
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.