Helium (HNT) — the network, measured

Generated 2026-09-02T14:29:17Z from live ClickHouse queries against this estate's ledger. Held inventory: 9,369 observations · 45 distinct series · 6 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 14:03:01 · 9,369/9,369 rows carry a verify_url. 36 series refreshed in the last 24h (865 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. The deeper change columns start 2026-08-22 in our archive and are shown from their first held row.

Network telemetry — the Helium entities API, as held (per subnetwork)

Read from the network's own public endpoint (entities.nft.helium.io/v2/hotspots/pagination-metadata): the IoT (LoRaWAN) subnetwork's gateway count and the Mobile (5G CBRS) subnetwork's hotspot count, both fresh-flowing at generation (560 rows each). The two subnetworks are different measurements of different hardware fleets — this estate never sums them into one "total hotspots" figure, and never reconciles them with the all-network total held separately below.

All-network hotspot total — helium_entity_api, as held

A second measurement family from the same endpoint's IoT metadata: the all-network hotspot total and the pagination-page count the read returned. Kept distinct from the per-subnetwork first-party series above — different semantics, different rows, each with its own provenance.

Fees & revenue — DefiLlama protocol data, as held

Protocol-level fees and revenue from DefiLlama's public summary API. Fees rows verify against /summary/fees/helium-network; revenue rows against /summary/fees/helium-network?dataType=dailyRevenue — each row keeps its own verify_url. The latest 24h/7d/30d fee values upstream are currently 0 as DefiLlama reports them; that is the live upstream answer and it is published exactly as answered (the history table shows the series was non-zero before). The 1y and all-time windows are archived on a sparser generation (123 rows at generation) than the 24h/7d/30d windows (180 rows) — shown as held, the archive's own shape, not smoothed.

On-chain state — Solana (post-migration), as held

HNT has lived on Solana since the 2023 migration; the estate's chain-RPC collector reads Solana state for this network. onchain_total_supply flows fresh daily. The holder-concentration series (top 1/10/20 share) were last stamped 2026-08-28 and are shown as held — never re-derived or presented as flowing. Holder rows verify against the Solscan token page because the RPC collector's upstream publishes no keyless JSON for them.

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

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

Full metric inventory — 45 measured series, each with provenance

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

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

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

Served by /v1/network/HNT — 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–5 hit the same upstream endpoints our collectors do (the coingecko.com browser coin page 403s plain curl, so the programmatic markets endpoint is given; Solscan serves a page, not keyless JSON, so its command prints the HTTP status); command 6 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) The network's own entities API — keyless, as of 2026-09-02T14:29:17Z:
#    (IoT subnetwork) curl -s -H "User-Agent: kairos-check" "https://entities.nft.helium.io/v2/hotspots/pagination-metadata?subnetwork=iot" | python3 -m json.tool
#    (Mobile subnetwork) curl -s -H "User-Agent: kairos-check" "https://entities.nft.helium.io/v2/hotspots/pagination-metadata?subnetwork=mobile" | python3 -m json.tool
# 2) Protocol fees (DefiLlama public API):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/helium-network" | 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/helium-network?dataType=dailyRevenue" | python3 -m json.tool | head -30
# 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=helium" | python3 -m json.tool
# 4) Dev velocity, repo-level (GitHub public API):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/helium/helium-program-library" | 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/helium" | python3 -m json.tool | head -20
# 5) On-chain holder reference (Solscan token page — page probe, prints HTTP code):
curl -s -H "User-Agent: kairos-check" "https://solscan.io/token/hntyVP6YFm1Hg25TN9WGLqM12b8TQmcknKrdu1oxWux" -o /dev/null -w "%{http_code}"
# 6) This estate's public API row for HNT:
curl -s "https://kairossignal.com/v1/network/HNT" | 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_hnt.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); iot_hotspots and mobile_hotspots both map to gateways_total (unit-verified) — two distinct subnetwork measurements under one canonical concept, which is why they are never summed. The remaining series are HNT-native network/market/on-chain metrics with no cross-network concept; grading them would be fabrication, so they are labelled "hnt-native (unmapped)". Collection generations (fresh-flowing vs last stamped 2026-08-28 holder series) are shown side by side as held, never summed, merged, or reconciled. The CoinGecko change-column generation two (from 2026-08-22) is shown from its first held row, never back-filled. DefiLlama fees and revenue rows carry different verify_urls (fees vs ?dataType=dailyRevenue) 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: Helium entities API (IoT subnetwork) HTTP 200; Helium entities API (Mobile subnetwork) HTTP 200; DefiLlama fees API HTTP 200; DefiLlama revenue API HTTP 200; CoinGecko markets API HTTP 200; GitHub helium/helium-program-library HTTP 200; GitHub orgs/helium HTTP 200; estate /v1/network/HNT HTTP 200.