Lava Network (LAVA) — the revision ledger

Generated 2026-09-02T18:47:07Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for Lava Network: 12,334 observations · 42 distinct series · 3 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 18:42:11 · 12,334 of 12,334 rows carry a verify_url · 41 series refreshed in the last 24h (1,104 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where LAVA's archive comes from

3 source families feed this network's archive. Every row they wrote carries its own source, as_of and verify_url; this table is the live rollup of that. The dominant family is CoinGecko's /coins/markets market reference; the chain-side family (cosmos_lcd) is Lava's own Cosmos LCD endpoints — the network's published chain state, read directly.

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

Queried live at generation time: default.depin_revision_ledger holds zero rows for LAVA, and the served /v1/revisions?symbol=LAVA feed reports the same zero (/v1/revisions?symbol=LAVA cross-check passed: the served API reports 0 row(s), matching the deduped ledger count rendered on this page.). Lava Network's declared-cumulative series have been monotonic for the entire 2026-08-09 → 2026-09-01 daily-snapshot archive: the block height never moved backwards, the account counter never moved backwards, the proposal and IBC-channel counters never moved backwards. Upstream Lava endpoints have not (yet) rewritten any historical value this estate holds.

The watchlist — what we monitor for LAVA, and its live monotonicity status

The detector only judges series that are cumulative by construction: a chain height, an account counter, a proposal counter. A gauge (price, market cap, bonded tokens) legitimately falls when the market or the validator set moves — that is not a revision and is never recorded as one. Every LAVA series in the daily archive, measured across its full span, queried live:

Declared-cumulative series (detector-judged)

Gauges — legitimately backward-moving, excluded by detector construction

These fall for real reasons (markets move, validator sets churn). A drop here is a population change, not a rewrite — listed for completeness, never entered in the ledger.

Same-timestamp rewrite check: clean

The revision ledger keys on daily snapshots; a second rewrite channel would be two different values written for the same (metric, as_of) instant in the raw stream. Queried live at generation across all 12,334 LAVA observations: every duplicate (metric, as_of) group carries identical values — zero conflicting groups. The ledger table is the canonical revision record for this network, as designed.

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. LAVA is currently the clean case; these networks are not.

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, account counts, proposal counts). 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 deleted. Population gauges (prices, market caps, bonded tokens) legitimately move both ways and are deliberately excluded — a drop there is a real change, not a rewrite. 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 Lava's own Cosmos LCD endpoint, the first-party chain-state source family this archive came from; command 4 is the estate's graded network row; command 5 is the frozen daily snapshot of the ledger. One polite call per endpoint, no hammering.

# 1) The served revision feed for LAVA — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=LAVA" | 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) Lava's own Cosmos LCD chain tip (the first-party source family for this network):
curl -s -H "User-Agent: kairos-check" "https://rest.cosmos.directory/lava/cosmos/base/tendermint/v1beta1/blocks/latest" | python3 -m json.tool | head -20
# 4) This estate's public API row for LAVA (grades + provenance):
curl -s "https://kairossignal.com/v1/network/LAVA" | python3 -m json.tool | head -60
# 5) 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 tables at generation time, not restamped copy — this page is regenerated by gen_revision_page_lava.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The LAVA revision count is the deduped live result of SELECT ... FROM default.depin_revision_ledger WHERE network='LAVA' GROUP BY revision identity; the page refuses to ship if the served /v1/revisions?symbol=LAVA disagrees with it. 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. Upstream probes ran serially by this generator immediately before rendering: estate /v1/revisions?symbol=LAVA HTTP 200; estate /v1/network/LAVA HTTP 200.