EIGEN (EigenCloud (prev. EigenLayer)) — the revision ledger

Generated 2026-09-02T19:25:16Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for EIGEN: 8,517 observations · 46 distinct series · 7 upstream sources · first row 2026-08-09 23:27:47 · newest row 2026-09-02 18:58:01 · every one of the 8,517 rows carries a verify_url · 46 series refreshed in the last 24h (884 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where EIGEN's archive comes from

7 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. EIGEN does not ship a first-party stats API (catalog: has_public_stats_api=0), so the estate rides seven upstream families: CoinGecko's market series, two DefiLlama families (fees and protocol TVL), two Ethereum-native families (PublicNode RPC and Blockscout) watching the EIGEN token contract 0xec53bf9167f50cdeb3ae105f56099aaab9061f83, and Layr-Labs GitHub activity. The restated counter itself comes from DefiLlama's fees summary — api.llama.fi/summary/fees/eigencloud.

Revision ledger — 1 backward revision(s) recorded for EIGEN (raw table holds 2 rows — the same identity re-detected; deduped on revision identity as /v1/revisions serves it)

Backward revisions are values upstream later replaced for a date this estate had already archived. The before-value is retained alongside the replacement — both snapshot dates, both numbers — which is what no overwriting vendor keeps. /v1/revisions?symbol=EIGEN cross-check passed: the served API reports 1 row(s), matching the deduped ledger count rendered on this page.

The trail behind the revision — fees_alltime_usd, every snapshot held

This is the actual counter trail the detector diffed for EIGEN, rendered live from the archive: every daily snapshot of fees_alltime_usd (DefiLlama's all-time protocol fees for EigenCloud), end to end. Each step is a series that cannot decrease unless upstream rewrote history — and on 2026-08-29 the snapshot for 2026-08-28's cumulative value came back lower than what 08-28 itself recorded. That drop is the revision above; the rows around it are the monotonic run that makes the drop unmistakable. This same shape is what the sibling pages for zero-revision networks (NKN, PKT, HOPR, GLM) watch for and do not find.

Why exactly one event — the noise floor, measured

The detector (propintel/revision_ledger.py) publishes a backward pair only when the move exceeds its noise floor NOISE_PCT = 0.0001 (0.01%) — sub-floor moves are measurement noise, not rewrites. Both EIGEN moves of this counter, re-derived live from the archive during this generation:

Reading this table. DefiLlama did not stop restating after 08-28 — the counter moved again the next day (-5,737.33 USD, -0.0035%) — but that move is smaller than the detector's noise floor, so it is treated as measurement noise rather than a rewrite. That is the floor doing its job: the ledger records history rewrites, not every wiggle of an upstream counter. The 08-28 rewrite cleared the floor and is on the ledger; the 08-29 → 08-30 move did not and is not. Both verdicts re-derived live at generation.

What the detector watches for EIGEN — the intersection, measured

The detector diffs every daily snapshot of every cumulative-by-construction series. Below is the live intersection of 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) — with what the daily archive holds for EIGEN. Five watched series are held and were fully diffed; exactly one produced a backward pair.

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 population or market change, not upstream rewriting history. Publishing them as "revisions" would be exactly the fake-metric behaviour this product exists to eliminate. EIGEN's archive holds 16 such series that moved backward across its snapshots — holders counts, price, rolling fee windows, market cap — every one a legitimate gauge, none a revision.

Same-timestamp conflicting values on record for EIGEN: 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 EIGEN 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. EIGEN's own event sits in this table — fees_alltime_usd, 2026-08-28, DefiLlama.

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; 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) legitimately move both ways and are deliberately excluded — a drop there is a real population change, not a rewrite; the gauge table on this page is 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.

Estate grades for EIGEN (graded 2026-08-20 13:54:15.000)

Served by /v1/network/EIGEN — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, published exactly as the engines emitted them, unflattering parts included.

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); commands 3–5 hit the upstream families the network-side rows came from — including the exact endpoint the restated counter came from; command 6 is the estate's graded network row; command 7 is the frozen daily snapshot of the ledger. One polite call per endpoint, no hammering.

# 1) The served revision feed for EIGEN — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=EIGEN" | 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) DefiLlama's fees summary for EigenCloud — the origin of the restated counter:
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/eigencloud" | python3 -m json.tool | head -40
# 4) Blockscout token endpoint (the onchain token-contract family):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0xec53bf9167f50cdeb3ae105f56099aaab9061f83" | python3 -m json.tool | head -30
# 5) GitHub API for Layr-Labs/eigenlayer-contracts (the dev-velocity upstream family):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/Layr-Labs/eigenlayer-contracts" | python3 -m json.tool | head -30
# 6) This estate's public API row for EIGEN (grades + provenance):
curl -s "https://kairossignal.com/v1/network/EIGEN" | python3 -m json.tool | head -60
# 7) 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_eigen.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The EIGEN revision count is the deduped live result of SELECT count() FROM (SELECT metric, prior_date, current_date_ FROM default.depin_revision_ledger WHERE network='EIGEN' GROUP BY metric, prior_date, current_date_) — the raw table holds 2 rows because the detector re-detected the same identity on its next run and detected_at is the first detection (never moved); the page refuses to ship if the served /v1/revisions?symbol=EIGEN disagrees with the deduped count. 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. The noise-floor table is arithmetic over live archive values, not a copy of the detector's verdicts. 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: api.llama.fi /summary/fees/eigencloud (the origin of the restated counter itself) HTTP 200; defillama.com /protocol/eigencloud (the /protocols family) HTTP 403; ethereum-rpc.publicnode.com (the deep_stats_eth_rpc family) HTTP 200; eth.blockscout.com token endpoint (the deep_stats_eth_blockscout family) HTTP 200; eth.blockscout.com address counters (the evm_blockscout family) HTTP 200; GitHub API Layr-Labs/eigenlayer-contracts (the github family) HTTP 200; CoinGecko EIGEN page (browser-verified origin; 403 here is its bot wall) HTTP 403; estate /v1/revisions?symbol=EIGEN HTTP 200; estate /v1/network/EIGEN HTTP 200.