EIGEN (EigenCloud, prev. EigenLayer) — the network, measured

Generated 2026-10-12T04:39:34Z from live ClickHouse queries against this estate's ledger. Held inventory: 37,640 observations · 53 distinct series · 8 upstream sources · first row 2026-08-09 23:27:47 · newest row 2026-10-12 04:18:01 · 37,640/37,640 rows carry a verify_url. 52 series refreshed in the last 24h (794 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number comes from

8 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: 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 CoinGecko circulating_supply / total_supply rows and the chain reads are separate measurements from separate endpoints, shown side by side and never merged.

Fees & revenue — DefiLlama, as held

Protocol fee and revenue rollups for the EigenCloud economy, from api.llama.fi/summary/fees/eigencloud (fees) and its ?dataType=dailyRevenue sibling (revenue). The fee rows flow at every window the endpoint publishes; the revenue rows are withdrawn — see the note below. EIGEN's fee accrual is the EigenCloud services market, not staking yield.

TVL — DefiLlama protocol page, as held

The DefiLlama protocol page's two TVL answers, published exactly as read: both are live at generation and are different dataTypes — they are never summed.

On-chain reads — Ethereum (RPC + Blockscout), as held

Chain reads for the EIGEN token (0xec53bf91…): total supply, holder count, transfer count, and the token contract's gas/transaction counters. Dual-source series (publicnode RPC, deep_stats_eth_blockscout, evm_blockscout) are separate rows with their own stamps — the day-ago gaps are shown, not smoothed. At generation the top-holder read is 221,325,352.2671 tokens — 11.95% of the chain total-supply read (1,851,562,795.9688), a live ratio of the two held values, not a new source.

Dev velocity — GitHub, as held

Public repo activity for EIGEN: the Layr-Labs/eigenlayer-contracts repo for stars, forks, issues, watchers and days-since-push, plus the org-level public-repo count. Daily snapshots; each row keeps its own as-of stamp.

Full metric inventory — 53 measured series, each with provenance

Every series held for EIGEN 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.

Revision ledger — 1 recorded revision row(s) for EIGEN

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 table below is the RAW ledger content, so it matches the count in the heading exactly.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–6 hit the same upstream endpoints our collectors do (the coingecko.com and defillama.com browser pages 403 plain curl, so the programmatic API endpoints are given); command 7 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) Market reference (CoinGecko public API) — keyless, as of 2026-10-12T04:39:34Z:
# CoinGecko public markets API (the endpoint family our collector
# reads for the price/supply/cap rows) — the coingecko.com browser
# coin page 403s plain curl, so the programmatic endpoint is given:
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=eigenlayer" | python3 -m json.tool
# 2) Fees & revenue (DefiLlama public API):
# DefiLlama fees+revenue rollup — the exact endpoint family the
# fees/revenue series read (the defillama.com browser pages 403
# plain curl; api.llama.fi is the programmatic interface):
curl -s "https://api.llama.fi/summary/fees/eigencloud" | python3 -m json.tool | head -40
# 3) TVL (DefiLlama protocol API):
# DefiLlama protocol TVL (tvl_usd / staking_tvl_usd rows):
curl -s "https://api.llama.fi/protocol/eigencloud" | python3 -m json.tool | head -30
# 4) On-chain supply (Ethereum public RPC, eth_call):
# On-chain supply (Ethereum public RPC — eth_call totalSupply on
# the EIGEN token contract; this is the deep_stats_eth_rpc path):
curl -s -X POST "https://ethereum-rpc.publicnode.com" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xec53bf9167f50cdeb3ae105f56099aaab9061f83","data":"0x18160ddd"},"latest"]}' | python3 -m json.tool
# 5) Token stats (Blockscout public API):
# Blockscout token stats (holders_count, token_transfers_total,
# evm_blockscout supply read — the exact endpoints the rows cite):
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0xec53bf9167f50cdeb3ae105f56099aaab9061f83" | python3 -m json.tool | head -25
# 6) Dev velocity (GitHub public API):
# GitHub public API — the repo our dev-velocity series reads:
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/Layr-Labs/eigenlayer-contracts" | python3 -m json.tool | head -20
# 7) This estate's public API row for EIGEN:
curl -s "https://kairossignal.com/v1/network/EIGEN" | 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_eigen.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 EIGEN-native chain/market/fee metrics with no cross-network concept; grading them would be fabrication, so they are labelled "eigen-native (unmapped)". Dual-source series (chain supply, holders, transfers) are published as separate rows with their own stamps, never merged; the day-ago gaps between the two Blockscout generations are stated, not smoothed. The three supply reads (RPC chain, Blockscout, CoinGecko) are published side by side, never merged; the three supply reads are published side by side, never merged (two agree exactly; the CoinGecko reference sits +0.020% away at generation). The revenue series are withdrawn (2026-09-25), stated here rather than silently dropped: DefiLlama's EigenLayer adapter (dimension-adapters fees/eigenlayer.ts) returns dailyRevenue: 0 unconditionally, so every revenue row stored since 2026-08-23 was a code constant rather than a reading, and the adapter cannot observe the protocol-fee mechanism EigenLayer's live RewardsCoordinator has carried since 2026-03-12 (quality incident defillama_hardcoded_zero_revenue_20260925); nothing is re-allocated from the fees rows. tvl_usd and staking_tvl_usd are different DefiLlama dataTypes, published side by side and never summed. The top-holder percentage is a live ratio of two held reads, labelled as such. Where a section has no data, it is absent — we do not publish zeros for gaps. Upstream probes run serially by this generator immediately before rendering: CoinGecko markets API HTTP 200; DefiLlama fees API HTTP 200; DefiLlama protocol API HTTP 200; Publicnode Ethereum RPC HTTP 200; Blockscout token API HTTP 200; GitHub Layr-Labs/eigenlayer-contracts HTTP 200; estate /v1/network/EIGEN HTTP 200.