Filecoin (FIL) — the network, measured

Generated 2026-09-02T14:50:22Z from live ClickHouse queries against this estate's ledger. Held inventory: 9,204 observations · 51 distinct series · 8 upstream sources · first row 2026-08-09 23:28:06 · newest row 2026-09-02 14:34:01 · 9,204/9,204 rows carry a verify_url. 40 series refreshed in the last 24h (912 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, 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. All 23 market series start 2026-08-22 in this archive and are shown from their first held row. The coingecko.com browser coin page 403s plain curl — verify through the programmatic markets endpoint given in the commands section.

Storage power & verified-deal utilisation — filecoin_power_util (rpc/v1), as held

The estate's Filecoin utilisation collector reads the same official Lotus RPC (api.node.glif.io/rpc/v1, a different endpoint path from the first-party family above — separate rows, separate verify_urls, never merged) and cross-checks it against an independent indexer (filfox.info) before writing: if the two disagree beyond tolerance, nothing is written. The derived numerator below is arithmetic on two published integers, not an estimate — since FIP-0034, QAP = RBP + 9 × (raw bytes carrying verified deals), so VERIFIED_DEAL_BYTES = (QAP − RBP) / 9, and VERIFIED_DEAL_UTILISATION_PCT is that numerator over sealed bytes. What it is not: unverified deals are invisible (1x multiplier) so the figure is a lower bound; every replica counts separately so it is occupied capacity, not distinct data; FIL+ datacap quality is not audited; and the multiplier is space-time weighted inside sector lifetimes. The native names say VERIFIED_DEAL — never “storage used”. QUALITY_ADJ_BYTES is a consensus weight, not storage, and is never divided by raw byte power into a “utilisation” ratio.

Chain telemetry — first-party Lotus RPC (rpc/v0), as held

Read from the official Filecoin Lotus JSON-RPC (api.node.glif.io/rpc/v0) by the estate's first-party collector: the chain head epoch and the network's storage power. StateMinerPower's miner argument only affects the per-miner half of the answer, which is discarded — the published numbers are the network's TotalPower. chain_epoch and both power series flow fresh hourly; the two power quantities are consensus quantities in byte units and are never presented as a used/total pair.

Single-observation seed metrics — held as read, never refreshed

Four series exist as exactly one observation each, stamped 2026-08-09T23:53:17Z by the estate's original first-party seeding run. They are published exactly as held — with the single-read caveat attached, never presented as flowing, and never back-filled or re-derived. network_version is checkable against the chain at origin via StateNetworkVersion (the commands section ships the exact call).

Fees & revenue — DefiLlama protocol data, as held

Protocol-level fees and revenue from DefiLlama's public summary API. Fees rows verify against /summary/fees/filecoin; revenue rows against /summary/fees/filecoin?dataType=dailyRevenue — each row keeps its own verify_url. Values are published exactly as upstream answers them, zero included; the history table shows each series' own shape.

On-chain activity — DefiLlama chain family, as held

Three different DefiLlama endpoints, three different verify paths, never merged into one “DefiLlama” object: DEX volume verifies against /overview/dexs/filecoin; chain TVL against /v2/chains; stablecoin supply against stablecoins.llama.fi/stablecoinchains. Each metric below carries its own origin link.

Dev velocity — GitHub, as held (repo + org provenance)

Public activity for Filecoin's filecoin-project/lotus repo — the protocol's principal node implementation. Repo-level metrics (stars, forks, open issues, watchers, days since push) verify against repos/filecoin-project/lotus; the public-repos count is an org-level metric and verifies against orgs/filecoin-project. Each metric keeps its own verify_url — the page does not pretend they share one source object.

Full metric inventory — 51 measured series, each with provenance

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

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 FIL. Zero here is the live query result, not a gap — the ledger itself is at /v1/revisions.

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

