Walrus (WAL) — the network, measured

Generated 2026-10-17T05:07:33Z from live ClickHouse queries against this estate's ledger. Held inventory: 38,269 observations · 37 distinct series · 4 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-17 04:58:01 · 38,269/38,269 rows carry a verify_url. 36 series refreshed in the last 24h (780 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number comes from

4 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 change columns / rank / ATH-ATL / high-low series start later in the archive than the price rows (each metric's caveat in the full inventory states its own first-held row) and are shown from their first held row. The circulating and total supply rows are different quantities (circulating vs total) and are never netted against each other; the estate holds no Sui-chain supply read for WAL, so there is no chain row to merge — absence, not zero.

Fees & revenue — DefiLlama protocol data, as held

Protocol-level fees and revenue from DefiLlama's public summary API for walrus-protocol. Fees rows verify against /summary/fees/walrus-protocol; revenue rows against /summary/fees/walrus-protocol?dataType=dailyRevenue — each row keeps its own verify_url. All windows read non-zero and flowing at generation. Revenue is DefiLlama's dailyRevenue slice (fees kept by the protocol after contributor payments) — a different measurement from fees, never netted against it on this page, even where their latest values read alike.

Network telemetry — first-party reads, as held

First-party network telemetry rows held for this symbol.

Full metric inventory — 37 measured series, each with provenance

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

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 WAL. 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–2 hit the same upstream endpoints our collectors do (the coingecko.com browser coin page 403s plain curl, so the programmatic markets endpoint is given, id walrus-2); command 3 hits this estate's public API, where every row carries the same source / as_of / verify_url fields. One polite call per endpoint, no hammering.

# 1) Protocol fees (DefiLlama public API, walrus-protocol) — as of 2026-10-17T05:07:33Z:
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/walrus-protocol" | python3 -c "import json,sys; d=json.load(sys.stdin); print('total24h', d.get('total24h')); print('total30d', d.get('total30d')); print('totalAllTime', d.get('totalAllTime'))"
# 1b) Protocol revenue (same family, revenue slice):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/walrus-protocol?dataType=dailyRevenue" | python3 -c "import json,sys; d=json.load(sys.stdin); print('total24h', d.get('total24h'))"
# 2) Market reference (CoinGecko public API, id walrus-2):
# 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
# (note the id: walrus-2; the bare "walrus" id is a different coin):
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=walrus-2" | python3 -m json.tool
# 2b) Human-view check of the verify_url target (the browser coin page 403s plain curl — that is the documented 403, the programmatic command above is the verification path):
curl -s -o /dev/null -w "%{http_code}\n" "https://www.coingecko.com/en/coins/walrus-2"
# 3) This estate's public API row for WAL:
curl -s "https://kairossignal.com/v1/network/WAL" | 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_wal.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 WAL-native market/telemetry metrics with no cross-network concept; grading them would be fabrication, so they are labelled "wal-native (unmapped)". The two DefiLlama slices are declared, not merged: fees (all windows) and revenue (dataType=dailyRevenue) are different measurements, each with its own verify_url, never netted against each other even where their latest values read alike; the 1y/all-time windows and both revenue windows ride a sparser collector generation (first held 2026-08-23) and are shown from first held row, never back-filled. The CoinGecko circulating and total supply rows are different quantities (circulating vs total) and are never netted; the estate holds no Sui-chain supply read for WAL, so no chain-vs-reference reconciliation exists or is implied — absence, not zero. The estate holds no DefiLlama TVL-bucket, no GitHub, and no first-party rows — those sections are absent rather than zero-filled, and the queries rerun at every regeneration. Estate grades, where the engines serve any, are published exactly as served, unflattering parts included; they are the engines' own outputs, not derived from any series on this page. 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: DefiLlama fees API HTTP 200; DefiLlama revenue API HTTP 200; CoinGecko markets API (walrus-2) HTTP 200; estate /v1/network/WAL HTTP 200.