bytenews.io

Archive About

Coverage boundary

What this site does not see. Every row below is generated from what the site is actually configured to watch, rather than from a list anyone maintains by hand — so a gap that opens up appears here whether or not somebody remembered to write it down. A hand-maintained list of blind spots is a list of the blind spots somebody remembered.

The other half of this is on every dataset: each download carries an integrity report saying when its producer was not looking. This page is the prior question — what has no producer at all.

Detectors

This site watches for 10 kinds of event. 5 of them have never produced one, and they do not all mean the same thing: 1 “we are not watching this”; 1 “it is switched on and there is nothing for it to watch”; 1 “we are watching, and the bar may be untestable”; 2 “we are watching and nothing has happened”. The record they are measured against runs from 2026-08-11 to 2026-10-07 — 58 days.

Holes in the record in the last 24 hours

Chains with no watcher

The liveness board draws these as unwatched rather than green, which is the rule this whole page extends: a green dot for a chain nobody is watching is the one lie this site cannot tell.

Exchanges we watch for and cannot read

Prices we quote and do not fully cover

Recorded, and never written up as a story

Things this wire writes down and will not turn into a story: Large token transfers, Token unlocks as they happen. Things it records as a running series and never reports as an event at all: Open interest. Both are deliberate, and both are in the download.

Uptime and incidents · Accuracy · the on-chain ledger · the datasets