Flux (FLUX) — the network, measured

Generated 2026-10-12T04:42:06Z from live ClickHouse queries against this estate's ledger. Held inventory: 60,645 observations · 72 distinct series · 5 upstream sources · first row 2026-08-09 23:08:53 · newest row 2026-10-12 04:26:04 · 60,645/60,645 rows carry a verify_url. 72 series refreshed in the last 24h (1,491 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.

First-party utilization — Flux's own endpoints, read by this estate

What the benchmarked Flux fleet totals (cores, memory, storage) and what the network's deployed global apps have allocated, read directly from Flux's public APIs (api.runonflux.io, stats.runonflux.io) by this estate's first-party collector. The *_ALLOCATION_PCT rows are derived at read time (allocated ÷ fleet total); both operand series are on this page, so the division is reproducible by any buyer. Fresh rows in every one of the last 10+ days.

Node counts — three upstreams, three denominators, declared

Flux's own endpoints disagree about "how many nodes", because each counts a different thing: the deterministic daemon list (viewdeterministiczelnodelist) reports the chain-registered node set with per-tier splits (cumulus/nimbus/stratus); getzelnodecount reports stable/ipv4/ipv6/onion confirmations; and stats.runonflux.io's fluxinfo projection reports "arcane" (5,839) and "reporting" (6,481) denominators. They are never summed, averaged, or reconciled into a single invented number — each row is shown as held, with its own provenance. Only node_count (the deterministic daemon-list total) is graded cross-network (nodes_total, unit-verified).

Market reference — CoinGecko coin page, as held

Market-data reference rows: price, supply, capitalisation, and the published change columns. These are the coin-page reference's own numbers — the estate does not model, smooth, or forward-fill them. Flux's CoinGecko coin id is zelcash (the historical ZelCash lineage — visible in every verify_url below and stated, not hidden).

Development velocity — GitHub org, as held

Repository and org telemetry from the public GitHub API: stars, forks, watchers, open issues, public repos, and days since last push on the main repo. Read as-is; no smoothing.

Full metric inventory — 72 measured series, each with provenance

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

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 FLUX. 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; command 6 hits the named market reference; command 7 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) Global app specifications (app allocations, fleet read) — keyless, as of 2026-10-12T04:42:06Z:
curl -s -H "User-Agent: kairos-check" "https://api.runonflux.io/apps/globalappsspecifications" | python3 -m json.tool | head -40
# 2) Benchmarked fleet totals (stats projection benchmark.bench):
curl -s -H "User-Agent: kairos-check" "https://stats.runonflux.io/fluxinfo?projection=benchmark.bench" | python3 -m json.tool | head -40
# 3) Deterministic node list (the node_count series):
curl -s -H "User-Agent: kairos-check" "https://api.runonflux.io/daemon/viewdeterministiczelnodelist" | python3 -m json.tool | head -30
# 4) Stats projection (arcane / reporting node counts):
curl -s -H "User-Agent: kairos-check" "https://stats.runonflux.io/fluxinfo?projection=flux" | python3 -m json.tool | head -40
# 5) Node confirmations by address family:
# getzelnodecount was not re-probed during this build (row provenance carried from the ledger):
curl -s -H "User-Agent: kairos-check" "https://api.runonflux.io/daemon/viewdeterministiczelnodelist" | python3 -m json.tool
# 6) Market reference (CoinGecko public API):
# CoinGecko public markets API (the endpoint family our collector
# reads for the price/supply/cap rows; not re-probed during this
# build):
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=zelcash" | python3 -m json.tool
# 7) This estate's public API row for FLUX:
curl -s "https://kairossignal.com/v1/network/FLUX" | 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_flux.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: APP_CORES_ALLOCATED maps to compute_cores_in_use, NODE_CORES_TOTAL to compute_cores_total, APP_MEMORY_BYTES_ALLOCATED to memory_bytes_in_use, NODE_MEMORY_BYTES_TOTAL to memory_bytes_total, APP_STORAGE_BYTES_ALLOCATED to storage_bytes_in_use, NODE_STORAGE_BYTES_TOTAL to storage_bytes_total (all question-verified); node_count maps to nodes_total (unit-verified); total_supply maps to token_supply_total (question-verified). The remaining series are Flux-native node/utilization/market metrics with no cross-network concept; grading them has no basis in the held data, so they are labelled "flux-native (unmapped)". The three node count denominators are different upstream measurements and are never reconciled into one number. The allocation percentages are collector-side derived values published as emitted, with both operand series shown. Where a section has no data, it is absent — we do not publish zeros for gaps.