Coverage boundary
What this site does not see. Every row below is computed from the registries the code itself switches on — the watcher list, the chain list, the instrument classes, the exchange sources — so a detector added without a line here is impossible rather than merely discouraged. 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
9 event kinds are declared in the code. 4 of them have never produced an event, and they are not the same statement: 1 “we are not watching this”; 1 “we are watching, and the bar may be untestable”; 2 “we are watching and nothing has happened”. The archive they are measured against runs from 2026-08-11 to 2026-08-31 — 21 days.
Switched off
“we are not watching this”
- eth_whale
- `eth_whales` is `enabled: false` in config. The kind is declared, carries thresholds and is in the routing table; nothing polls for it. Owned by the
eth_whaleswatcher.
Watching, with a bar nothing has come near
“we are watching, and the bar may be untestable”
- funding_extreme
- Watching. The bar (`threshold_rate` 0.00075) is 4.97x the largest reading this site has ever recorded (0.00015092), so nothing in the record has come close to it. Owned by the
fundingwatcher.
Watching, and nothing has happened
“we are watching and nothing has happened”
- chain_degraded
- Watching, and it has not happened. This site records no series here independent of the bar, so nothing can say whether the bar is reachable — only that nothing has crossed it. Owned by the
chain_healthwatcher. - chain_recovered
- Watching, and it has not happened. This site records no series here independent of the bar, so nothing can say whether the bar is reachable — only that nothing has crossed it. Owned by the
chain_healthwatcher.
Watching, and it has fired
“watching, and it has fired”
- btc_whale
- 30,741 event(s) recorded across 21 day(s) of archive. Owned by the
btc_whaleswatcher. - liquidation_cascade
- 892 event(s) recorded across 21 day(s) of archive. Owned by the
liquidationswatcher. - stablecoin_burn
- 519 event(s) recorded across 21 day(s) of archive. Owned by the
stablecoinswatcher. - stablecoin_mint
- 581 event(s) recorded across 21 day(s) of archive. Owned by the
stablecoinswatcher. - token_transfer
- 943 event(s) recorded across 21 day(s) of archive. Owned by the
erc20_transferswatcher.
Holes in the record in the last 24 hours
None recorded.
Chains with no watcher
- unwatched · configured but switched off — no height is read, so no halt on it could be detected
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
- No public status API. bybit.statuspage.io is an unrelated tenant (page.name "Login", components named "Coinbase Horizen") and is refused. An official announcements API exists at api.bybit.com/v5/announcements but publishes marketing alongside operational notices and states no current status, so deriving a live dot from it would be inference.
- status.kucoin.com does not resolve. An announcements API exists (www.kucoin.com/_api/cms/articles) but carries no current-status field.
- bitget.statuspage.io answers 401 — the tenant is private.
- status.gate.io does not resolve and the v4 announcements endpoint rejects unauthenticated requests.
- status.htx.com does not resolve; no keyless machine-readable status found.
- status.upbit.com does not resolve. api-manager.upbit.com serves an announcements feed with no current-status field.
- deribit.statuspage.io answers 401 — the tenant is private.
Instruments with no perpetual, and the rail’s off-tape seven
- no row on the tape · quoted in the same request as the tape's three coins and deliberately kept off it — the tape is what the price-claim guardrail checks a story's figures against
- no row on the tape · quoted in the same request as the tape's three coins and deliberately kept off it — the tape is what the price-claim guardrail checks a story's figures against
- no row on the tape · quoted in the same request as the tape's three coins and deliberately kept off it — the tape is what the price-claim guardrail checks a story's figures against
- no row on the tape · quoted in the same request as the tape's three coins and deliberately kept off it — the tape is what the price-claim guardrail checks a story's figures against
- no row on the tape · quoted in the same request as the tape's three coins and deliberately kept off it — the tape is what the price-claim guardrail checks a story's figures against
- no row on the tape · quoted in the same request as the tape's three coins and deliberately kept off it — the tape is what the price-claim guardrail checks a story's figures against
- no row on the tape · quoted in the same request as the tape's three coins and deliberately kept off it — the tape is what the price-claim guardrail checks a story's figures against
- no funding and open interest · nothing in the commodity class has a perpetual funding rate to read
- no funding and open interest · nothing in the equity class has a perpetual funding rate to read
- no funding and open interest · nothing in the fx class has a perpetual funding rate to read
- no funding and open interest · nothing in the index class has a perpetual funding rate to read
- no funding and open interest · nothing in the rate class has a perpetual funding rate to read
Recorded but never carded
Kinds this wire writes down and will not turn into a story: token_transfer. Watchers that record a series and emit no event at all: open_interest. Both are deliberate and both are in the download.
Uptime and incidents · Accuracy · the on-chain ledger · the datasets