FLock.io (FLOCK) — the network, measured

Generated 2026-10-17T04:40:30Z from live ClickHouse queries against this estate's ledger. Held inventory: 38,107 observations · 46 distinct series · 6 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-17 03:51:53 · 38,107/38,107 rows carry a verify_url. 36 series refreshed in the last 24h (693 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number comes from

6 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. Core columns span the window from 2026-09-17 (CoinGecko generation one); the change/reference columns start 2026-09-17 in this archive (each metric's caveat in the full inventory states its own first-held row) 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.

Supply telemetry — first-party Base chain reads (base_rpc), as held

Read straight off Base mainnet via public JSON-RPC (mainnet.base.org) by the estate's evm first-party collector: the token contract's totalSupply() and the burn-sink balanceOf(0x…dEaD), both eth_call reads decimal-adjusted with the contract's own decimals() (read live at generation). A reverting or empty read is SKIPPED by the collector, never zero-filled; a genuinely-zero burn balance would be written as a measurement. This is first-party chain telemetry — no aggregator sits between the estate and the chain.

Token counters — Base Blockscout, as held

Holder count and cumulative transfer counter from Blockscout's public no-key v2 token API for the FLOCK Base contract. The collector polls ~once/day per token with a 24h fresh-pair dedupe, so rows are daily-resolution, not sub-hourly — shown as held, never interpolated.

Fees & revenue — DefiLlama protocol data, as held

Protocol-level fees and revenue from DefiLlama's public summary API. Fees rows verify against /summary/fees/flock.io; revenue rows against /summary/fees/flock.io?dataType=dailyRevenue — each row keeps its own verify_url. The small and near-zero values are the live upstream answers, published exactly as answered — the estate never smooths, rounds up, or hides an upstream number, and the estate's own Revenue grade reads these same values.

TVL & staking — DefiLlama /protocols, as held

Two different upstream fields from the DefiLlama protocol object for flock.io: tvl_usd and staking_tvl_usd. They are different objects — shown side by side, never summed or merged. tvl_usd answers 0 at generation — a live upstream answer (a measurement), not a gap, and staking_tvl_usd is held separately as upstream reports it. The rows' verify_url points at the defillama.com protocol page; the verify-commands section gives the programmatic api.llama.fi path.

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

Public activity for FLock's FLock-io/llm-loss-validator repo — the network's principal open training codebase. Repo-level metrics (stars, forks, open issues, watchers, days since push) verify against repos/FLock-io/llm-loss-validator; the public-repos count is an org-level metric and verifies against orgs/FLock-io. Each metric keeps its own verify_url — the page does not pretend they share one source object.

Full metric inventory — 46 measured series, each with provenance

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

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.

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 Base RPC calls are POST-only JSON-RPC (eth_call), and 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) The Base chain itself — keyless, POST-only, as of 2026-10-17T04:40:30Z:
#    (token totalSupply) curl -s -X POST -H 'Content-Type: application/json' -d '{"jsonrpc": "2.0", "id": 1, "method": "eth_call", "params": [{"to": "0x5ab3d4c385b400f3abb49e80de2faf6a88a7b691"}, "0x18160ddd"]}' https://mainnet.base.org   # raw hex: divide by 10**decimals() — or read https://basescan.org/token/0x5ab3d4c385b400f3abb49e80de2faf6a88a7b691
#    (burn-sink balanceOf(0x…dEaD)) curl -s -X POST -H 'Content-Type: application/json' -d '{"jsonrpc": "2.0", "id": 1, "method": "eth_call", "params": [{"to": "0x5ab3d4c385b400f3abb49e80de2faf6a88a7b691"}, "0x000000000000000000000000000000000000dead"]}' https://mainnet.base.org   # raw hex: divide by 10**decimals() — or read https://basescan.org/token/0x5ab3d4c385b400f3abb49e80de2faf6a88a7b691
# 2) Token counters (Blockscout public v2 API for the FLOCK Base contract):
curl -s -H "User-Agent: kairos-check" "https://base.blockscout.com/api/v2/tokens/0x5ab3d4c385b400f3abb49e80de2faf6a88a7b691" | python3 -m json.tool | head -30
# 3) Protocol fees (DefiLlama public API):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/flock.io" | python3 -m json.tool | head -30
# 3b) Protocol revenue (same family, revenue slice):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/flock.io?dataType=dailyRevenue" | python3 -m json.tool | head -30
# 3c) TVL & staking (programmatic protocol object — the rows' verify_url
#     points at the defillama.com page):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/protocol/flock.io" | python3 -m json.tool | head -40
# 4) 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=flock-2" | python3 -m json.tool
# 5) Dev velocity, repo-level (GitHub public API):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/FLock-io/llm-loss-validator" | python3 -m json.tool | head -20
# 5b) Dev velocity, org-level (GitHub public API):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/orgs/FLock-io" | python3 -m json.tool | head -20
# 6) This estate's public API row for FLOCK:
curl -s "https://kairossignal.com/v1/network/FLOCK" | 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_flock.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 FLOCK-native network/market telemetry with no cross-network concept; grading them would be fabrication, so they are labelled "flock-native (unmapped)". This estate holds no device count, GPU/compute inventory, or training-jobs telemetry for FLOCK — no such figure appears on this page and none is implied. The two supply families (the CoinGecko coin-page total_supply reference and the chain's own onchain_total_supply read) are different collectors with different stamps; they are shown side by side and never summed, merged, or reconciled. At generation the coin-page total_supply reference answers 1,000,000,000 tokens while the chain's own totalSupply() read answers 486,607,604.4357 tokens — different objects from different sources; both are published exactly as held and never reconciled. The burn metric is the 0x…dEaD sink balance only — an effective-supply input, never presented as "total burned", since projects can burn through other sinks. CoinGecko change/reference columns and the DefiLlama fees_1y/alltime + revenue family each start on their own first-held date in this archive (each metric's caveat states its own date) and are shown from their first held row, never back-filled. DefiLlama TVL and staking are different upstream fields held side by side; a zero there is the upstream answer, not a gap. 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: Base public RPC (eth_blockNumber POST) HTTP 200; Base Blockscout token API HTTP 403; DefiLlama fees API HTTP 200; DefiLlama revenue API HTTP 200; DefiLlama protocol API HTTP 200; CoinGecko markets API HTTP 429; CoinGecko browser coin page (expected 403) HTTP 403; GitHub FLock-io/llm-loss-validator HTTP 200; GitHub orgs/FLock-io HTTP 200; estate /v1/network/FLOCK HTTP 200.