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.
"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.
Read from the public RPC by this page, in your browser, just now. Every 32nd block carries a certificate of Falcon-512 validator seals bound under the block hash; the seal estimate is (extraData − plain header) / one seal. Verify without this page: the toolkit at git.aere.network runs the same reads against any node you operate.
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.