Storj (STORJ) — the revision ledger

Generated 2026-09-02T18:29:14Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for Storj: 20,243 observations · 74 distinct series · 4 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 17:50:30 · every one of the 20,243 rows carries a verify_url · 68 series refreshed in the last 24h (1,724 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where STORJ's archive 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. The largest family is Storj's own node stats endpoint (https://stats.storjshare.io/nodes.json) — first-party telemetry from the network's own published API.

Revision ledger — 1 backward revision(s) recorded for STORJ

Backward revisions are values upstream later replaced for a date this estate had already archived. The before-value is retained alongside the replacement — both snapshot dates, both numbers — which is what no overwriting vendor keeps. The ledger table is a ReplacingMergeTree the detector re-writes daily; this table shows the DEDUPED event set (min(detected_at) kept — the same dedupe rule /v1/revisions and the daily exports use). Raw detection rows behind this event set: 2. /v1/revisions?symbol=STORJ cross-check passed: the served API reports 1 row(s), matching the deduped ledger count rendered on this page.

The daily-snapshot trail behind the revision (raw archive)

Straight from default.depin_daily at generation: the disqualified-nodes counter as each daily snapshot recorded it around the event. The 80,238 → 79,569 rewrite is visible in the held history — the 2026-08-10 snapshot already carried the replaced value, so the before-value exists only because this estate kept it. Snapshot 2026-08-09 is the date whose value upstream replaced.

The per-satellite disqualification/exit counters (live rollup)

The aggregate DISQUALIFIED_NODES counter that was revised rolls up per-satellite series the estate also holds, from the same first-party source. Values below are the LATEST row per series in default.depin_onchain at generation — a gauge that moves, provenance attached.

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 (alltime fees, token transfers, block heights, node disqualifications). 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 (node counts, TVL, prices) legitimately move both ways and are deliberately excluded — a drop there is a real population change, not a rewrite. 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.

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 Storj's own stats endpoint, the first-party source the revision family came from; command 4 is the estate's graded network row; command 5 is the frozen daily snapshot of the ledger. One polite call per endpoint, no hammering.

# 1) The served revision feed for STORJ — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=STORJ" | 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) Storj's own stats endpoint (the first-party source this ledger family came from):
curl -s -H "User-Agent: kairos-check" "https://stats.storjshare.io/nodes.json" | python3 -m json.tool | head -40
# 4) This estate's public API row for STORJ (grades + provenance):
curl -s "https://kairossignal.com/v1/network/STORJ" | python3 -m json.tool | head -60
# 5) 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_storj.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The STORJ revision count is the deduped live result of SELECT ... FROM default.depin_revision_ledger WHERE network='STORJ' GROUP BY revision identity; the page refuses to ship if the served /v1/revisions?symbol=STORJ disagrees with it. 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. Upstream probes ran serially by this generator immediately before rendering: stats.storjshare.io/nodes.json (first-party) HTTP 200; estate /v1/revisions?symbol=STORJ HTTP 200; estate /v1/network/STORJ HTTP 200.