GFI (Goldfinch) — the network, measured

Generated 2026-10-12T04:42:54Z from live ClickHouse queries against this estate's ledger. Held inventory: 32,973 observations · 36 distinct series · 5 upstream sources · first row 2026-08-17 23:01:56 · newest row 2026-10-12 03:51:55 · 32,973/32,973 rows carry a verify_url. 36 series refreshed in the last 24h (682 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 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/max supply rows are different quantities (circulating vs total vs cap) and are never netted against each other.

Protocol fees & revenue — DefiLlama fees dimension, as held

DefiLlama's fees dimension for Goldfinch (api.llama.fi /summary/fees/goldfinch). These are upstream's own published window figures for the protocol — the estate holds and shows them as reported, with no re-derivation. The fees_24h/7d/30d/1y/alltime and revenue_24h/30d series are different windows of that same upstream publication — the fees_* and revenue_* pairs carry the same figures at generation (Goldfinch's DefiLlama methodology makes revenue equal fees) and are never netted, differenced, or merged with each other, with the TVL family, or with any market row. fees_24h_usd and revenue_24h_usd read 0 at generation: that zero is the live row's value (upstream answered 0 for the 24h window) while the longer windows in the same family are non-zero — the window value is published exactly as held, and a zero window is a measurement, not a gap. Cumulative counters are published raw — never differenced into rates.

Protocol TVL — DefiLlama /protocols, as held

The DefiLlama /protocols family for Goldfinch: tvl_usd, the protocol's total value locked as the endpoint reports it. This is a DIFFERENT DefiLlama endpoint (and a different quantity) from the fees/revenue dimension above — value locked is not a fee measure — and it keeps its own verify_url (defillama.com/protocol/goldfinch). Never combined with the fees rows or with any market row.

Chain-side telemetry — Ethereum mainnet, token 0xdab396ccf3d84cf2d07c4454e10c8a6f5b008d2b, as held

Two chain-side families read this token contract directly on Ethereum mainnet: the estate's ethereum_rpc family (on-chain total supply and the burn-address balance) and ethereum_blockscout (holder count and cumulative transfers from eth.blockscout.com's public API — each row's verify_url re-executes the same keyless GET the collector ran). These are the raw on-chain quantities for the contract — the strongest provenance class on this page after nothing-first-party is declared: the estate holds NO first-party self-telemetry family for GFI (Goldfinch publishes no keyless stats API the estate reads; has_public_stats_api = 0 in the catalog), and no such section exists here — absence, not zero. The on-chain supply is a separate measurement from the CoinGecko total/max supply references above; at generation all three read the same figure, shown side by side, never merged. Balances and counters are published raw — never differenced into rates.

Full metric inventory — 36 measured series, each with provenance

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

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 GFI. 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–3 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 goldfinch); command 4 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) Market reference (CoinGecko public API — the coingecko.com browser
#    coin page 403s plain curl, so the programmatic endpoint is given):
# 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
# (id: goldfinch):
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=goldfinch" | python3 -m json.tool
# 1b) 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/goldfinch"
# 2) Protocol fees (DefiLlama public API, as upstream publishes them):
curl -s "https://api.llama.fi/summary/fees/goldfinch" | python3 -c "import json,sys; d=json.load(sys.stdin); print(d.get('total24h'), d.get('total30d'), d.get('totalAllTime'))"
# 2b) Protocol revenue (DefiLlama dailyRevenue):
curl -s "https://api.llama.fi/summary/fees/goldfinch?dataType=dailyRevenue" | python3 -c "import json,sys; d=json.load(sys.stdin); print(d.get('total24h'), d.get('total30d'))"
# 2c) Protocol TVL (DefiLlama protocols API — different endpoint family):
# DefiLlama protocols API (protocol TVL — a different
# endpoint family from the fees summary above):
curl -s "https://api.llama.fi/protocol/goldfinch" | python3 -c "import json,sys; d=json.load(sys.stdin); print(d.get('name'), list(d.get('currentChainTvls', {}).items())[:8])"
# 3) Chain-side supply (token contract on Ethereum mainnet):
# Chain-side supply read (token contract on Ethereum
# mainnet; the HTML page shows the supply the row holds):
curl -s -o /dev/null -w "%{http_code}\n" "https://etherscan.io/token/0xdab396ccf3d84cf2d07c4454e10c8a6f5b008d2b"
# 3b) Chain-side token endpoint (Blockscout keyless JSON):
# Blockscout token endpoint (keyless JSON — holders & transfers
# counters the estate's ethereum_blockscout collector reads):
curl -s "https://eth.blockscout.com/api/v2/tokens/0xdab396ccf3d84cf2d07c4454e10c8a6f5b008d2b" | python3 -m json.tool | head -20
# 3c) Chain-side holders/transfers counters (Blockscout keyless JSON):
curl -s "https://eth.blockscout.com/api/v2/tokens/0xdab396ccf3d84cf2d07c4454e10c8a6f5b008d2b/counters" | python3 -m json.tool
# 4) This estate's public API row for GFI:
curl -s "https://kairossignal.com/v1/network/GFI" | 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_gfi.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 GFI-native market/chain metrics with no cross-network concept; grading them would be fabrication, so they are labelled "gfi-native (unmapped)". No first-party family: the catalog lists has_public_stats_api = 0 for Goldfinch, the ledger holds zero first_party_api rows for this symbol, and no self-reported-telemetry section exists on this page — that is absence, not zero. No github family: the ledger holds zero github rows for this symbol; none are fabricated. The chain-side family reads token 0xdab396ccf3d84cf2d07c4454e10c8a6f5b008d2b on Ethereum mainnet via two independent families (ethereum_rpc, ethereum_blockscout); the on-chain total supply is a separate measurement from the CoinGecko total/max supply references — at generation all three read the same figure, shown side by side, never merged. The DefiLlama fees and revenue rows are upstream's own published window figures and are labelled as such wherever they appear; the fees_*/revenue_* pairs carry the same figures at generation and are never netted or merged, and the fees_24h/revenue_24h zeros at generation are the live rows' values, not gaps. The DefiLlama TVL row is a different endpoint and a different quantity from the fees family and is never combined with it. Chain-side balances and counters are published raw, never differenced into rates. The estate grades are published exactly as the engines served them, 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: CoinGecko markets API (goldfinch) HTTP 200; DefiLlama fees summary (goldfinch) HTTP 200; DefiLlama dailyRevenue summary (goldfinch) HTTP 200; DefiLlama protocols API (goldfinch) HTTP 200; Blockscout token endpoint (0xdab3...d2b) HTTP 200; Blockscout token counters (0xdab3...d2b) HTTP 200; Etherscan token page (0xdab3...d2b) HTTP 200; estate /v1/network/GFI HTTP 200.