Crust Network (CRU) — the network, measured

Generated 2026-10-12T04:36:14Z from live ClickHouse queries against this estate's ledger. Held inventory: 29,440 observations · 43 distinct series · 5 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-12 04:17:05 · 29,440/29,440 rows carry a verify_url. 43 series refreshed in the last 24h (652 fresh rows). 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. Series absent from the 30-day window are omitted from this table, not zero-filled.

Market reference — CoinGecko, 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. Five series start 2026-08-09 in this archive (coingecko id crust-network); the volume, change-column, rank, ATH/ATL and 24h high/low series start 2026-08-22 (CoinGecko generation two) and are shown from their first held row, each metric's caveat stating its own start. The circulating and total supply rows are different quantities (circulating vs total) and are never netted against each other. The coingecko.com browser coin page 403s plain curl — verify through the programmatic markets endpoint given in the commands section.

Chain telemetry — Substrate JSON-RPC (substrate_rpc), as held

Read from Crust's public Substrate JSON-RPC (crust.api.onfinality.io/public) by the estate's substrate_rpc collector with a double-read gate: every value written must come from that run's live read and a second confirmation read must corroborate it (block height must be ≥ the captured height — the chain is live and advancing; peer count must be a sane non-negative int). Rows that fail the gate are skipped, never invented, never back-filled. chain_health_peers is one node's own libp2p peer count at read time — a snapshot, not a network total, so it is withheld since 2026-10-06 (quality incident substrate_rpc_peers_one_rpc_node_not_network_20261006). The block-height series flows fresh every ~10 minutes.

Single-observation seed metrics — held as read, never refreshed

Series exist as exactly one observation each, stamped 2026-08-10 by the estate's original first-party seeding run (the first_party_api family). They are published exactly as held — with the single-read caveat attached, never presented as flowing, and never back-filled or re-derived. The flowing substrate_rpc family now holds a series of the same name that has advanced past the seed value; the two families are kept separate and never merged or averaged.

Full metric inventory — 43 measured series, each with provenance

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

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 CRU. 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. Command 1 hits Crust's own Substrate JSON-RPC — the same endpoint family our collector does; the calls are Substrate JSON-RPC POSTs (the endpoint answers HTTP 405 to plain GETs, so plain GETs will not work). Command 2 hits the CoinGecko public programmatic API (the coingecko.com browser coin page 403s plain curl — that is the documented 403; the programmatic command is the verification path). Command 3 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) Crust's own Substrate JSON-RPC (onfinality gateway) — keyless, POST-only, as of 2026-10-12T04:36:14Z:
#    (finalized block height) curl -s -X POST -H "Content-Type: application/json" --data-binary '{"jsonrpc":"2.0","id":1,"method":"chain_getHeader","params":[]}' "https://crust.api.onfinality.io/public" | python3 -c "import sys,json; print(int(json.load(sys.stdin)['result']['number'], 16))"
# 2) Market reference (CoinGecko public API — the coingecko.com browser\n#    coin page 403s plain curl, so the programmatic endpoint is given):\n# 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
# (id: crust-network):
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=crust-network" | python3 -m json.tool
# 2b) Human-view check of the verify_url target (the browser coin page 403s plain curl — that is the documented 403, the programmatic command above is the verification path):\ncurl -s -o /dev/null -w "%{http_code}\n" "https://www.coingecko.com/en/coins/crust-network"
# 3) This estate's public API row for CRU:\ncurl -s "https://kairossignal.com/v1/network/CRU" | 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_cru.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 CRU-native market/telemetry metrics with no cross-network concept; grading them would be fabrication, so they are labelled "cru-native (unmapped)". This estate holds no GitHub rows, no DefiLlama fees/revenue/TVL rows, and no storage-specific series (file counts, capacity, staking) for CRU — no such figure appears on this page and none is implied. The two finalized_block_height families (the flowing gated substrate_rpc series and the single-observation first_party_api seed row) are different collectors with different stamps; they are shown side by side and never summed, merged, or reconciled. CoinGecko series start 2026-08-09 (five series) and 2026-08-22 (the remaining eighteen) in this archive and are shown from their first held row, never back-filled. CRU trades near $0.0102, so sub-10-cent cells are rendered to their 8th decimal — a truncated cell can never round onto a wrong value. 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: onfinality Crust RPC (chain_getHeader POST) HTTP 200; onfinality Crust RPC (system_health POST) HTTP 200; CoinGecko markets API (crust-network) HTTP 200; CoinGecko browser coin page (expected 403) HTTP 403; estate /v1/network/CRU HTTP 200.