Iagon (IAG) — the revision ledger

Generated 2026-09-02T20:30:24Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for Iagon: 7,493 observations · 30 distinct series · 3 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 19:49:20 · every one of the 7,493 rows carries a verify_url · 30 series refreshed in the last 24h (792 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where Iagon's archive 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. Iagon (the catalog name here is Iagon, category storage, chain cardano) does not publish a public stats API this estate polls — the network-side series come from the Koios Cardano chain-tip endpoint, captured hourly by this estate's collector since 2026-08-31 (the solve that took IAG off the zero-coverage list): block height, absolute slot, epoch and epoch-slot, with CoinGecko's market series and DefiLlama's protocol series alongside. The catalog's token_address for IAG is the Cardano policy id 5d16cc1a177b5d9ba9cfa9793b07e60f1fb70fea1f8aef064415d114494147 — Iagon is Cardano-native, so there is no EVM contract; the policy id is the on-chain asset identity.

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

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?symbol=IAG (the same query this page ran, served live), and a restatement would appear on this page the day the detector records one. /v1/revisions cross-check: the estate API's free-tier daily quota answered HTTP 429 at generation time (resets 00:00 UTC); the ledger count on this page is the live ClickHouse result, and the served endpoint was probed and found quota-gated, not missing.

Why zero is the interesting answer. The detector does not skip IAG — below, the live trail shows the four Cardano chain-tip series this estate captures hourly from Koios (4 series, every one of their hourly stamps rendered end to end so the monotone runs are visible raw), plus the daily-archive watchlist intersection. Both monotone-class chain-tip counters — the Cardano block height and the absolute slot — never moved backward anywhere in the held window, measured live below. The only backward move that exists in any IAG counter trail is the cardano_epoch_slot reset at the epoch-653 boundary — measured, printed, and explained: an epoch slot counter is relative to the current epoch by design, and a new epoch legally restarts it. That is protocol behaviour, not upstream rewriting history, and it is deliberately not ledgered. The classification is checkable against the raw rows below. That is the structural zero: the detector was watching, the counters were fully exposed to it, and upstream did not rewrite history for this network in the window this estate holds. Publishing an empty ledger as a live query result — instead of padding it with gauge or boundary noise — is the same retention discipline the ledger exists to sell.

What the detector watches for Iagon — the chain-tip counters, measured

The detector diffs every daily snapshot of every cumulative-by-construction series. For IAG the counter class is the Cardano chain tip: this estate captures four series hourly from the Koios /tip endpoint into depin_onchain (4 series × 184 hourly stamps total, 2026-08-31 23:31:03 → 2026-09-02 19:38:02). The estate detector's cumulative watchlist — imported directly from propintel/revision_ledger.py (75 declared names, so this page can never drift from the detector) — declares the chain-tip families (block_height, slot and epoch spellings among them) restatement-class by its own comment block. The four Cardano spellings are diffed below, live, over the full held window.

Live query result: 0 watchlist spellings held in the daily archive for IAG. The intersection query ran during generation and returned an empty set — none of the 75 cumulative-by-construction names the detector watches appear in IAG's depin_daily slice, because IAG's chain-tip counters are captured at hourly cadence into depin_onchain instead. The daily archive holds the CoinGecko market gauges and DefiLlama TVL series; the counter class for this network is the four chain-tip trails, fully diffed below.

cardano_abs_slot — absolute slot — the chain-wide slot counter since Cardano genesis (Shelley era), captured hourly from Koios (measured strictly monotone (never backward) across all 46 held stamps). Every held stamp, first and last shown here; the full trail is one ClickHouse query away (command 5 below):

cardano_block_height — block height — the number of blocks in the longest chain, captured hourly from Koios (measured strictly monotone (never backward) across all 46 held stamps). Every held stamp, first and last shown here; the full trail is one ClickHouse query away (command 5 below):

cardano_epoch — epoch number — increments exactly once per epoch (5 days), captured hourly from Koios (measured strictly monotone (never backward) across all 46 held stamps). Every held stamp, first and last shown here; the full trail is one ClickHouse query away (command 5 below):

cardano_epoch_slot — slot within the current epoch — RELATIVE by design: it restarts at every epoch boundary, captured hourly from Koios (not monotone — every backward step is itemised below). Every held stamp, first and last shown here; the full trail is one ClickHouse query away (command 5 below):

Every backward move in the chain-tip trails, measured live: 1 move(s), all in cardano_epoch_slot. The largest: cardano_epoch_slot 2026-09-01 21:38:02 → 2026-09-01 22:38:02 (431,572 → 3,176, Δ -428,396, -99.26%). This is the epoch-653 boundary: cardano_epoch_slot counts slots within the current epoch (432,000 slots per epoch on Cardano), so a new epoch restarting it at 0 is the protocol working exactly as designed — the same class of legal reset as a monthly counter rolling over. The detector's cumulative class (CUMULATIVE in propintel/revision_ledger.py) covers chain-tip regressions; a relative-position counter restarting on schedule is not a regression, and ledgering it would be manufacturing a fake revision — the exact behaviour this product exists to eliminate. cardano_epoch itself stepped 652 → 653 across the window: the only legal direction, and measured never backward (46 stamps).

Gauges that moved backward — deliberately NOT revisions

These series fall outside the detector's cumulative-by-construction class (NOT_TRULY_CUMULATIVE and plain gauges in propintel/revision_ledger.py): a drop there is a real market or window change, not upstream rewriting history. For IAG the market series dominate this table — price, market cap, fully-diluted valuation, TVL, staking TVL and the rolling change windows all oscillate as the market revalues and windows roll off; a drop there is the market, not a rewrite. Publishing them as "revisions" would be exactly the fake-metric behaviour this product exists to eliminate.

Same-timestamp conflicting values on record for IAG: none

The task-level conflict check, run live: any (metric, timestamp) family where this estate recorded two or more different values. The query ran at generation and returned 0 groups in both depin_onchain and depin_daily — every (metric, timestamp) pair the estate holds for IAG carries exactly one value. Zero here is the live query result, not a gap; the archive kept every write it made, and none of them disagree.

The ledger, live — every restatement recorded estate-wide (18 deduped events)

Deduped on revision identity exactly as /v1/revisions dedupes it. This is the same feed a subscriber polls; it is rendered live from ClickHouse at generation, not copied from a snapshot. Each row is an upstream source replacing the value of a (network, metric, date) it had already published — after this estate recorded the original. The superseded value is retained, never deleted; that retention is the only reason a rewrite is detectable, and it is the part every overwriting vendor discards. The Arweave rows (BLOCKS −14.4%) are the canonical example of what this product catches; IAG's own ledger slice is the zero above.

How detection works — and what it cannot see

The detector (propintel/revision_ledger.py) diffs every daily snapshot this estate holds of every cumulative-by-construction series — counters that cannot decrease unless upstream rewrote them (block heights, transaction and transfer counters, lifetime fees). A row enters default.depin_revision_ledger iff two snapshots disagree for an already-observed date by more than the 0.01% float-noise floor; zero human judgement. Resolution rule: latest observation wins for current-state reads, the superseded value is retained, never deleted. Population gauges (provider sets, node counts, prices, capacity, rolling windows) legitimately move both ways and are deliberately excluded — a drop there is a real change, not a rewrite; the gauge table on this page is the worked example. For IAG the counter class lives in the hourly Koios chain-tip archive, diffed live on this page above. Honest boundary: this catches value-history rewrites ex-post; identical-schema semantic drift with plausible values is what the hash-pinned derivation_replay layer is for. The detector's full classification is inspectable at /v1/revisions and frozen daily at /revision-ledger/REVISIONS_20260902.json.

The snapshot archive the detection runs over

IAG's slice of depin_daily: 321 rows over 17 snapshot days (2026-08-09 → 2026-09-01), from 2 source families. Each snapshot is a same-day capture of every series the collectors touched; the detector diffs consecutive snapshots of cumulative series across this window, and for IAG additionally the hourly chain-tip archive measured above. This is the substrate the zero above is measured over — not an assumption, a measured archive.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–2 hit this estate's public API (the same rows this page queried — every row carries source / as_of / verify_url); command 3 hits the Koios origin endpoint the chain-tip rows came from; commands 4–7 are the DefiLlama, estate, CoinGecko and Iagon origin surfaces; command 8 is the frozen daily snapshot of the ledger. One polite call per endpoint, no hammering.

# 1) The served revision feed for IAG — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=IAG" | python3 -m json.tool
# 2) The estate-wide feed (every network, both sides of every diff):
curl -s "https://kairossignal.com/v1/revisions" | python3 -m json.tool | head -80
# 3) Koios chain-tip API for Cardano (the cardano_* series origin):
curl -s -H "User-Agent: kairos-check" "https://api.koios.rest/api/v1/tip" | python3 -m json.tool
# 4) DefiLlama protocol page for iagon (the tvl_usd origin):
curl -s -o /dev/null -w "%{http_code}\n" -H "User-Agent: kairos-check" "https://defillama.com/protocol/iagon"
# 5) The full hourly chain-tip trail, live from ClickHouse (block height):
curl -s "https://kairossignal.com/v1/network/IAG" | python3 -m json.tool | head -60
# 6) CoinGecko Iagon page (the market-series origin; browser-verified, bot-walled to curl):
curl -s -o /dev/null -w "%{http_code}\n" "https://www.coingecko.com/en/coins/iagon"
# 7) Iagon project site (network origin):
curl -s -o /dev/null -w "%{http_code}\n" -H "User-Agent: kairos-check" "https://iagon.com"
# 8) The public daily snapshot of the ledger (frozen copy):
curl -s -o /dev/null -w "%{http_code}\n" "https://kairossignal.com/revision-ledger/REVISIONS_20260902.json"

Method & honesty notes. All counts are queries against the live ledger at generation time, not restamped copy — this page is regenerated by gen_revision_page_iag.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The IAG revision count is the live result of SELECT count() FROM default.depin_revision_ledger WHERE network='IAG'; the page refuses to ship if the served /v1/revisions?symbol=IAG is reachable and disagrees with it (at generation the estate API was answering its free-tier daily-quota 429, so the cross-check ran against ClickHouse as the authority and the endpoint was verified quota-gated, not missing). The 18 estate-wide events shown are deduped on revision identity (deterministic hash of network, metric, current_date, prior_date) exactly as the API dedupes them; detected_at is the first detection and never moves. Series absent from a section are absent, not zero. The same-stamp conflict check is the honest live answer: 0 groups in depin_onchain and 0 in depin_daily. Upstream probes ran serially by this generator immediately before rendering: CoinGecko Iagon page (browser-verified origin; 403 here is its bot wall) HTTP 403; DefiLlama protocol page for iagon (the tvl_usd origin) HTTP 403; Koios Cardano chain-tip API (the cardano_* series origin) HTTP 200; Iagon project site (network origin) HTTP 200; estate /v1/revisions?symbol=IAG HTTP 429; estate /v1/network/IAG HTTP 429.