Nosana (NOS) — the network, measured

Generated 2026-10-17T04:53:16Z from live ClickHouse queries against this estate's ledger. Held inventory: 55,363 observations · 81 distinct series · 9 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-17 04:51:55 · 55,363/55,363 rows carry a verify_url. 78 series refreshed in the last 24h (1,414 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number comes from

9 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.

Network telemetry — the Nosana dashboard, as held

Read from the network's own public dashboard API (dashboard.k8s.prd.nos.ci): /api/stats for the staking state (nos_staked, stakers), /api/markets for the GPU node market (markets held, median hourly reward) — and an archived 2026-08-10 supply pair. Two series flow fresh (nos_staked, stakers — 567 rows each at generation); the idle-node and node-queue fields are withdrawn (see the note below); the supply pair and total_xnos_staked are archived single rows from the collector's first generation, labelled as such and shown exactly as held — never re-derived, never summed.

GPU job board — dashboard /api/jobs, as held

The network's job board, polled via /api/jobs?state=QUEUED and ?state=RUNNING: what the container market actually has in flight. 208 rows of each at generation, fresh to the hour.

Dev velocity — GitHub, as held

Public repo activity for Nosana: the nosana-cli repo for stars, forks, issues, watchers and days-since-push. Daily snapshots; each row keeps its own as-of stamp.

On-chain reads — Solana RPC, as held

Chain reads for the NOS token (nosX…Moo7): a fresh daily total-supply read and the holder-concentration snapshots (top-1/10/20 percentages). The verify_url on these rows is the Solscan token page — a browser page, not a keyless JSON API; the verify section gives the public-RPC alternative.

Full metric inventory — 80 measured series, each with provenance

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

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

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 and the Solscan token page 403 plain curl, so the programmatic markets endpoint and the public RPC are given); command 5 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) The network's own dashboard stats endpoint (staking state) — keyless, as of 2026-10-17T04:53:16Z:
curl -s -H "User-Agent: kairos-check" "https://dashboard.k8s.prd.nos.ci/api/stats" | python3 -m json.tool
# 1b) The dashboard node-market endpoint (markets, reward median):
# The dashboard node-market endpoint (gpu_markets_total, reward median):\ncurl -s -H "User-Agent: kairos-check" "https://dashboard.k8s.prd.nos.ci/api/markets" | python3 -m json.tool | head -40
# 2) Market reference (CoinGecko public API):
# 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:
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=nosana" | python3 -m json.tool
# 3) Dev velocity (GitHub public API):
# GitHub public API — the repo our dev-velocity series reads:
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/nosana-ci/nosana-cli" | python3 -m json.tool | head -20
# 4) On-chain supply (Solana public RPC):
# On-chain reads: the verify_url on the solana_rpc rows is the
# Solscan browser token page (https://solscan.io/token/nosXBVoaCTtYdLvKY6Csb4AC8JCdQKKAaWYtx2ZMoo7) — fine in a
# browser, not a curl target. The keyless public RPC alternative:
curl -s -X POST "https://api.mainnet-beta.solana.com" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"getTokenSupply","params":["nosXBVoaCTtYdLvKY6Csb4AC8JCdQKKAaWYtx2ZMoo7"]}' | python3 -m json.tool
# 5) This estate's public API row for NOS:
curl -s "https://kairossignal.com/v1/network/NOS" | 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_nos.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 Nosana-native network/market metrics with no cross-network concept; grading them would be fabrication, so they are labelled "nos-native (unmapped)". Collection generations (fresh-flowing vs archived single rows) are shown side by side as held, never summed, merged, or reconciled. The three supply reads (chain, network API, CoinGecko) are published side by side, never merged. Two dashboard fields that were not measurements are withdrawn and say so above, rather than silently dropped or re-invented. 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: dashboard /api/stats HTTP 200; dashboard /api/markets HTTP 200; dashboard /api/jobs?state=QUEUED HTTP 200; CoinGecko markets API HTTP 200; GitHub nosana-cli HTTP 200; Solana public RPC HTTP 200; estate /v1/network/NOS HTTP 200.