ARIO (AR.IO Network) — the network, measured

Generated 2026-09-02T17:13:54Z from live ClickHouse queries against this estate's ledger. Held inventory: 7,651 observations · 32 distinct series · 3 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 16:49:30 · 7,651/7,651 rows carry a verify_url. 25 series refreshed in the last 24h (720 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number 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.

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. A series held for a single day renders a one-bar sparkline and says so via its day count — e.g. arweave_nodes_count is a one-day series in the archive.

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/max supply rows are different quantities (circulating vs total vs cap) and are never netted against each other. Unlike the EVM-network siblings, no chain-side supply read exists for ARIO in the ledger — the catalog's token address is an Arweave-format identifier, not an EVM contract — so these references are the only supply-side figures held, and the page says exactly that rather than inventing a third number.

Network self-telemetry — AR.IO's own peers endpoint, as held (first-party)

First-party reads of AR.IO's own public peers register (ar-io.dev/ar-io/peers, the catalog's listed stats API — has_public_stats_api = 1) by this estate's collectors: the network's own counts of gateways (gateways dict) and tracked Arweave node endpoints (arweaveNodes dict). This is the network's self-reported supply-side telemetry — the strongest provenance class in the ledger: the upstream is the network itself, and each row's verify_url re-fetches the same JSON document the collector read (the document is {"gateways": {host: …}, "arweaveNodes": {host: …}}; the verify command prints the two dict lengths — probe-verified with a live cross-check against the ledger values before this page shipped). gateway_count is sampled repeatedly every day in the 30-day window; arweave_nodes_count exists as a single held row and is shown from its first held row — newer rows are absent from the ledger and that absence is shown, not smoothed.

Dev velocity — GitHub, as held

Raw GitHub API counters for ar-io — repo-level (ar-io/ar-io-node) and one org-level row (public_repos via api.github.com/orgs/ar-io, 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 — 32 measured series, each with provenance

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

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

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

Served by /v1/network/ARIO — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth. Unflattering grades ship with the flattering ones, unsmoothed: the engines' outputs are published exactly as computed, and the measured-series count this page derives is the coverage engine's input — not derived from any series on this page.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–3 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 ar-io-network); command 4 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) AR.IO's OWN peers register — the network's self-published supply-side counts (keyless, as of 2026-09-02T17:13:54Z):\ncurl -s "https://ar-io.dev/ar-io/peers" | python3 -c 'import json,sys; d=json.load(sys.stdin); print("gateways:", len(d["gateways"]), "| arweaveNodes:", len(d["arweaveNodes"]))'
# 1b) Human-view check of the verify_url target (the JSON document itself):\ncurl -s -o /dev/null -w "%{http_code}\n" "https://ar-io.dev/ar-io/peers"
# 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: ar-io-network):
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=ar-io-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/ar-io-network"
# 3) Dev velocity, repo-level (GitHub public API):\ncurl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/ar-io/ar-io-node" | python3 -m json.tool | head -20
# 3b) Dev velocity, org-level (GitHub public API):\ncurl -s -H "User-Agent: kairos-check" "https://api.github.com/orgs/ar-io" | python3 -c "import json,sys; print('public_repos', json.load(sys.stdin).get('public_repos'))"
# 4) This estate's public API row for ARIO:\ncurl -s "https://kairossignal.com/v1/network/ARIO" | 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_ario.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: gateway_count maps to gateways_total (unit-verified) and total_supply maps to token_supply_total (question-verified). The remaining series are ARIO-native market/telemetry metrics with no cross-network concept; grading them would be fabrication, so they are labelled "ario-native (unmapped)". Chain-side rows: there are none. The catalog lists ARIO's chains as base,solana and the estate holds no chain-side telemetry for this network — the catalog's token address is an Arweave-format identifier, not an EVM contract — so no contract section exists on this page, and that is absence, not zero. The CoinGecko circulating and total/max supply rows are different quantities (circulating vs total vs cap) and are never netted; with no chain-side read held, they are the only supply-side references on the page, each labelled a market-data figure. The first-party family reads AR.IO's own peers register at ar-io.dev — the network's self-published counts, labelled as such and never merged with the market-reference rows; the generator live-cross-checked the fetched dict lengths against the ledger's argMax values immediately before rendering and ships the result of that check below, whatever it was. 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. 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 (ar-io-network): fetched; AR.IO peers endpoint (first-party upstream, live cross-check): 200 cross-check gateways=645 (ledger argMax 645), arweaveNodes=131 (ledger argMax 131); GitHub ar-io/ar-io-node: fetched; GitHub orgs/ar-io: fetched; estate /v1/network/ARIO: fetched.