Swarm (BZZ) — the network, measured

Generated 2026-10-12T04:35:25Z from live ClickHouse queries against this estate's ledger. Held inventory: 33,663 observations · 48 distinct series · 7 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-12 03:51:55 · 33,663/33,663 rows carry a verify_url. 48 series refreshed in the last 24h (700 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number 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.

30-day history — headline series (daily last-value, live)

One row per series: latest value, a 30-day sparkline of daily last-known values (scaled to the series' own min→max), day count, and window change. Series absent from the 30-day window are omitted from this table, not zero-filled.

Market reference — CoinGecko coin page, as held

Market-data reference rows: price, supply, capitalisation, diluted valuation, and the published change columns including ATH/ATL. These are the coin-page reference's own numbers — the estate does not model, smooth, or forward-fill them. The CoinGecko circulating_supply / total_supply rows and the chain reads are separate measurements from separate endpoints, shown side by side and never merged — and at generation the coin-page figures and the chain reads AGREE; that agreement is stated, not manufactured, and the rows stay separate.

On-chain reads — Ethereum (RPC + Blockscout), as held

Chain reads for the BZZ ERC-20 token (0x19062190…, 16 decimals — contract-verified live at generation): total supply, holder count, transfer count, the largest single holder's balance, and the token contract's gas/transaction counters. The estate's on-chain read for BZZ is the ERC-20 token ledger on Ethereum (publicnode RPC + Blockscout), read directly from public endpoints. Dual-source series (publicnode RPC, deep_stats_eth_blockscout, evm_blockscout) are separate rows with their own stamps — the value and stamp gaps are shown, not smoothed. At generation the top-holder read is 5,555,465.3606 tokens — 8.80% of the chain total-supply read (63,149,437.8366), a live ratio of the two held values, not a new source. A balance of that size on a bridged token is typically an exchange, treasury, bridge or staking contract; it is a raw read and is never labelled as owner concentration.

Dev velocity — GitHub, as held

Public repo activity for Swarm: the ethersphere/bee repo (the Swarm node client) for stars, forks, issues, watchers and days-since-push, plus the org-level public-repo count. Daily snapshots; each row keeps its own as-of stamp.

Full metric inventory — 48 measured series, each with provenance

Every series held for BZZ with rows in the last 30 days: latest value, when it was observed, which source observed it, how many rows we hold, how many of the last 30 days it reported, its comparability grade, and the origin link. "days/30" counts distinct dates with at least one row in the window.

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

Backward revisions are values upstream later replaced for a date we had already archived. The before-value is retained — that retention is the only reason a rewrite is detectable, and it is the part every overwriting vendor discards.

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.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–4 hit the same upstream endpoints our collectors do (the coingecko.com browser coin page 403s plain curl, so the programmatic markets endpoint is given); command 5 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) Market reference (CoinGecko public API) — keyless, as of 2026-10-12T04:35:25Z:
# CoinGecko public markets API (the endpoint family our collector
# reads for the price/supply/cap rows) — the coingecko.com browser
# coin page 403s plain curl, so the programmatic endpoint is given:
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=swarm-bzz" | python3 -m json.tool
# 2) On-chain supply (Ethereum public RPC, eth_call):
# On-chain supply (Ethereum public RPC — eth_call totalSupply on
# the BZZ ERC-20 token contract; this is the deep_stats_eth_rpc path):
curl -s -X POST "https://ethereum-rpc.publicnode.com" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x19062190b1925b5b6689d7073fdfc8c2976ef8cb","data":"0x18160ddd"},"latest"]}' | python3 -m json.tool
# 2b) Decimals check (eth_call decimals, 0x10 = 16):
# Decimals check (eth_call decimals — BZZ is a 16-decimal token,
# not the ERC-20 default 18; the result is raw, 0x10 = 16):
curl -s -X POST "https://ethereum-rpc.publicnode.com" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x19062190b1925b5b6689d7073fdfc8c2976ef8cb","data":"0x313ce567"},"latest"]}' | python3 -m json.tool
# 3) Token stats (Blockscout public API):
# Blockscout token stats (holders_count, token_transfers_total,
# evm_blockscout supply read — the exact endpoint the rows cite):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x19062190b1925b5b6689d7073fdfc8c2976ef8cb" | python3 -m json.tool | head -25
# 3b) Token contract counters (Blockscout address counters):
# Blockscout address counters (contract_transactions_total,
# contract_gas_used_total — the BZZ token contract on Ethereum):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/addresses/0x19062190b1925b5b6689d7073fdfc8c2976ef8cb/counters" | python3 -m json.tool | head -20
# 3c) Top holders (Blockscout holders endpoint):
# Blockscout top holders (top_holder_balance — the source of
# the largest-single-holder row):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x19062190b1925b5b6689d7073fdfc8c2976ef8cb/holders" | python3 -m json.tool | head -30
# 4) Dev velocity (GitHub public API):
# GitHub public API — the repo our dev-velocity series reads
# (the Swarm node client):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/ethersphere/bee" | python3 -m json.tool | head -20
# 4b) Org-level repo counter (same API, org endpoint):
# Org-level public-repo counter (same API, org endpoint):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/orgs/ethersphere" | python3 -c "import json,sys; d=json.load(sys.stdin); print('public_repos', d.get('public_repos'))"
# 5) This estate's public API row for BZZ:
curl -s "https://kairossignal.com/v1/network/BZZ" | python3 -m json.tool | head -60

Method & honesty notes. All counts are queries against the live ledger at generation time, not restamped copy — this page is regenerated by gen_deep_dive_bzz.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. Comparability grades come from the served canonical-metric system via its own resolver: total_supply maps to token_supply_total (question-verified). The remaining series are BZZ-native chain/market metrics with no cross-network concept; grading them would be fabrication, so they are labelled "bzz-native (unmapped)". The estate holds no DefiLlama fees, revenue or TVL rows for BZZ — no such section exists on this page; that is absence, not zero, and the DefiLlama queries rerun at every regeneration so a section would appear the day rows exist. Dual-source series (chain supply, holders, transfers) are published as separate rows with their own stamps, never merged; the hour-level gaps between the two Blockscout generations are stated, not smoothed. The supply reads (RPC chain, Blockscout, CoinGecko total) are published side by side, never merged; the chain reads and the CoinGecko total-supply reference all read the same value at generation — shown side by side, never merged. The CoinGecko circulating_supply row (equal to total on the coin page for BZZ) is a different measurement path and is never netted against or merged with the chain reads. ethereum_block_height and ethereum_gas_price_gwei are Ethereum host-chain context for the ERC-20 read, never presented as Swarm network telemetry. The estate's reads are the Ethereum mainnet ERC-20 ledger; the catalog also lists an xDai/Gnosis chain for BZZ, whose bridge token is a separate contract the estate does not read — nothing here is a Gnosis-chain measurement. BZZ uses 16 decimals (contract-verified live at generation via eth_call decimals), not the ERC-20 default 18. The top-holder percentage is a live ratio of two held reads, labelled as such; the underlying balance may be an exchange, treasury, bridge or staking contract and is never relabelled as owner concentration. Where a section has no data, it is absent — we do not publish zeros for gaps. Upstream probes run serially by this generator immediately before rendering: CoinGecko markets API HTTP 200; Publicnode Ethereum RPC (totalSupply) HTTP 200; Publicnode Ethereum RPC (decimals) HTTP 200; Blockscout token API HTTP 200; Blockscout address counters API HTTP 200; Blockscout holders API HTTP 200; GitHub ethersphere/bee HTTP 200; estate /v1/network/BZZ HTTP 200.