NKN (NKN) — the network, measured

Generated 2026-10-17T04:51:37Z from live ClickHouse queries against this estate's ledger. Held inventory: 37,045 observations · 44 distinct series · 5 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-17 04:34:01 · 37,045/37,045 rows carry a verify_url. 43 series refreshed in the last 24h (685 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 deeper change columns start 2026-08-22 in our archive (each metric's caveat in the full inventory states its own first-held row) and are shown from their first held row.

Chain-usage telemetry — NKN's own statistics API, as held

Read from the network's own public endpoint (openapi.nkn.org/api/v1/statistics/counts): cumulative address, block, and transaction counts on the NKN chain. At generation, 3 series flow fresh (address_count, block_count, tx_count) and 0 are archived single rows () — each row's label states which it is. The counters are monotonic cumulative totals exactly as NKN reports them; this estate never differences them into rates. Nothing is re-derived or presented as flowing when it is not.

Dev velocity — GitHub, as held (repo + org)

Public repo activity for nknorg/nkn, the reference NKN node implementation. dev_public_repos is an org-level count and verifies against the nknorg org endpoint — each row keeps its own verify_url. Rows are shown as held; nothing is merged or reconciled.

Full metric inventory — 44 measured series, each with provenance

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

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 NKN. 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–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); command 4 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) The network's own statistics endpoint — keyless, as of 2026-10-17T04:51:37Z:
curl -s -H "User-Agent: kairos-check" "https://openapi.nkn.org/api/v1/statistics/counts" | python3 -m json.tool
# 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=nkn" | python3 -m json.tool
# 3) Dev velocity, repo level (GitHub public API):
# GitHub public API — the repo our dev-velocity series reads
# (repo-level stars/forks/issues/watchers; dev_public_repos
# verifies against the org endpoint instead):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/nknorg/nkn" | python3 -m json.tool | head -20
# 3b) Dev velocity, org level (the endpoint behind dev_public_repos):
# The org endpoint behind dev_public_repos:
curl -s -H "User-Agent: kairos-check" "https://api.github.com/orgs/nknorg" | python3 -m json.tool | head -20
# 4) This estate's public API row for NKN:
curl -s "https://kairossignal.com/v1/network/NKN" | 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_nkn.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: tx_count maps to transactions_total (question-verified) and total_supply maps to token_supply_total (question-verified). The remaining series are NKN-native network/market metrics with no cross-network concept; grading them would be fabrication, so they are labelled "nkn-native (unmapped)". Collection generations (fresh-flowing vs archived single rows) are derived from row counts at generation and shown side by side as held, never summed, merged, or reconciled. The first-party counters stay cumulative totals as NKN's statistics API reports them — never differenced into rates. dev_public_repos verifies against the org endpoint; repo-level series against the repo endpoint; each row keeps its own verify_url. 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: NKN openapi statistics counts HTTP 200; CoinGecko markets API HTTP 200; GitHub nknorg/nkn HTTP 200; GitHub nknorg org HTTP 200; estate /v1/network/NKN HTTP 200.