Meshtastic vs Helium: The Sovereignty Test (Who Owns It, Token vs Free, Use Cases)

What each network actually is

Meshtastic: peer-to-peer LoRa mesh

Meshtastic is an open-source project (GPLv3) that runs a custom mesh networking protocol directly over LoRa radio hardware. There is no central server, no blockchain, no token. A Meshtastic network is simply a group of nodes — typically inexpensive ESP32-based hardware — that relay messages from one to another through a managed-flooding algorithm. Direct node-to-node messages use Public Key Cryptography (PKC); channel broadcasts use AES-256-CTR encryption. The firmware, apps, and protocol specifications are all publicly available and community-governed through an open collective. As of 2025–2026, the project has thousands of GitHub stars and a rapidly growing global community.

Critically, Meshtastic is not LoRaWAN. It uses LoRa’s physical radio layer (the modulation scheme) but replaces the LoRaWAN protocol stack entirely with its own mesh-first design. That distinction matters: LoRaWAN requires gateways and network servers; Meshtastic nodes talk directly to each other.

Helium: token-incentivized LoRaWAN DePIN

Helium is a decentralized physical infrastructure network originally launched in 2019 by Nova Labs. It works by incentivizing individuals to deploy LoRaWAN-compatible hotspots: operators earn HNT tokens for providing coverage and routing packets. IoT devices connect using standard LoRaWAN and consume Data Credits (DCs) to transmit data — 1 DC equals one 24-byte uplink, and 100,000 DCs can be purchased for approximately $5 USD in fiat currency (pricing as of 2025; verify current rates at docs.helium.com). The Helium ledger migrated from its own blockchain to Solana in April 2023.

As of Q3 2025, the IoT network had over 384,600 onboarded hotspots globally with coverage in major cities across North America, Europe, and Southeast Asia. In Canada, Helium operates through a roaming partnership with LoRaWAN provider X-TELIA. Nova Labs reached a settlement with the US SEC in April 2025 (no admission of wrongdoing; $200,000 fine), removing a significant regulatory overhang from the project.

The sovereignty test: who owns it?

The sovereignty question has three dimensions: infrastructure ownership, protocol ownership, and economic dependency.

Dimension	Meshtastic	Helium
Infrastructure owner	You. Each node is owned and operated by its deployer. No central authority exists.	Hotspot operators own their hardware. The network governance resides with the Helium DAO (HIP voting) and Nova Labs as protocol developer.
Protocol owner	The open-source community. GPLv3 — forks must remain open. No company can close it.	Nova Labs, with community input via Helium Improvement Proposals (HIPs). Solana dependency for ledger.
Can access be revoked?	No. You run the firmware; you run the network. No accounts required.	Access requires Data Credits. If you run out of credits — or if the DC mechanism changes — you lose access.
Economic dependency	None. Hardware cost only (one-time).	Ongoing data credit costs for device operators. Hotspot operators depend on token rewards, which fluctuate.
Censorship resistance	High. No choke point. Messages hop node-to-node with no server in the path.	Moderate. The network is distributed, but the Helium Console and LNS (LoRaWAN Network Server) layer introduces service dependencies.

Verdict on sovereignty: Meshtastic wins on pure sovereignty. Your nodes, your keys, your network. Helium is decentralized in its infrastructure distribution but introduces economic and governance dependencies that do not exist in Meshtastic. That is not an attack on Helium — it is a structural difference you should understand before building on either.

Token vs. free: the real economics

Meshtastic has no ongoing cost after hardware purchase. A node that costs $30–$80 USD (prices vary; verify with current retailers) operates indefinitely on battery, solar, or mains power, communicating with every other Meshtastic node within range at zero marginal cost per message.

Helium’s cost model is designed for low-volume IoT sensor data. At the time of writing (2025), 100,000 Data Credits — enough for 100,000 uplink packets of up to 24 bytes each — costs approximately $5 USD in fiat. For a sensor sending one packet per hour, that represents roughly 11 years of data transmission. Helium’s per-byte economics are well-suited for small, infrequent sensor payloads. They are poorly suited for voice, image, or high-frequency messaging — which Meshtastic also does not support at high data rates, given LoRa’s physical limitations.

The token dimension matters most for hotspot operators, not device users. Operators deploy hardware, earn HNT rewards, and bear market-price risk on those rewards. If you are evaluating Helium as an investor in network infrastructure, that is a separate analysis (and outside the scope of this comparison). If you are evaluating it as a user of connectivity, the fiat-denominated Data Credit path means you do not need to touch HNT at all.

Architecture and technical comparison

Attribute	Meshtastic	Helium (IoT)
Radio protocol	LoRa (custom mesh stack, NOT LoRaWAN)	LoRaWAN (industry standard)
Network topology	Peer-to-peer mesh; every node relays	Star-of-stars; end devices → gateway → network server
Encryption	AES-256-CTR (channels); PKC (direct messages)	LoRaWAN AES-128 (standard); app-layer encryption optional
Typical range	2–10 km line-of-sight (terrain-dependent; see range calculator)	Gateway-dependent; urban ~1–3 km; rural up to 10+ km with good antenna placement
Power requirement	Battery-friendly; devices run weeks on small LiPo	Hotspots require mains power; end devices are low-power
Data rate	~250 bps – ~5.5 kbps depending on spreading factor	LoRaWAN: 0.3 – ~27 kbps (SF-dependent); optimized for short bursts
Payload type	Text, GPS position, telemetry, small binary payloads	Sensor data, telemetry, tracking (small uplink packets)
Infrastructure required	None. Two nodes = a network.	Requires at least one nearby Helium hotspot for coverage
Internet connection needed?	No. Fully offline-capable.	Yes, at the gateway level (hotspot needs internet backhaul)
Open source	Yes — firmware, apps, protocol (GPLv3)	Partially — hotspot firmware is open; some components are proprietary
Frequency (North America)	915 MHz ISM band	915 MHz ISM band (same physical layer)

