Iagon (IAG) — the network, measured

Generated 2026-10-12T04:46:27Z from live ClickHouse queries against this estate's ledger. Held inventory: 33,833 observations · 42 distinct series · 4 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-12 04:38:02 · 33,833/33,833 rows carry a verify_url. 42 series refreshed in the last 24h (744 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number comes from

4 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 for the IAG token (id iagon): 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 reference publishes total_supply = max_supply = 1,000,000,000 with circulating 487.3M; all rows ship exactly as the reference publishes them. The endpoint was probed live during generation (HTTP 200): its ATH 0.389333 and ATL 0.00070422 exact-match the held rows, and its market cap sat in the same family as the held figure.

Aggregator — DefiLlama /protocol/iagon, as held

DefiLlama derives these from its own adapters over public chain data — an aggregator tier, explicitly not first-party telemetry. The writer (collectors_clean/defillama_fees_tvl.py) stores an API-returned zero as a real observation and skips only missing/null fields; IAG's tvl_usd series is all zeros as published upstream (see caveat), while staking TVL from the same response is non-zero. The api.llama.fi origin could not be probed from this generation run (run-level command gate); the zero's provenance stands on the same-response cross-check above.

Chain tip — Koios Cardano API, as held

These four series are Cardano CHAIN-TIP gauges — epoch, block height, absolute slot and epoch slot — read from the free public Koios API (api.koios.rest, keyless, probed HTTP 200 during generation: epoch 653, block 13889453, monotone-consistent with the held rows). They describe the chain the IAG token is issued on, not Iagon's storage-network internals; the estate holds no first-party stats API for the storage network itself (catalog has_public_stats_api = 0), so there is no network-telemetry section on this page — absence is stated, never zero-filled.

Full metric inventory — 42 measured series, each with provenance

Every series held for IAG 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. The all-zero tvl_usd series and the cardano_* chain gauges are included with their caveats — the inventory shows what is held, at the depth it is held.

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

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 IAG. 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 (Koios and CoinGecko were probed HTTP 200 at generation; the DefiLlama programmatic endpoint is given with the collector's own slug — its browser verify_url is on every held row); command 4 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) Koios Cardano chain tip (free, keyless — probed HTTP 200 at 2026-10-12T04:46:27Z):
curl -s -H "User-Agent: kairos-check" "https://api.koios.rest/api/v1/tip" | python3 -m json.tool
# 2) Market reference (CoinGecko public API, collector id iagon):
# CoinGecko public markets API — id "iagon", the exact id our
# market collector reads (data/coingecko_ids.json). The verify_urls on
# the held rows point at the browser coin page; this is the programmatic
# endpoint of the same reference:
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=iagon" | python3 -m json.tool | head -30
# 3) Aggregator (DefiLlama protocol API, collector slug iagon):
# DefiLlama protocol page — slug "iagon" from the same registry the
# collector reads (data/defillama_slugs.json). The API endpoint behind
# the held rows:
curl -s "https://api.llama.fi/protocol/iagon" | python3 -c "import json,sys; d=json.load(sys.stdin); print(d['tvl'][-1], d.get('currentChainTvls'))"
# 4) This estate's public API row for IAG:
curl -s "https://kairossignal.com/v1/network/IAG" | 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_iag.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 IAG-native network/market/chain metrics with no cross-network concept; grading them has no basis in the held data, so they are labelled "iag-native (unmapped)". The chain-tip gauges are the issuance chain's, not storage internals; the all-zero TVL is the upstream's published answer with the same-response cross-check documented where it appears; supply figures are held as the reference publishes them. Where a section has no data, it is absent — we do not publish zeros for gaps.