RSS3 (RSS3) — the revision ledger

Generated 2026-09-02T19:55:23Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for RSS3: 7,894 observations · 37 distinct series · 5 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 19:49:20 · every one of the 7,894 rows carries a verify_url · 31 series refreshed in the last 24h (770 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where RSS3's archive 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. RSS3 (the catalog name here is RSS3, category storage, chains ethereum + rss3-vsl) publishes no first-party stats API of its own in this catalog — the network-side series held for RSS3 come from this estate's own depin_first_party HOLDERS collector and Ethereum chain reads via Blockscout (holder count, total supply, and the token-transfer / contract-transaction / gas counters at the token contract 0xc98d64da73a6616c42117b582e832812e7b8d57f) and an ETH RPC family (block height, gas price), with CoinGecko's market series and GitHub dev-activity series for RSS3-Network/Node alongside.

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

The ledger query ran during generation and returned 0 rows for RSS3. Zero here is the live query result, not a gap — the ledger itself is at /v1/revisions?symbol=RSS3 (the same query this page ran, served live), and a restatement would appear on this page the day the detector records one. /v1/revisions cross-check unavailable at generation (HTTP Error 429: Too Many Requests); counts re-derived live from ClickHouse.

Why zero is the interesting answer. The detector does not skip RSS3 — below, the live intersection shows the 3 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 RSS3 — 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 RSS3. All three series held are Blockscout address-counter reads at the RSS3 token contract: transfers, contract transactions, and gas used — 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 RSS3, 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.

token_transfers_total — the cumulative ERC-20 transfer counter for the RSS3 token contract (0xc98d64da73a6616c42117b582e832812e7b8d57f), read from Blockscout's address-counters endpoint, across all 11 snapshot days:

contract_transactions_total — the cumulative transaction counter at the RSS3 token contract address, same Blockscout counters endpoint, across all 10 snapshot days:

contract_gas_used_total — the cumulative gas-used counter at the RSS3 token contract address, same Blockscout counters endpoint, across all 10 snapshot days:

Cross-source agreement — two independent pipelines, one quantity

This estate's first-party HOLDERS collector and Blockscout's holders_count counters are two independent pipelines measuring the same quantity: the holder count of token 0xc98d64da73a6616c42117b582e832812e7b8d57f. On the snapshot days where both hold a value, the captures agree exactly on 7 of 23 overlapping days, and on the 16 divergent days the two captures differ by at most 7 holders (≈0.0360%) — the signature of two indexing pipelines reading the same chain at different moments, not of a history rewrite. A live-computed check, not an assertion — every overlapping day, both values, and the delta:

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 RSS3, and the holder count legitimately wobbles both ways as tokens change hands. Publishing them as "revisions" would be exactly the fake-metric behaviour this product exists to eliminate.

Same-timestamp conflicting values on record for RSS3: 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 RSS3 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

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

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 Blockscout upstream family the counter rows came from; command 4 is the GitHub origin of the dev-activity series; command 5 is the estate's graded network row; command 6 is the frozen daily snapshot of the ledger. The CoinGecko market-series origin page is linked per-source in the provenance table above. One polite call per endpoint, no hammering.

# 1) The served revision feed for RSS3 — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=RSS3" | 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) Blockscout address counters for the RSS3 token contract (the token_transfers_total / contract_* origin):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/addresses/0xc98d64da73a6616c42117b582e832812e7b8d57f/counters" | python3 -m json.tool | head -30
# 4) GitHub API for RSS3-Network/Node (the dev_* origin family):
curl -s "https://api.github.com/repos/RSS3-Network/Node" | python3 -m json.tool | head -30
# 5) This estate's public API row for RSS3 (grades + provenance):
curl -s "https://kairossignal.com/v1/network/RSS3" | 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_rss3.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The RSS3 revision count is the live result of SELECT count() FROM default.depin_revision_ledger WHERE network='RSS3'; the page refuses to ship if the served /v1/revisions?symbol=RSS3 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 RSS3 page (browser-verified origin; 403 here is its bot wall) HTTP 403; Blockscout address counters for the RSS3 token contract (the token_transfers_total origin family) HTTP 200; GitHub API for RSS3-Network/Node (the dev_* origin family) HTTP 200; estate /v1/revisions?symbol=RSS3 HTTP 429; estate /v1/network/RSS3 HTTP 429.