Use case comparison: where each network fits

Scenario	Better fit	Why
Off-grid hiking / backcountry comms	Meshtastic	No infrastructure required; battery-powered nodes; text and GPS sharing
Emergency preparedness mesh	Meshtastic	No central point of failure; works when internet is down
Permanent IoT sensor deployment in a city	Helium	LoRaWAN coverage already exists in many urban areas; pay-per-use model suits low-traffic sensors
Asset tracking (fleet, equipment)	Helium (urban); Meshtastic (rural)	Helium has urban coverage density; Meshtastic is self-sufficient where infrastructure is absent
Community mesh network	Meshtastic	Grows organically with each node added; no token onboarding required
Agriculture / precision farming IoT	Either, depending on coverage	Helium has rural coverage gaps; Meshtastic requires node placement but works anywhere
Disaster response / infrastructure-down scenarios	Meshtastic	Zero dependencies on internet, power grid, or third-party services
Commercial sensor-as-a-service product	Helium	Standard LoRaWAN makes device integration straightforward; Data Credits provide predictable billing

The sovereignty verdict

If your primary concern is control — knowing that no company, token price, or network policy change can interrupt your communications — Meshtastic is the answer. The protocol belongs to its community under a copyleft license. The network belongs to whoever deploys nodes. There is nothing to revoke.

If your primary concern is coverage without infrastructure investment — connecting IoT devices to the internet in cities where Helium hotspots already exist — Helium provides that coverage at a modest per-byte cost, without requiring you to deploy your own gateways. The economic dependency is real but modest for typical sensor workloads.

These networks are not in competition in practice. Many operators run Meshtastic nodes for off-grid or emergency communications and deploy Helium-compatible sensors for commercial IoT use cases. The distinction is architectural and philosophical, not a product war.

Both projects have built something that deserves credit: Meshtastic’s community pioneered a genuinely open, zero-infrastructure approach to long-range mesh communication. Helium’s community proved that token-incentivized infrastructure deployment can build real-world coverage at scale. Understanding what each one actually is — rather than accepting marketing framings from either direction — is the prerequisite to using either effectively.

For a deeper look at Meshtastic hardware options and the devices that power a sovereign mesh, see our Meshtastic device comparison and the mesh networking hub.

Related resources

• Mesh networking hub — Meshtastic, LoRa, and off-grid comms
• Meshtastic device comparison — hardware guide
• Meshtastic range calculator
• Nostr: sovereign communication at the protocol layer
• Digital sovereignty for Canadians
• The sovereign stack: communications, compute, and infrastructure

Frequently asked questions

Can Meshtastic connect to the Helium network?

No — Meshtastic uses a custom protocol over LoRa radio that is incompatible with LoRaWAN. Helium’s IoT network is built on standard LoRaWAN, which requires end devices to implement the LoRaWAN MAC layer. Meshtastic nodes cannot register with or send data through a Helium hotspot. They use the same radio spectrum but speak different protocols.

Do I need to buy HNT tokens to use Helium?

Not necessarily. As of 2025, you can purchase Data Credits directly with USD fiat currency through the Helium Console and hosted LoRaWAN Network Server providers. HNT token involvement is required only if you are operating a hotspot and want to receive rewards, or if you prefer to acquire Data Credits through token conversion rather than direct fiat purchase.

Does Meshtastic work without internet?

Yes. Meshtastic is fully offline by design. Messages travel directly from node to node via radio. An internet connection is optional — some nodes run a MQTT bridge to connect a local mesh to the internet, but this is not required and the mesh operates independently of it.

How many Meshtastic nodes do you need to form a network?

Two. Any two Meshtastic-compatible devices within radio range form a working network immediately. Additional nodes extend range and resilience through multi-hop relaying. There is no minimum or maximum — the network scales from a two-person hiking pair to a city-wide community mesh.

Is Helium coverage available across Canada?

Helium has a roaming partnership with X-TELIA for LoRaWAN coverage in Canada (established 2022). Urban coverage in major Canadian cities exists through this arrangement and through independently deployed Canadian hotspots. Rural coverage is sparse and uneven — verify coverage for your specific location using the Helium Explorer before deploying devices.

Which network is better for emergency communications?

Meshtastic is the clear choice for emergency use. It has no infrastructure dependencies, no internet requirement, and no token or service that can fail. A Meshtastic mesh continues functioning as long as at least two nodes with charged batteries remain within radio range of each other. Helium requires functioning internet backhaul at the gateway — in a grid-down or internet-outage scenario, the Helium network in that area ceases to function for end devices.

Is Meshtastic legal to use in Canada?

Yes. Meshtastic operates in the 915 MHz ISM (Industrial, Scientific, and Medical) band in North America, which is license-exempt under Innovation, Science and Economic Development Canada (ISED) regulations for low-power devices. Standard disclaimer: verify your specific hardware’s certification and power levels comply with RSS-210 (or the applicable ISED standard current at time of deployment). This is general information, not legal or regulatory advice.

Can I run both Meshtastic and a Helium hotspot?

Yes. They occupy the same 915 MHz band in North America, so you would need to ensure your antenna setups are physically separated or use filters to avoid self-interference, but there is no technical or policy reason you cannot operate both. Many operators do exactly this — a Meshtastic mesh for local off-grid communications and a Helium hotspot for commercial IoT connectivity.