Golem (GLM) — the network, measured

Generated 2026-10-17T04:43:15Z from live ClickHouse queries against this estate's ledger. Held inventory: 42,489 observations · 48 distinct series · 6 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-17 04:34:01 · 42,489/42,489 rows carry a verify_url. 47 series refreshed in the last 24h (781 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. CoinGecko reports circulating_supply = total_supply = 1,000,000,000 for GLM; both rows ship exactly as the reference publishes them.

Network telemetry — api2.stats.golem.network /v2/network/online/stats, as held

Read from Golem's own public stats service (keyless): providers online now, CPU cores, RAM (GB) and storage (GB) offered by the live provider set, and the GPUs gauge. Golem has no on-chain provider registry — a provider exists to the network only while its yagna daemon announces itself, so the online set is the supply set and these are not registration counts. The gauges are scrape-based and move inside a day (the online gauge ran 666→1181 in twelve hours on 2026-08-24); judge trends on the 30-day sparklines below, not one sample.

Supply-side demand — providers computing right now (golem_stats_util), as held

The demand half of the network: how many of the online providers are running a task right now, and the utilisation ratio the dedicated collector writes. That collector (added 2026-08-24) reads BOTH halves from Golem's own endpoints, and verified the two scalars range over the same population by counting computing_now=true records in the per-provider list — the cross-check that separates a real ratio from a numerator from one population over a denominator from another. "Providers online" alone is a supply chart with no demand in it; this ratio is the number an allocator underwrites.

Development signals — GitHub, as held

Repo-level counts for golemfactory/golem (stars, forks, watchers, open issues, days since last push) and the org-level public-repo count for golemfactory (274 repos). The two scopes are never mixed into one number here. The days-since-push figure is the monolith repo's own age — Golem's active development has moved to successor repos the collector does not follow; it is published as held with that caveat, not rescaled to flatter it.

Full metric inventory — 48 measured series, each with provenance

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

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 GLM. 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–4 hit the same upstream endpoints our collectors do (Golem's stats service is fully public; the CoinGecko and GitHub verify_urls point at browser pages, so the programmatic endpoints are given); command 5 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) Golem's own wide stats gauge (providers, cores, memory, storage, gpus) — keyless, as of 2026-10-17T04:43:15Z:
curl -s -H "User-Agent: kairos-check" "https://api2.stats.golem.network/v2/network/online/stats" | python3 -m json.tool
# 2) The demand gauge — providers computing right now:
# The demand gauge — Golem's own computing-now endpoint (the
# numerator of the utilisation ratio):
curl -s -H "User-Agent: kairos-check" "https://api2.stats.golem.network/v1/network/computing" | python3 -m json.tool
# 3) Market reference (CoinGecko public API):
# CoinGecko public markets API (the endpoint family our collector
# reads for the price/supply/cap rows):
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=golem" | python3 -m json.tool
# 4) Development signals (GitHub public API):
# GitHub public API (repo-level counts; org repos at /orgs/golemfactory):
curl -s "https://api.github.com/repos/golemfactory/golem" | python3 -m json.tool | head -30
# 5) This estate's public API row for GLM:
curl -s "https://kairossignal.com/v1/network/GLM" | 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_glm.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, PROVIDERS_ONLINE_UTIL to providers_online, and PROVIDERS_COMPUTING_UTIL to providers_computing (all question-verified). The remaining series are Golem-native network/market metrics with no cross-network concept; grading them would be fabrication, so they are labelled "glm-native (unmapped)". The online-set-is-the- supply-set construction, the scrape noise, the measured-zero GPUs gauge, and the repo-vs-org GitHub scopes are declared where they occur. Where a section has no data, it is absent — we do not publish zeros for gaps.