Livepeer (LPT) — the network, measured

Generated 2026-10-12T04:48:31Z from live ClickHouse queries against this estate's ledger. Held inventory: 37,287 observations · 48 distinct series · 5 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-12 04:34:01 · 37,241/37,287 rows carry a verify_url. 44 series refreshed in the last 24h (765 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number comes from

5 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 high/low and ATH/ATL. These are the coin-page reference's own numbers — the estate does not model, smooth, or forward-fill them. The deeper change columns start 2026-08-22 in our archive and are shown from their first held row.

Network telemetry — Livepeer's own public APIs, as held

Two endpoint families live under first_party_api. The Livepeer Explorer usage API (explorer.livepeer.org/api/usage) flows fresh, hourly: active orchestrators, total delegators, 1-day fee-derived transcoding minutes, 1-day fee volume in USD, and stake participation. The leaderboard-serverless endpoints (aggregated_stats, regions) are ARCHIVED in this estate — orchestrators_scored last returned 2026-08-21T17:34Z and test_regions is a single row from 2026-08-09 — and are shown exactly as held, never re-derived, never presented as flowing.

Fees & revenue — DefiLlama protocol data, as held

Protocol-level fees and revenue from DefiLlama's public summary API. Fees rows verify against /summary/fees/livepeer; revenue rows against /summary/fees/livepeer?dataType=dailyRevenue — each row keeps its own verify_url. The 1y and all-time windows are archived on a sparser generation (123 rows at generation) than the 24h/7d/30d windows (130 rows) — shown as held, the archive's own shape, not smoothed.

On-chain — Arbitrum RPC, live

LPT's orchestration chain is Arbitrum; our chain-RPC collector reads arb1.arbitrum.io/rpc directly. block_height and gas_price_gwei flow fresh (17 rows each at generation). These are chain-health reads only: this estate holds no on-chain LPT supply series (no eth_call totalSupply read), and nothing here implies one. A buyer can re-derive block_height with the eth_blockNumber command in the verify section below.

Dev velocity — GitHub, as held (repo and org levels)

Public repo activity for livepeer/go-livepeer, the network's core node implementation. Five series are repo-level and verify against api.github.com/repos/livepeer/go-livepeer; dev_public_repos is an org-level count and verifies against api.github.com/orgs/livepeer. Each row keeps its own verify_url; the two levels are never merged.

Full metric inventory — 44 measured series, each with provenance

Every series held for LPT 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 — 0 backward revision(s) recorded for LPT

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 ledger query ran during generation and returned 0 rows for LPT. Zero here is the live query result, not a gap — the ledger itself is at /v1/revisions.

Verify any cell yourself — the exact commands

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

# 1) Livepeer Explorer usage API — keyless, as of 2026-10-12T04:48:31Z:
curl -s -H "User-Agent: kairos-check" "https://explorer.livepeer.org/api/protocol-day-data" | python3 -m json.tool
# 1b) Orchestrator leaderboard (the orchestrators_scored source):
# Orchestrator leaderboard (aggregated_stats) — the endpoint
# our orchestrators_scored series reads:
curl -s -H "User-Agent: kairos-check" "https://leaderboard-serverless.vercel.app/api/aggregated_stats" | python3 -m json.tool | head -30
# 2) Protocol fees (DefiLlama public API):
# Protocol fees (the endpoint family our collector reads):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/livepeer" | python3 -m json.tool | head -30
# 2b) Protocol revenue (same family, revenue slice):
# Protocol revenue (same family, revenue slice):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/livepeer?dataType=dailyRevenue" | python3 -m json.tool | head -30
# 3) Market reference (CoinGecko public API):
# 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=livepeer" | python3 -m json.tool
# 4) Dev velocity (GitHub public API):
# GitHub public API — the repo our repo-level dev series read
# (org-level dev_public_repos verifies against /orgs/livepeer):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/livepeer/go-livepeer" | python3 -m json.tool | head -20
# 5) Live on-chain (Arbitrum public RPC — re-derive block_height):
# Live on-chain (Arbitrum public RPC — Livepeer's orchestration
# chain). eth_blockNumber re-derives block_height directly:
curl -s -X POST "https://arb1.arbitrum.io/rpc" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}' | python3 -m json.tool
# 6) This estate's public API row for LPT:
curl -s "https://kairossignal.com/v1/network/LPT" | 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_lpt.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 and block_height to chain_height (both question-verified). The remaining series are Livepeer-native network/market metrics with no cross-network concept; grading them would be fabrication, so they are labelled "lpt-native (unmapped)". Collection generations (fresh-flowing Explorer vs archived leaderboard endpoints) are shown side by side as held, never summed, merged, or reconciled. The on-chain block is chain health only — this estate holds no on-chain LPT supply series. DefiLlama fees and revenue rows carry different verify_urls (fees vs ?dataType=dailyRevenue) and each keeps its own. GitHub dev series are split repo-level vs org-level and each row keeps its own verify_url. 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: Livepeer Explorer usage API HTTP 502; Leaderboard aggregated_stats API HTTP 200; Leaderboard regions API HTTP 200; DefiLlama fees API HTTP 200; DefiLlama revenue API HTTP 200; CoinGecko markets API HTTP 200; GitHub livepeer/go-livepeer HTTP 200; GitHub orgs/livepeer HTTP 200; Arbitrum RPC HTTP 200; estate /v1/network/LPT HTTP 200.