chain health

live bft signer participation trend and finality gap. flags a cert as degraded when its signer count falls below the recent-window median minus a threshold. auto-refresh every 20s.

signer count over recent window

each bar is one observed cert in the recent 40-cert window, oldest on the left, newest on the right. bar height is signer count normalized to the max.

json api

programmatic at /api/chain-health. returns {tip, peers, finalized_height, health: {latest_signer_count, median_signers, degraded, sparkline, ...}}. curl-friendly, no auth, no rate limit.

silent finalizers

6 finalizers who signed at least once but have not appeared in the last 50+ observed certs. could indicate node offline, restart drift, or quorum exclusion below the 67% packing threshold. observer-local, not authoritative.

node version fingerprint

our node is running /Zebra:2.5.0/ with protocol version 170130 on chain test. if your own node reports a different subversion or protocol version you may be running a v1 build of crosslink, which can produce mutually invalid bft messages against v2 and cause sustained sidechain mining. check your own node with curl http://127.0.0.1:58000 -H "content-type: application/json" -d '{"jsonrpc":"2.0","method":"getinfo","params":[],"id":1}' and compare.

what this catches

when a server node falls behind on bft and wallets syncing from that node start diverging into sidechains, the live cert signer count typically dips below the recent median. this page surfaces that dip programmatically. for node-state recovery snapshots see community endpoints in the crosslink updates channel. for canonical-chain fork detection see /sync-check.