BTT (BitTorrent) — the network, measured

Generated 2026-09-03T18:09:48Z from live ClickHouse queries against this estate's ledger. Held inventory: 7,954 observations · 32 distinct series · 4 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-03 17:49:20 · 7,954/7,954 rows carry a verify_url. 32 series refreshed in the last 24h (606 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number comes from

4 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 change columns / rank / ATH-ATL / high-low series start later in the archive than the price rows (each metric's caveat in the full inventory states its own first-held row) and are shown from their first held row. The circulating, total and max supply rows are different quantities (circulating vs total vs cap) and are never netted against each other or against the Blockscout onchain_total_supply chain-side read in the chain-state section below — different measurements from different endpoints, shown side by side. The token trades far below one cent (near $0.0000003); the sub-cent cells are rendered to full precision so no published value rounds onto a different one.

Chain-level slices — DefiLlama, as held

Two different chain-level measurements DefiLlama publishes for the BitTorrent chain, from two different endpoints: chain_tvl_usd is the total protocol TVL DefiLlama attributes to the BitTorrent chain (/v2/chains chain entry's tvl field, reading 71,300.1602 at generation) and stablecoin_supply_usd is the stablecoin circulating supply on that chain (/stablecoinchains entry's totalCirculatedUSD, reading 332,313.0989). Both are CHAIN measurements — all protocols on the chain, not the BTT token or this Ethereum contract — and they are different quantities from each other and from every supply read on this page: published side by side, never netted, summed, or reconciled against anything.

Token & chain counters — Blockscout, as held

Chain-side reads for the Ethereum-mainnet contract 0xc669928185dbce49d2230cc9b0979be6dc797957 — the catalog's own token_address field, verbatim (catalog chains field: binance-smart-chain,bittorrent,energi,ethereum,tron) — from the public Blockscout v2 API. This source is deliberately distinct from any RPC family so its freshness identity stays untouched. At generation the chain-side total-supply read is 36,542,206,310,204.4375 (the tokens that exist for THAT contract — BTT also exists on other chains the catalog lists, so this is NOT a whole-ecosystem figure), holders 20,832, transfers 140,314. Polled roughly once per day; counters are published raw, never differenced into rates, never extrapolated. The top-holder balance is the largest single holder's balance — an ownership-concentration input, not a supply figure, and never netted against supply reads.

Full metric inventory — 32 measured series, each with provenance

Every series held for BTT 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 BTT

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 BTT. Zero here is the live query result, not a gap — the ledger itself is at /v1/revisions.

Estate grades for BTT (graded 2026-08-20 13:54:15.000)

Served by /v1/network/BTT — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth. They are published exactly as the engines emitted them, unflattering parts included: the revenue F reflects that the estate holds no fees/revenue series for this network (the absence is shown in the sections above, not papered over), and the data-coverage D reflects a thin measured-series set relative to first-party-telemetry networks. The node-quality and dev-velocity A grades sit on third-party and chain-side series alone. The grade stamp is dated; the engines re-grade on their own schedule.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–3 hit the same upstream endpoints our collectors do (the coingecko.com browser coin page 403s plain curl, so the programmatic markets endpoint is given; the Blockscout commands use the public eth.blockscout.com instance the verify_urls point at; the DefiLlama commands filter the full chain lists down to the BitTorrent row); command 4 hits this estate's public API, where every row carries the same source / as_of / verify_url fields. One polite call per endpoint, no hammering.

# 1) On-chain token record (Blockscout v2 token API — the collector's method), as of 2026-09-03T18:09:48Z:
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0xc669928185dbce49d2230cc9b0979be6dc797957" | python3 -c "import json,sys; d=json.load(sys.stdin); print('total_supply', d.get('total_supply')); print('holders', d.get('holders')); print('transfers', d.get('transfers'))"
# 1b) Token counters (transfers + holder count):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0xc669928185dbce49d2230cc9b0979be6dc797957/counters" | python3 -c "import json,sys; d=json.load(sys.stdin); print('transfers_count', d.get('transfers_count')); print('token_holders_count', d.get('token_holders_count'))"
# 1c) Contract address counters (transactions + gas usage):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/addresses/0xc669928185dbce49d2230cc9b0979be6dc797957/counters" | python3 -c "import json,sys; d=json.load(sys.stdin); print('transactions_count', d.get('transactions_count')); print('gas_usage_count', d.get('gas_usage_count'))"
# 1d) Top holder (raw largest-holder balance):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0xc669928185dbce49d2230cc9b0979be6dc797957/holders" | python3 -c "import json,sys; d=json.load(sys.stdin); items=(d.get('items') or []); v=((items[0].get('value') if items else None)); print('top_holder_raw_value', v)"
# 1e) The per-token page our verify_url points at (human view):
curl -s -o /dev/null -w "%{http_code}\n" "https://eth.blockscout.com/api/v2/tokens/0xc669928185dbce49d2230cc9b0979be6dc797957"
# 2) Chain-level TVL for the BitTorrent chain (DefiLlama /v2/chains — filter to the chain row):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/v2/chains" | python3 -c "import json,sys; rows=json.load(sys.stdin); row=(next((r for r in rows if (r.get('name') or '').lower()=='bittorrent'), None) or {}); print('chain_tvl_usd', row.get('tvl'))"
# 2b) Stablecoin supply on the BitTorrent chain (DefiLlama stablecoinchains — filter to the chain row):
curl -s -H "User-Agent: kairos-check" "https://stablecoins.llama.fi/stablecoinchains" | python3 -c "import json,sys; rows=json.load(sys.stdin); row=(next((r for r in rows if (r.get('name') or '').lower()=='bittorrent'), None) or {}); d=(row.get('totalCirculatingUSD') or {}); print('stablecoin_usd', (list(d.values())[-1] if d else None))"
# 3) Market reference (CoinGecko public API):
# 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=bittorrent" | python3 -m json.tool
# 4) This estate's public API row for BTT:
curl -s "https://kairossignal.com/v1/network/BTT" | python3 -m json.tool | head -60
#    (This estate endpoint is keyed: anonymous IPs share a 1,000/day pool that
#    resets at 00:00 UTC. If you see a quota-exceeded JSON, self-register
#    free credits at https://kairossignal.com/v1/credits/register and add
#    -H "Authorization: Bearer <your key>".)

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_btt.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 BTT-native market/on-chain/chain-slice metrics with no cross-network concept; grading them would be fabrication, so they are labelled "btt-native (unmapped)". FOUR supply references are shown side by side as held, never summed, merged, or reconciled: CoinGecko's circulating, total and max supply, and the Blockscout chain-side token supply for the ETHEREUM contract. At generation the chain-side read (~36.5T) is FAR SMALLER than the CoinGecko circulating reference (~987T) and the 990T total/max cap — exactly as expected: the chain-side read counts one Ethereum contract while the market references count the whole multi-chain BTT ecosystem. They remain different measurements from different endpoints and no ratio is derived between any of them. The CoinGecko circulating_supply row is a different quantity (circulating vs total) and is never netted against the other reads. The DefiLlama rows are CHAIN-level slices (all protocols on the BitTorrent chain; all stablecoins on it) — different quantities from every token-level figure, published as answered, never netted or summed with anything. The top-holder balance stays the raw largest-holder balance as the API reports it — an ownership-concentration input, never relabelled as supply, never presented as investment advice. The Blockscout counters are ~daily polls, published as answered. The catalog's token_address field is filled for BTT (0xc669928185dbce49d2230cc9b0979be6dc797957) and the chain-side family reads exactly that contract, with every verify_url pointing at eth.blockscout.com for the same address. The catalog's chains field lists binance-smart-chain, bittorrent, energi, ethereum and tron; the estate's chain-side family covers the Ethereum contract only, and no BSC, BTTC, energi or tron chain-side rows are held — those sections are absent rather than implied. The estate holds no GitHub, no DefiLlama fees slice, no RPC eth_call rows, and no first-party snapshot rows for BTT — those sections are absent rather than zero-filled, and the queries rerun at every regeneration. Where a section has no data, it is absent — we do not publish zeros for gaps. Upstream probes ran serially by this generator immediately before rendering: DefiLlama chains API (/v2/chains) HTTP 200; DefiLlama stablecoins API (stablecoinchains) HTTP 200; CoinGecko markets API (bittorrent) HTTP 200; Blockscout token API HTTP 200; Blockscout token counters API HTTP 200; Blockscout address counters API HTTP 200; Blockscout token holders API HTTP 200; estate /v1/network/BTT HTTP 200.