RSS3 — the network, measured

Generated 2026-09-02T16:56:10Z from live ClickHouse queries against this estate's ledger. Held inventory: 7,810 observations · 37 distinct series · 5 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 16:49:30 · 7,810/7,810 rows carry a verify_url. 37 series refreshed in the last 24h (799 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 coin page, 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. The change columns / rank / ATH-ATL / high-low series start later in the archive than the price rows (each metric's caveat in the full inventory states its own first-held row) and are shown from their first held row. The circulating and total supply rows are different quantities (circulating vs total) and are never netted against each other or against the chain-side contract reads in the token sections below — different measurements from different endpoints, shown side by side.

Chain reads — publicnode Ethereum RPC, as held (first-party)

First-party JSON-RPC reads by the estate's deep_network_stats.py collector against the publicnode public Ethereum endpoint (ethereum-rpc.publicnode.com): ETHEREUM mainnet block height and gas price, plus the RSS3 ERC-20 contract's totalSupply read by eth_call (selector 0x18160ddd, 18 decimals). The RSS3-native VSL endpoints were probed 2026-08-25 and found unreachable from this host (documented in the collector), so the estate reads the token's canonical ERC-20 ledger state on ethereum — these are Ethereum-chain and token-contract values, not RSS3-VSL chain values; the estate holds zero RSS3-native VSL telemetry, which is absence, not zero.

Token counters — deep_stats eth.blockscout reads, as held

Token-level counters (holders, transfers) for the RSS3 ERC-20 contract 0xc98d64da73a6616c42117b582e832812e7b8d57f on ethereum, written by the estate's deep_network_stats.py family. Counters are cumulative and published raw — never differenced into rates. These describe the bridged/ERC-20 token contract, not RSS3-native accounts.

Token & contract counters — evm_blockscout family, as held

The estate's EVM family reading the same RSS3 ERC-20 contract 0xc98d64da73a6616c42117b582e832812e7b8d57f on eth.blockscout at its own cadence: token counters (holders, transfers, the contract's totalSupply), contract-level address counters (transactions, gas used), and the top holder's balance. holders_count / token_transfers_total / onchain_total_supply therefore appear from TWO collector families in this estate's archive — the same contract on the same explorer measured at different times, each keeping its own verify_url, published side by side and never merged. Cumulative counters are published raw — never differenced into rates.

Dev velocity — GitHub, as held

Raw GitHub API counters for RSS3-Network — repo-level (RSS3-Network/Node) and one org-level row (public_repos via api.github.com/orgs/RSS3-Network, a different measurement from the repo rows; each keeps its own verify_url). Counters are published raw, never differenced into rates; dev_days_since_push is a raw time delta from the repo's real pushed_at timestamp.

Full metric inventory — 37 measured series, each with provenance

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

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 RSS3. Zero here is the live query result, not a gap — the ledger itself is at /v1/revisions.

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

Served by /v1/network/RSS3 — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth. The dev-velocity and revenue grades are F and data coverage D, and they are published exactly as computed: the estate's dev-velocity engine scores RSS3's GitHub activity at zero against its own window, the estate holds no protocol-revenue adapter rows for RSS3, and the measured-series count this page derives is the coverage engine's input — the unflattering parts ship with the flattering ones, unsmoothed.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–4 hit the same upstream endpoints our collectors do (the coingecko.com browser coin page 403s plain curl, so the programmatic markets endpoint is given, id rss3); command 5 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) The token's settlement chain (Ethereum) via the publicnode public JSON-RPC — keyless, as of 2026-09-02T16:56:10Z:
#    (chain head height) curl -s -X POST -H "Content-Type: application/json" --data-binary '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}' "https://ethereum-rpc.publicnode.com"
#    (gas price, wei -> the held ethereum_gas_price_gwei is this / 1e9) curl -s -X POST -H "Content-Type: application/json" --data-binary '{"jsonrpc":"2.0","id":1,"method":"eth_gasPrice","params":[]}' "https://ethereum-rpc.publicnode.com"
#    (the held onchain_total_supply: eth_call totalSupply on the RSS3 contract, 18 decimals) curl -s -X POST -H "Content-Type: application/json" --data-binary '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xc98d64da73a6616c42117b582e832812e7b8d57f","data":"0x18160ddd"},"latest"]}' "https://ethereum-rpc.publicnode.com" | python3 -c "import sys; r=sys.stdin.read(); h=json.loads(r)['result']; print('totalSupply (18 decimals)', int(h,16)/1e18)"
# 2) Token counters on eth.blockscout (holders / transfers for the RSS3 ERC-20 contract):\ncurl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0xc98d64da73a6616c42117b582e832812e7b8d57f" | python3 -m json.tool | head -20
# 2b) Token transfer counter detail:\ncurl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0xc98d64da73a6616c42117b582e832812e7b8d57f/counters" | python3 -m json.tool
# 2c) Contract ADDRESS counters (transactions, gas used):\ncurl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/addresses/0xc98d64da73a6616c42117b582e832812e7b8d57f/counters" | python3 -m json.tool
# 2d) Top holder balance (token holders listing):\ncurl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0xc98d64da73a6616c42117b582e832812e7b8d57f/holders" | python3 -m json.tool | head -20
# 3) 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: rss3):
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=rss3" | python3 -m json.tool
# 3b) 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/rss3"
# 4) Dev velocity, repo-level (GitHub public API):\ncurl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/RSS3-Network/Node" | python3 -m json.tool | head -20
# 4b) Dev velocity, org-level (GitHub public API):\ncurl -s -H "User-Agent: kairos-check" "https://api.github.com/orgs/RSS3-Network" | python3 -c "import json,sys; print('public_repos', json.load(sys.stdin).get('public_repos'))"
# 5) This estate's public API row for RSS3:\ncurl -s "https://kairossignal.com/v1/network/RSS3" | 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_rss3.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 RSS3-native market/telemetry metrics with no cross-network concept; grading them would be fabrication, so they are labelled "rss3-native (unmapped)". Chain-side rows are Ethereum-side by documented upstream shape: the RSS3-native VSL endpoints were probed 2026-08-25 and found unreachable from this host, so the estate reads the token's canonical ERC-20 ledger state on ethereum (publicnode eth_call + eth.blockscout) — no RSS3-VSL-native telemetry exists on this page, and that is absence, not zero. The CoinGecko circulating and total supply rows are different quantities (circulating vs total) and are never netted; the ERC-20 contract's totalSupply (publicnode eth_call and blockscout) is a third, chain-side measurement of the token contract, shown side by side and never reconciled into one number. Two blockscout families (deep_stats_eth_blockscout and evm_blockscout) measure the same contract at different cadences; both are labelled with their own provenance and never merged. GitHub rows mix repo-level and org-level counters; both are labelled with their own provenance and never combined, and dev_days_since_push is a raw time delta from a real timestamp. The estate grades are published exactly as the engines served them, unflattering parts included; dev velocity F, revenue F and data coverage D are the engines' own outputs, not derived from any series on this page. 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: CoinGecko markets API (rss3) HTTP 200; publicnode Ethereum RPC (eth_blockNumber POST) HTTP 200; eth.blockscout token endpoint (rss3 contract) HTTP 200; eth.blockscout token counters (rss3 contract) HTTP 200; eth.blockscout address counters (rss3 contract) HTTP 200; GitHub RSS3-Network/Node HTTP 200; GitHub orgs/RSS3-Network HTTP 200; estate /v1/network/RSS3 HTTP 200.