Swarm (BZZ) — the revision ledger

Generated 2026-10-17T05:14:04Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for Swarm: 37,289 observations · 48 distinct series · 7 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-17 04:51:55 · every one of the 37,289 rows carries a verify_url · 48 series refreshed in the last 24h (721 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where Swarm's archive comes from

7 source families feed this network's ledger. Every row they wrote carries its own source, as_of and verify_url; this table is the live rollup of that. BZZ (the catalog name here is Swarm, category storage, chains ethereum and xdai) publishes no first-party stats API of its own in this catalog — the network-side series held for BZZ come from this estate's own deep-stats collectors (deep_stats_eth_rpc and deep_stats_eth_blockscout, Ethereum chain reads against the BZZ token contract) and Blockscout address counters (evm_blockscout), with CoinGecko's market series and the estate's github collector (ethersphere/bee repository activity) alongside.

Revision ledger — 0 backward revision(s) recorded for BZZ

The ledger query ran during generation and returned 0 rows for BZZ. Zero here is the live query result, not a gap — the ledger itself is at /v1/revisions?symbol=BZZ (the same query this page ran, served live), and a restatement would appear on this page the day the detector records one. /v1/revisions?symbol=BZZ cross-check passed: the served API reports 0 row(s), matching the ledger count rendered on this page.

Why zero is the interesting answer. The detector does not skip BZZ — below, the live intersection shows the 0 cumulative-by-construction series the archive holds for this network, each fully diffed across its whole snapshot window (where it has more than one observation), and each rendered here end to end so the monotone runs are visible raw. Nothing moved backward. That is the structural zero: the detector was watching, the counters were fully exposed to it, and upstream did not rewrite history for this network in the window this estate holds. Publishing an empty ledger as a live query result — instead of padding it with gauge noise — is the same retention discipline the ledger exists to sell.

What the detector watches for Swarm — the intersection, measured

The detector diffs every daily snapshot of every cumulative-by-construction series. Below is the live intersection of the estate detector's cumulative watchlist — imported directly from propintel/revision_ledger.py (11 declared names, so this page can never drift from the detector) — with what the daily archive holds for BZZ. All three watched series here are Blockscout contract counters for the BZZ token address on Ethereum mainnet.

Live query result: 0 watchlist series held for BZZ. The intersection query ran during generation and returned an empty set — none of the 11 cumulative-by-construction metric families the detector watches appear in BZZ's daily archive. This is the structural zero behind the ledger count above, published as the query found it.

The trails behind the ledger — watched counters, end to end

These are the actual counter trails the detector diffed for BZZ, rendered live from the archive. Each is a series that cannot decrease unless upstream rewrote history — and each is monotonic across its entire held window, which is exactly why the ledger above is empty. The raw runs are the evidence; the reader does not have to trust the summary.

contract_gas_used_total — total gas used by calls to the BZZ token contract, captured by the estate's Blockscout collector across all 53 snapshot days:

contract_transactions_total — the count of transactions against the BZZ token contract, same Blockscout origin — 53 snapshot days:

token_transfers_total — the token transfer counter for the BZZ contract, also held by the deep-stats family (see the cross-source check below) — 54 snapshot days:

Cross-source agreement — two independent pipelines, one number

On the days where both the Blockscout daily token_transfers_total and the deep-stats family's own capture of the same counter hold a value, the two independent captures are checked live: a cumulative transfer counter cannot decrease, so agreement means the deep-stats value is >= the Blockscout value and within 2% of it. A live-computed check, not an assertion: 49 agreeing days, 2 divergent.

Gauges that moved backward — deliberately NOT revisions

These series fall outside the detector's cumulative-by-construction class (NOT_TRULY_CUMULATIVE and plain gauges in propintel/revision_ledger.py): a drop there is a real network or market change, not upstream rewriting history. For BZZ the node-population sets (known nodes day/week, unreachable and unstable node gauges), holder counts, and the market series dominate this table — a smaller node set is a smaller reachable swarm on that day, not a rewrite. Publishing them as "revisions" would be exactly the fake-metric behaviour this product exists to eliminate.

Same-timestamp conflicting values on record for BZZ: none

The task-level conflict check, run live: any (metric, timestamp) family where this estate recorded two or more different values. The query ran at generation and returned 0 groups in both depin_onchain and depin_daily — every (metric, timestamp) pair the estate holds for BZZ carries exactly one value. Zero here is the live query result, not a gap; the archive kept every write it made, and none of them disagree.

The ledger, live — every restatement recorded estate-wide (39 deduped events)

Deduped on revision identity exactly as /v1/revisions dedupes it. This is the same feed a subscriber polls; it is rendered live from ClickHouse at generation, not copied from a snapshot. Each row is an upstream source replacing the value of a (network, metric, date) it had already published — after this estate recorded the original. The superseded value is retained, never overwritten; that retention is the only reason a rewrite is detectable, and it is the part every overwriting vendor discards.

How detection works — and what it cannot see

The detector (propintel/revision_ledger.py) diffs every daily snapshot this estate holds of every cumulative-by-construction series — counters that cannot decrease unless upstream rewrote them (block heights, transaction and transfer counters, lifetime fees). A row enters default.depin_revision_ledger iff two snapshots disagree for an already-observed date; zero human judgement. Resolution rule: latest observation wins for current-state reads, the superseded value is retained, never overwritten. Population gauges (provider sets, node counts, prices, capacity, rolling windows) legitimately move both ways and are deliberately excluded — a drop there is a real change, not a rewrite; the gauge table on this page is the worked example. Honest boundary: this catches value-history rewrites ex-post; identical-schema semantic drift with plausible values is what the hash-pinned derivation_replay layer is for. The detector's full classification is inspectable at /v1/revisions and frozen daily at /revision-ledger/REVISIONS_20260902.json.

The snapshot archive the detection runs over

BZZ's slice of depin_daily: 2,194 rows over 69 snapshot days (2026-08-09 → 2026-10-16), from 4 source families. Each snapshot is a same-day capture of every series the collectors touched; the detector diffs consecutive snapshots of cumulative series across this window. This is the substrate the zero above is measured over — not an assumption, a measured archive.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–2 hit this estate's public API (the same rows this page queried — every row carries source / as_of / verify_url); commands 3–4 hit the Blockscout upstream family the watched counter rows came from; command 5 is the CoinGecko origin page; command 6 is the GitHub repository feed; command 7 is the estate's graded network row; command 8 is the frozen daily snapshot of the ledger. One polite call per endpoint, no hammering.

# 1) The served revision feed for BZZ — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=BZZ" | python3 -m json.tool
# 2) The estate-wide feed (every network, both sides of every diff):
curl -s "https://kairossignal.com/v1/revisions" | python3 -m json.tool | head -80
# 3) Blockscout counters for the BZZ token contract (the watched-counter origin):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/addresses/0x19062190b1925b5b6689d7073fdfc8c2976ef8cb/counters" | python3 -m json.tool | head -30
# 4) Blockscout token endpoint (the holders/supply origin):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x19062190b1925b5b6689d7073fdfc8c2976ef8cb" | python3 -m json.tool | head -30
# 5) CoinGecko BZZ page (the market-series origin; browser-verified, bot-walled to curl):
curl -s -o /dev/null -w "%{http_code}\n" "https://www.coingecko.com/en/coins/swarm-bzz"
# 6) GitHub repository activity for ethersphere/bee (the dev-velocity source family):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/ethersphere/bee" | python3 -m json.tool | head -20
# 7) This estate's public API row for BZZ (grades + provenance):
curl -s "https://kairossignal.com/v1/network/BZZ" | python3 -m json.tool | head -60
# 8) The public daily snapshot of the ledger (frozen copy):
curl -s -o /dev/null -w "%{http_code}\n" "https://kairossignal.com/revision-ledger/REVISIONS_20260902.json"

Method & honesty notes. All counts are queries against the live ledger at generation time, not restamped copy — this page is regenerated by gen_revision_page_bzz.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The BZZ revision count is the live result of SELECT count() FROM default.depin_revision_ledger WHERE network='BZZ'; the page refuses to ship if the served /v1/revisions?symbol=BZZ is reachable and disagrees with it (at generation the estate API was reachable and the cross-check passed). The 39 estate-wide events shown are deduped on revision identity (deterministic hash of network, metric, current_date, prior_date) exactly as the API dedupes them; detected_at is the first detection and never moves. Series absent from a section are absent, not zero. The same-stamp conflict check is the honest live answer: 0 groups in depin_onchain and 0 in depin_daily. Upstream probes ran serially by this generator immediately before rendering: CoinGecko BZZ page (browser-verified origin; 403 here is its bot wall) HTTP 403; Blockscout token endpoint for the BZZ contract (the evm_blockscout origin) HTTP 200; Blockscout address counters for the BZZ contract (the counter-trail origin) HTTP 200; GitHub API for ethersphere/bee (the dev-activity source family) HTTP 200; estate /v1/revisions?symbol=BZZ HTTP 200; estate /v1/network/BZZ HTTP 200.