Other system · settles to Solana
Helium ticker HNT
Historical network. Its profile describes the design as history. The evidence is in the system note below.
Summary
Helium runs no consensus of its own. Since the migration on 18 April 2023, HNT, Data Credits, the IOT and MOBILE tokens, Hotspot records (compressed NFTs) and veHNT staking positions are Solana accounts managed by Helium's open-source Solana programs, and Solana validators order and finalize every Helium transaction. Off-chain oracles, which HIP 70 said Nova Labs would build and run for the Helium Foundation, check what Hotspots report and write each Hotspot's lifetime reward total on chain, where the lazy distributor program pays out the unclaimed part. Under HIP 149, approved by veHNT vote and recorded as approved in the HIP repository on 6 July 2026, rewards follow verified data transfer and Proof-of-Coverage is retired. veHNT holders approve protocol changes through HIPs and monthly release proposals. 47131417202327
Design
- System
- Other systemHelium no longer runs a chain of its own. From July 2019 to the migration on 18 April 2023 it ran a purpose-built layer 1 whose Erlang node software is now archived; that chain is history. Today HNT, Data Credits, the IOT and MOBILE tokens, Hotspot records and staking positions are Solana accounts managed by Helium's open-source Solana programs, and off-chain oracles compute rewards. Helium has no validators and posts no batches or proofs, so it is neither a rollup nor a sidechain. It uses the other class, and the pre-migration design is described as history.
- Settles to
- SolanaEvery Helium transaction is a Solana transaction: token transfers, Data Credit burns, Hotspot onboarding, reward claims and veHNT votes are instructions to Helium's Solana programs, so ordering, finality, fees (paid in SOL) and availability are Solana's. Helium posts nothing to Solana beyond ordinary transactions and has no validators of its own. The oracles that compute rewards run off chain and write their results through those same transactions.
- Settlement family
- Solana / SVM
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Other
- Who makes blocks
- Solana's leader schedule assigns each slot to a validator, which orders the Helium transactions it includes; Helium has no block producers. Reward inputs have their own gatekeepers: a reward claim carries a transaction the oracles partially sign, and a new Hotspot joins only with an onboarding transaction approved by its Maker, which the subnetwork must have approved. Before 2023, blocks came from a consensus group elected from validators that each staked 10,000 HNT (HIP 25).
- Fork choice
- Helium follows Solana's fork choice: validators vote on forks under lockouts, and a block is final once validators holding two-thirds of stake share it as a common root. Helium's programs act only on transactions in that ledger, and its oracles read it. The pre-migration layer 1 had no open chain selection either: an elected consensus group agreed on blocks with HoneyBadgerBFT, through Helium's erlang-hbbft library, and HIP 70 records that the chain had halts.
Qualifications
- Settlement family · Partial. The Solana family describes where Helium's accounts and programs run. Helium's own software is a set of Solana programs, off-chain oracles and Hotspot firmware; it ships no ledger node. The pre-migration layer 1 ran Helium's own Erlang node software.
- Scarce resource · Partial. The stake that orders and finalizes Helium transactions is Solana validators' SOL stake. HNT is not staked to produce blocks: it is locked as veHNT for governance votes and a share of rewards. Hotspots earn for verified data transfer, measured by oracles; until July 2026 they also earned for Proof-of-Coverage.
- Finality · Partial. Recorded as other. Helium's own terms: a Helium transaction is final when Solana finalizes the block that holds it, which Solana defines as validators holding two-thirds of stake sharing a common root; Solana's staking docs say there is no in-protocol slashing today. Rewards settle separately: oracles write each Hotspot's lifetime total on chain, and only then can the owner claim it.
- Legacy layer 1 · Not applicable. The purpose-built Helium layer 1 (July 2019 to April 2023) is history. Its validator-staked consensus group (HIP 25), on-chain Proof-of-Coverage challenges and on-chain packet purchasing through state channels ended with the migration; its node repositories are archived and its data is offered only as archives. No live field in this profile describes that chain unless it says so.
- Proof of coverage · Not applicable. Proof-of-Coverage paid Hotspots for radio coverage, checked on the layer 1 and from 2023 by oracles. HIP 149, recorded as approved in the HIP repository on 6 July 2026, retired it on both the Mobile and IoT networks; Helium's oracle-data docs mark it removed as of that date, and oracle release 4.1.0 on 29 July 2026 removed the Mobile reward path.
- Oracle trust · Partial. Oracles decide reward amounts, and a claim needs their partial signatures. HIP 70 said Nova Labs would build and run them for the Helium Foundation at first, with multiple operators left to later proposals; HIP 150 records that HIP 148 retired the oracle-operator reward allocation. Oracle code is open source and raw reports and reward outputs sit in a requester-pays bucket that readers can inspect at their own cost; reproducing reward totals from them was not tested. Other oracle operators today were not verified.
- Max supply · Partial. HIP 20 set a two-year halving schedule with a projected maximum of about 223 million HNT, which Helium's token page still shows. HIP 149 adds a separate supplement mint of about 141 million HNT over 36 months to a vault administered by Nova Labs, and says this raises the effective maximum from about 206 million to about 347 million HNT.
- Hotspot onboarding · Partial. Hotspots are issued as NFTs by Helium's entity manager program only with an onboarding transaction approved by the hardware's Maker, and each subnetwork approves its Makers. Converted Wi-Fi networks join through the Helium Plus program or self-serve tooling.
- Upgrade authority · Unknown. Helium's core developers propose program upgrades, and veHNT holders approve them in monthly release votes under HIP 141; HIPs leave implementation to the core developers. Who holds the program upgrade keys, and how a vote result binds them, was not verified.
- Block metrics · Not applicable. Helium has no blocks of its own; block, slot and fee-market measures describe Solana.
- Tps · Not applicable. Helium publishes no transaction-rate figure of its own; its transactions share Solana's capacity, and no figure is recorded here.
Tradeoffs
- Emphasizes
- Scalability
- Gives up
- Independence and self-checkable rewards. Helium's ordering, finality, fees and uptime are Solana's, so a Solana outage or rule change reaches Helium directly. Reward amounts come from oracles that HIP 70 said Nova Labs would run for the Helium Foundation, with several operators left to later proposals; their raw reports sit in a requester-pays storage bucket, so checking them costs the reader money. veHNT votes can also change emissions, as HIP 149 did by adding a supplement mint that raises the effective supply ceiling.HIP 70 argued that moving Proof-of-Coverage and data accounting to oracles and the tokens to Solana would make data transfer and rewards more reliable and let the network grow to millions of Hotspots. Whether depending on another chain and on a small set of oracle operators is a sound trade is left open here.
- Full node at home
- Data-center class 46729Helium publishes no node software for its ledger. Following HNT balances, Hotspot records and program state yourself means running a Solana node, and Anza's requirements for a validator (12 or more cores, 256 GB or more of RAM, separate NVMe drives for accounts, ledger and snapshots) and for an RPC node (more) describe data-center hardware. Reading compressed Hotspot records also needs an indexing RPC service. Hotspots are radios and keep no ledger. The pre-migration layer 1 had its own node software, now archived.
- Throughput claims
- No classified figure recorded
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Built into the protocolLimited scope | Limited to exchanges on Solana, where Helium's tokens live as Solana accounts. A Solana transaction is signed with one or more keypairs and executed atomically, so two parties can exchange HNT and other Solana tokens in one transaction that both sign, settling in full or not at all. The rule is Solana's protocol, which Helium's own proposals and releases do not control. This is an inference from Solana's documented behaviour; no tool using it for HNT swaps, and no cross-chain hash-time-locked swap, was reviewed. 427 |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. Helium's oracles publish their input and reward reports as files in a requester-pays storage bucket, and reward totals reach the chain signed by the oracles, but no on-chain commitment to those files that readers could check them against was found. 57 |
| Light clients | Unknown | Helium ships no light client. Checking Helium state without a full node would depend on Solana's own verification paths, not reviewed here; Helium's docs point readers to RPC providers and to Helium's Entity API, a convenience service without uptime guarantees. 48 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | None found Earlier definition | No channel layer anchored to Helium was found. The nearest feature is Data Credit delegation: a buyer burns HNT for non-transferable Data Credits, delegates them once to a network operator, and packet verifier oracles account for data used. No two-party off-chain state is settled on chain, so it is not a channel. On the pre-migration layer 1, routers registered to an OUI opened on-chain state channels funded with Data Credits to pay for data transfer; they ended with that chain when HIP 70 moved data-transfer accounting to oracles. 21424 |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Helium's tokens, Hotspot records and staking positions are Solana accounts, so spend conditions come from Solana programs. Helium's own open-source programs add rules: veHNT lockups in the voter stake registry, the circuit breaker that wraps sensitive mint authorities and token accounts to prevent large movements, and oracle-signed reward claims in the lazy distributor. 426 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under this row's current definition. Helium's wallet docs say a lost private key cannot be recovered. The circuit breaker wraps Helium's sensitive mint authorities and token accounts to prevent large movements after an exploit or bug, and the April 2026 release lets a staker move a locked veHNT position to another wallet; neither is a user reversal or recovery path. 4921 |
| Rollups | None found Earlier definition | No rollup anchors to Helium, which is a set of programs on Solana, not a chain others settle to. The nearest feature, the lazy transactions program, compressed the migrated layer 1 transactions into a Merkle root so each would execute exactly once on Solana; it is a migration tool, not a rollup. 4 |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | ThinOrca (HNT pools on Solana), Jupiter (swap routing) | Helium runs no exchange. HNT is an ordinary Solana token: Orca's pool API listed several concentrated-liquidity pools pairing HNT with USDC, SOL and other tokens on 2026-09-29, and Jupiter's token API lists HNT as routable. Helium's wallet app opens Jupiter in its in-app browser. Both APIs showed little liquidity in HNT's pools that day; no figures are used, and other Solana venues were not reviewed. The subnetwork treasuries that exchange IOT and MOBILE for HNT by formula are a Helium program, not a market. 410153132 |
| Issuer-native stablecoins | Established in the ecosystemUSDC on Solana (Circle) | Helium issues no stablecoin. Its tokens live on Solana, where Circle issues USDC natively (Circle's address list includes Solana), so the same wallets hold both, and Helium's wallet app shows USDC balances. This is Circle's USDC as issued on Solana, reached without a bridge, not a Helium issuance. 1033 |
| Algorithmic stablecoins | Unknown | No algorithmic stablecoin tied to Helium was found; stablecoins available across Solana were not reviewed for this profile. |
| Bridges | Unknown | Helium runs no bridge. The only cross-ledger move it documents is the one-time 2023 migration, which carried layer 1 balances, Hotspots and stake into Solana from a snapshot. Whether third-party bridges on Solana carry HNT to other chains was not verified. 614 |
| Block explorers | First-partyHelium World (explorer.helium.com redirects there), Solana Explorer (token and program accounts) | Helium's home page links its explorer at explorer.helium.com, which redirected to Helium World on 2026-09-29; Helium's March 2026 post describes Helium World as its rebuilt web app for viewing and managing Hotspots. Helium World refused automated reads in this review. Helium's docs link the HNT mint and program accounts to the Solana Explorer. Explorer data is indexer output. 143839 |
| Hardware wallets | Established in the ecosystemTrezor (Trezor Suite, Solana network), Ledger (through the Helium Wallet App, Phantom or Solflare) | See the custody rows. Trezor's Helium page names Trezor Suite on the Solana network; Helium's docs route a Ledger through the Ledger Solana app and a Solana wallet. Helium's docs say Hotspot actions such as onboarding, location updates and reward claims need special tooling in the Helium Wallet App or Maker apps. 11123436 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Through an intermediaryHelium Wallet App, Phantom or Solflare, signing with the Ledger Solana appSame as native: Unknown | Can: View balances, transfer HNT, IOT and MOBILE and sign transactions through the Helium Wallet App with the Ledger Solana app, per Helium's Ledger guide Can: Use the device with Solflare or Phantom for Solana tokens, per Helium's Ledger guide Cannot: Onboard Hotspots or assert their locations with a Ledger; Helium's guide says these actions are not supported Cannot: Manage HNT directly in Ledger Live, according to Helium's guide; Ledger's own Helium page also routes users to a third-party walletLedger's Helium page (modified 2023-12-19) tells users to connect the device to a compatible third-party wallet, names MetaMask, and describes the pre-migration network. Ledger's Solana page says Ledger Wallet manages SPL tokens, the standard HNT uses, but whether Ledger Wallet shows HNT was not verified, so native support is not claimed. Helium's guide requires blind signing in the Solana app. 113435 |
| Trezor | Native supportSame as native: Unknown | Can: Send and receive HNT on the Solana network in Trezor Suite with a Trezor Safe 3, Safe 5 or Safe 7, per Trezor's Helium page Can: Use the device with Backpack or NuFi, the other wallet apps Trezor's Helium page lists Cannot: Onboard Hotspots, update their locations or claim Hotspot rewards in Trezor Suite: Helium's docs say these actions need special tooling in the Helium Wallet App or Maker appsTrezor's Helium page lists Solana as the supported network and says Trezor Suite handles Helium; its descriptive text still describes the pre-migration mining network. Trezor's Solana guide says SOL and all SPL tokens, the token standard HNT uses, are supported on the Safe 7, Safe 5, Safe 3 and Model T. No source compares this path with the Helium Wallet App, which also handles Hotspot actions. Whether Suite shows IOT, MOBILE or Hotspot NFTs was not checked. 123637 |
Public data
iKnow Blockchain has no public-data lookups for Helium yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Reviewed Sep 29, 2026 Next review due Oct 9, 2026, 12:00 UTC.
Publication date · newest first
-
HIP 150 approved: 80% target minimum, deployer pool at 94% and per-Hotspot multipliers
Helium announced that veHNT holders approved HIP 150 and that it applies from 31 August 2026. It raises the Mobile target minimum from half to 80% of what payers pay for rewardable data for one year, with a second year pre-authorized; mints the HIP 149 top-up straight into the deployer data pool; moves Nova Labs' Service Provider share into that pool, taking it from 70% to 94% until 31 July 2027; and allows per-Hotspot multipliers of up to 5, granted by Nova Labs.
- Proposal:HIP 150 approved by veHNT vote; HIP index status Approved
- Implementation:oracle release 4.6.0 (HIP-150) published 2026-08-31
- Release:announced by Helium on 2026-09-04
- Activation:applies from 31 August 2026 per Helium's post; the HIP index does not yet mark it deployed
Sources: Helium blog — HIP-150: Higher Earnings for Deployers, Premium Rates for High-Demand Venues (external site) · Helium (HIP repository) — HIP 150: Mobile Deployer Prioritization (external site) · Helium governance (hiptron gist linked from HIP 150) — HIP-150 vote summary (external site) · Helium (GitHub) — helium/oracles release 4.6.0 (HIP-150) (external site) · Helium (HIP repository) — Helium Improvement Proposals: index and status table (external site)
-
HIP 149 approved: Proof-of-Coverage retired, Mobile target minimum, supplement mint and Advisory Council
veHNT holders approved HIP 149, which bundles four decisions: Mobile deployers earn HNT for rewardable data within a band of half to three times the carrier rate; a supplement mint of about 141 million HNT over 36 months goes to a vault administered by Nova Labs; Proof-of-Coverage retires on both Mobile and IoT; and a 7-seat Advisory Council oversees the supplement. Helium's docs mark Proof-of-Coverage removed as of 6 July 2026.
- Proposal:HIP 149 approved by veHNT vote (two-thirds supermajority, 100,000,000 veHNT quorum); marked Approved in the HIP repository on 6 July 2026
- Implementation:oracle releases 4.0.0 (2026-07-02, HIP-149 tracking) and 4.1.0 (2026-07-29, Mobile Proof-of-Coverage reward path removed)
- Release:Helium's docs mark Proof-of-Coverage removed as of 6 July 2026; Helium's 7 August post describes the target minimum as live
- Activation:live per Helium's docs and blog; the HIP index still says Approved, and the supplement mint start was not checked at the vault on chain
Sources: Helium (HIP repository) — HIP 149: Helium Utility and Emissions Realignment (external site) · Helium (HIP repository) — HIP 149 file history (commit feed) (external site) · Helium Documentation — Helium Oracle Data (external site) · Helium (GitHub) — helium/oracles release 4.0.0 (HIP-149 tracking) (external site) · Helium (GitHub) — helium/oracles release 4.1.0 (external site) · Helium blog — New Earnings Safety Net for Helium Deployers (external site)
-
April 2026 release: staked HNT positions can move between wallets
The April 2026 Helium Release Proposal added a transfer instruction to the staking programs so a holder can move a locked veHNT position, represented by a frozen NFT, to another wallet without unlocking it. The position's amount, lock and rewards stay unchanged. The release note records it as released on 2 April 2026.
- Proposal:Helium Release Proposal 2026-04 approved by veHNT vote
- Implementation:transfer endpoint added to the staking programs
- Release:released 2026-04-02 per the release note
- Activation:live from release per the release note; not tested in this review
Sources: Helium Core Developers (helium-release-proposals repository) — Helium Release Proposal April 2026 (external site) · Helium Core Developers (GitHub) — Helium Release Proposals repository (external site)
-
Helium World rebuilt with email sign-up and built-in reward splitting
Helium announced a rebuilt Helium World for deployers: new accounts are created with an email address and passkeys through Privy, with no seed phrase; Hotspots can be onboarded and managed from a web dashboard; rewards can be split with venue hosts; and a migration tool moves Hotspots from the older app.
- Implementation:Released
- Release:announced as live by Helium
- Activation:available per Helium; not tested because the site refused automated reads
Source: Helium blog — Deployers, Rejoice! Helium World Is Getting a Major Upgrade. (external site)
Topics your AI can explain
Your AI can explain these topics for Helium through the connection, with sources.
Known gaps
What this profile's review did not establish:
- Who operates the reward oracles today, and whether any operator other than Nova Labs or the Helium Foundation runs one, was not verified; HIP 70's plan dates from 2022. Who operates the IoT packet router and configuration service was not verified either.
- Who holds the upgrade keys of Helium's Solana programs, and how a release or HIP vote binds them, was not verified.
- Whether the HIP 149 supplement mint has started was not checked at the vault on chain. HIP 150 dates the end of the supplement's flat window to 31 July 2027, and a Solana RPC read on 2026-09-29 showed about 192.5 million HNT in supply, above the roughly 182.5 million HIP 149 cited in June 2026; both are consistent with minting having begun.
- Helium's HNT token page still shows only the HIP 20 schedule and projected maximum; it does not yet reflect the HIP 149 supplement.
- The HIP index lists HIP 149 and HIP 150 as approved, not deployed, while Helium's docs, blog and oracle releases describe their changes as live, and HIP 150 says the HIP 149 top-up has fired in every epoch since HIP 149 went live; activation dates here come from those Helium sources.
- Helium World, the explorer Helium's site links, refused automated reads in this review, so its content was checked only through Helium's own post about it.
- Whether Ledger Wallet displays HNT directly was not verified; Ledger's Helium page dates from 2023 and describes the pre-migration network.
- Whether third-party bridges carry HNT from Solana to other chains was not verified.
- No Helium-specific light client, atomic-swap mechanism or data-publication commitment was found; absence was not exhaustively verified. The atomic-swap value rests on Solana's transaction rules, which Helium inherits by running on Solana.
- The exact last block of the legacy layer 1, and when it stopped producing blocks, were not verified from a primary source.
- HNT liquidity was read only from Orca's pool API and Jupiter's token API on 2026-09-29; other Solana venues were not reviewed, and no liquidity or volume figure is recorded.
- IoT network changes after Proof-of-Coverage retirement (an IoT Operations Fund absorbing the former coverage bucket) were read from HIP 149 only.
Sources
Oldest dated source check: Source checked Sep 29, 2026 Next check due Oct 29, 2026.
- The Helium Network Token (external site)
- Data Credit (external site)
- The Solana Token (external site)
- Helium Data on Solana (external site)
- Helium Oracle Data (external site)
- Legacy Blockchain Data (external site)
- Rewardable Entities (external site)
- Entity API Documentation (external site)
- Wallets (external site)
- Helium Wallet App (external site)
- Ledger (external site)
- Third-Party Wallets (external site)
- HIP 25: Validators (external site)
- HIP 70: Scaling the Helium Network (external site)
- HIP 138: Return to HNT (external site)
- HIP 141: Single-Token Governance and Helium Release Proposals (external site)
- HIP 149: Helium Utility and Emissions Realignment (external site)
- HIP 150: Mobile Deployer Prioritization (external site)
- Helium Improvement Proposals: index and status table (external site)
- HIP 149 file history (commit feed; status set to Voting Open on 2026-06-25 and to Approved on 2026-07-06) (external site)
- Helium Release Proposal April 2026 (staked HNT position transfers) (external site)
- helium/miner rebar.config (archived legacy node software; depends on blockchain-core and erlang-hbbft) (external site)
- erlang-hbbft: Erlang implementation of HoneyBadgerBFT's protocols (external site)
- helium/blockchain-core: state channel open transaction (archived legacy layer 1 code) (external site)
- helium/oracles release 4.1.0 (removes the Mobile Proof-of-Coverage reward path) (external site)
- helium-program-library repository (external site)
- Terminology (finality, lockout, leader schedule, root) (external site)
- Staking on Solana (external site)
- Agave Validator Requirements (external site)
- Solana mainnet RPC: getTokenSupply for the HNT mint (read 2026-09-29, 8 decimals) (external site)
- Jupiter token API: HNT (Helium Network Token) entry (external site)
- Orca pools API: pools containing HNT (external site)
- USDC contract addresses (external site)
- Helium wallet (external site)
- Solana wallet (external site)
- Helium wallet (external site)
- Solana: what it is and how it works with Trezor (external site)
- Helium home page (site navigation links Explorer at explorer.helium.com) (external site)
- Deployers, Rejoice! Helium World Is Getting a Major Upgrade. (external site)
- New Earnings Safety Net for Helium Deployers (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding