BYTE NEWS — integrity report for the `chain-liveness` dataset ======================================================================== 1 recorded gap(s) in the last 14 days, totalling 3 minutes when this site was not looking. SCOPE One row per chain we watch, as it stands now. The coverage windows below are our own: while we were not looking, a halt could have started and ended without ever reaching this record. COVERAGE — when this dataset's producers were not looking ledgers read: onchain (1 ledger row(s), merged into 1 window(s)) 2026-10-05T06:10:29.648417+00:00 -> 2026-10-05T06:13:29.648417+00:00 3.0 min Chain slowdowns and recoveries we were not reading this while the window was open DENSITY Not a continuous record. A day with no rows on this dataset is a quiet day in the world rather than a gap in ours, so no per-day expectation is stated. PROVENANCE — what produced these rows bitcoin: 1 row(s) — https://mempool.space/api ethereum: 1 row(s) — https://ethereum-rpc.publicnode.com solana: 1 row(s) — https://api.mainnet-beta.solana.com xrp: 1 row(s) — https://xrplcluster.com/ avalanche: 1 row(s) — https://api.avax.network/ext/bc/C/rpc near: 1 row(s) — https://free.rpc.fastnear.com — not currently watched sui: 1 row(s) — https://graphql.mainnet.sui.io/graphql CORRECTIONS — what has been revised since publication (none) OUR OWN DOWNTIME — recorded incidents inside this window 2026-10-07 38 min degraded The wire wrote no ledger row for 38 minutes (stage 'budget') [NOT YET WRITTEN UP] 2026-10-06 44 min degraded The wire wrote no ledger row for 44 minutes (stage 'budget') [NOT YET WRITTEN UP] 2026-10-06 107 min degraded The wire wrote no ledger row for 107 minutes (stage 'budget') [NOT YET WRITTEN UP] 2026-10-06 47 min degraded The wire wrote no ledger row for 47 minutes (stage 'budget') [NOT YET WRITTEN UP] 2026-10-03 39 min degraded The wire wrote no ledger row for 39 minutes (stage 'budget') [NOT YET WRITTEN UP] 2026-10-03 46 min degraded The wire wrote no ledger row for 46 minutes (stage 'budget') [NOT YET WRITTEN UP] 2026-10-02 65 min degraded The wire wrote no ledger row for 65 minutes (stage 'budget') [NOT YET WRITTEN UP] 2026-09-29 57 min degraded The wire wrote no ledger row for 57 minutes (stage 'budget') [NOT YET WRITTEN UP] 2026-09-28 44 min degraded The wire wrote no ledger row for 44 minutes (stage 'budget') [NOT YET WRITTEN UP] 2026-09-28 39 min degraded The wire wrote no ledger row for 39 minutes (stage 'budget') [NOT YET WRITTEN UP] 2026-09-28 37 min degraded The wire wrote no ledger row for 37 minutes (stage 'budget') [NOT YET WRITTEN UP] 2026-09-28 31 min degraded The wire wrote no ledger row for 31 minutes (stage 'budget') [NOT YET WRITTEN UP] 2026-09-25 31 min degraded The wire wrote no ledger row for 31 minutes (stage 'budget') [NOT YET WRITTEN UP] 2026-09-24 31 min degraded The wire wrote no ledger row for 31 minutes (stage 'budget') [NOT YET WRITTEN UP] WHAT THE CHECKS DID NOT CHECK gate of 2026-08-31: 2705/2710 checks passed, 4 skipped, 5 failing, 0 block(s) cut short SKIPPED: digest-2026-08-09-pm: its links resolve to published posts and to pages on disk (3 checks) — published before the wrap became a linked recap — the stored post is the audit trail and is never rewritten SKIPPED: the display rung (44) is asserted on the lead card's figure — the figure is the hero number INSIDE the card graphic — SVG user units in an 800x450 viewBox — so its rendered size is `units x (card width / 800)` and no one value makes it 44px on the front page, an article page and a share kit at once. Measured: 126px before this batch and 68.7px after, at 1440x900, because §6 put the lead in a 1/3 column. Reaching 44 means re-composing the card graphic, which is a batch and not a line — see docs/BATCH-K-REPORT.md FAILING: …and the tape carries PLAIN-TEXT rows as well as linked ones — a row with nothing behind it has no `href` at all, so the two states are distinguishable in the markup and not only in the styling (batch L §9), and a page where every row linked would not be exercising that rule FAILING: every recorded incident carries a written post-mortem FAILING: …and the timeline shows we were first FAILING: …which keeps the permalink, grows the timeline, and records the event that ended it FAILING: …and the measured row is 46px on a phone and 42px above 620 — the heights §1 asked for, read off the rendered page This report is assembled from records this site already keeps; it adds no new collection. The datasets it describes: /api/v1/chain-liveness.json and .csv