Served by /v1/network/FIL — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth. The revenue grade reflects what the engines read from the held fee/revenue series; it is published exactly as computed.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–4 hit the same upstream endpoints our collectors do — the glif calls are JSON-RPC POSTs (the Lotus API is POST-only, so plain GETs will not work). The coingecko.com browser coin page 403s plain curl, so the programmatic markets endpoint is given. Command 5 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) The network's own Lotus JSON-RPC — keyless, as of 2026-09-02T14:50:22Z:
#    (storage power: StateMinerPower TotalPower) curl -s -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"Filecoin.StateMinerPower","params":["f01000", null],"id":1}' https://api.node.glif.io/rpc/v1 | python3 -c "import sys,json; print(json.load(sys.stdin)['result']['TotalPower'])"
#    (chain head height) curl -s -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"Filecoin.ChainHead","params":[],"id":1}' https://api.node.glif.io/rpc/v0 | python3 -c "import sys,json; print(json.load(sys.stdin)['result']['Height'])"
#    (network version — live check of the held network_version=28) curl -s -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"Filecoin.StateNetworkVersion","params":[null],"id":1}' https://api.node.glif.io/rpc/v1 | python3 -c "import sys,json; print(json.load(sys.stdin)['result'])"
# 2) Protocol fees (DefiLlama public API):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/filecoin" | python3 -m json.tool | head -30
# 2b) Protocol revenue (same family, revenue slice):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/filecoin?dataType=dailyRevenue" | python3 -m json.tool | head -30
# 2c) DEX volume (DefiLlama overview/dexs):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/overview/dexs/filecoin" | python3 -m json.tool | head -20
# 2d) Chain TVL (DefiLlama v2/chains):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/v2/chains" | python3 -c "import sys,json; print([c for c in json.load(sys.stdin) if c.get('name')=='Filecoin'][:1])"
# 2e) Stablecoin supply (stablecoins.llama.fi):
curl -s -H "User-Agent: kairos-check" "https://stablecoins.llama.fi/stablecoinchains" | python3 -c "import sys,json; print([c for c in json.load(sys.stdin) if c.get('name')=='Filecoin'][:1])"
# 3) Market reference (CoinGecko public API — 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=filecoin" | python3 -m json.tool
# 4) Dev velocity, repo-level (GitHub public API):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/filecoin-project/lotus" | python3 -m json.tool | head -20
# 4b) Dev velocity, org-level (GitHub public API):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/orgs/filecoin-project" | python3 -m json.tool | head -20
# 5) This estate's public API row for FIL:
curl -s "https://kairossignal.com/v1/network/FIL" | 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_fil.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); COMMITTED_BYTES_TOTAL maps to storage_bytes_total and VERIFIED_DEAL_BYTES to storage_bytes_in_use (both question-verified, with the estate's own FIL-specific caveats quoted on the rows — the numerator is a derived proxy, the denominator is sealed-and-proven bytes, and neither is a “storage used” measurement). The remaining series are FIL-native network/market telemetry with no cross-network concept; grading them would be fabrication, so they are labelled "fil-native (unmapped)". The two storage-power families (first-party rpc/v0 and filecoin_power_util rpc/v1) are different collectors with different verify_urls reading the same chain; they are shown side by side and never summed, merged, or reconciled, and QUALITY_ADJ_BYTES is never divided by raw byte power into a ratio. The four single-observation seed metrics are shown as held from their 2026-08-09 stamp. CoinGecko series start 2026-08-22 in this archive and are shown from their first held row, never back-filled. DefiLlama fees, revenue, DEX, TVL and stablecoin rows carry different verify_urls and each keeps its own. GitHub repo-level and org-level dev metrics keep their separate verify targets. 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: glif Lotus RPC v0 (ChainHead POST) HTTP 200; glif Lotus RPC v1 (StateMinerPower POST) HTTP 200; DefiLlama fees API HTTP 200; DefiLlama revenue API HTTP 200; DefiLlama dexs API HTTP 200; DefiLlama v2/chains API HTTP 200; DefiLlama stablecoinchains API HTTP 200; CoinGecko markets API HTTP 200; GitHub filecoin-project/lotus HTTP 200; GitHub orgs/filecoin-project HTTP 200; estate /v1/network/FIL HTTP 200.