Ankr Network (ANKR) — the revision ledger

Generated 2026-10-17T05:10:30Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for Ankr Network: 40,320 observations · 81 distinct series · 5 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-17 04:58:01 · every one of the 40,320 rows carries a verify_url · 34 series refreshed in the last 24h (720 fresh rows). Nothing on this page is cached, estimated, or remembered.

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

Queried live at generation time: default.depin_revision_ledger holds zero rows for ANKR (raw detector output for this network: 0 rows). /v1/revisions?symbol=ANKR cross-check passed: the served API reports 0 row(s), matching the deduped ledger count rendered on this page.

What we monitor for ANKR — live monotonicity of every held series

The detector only judges series that are declared cumulative-by-construction: a counter that cannot legitimately decrease. A gauge (price, staked balances, rolling fee windows, staker populations) legitimately falls when the market moves or stakers exit — that is not a revision and is never recorded as one. For every daily-snapshot series we hold for ANKR (76 metrics, 2,316 rows, 72 snapshot dates), this is its measured state across the full archive, queried live at generation. The 0 declared-cumulative counter series show 0 backward moves in total — that is the measured content of the zero above. The 76 gauge-class series move both ways by nature and are excluded from the detector by design. Classification is imported from the detector at generation (propintel/revision_ledger.py) — this page does not maintain its own opinion.

Resolution rule: latest observation wins for current-state reads; the superseded value is retained, never deleted — retaining the before-value is the only reason a restatement is detectable at all.

The one counter the detector grades for ANKR: fees_alltime_usd, every snapshot on record

This is the full declared-cumulative class for Ankr in this estate's daily archive — the DefiLlama alltime fees series, sourced from api.llama.fi/summary/fees/ankr. It is shown in full because it is the only series a history rewrite would surface on: every held value, in order, live-queried. It rises at every step — that is the measured content of the zero-restatement ledger count above.

Same-timestamp conflicting values on record for ANKR: none

The rewrite-vector 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 (raw stream) and depin_daily (daily snapshots) — every (metric, timestamp) pair the estate holds for ANKR 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 (39 deduped events)

ANKR is currently the clean case. These networks are not: upstream sources for AR, ATH, AUKI, EIGEN, FLOCK, GRT, NODE, OBOT, OPEN, OVPP, R1, SOGNI, STORJ replaced already-published values after this estate recorded the original. Deduped on revision identity exactly as /v1/revisions dedupes it; rendered live from ClickHouse at generation, not copied from a snapshot. The superseded value is retained, never overwritten; that retention is the only reason a rewrite is detectable, and it is the part every overwriting vendor discards.

Provenance — where ANKR's archive comes from

Ankr Network is a multi-chain staking and node infrastructure network (catalog category compute, chains: arbitrum-one,avalanche,binance-smart-chain,blast,ethereum,fantom,linea,mode,optimistic-ethereum,polygon-pos,polygon-zkevm,scroll). Its own public staking metrics endpoint (api.staking.ankr.com/v1alpha/metrics) supplies the supply-side telemetry — services tracked, staker positions, per-chain APYs and staked balances — collected directly by this estate, beside DefiLlama fee windows (the family fees_alltime_usd — the one declared-cumulative series — belongs to), CoinGecko market rows, and the Ankr-network GitHub activity series. Every row they wrote carries its own source, as_of and verify_url; this table is the live rollup of that.

How detection works — and what it cannot see

The detector (propintel/revision_ledger.py) diffs every daily snapshot this estate holds of every declared cumulative-by-construction series — counters that cannot decrease unless upstream rewrote them (alltime fees, token transfers, block heights, reward and claim counters). A row enters default.depin_revision_ledger iff two snapshots disagree for an already-observed date; zero human judgement. Resolution rule: latest observation wins for current-state reads, the superseded value is retained, never overwritten. Gauges (prices, staked balances, rolling fee windows, staker populations) legitimately move both ways and are deliberately excluded — a drop there is a real market or population change, not a rewrite; the 28 backward-moving ANKR gauge series in the watchlist above are the worked example. 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.

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 Ankr's own staking metrics endpoint, the first-party source of the supply-side family; command 4 is the upstream origin of the one declared-cumulative counter; command 5 is the estate's graded network row; command 6 is the frozen daily snapshot of the ledger. One polite call per endpoint, no hammering.

# 1) The served revision feed for ANKR — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=ANKR" | 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) Ankr's own public staking metrics endpoint (the first-party source):
curl -s -H "User-Agent: kairos-check" "https://api.staking.ankr.com/v1alpha/metrics" | python3 -m json.tool | head -40
# 4) The alltime-fees series' origin (the declared-cumulative counter's upstream):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/ankr" | python3 -m json.tool | head -40
# 5) This estate's public API row for ANKR (grades + provenance):
curl -s "https://kairossignal.com/v1/network/ANKR" | python3 -m json.tool | head -60
# 6) 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_ankr.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The ANKR revision count is the deduped live result of SELECT ... FROM default.depin_revision_ledger WHERE network='ANKR'; the page refuses to ship if the served /v1/revisions?symbol=ANKR disagrees with it. The 39 estate-wide events shown are deduped on revision identity exactly as the API dedupes them; detected_at is the first detection and never moves. The zero-restatement claim is backed on this page by the per-series monotonicity table and the full fees_alltime_usd snapshot trail (both queried live), plus the same-stamp check. Series absent from a section are absent, not zero. Upstream probes ran serially by this generator immediately before rendering: api.staking.ankr.com/v1alpha/metrics (first-party) HTTP 200; api.llama.fi/summary/fees/ankr (fees_alltime_usd source) HTTP 200; estate /v1/revisions?symbol=ANKR HTTP 200; estate /v1/network/ANKR HTTP 200.