ThreeFold (TFT) — the network, measured

Generated 2026-10-12T05:03:30Z from live ClickHouse queries against this estate's ledger. Held inventory: 59,947 observations · 71 distinct series · 5 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-12 04:53:03. All 59,947 rows carry a verify_url — coverage is 100.0%. Freshness right now: 66 series reported in the last 24h (1,359 rows), 66 in the last 7d. Nothing on this page is cached, estimated, or remembered.

Provenance — where every number comes from

5 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. Each row carries its source and origin link. Series absent from the 30-day window are omitted from this table, not zero-filled.

Grid capacity — cores, memory, storage (total vs used)

ThreeFold's own inventory model, measured from the network's stats endpoint: raw capacity (CRU cores, MRU memory, SRU SSD, HRU HDD), what is actually used, and the utilisation percentage the network itself publishes. Byte figures show the exact held value with a human unit in parentheses — the exact number is the published one.

Grid composition — nodes, farms, contracts

Every grid-structure series we hold, each with its own source and as-of. nodes (total registered) comes from the gridproxy stats endpoint; nodes_up and the dedicated/GPU counts come from the first-party grid snapshot collector — related series, published separately with their own provenance rather than blended into one derived ratio.

Token market data — CoinGecko reference

Market reference from CoinGecko. Not published since 2026-09-25: market_cap_usd and circulating_supply. CoinGecko answers 0 for both when it does not track a coin's circulating supply, so that 0 means unknown, not zero; every published figure in the estate now reads it that way. An earlier version of this page presented the 0 as upstream's answer for ThreeFold's market cap; that reading was wrong. We still do not substitute FDV or model a market cap.

Development activity — GitHub

Full metric inventory — 66 measured series, each with provenance

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

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 TFT: upstream sources for this network have not rewritten any dated value we hold. 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. The first two hit the same upstream endpoints our collectors do; the third hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) The network's own gridproxy endpoint (keyless, as of 2026-10-12T05:03:30Z):
curl -s "https://gridproxy.grid.tf/nodes" | python3 -m json.tool | head -40
# 2) Market reference (keyless):
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=threefold-token" | python3 -m json.tool | head -40
# 3) This estate's public API row for TFT:
curl -s "https://kairossignal.com/v1/network/TFT" | python3 -m json.tool | head -60

All 3 command(s) above were executed at generation time (2026-10-12T05:03:30Z) against the exact URLs printed — each returned HTTP 200 with a JSON body before being published. A command that fails this build-time check is omitted from this block, never shipped unverified.

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_tft.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: 13 of 66 series map to cross-network concepts (compute/storage/memory totals and in-use, nodes, gateways, gpus, countries, token supply); the rest are TFT-native grid metrics and are labelled as such rather than graded. market_cap_usd and circulating_supply are not published: CoinGecko's 0 for them means supply not tracked (unknown), not zero. Where a section has no data, it is absent — we do not publish zeros for gaps.