Crust Network (CRU) — the revision ledger

Generated 2026-09-02T20:09:20Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for Crust Network (CRU): 7,815 observations · 25 distinct series · 3 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 19:49:20 · every one of the 7,815 rows carries a verify_url · 25 series refreshed in the last 24h (692 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where Crust Network (CRU)'s archive comes from

3 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. Crust Network (the catalog name here is Crust Network, category storage, chains ethereum) publishes no first-party stats API of its own in this catalog — the network-side series held for CRU come from this estate's own depin_first_party BLOCK_HEIGHT collector and Substrate RPC reads via the public OnFinality Crust endpoint (finalized block height and peer count), with CoinGecko's market series alongside. The Crust token contract on Ethereum is 0x32a7c02e79c4ea1008dd6564b35f131428673c41.

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

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?symbol=CRU (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=CRU 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 CRU — below, the live intersection shows the 2 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 Crust Network — 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 (75 declared names, so this page can never drift from the detector) — with what the daily archive holds for CRU. Both series held are chain-height counters: the first-party collector's BLOCK_HEIGHT and the Substrate RPC's finalized_block_height — quantities that cannot decrease unless upstream rewrote history.

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

These are the actual counter trails the detector diffed for CRU, 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.

BLOCK_HEIGHT — the cumulative Crust chain height captured by this estate's depin_first_party collector, across all 24 snapshot days:

finalized_block_height — the cumulative Crust finalized-block height read from the public Substrate RPC endpoint (https://crust.api.onfinality.io/public), across all 24 snapshot days:

Cross-source agreement — two independent pipelines, one chain

This estate's first-party BLOCK_HEIGHT collector and the Substrate RPC's finalized_block_height are two independent pipelines measuring the same chain: Crust. They are not expected to be identical — a finalized height legitimately trails the chain head by the finality lag — so the check is published as the measured per-day offset, raw: on the 24 overlapping snapshot days, the first-party head read sits above the finalized read by between 258 and 426 blocks (worst day ≈0.0016% of the height). Both captures rise in lockstep, day after day — the signature of two pipelines reading the same growing chain, not of a history rewrite. A live-computed check, not an assertion — every overlapping day, both values, and the offset:

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 market change or tokens moving, not upstream rewriting history. Price, market-cap and volume classes dominate this table for CRU, and the peer count legitimately wobbles both ways as nodes join and leave. Publishing them as "revisions" would be exactly the fake-metric behaviour this product exists to eliminate.

Same-timestamp conflicting values on record for CRU: 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 CRU 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 (18 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 deleted; 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 deleted. 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

CRU's slice of depin_daily: 379 rows over 24 snapshot days (2026-08-09 → 2026-09-01), 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.

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

Served by /v1/network/CRU — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, published exactly as the engines emitted them, unflattering parts included.

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); command 3 hits the Substrate RPC the chain-height rows came from; command 4 checks the CoinGecko origin of the market series; command 5 is the estate's graded network row; command 6 is the frozen daily snapshot of the ledger. Per-row verify URLs are linked in the provenance table above. One polite call per endpoint, no hammering.

# 1) The served revision feed for CRU — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=CRU" | 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) The public Substrate RPC for Crust (the finalized_block_height / chain_health_peers origin family):
curl -s -H "User-Agent: kairos-check" -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"chain_getFinalizedHead","params":[],"id":1}' "https://crust.api.onfinality.io/public"
# 4) CoinGecko's Crust Network page (the market-series origin; 403 on curl is its bot wall — open in a browser):
curl -s -o /dev/null -w "%{http_code}\n" "https://www.coingecko.com/en/coins/crust-network"
# 5) This estate's public API row for CRU (grades + provenance):
curl -s "https://kairossignal.com/v1/network/CRU" | python3 -m json.tool | head -60
# 6) 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_cru.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The CRU revision count is the live result of SELECT count() FROM default.depin_revision_ledger WHERE network='CRU'; the page refuses to ship if the served /v1/revisions?symbol=CRU disagrees with it, and states the fact plainly if that endpoint is unavailable at generation. The 18 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 Crust Network page (browser-verified origin; 403 here is its bot wall) HTTP 403; public Substrate RPC for Crust (the finalized_block_height / chain_health_peers origin family) HTTP 405; estate /v1/revisions?symbol=CRU HTTP 429; estate /v1/network/CRU HTTP 429.