The Civic Node

Helium HIP-143 and the DePIN Franchise Architecture

10 min read

Answer

Helium hotspot operators bought a franchise. They were sold a business. The hardware they paid for is theirs. The pricing authority that determines what their hardware earns is not.

The case is documented in the April 3, 2025 vote on HIP-143, which formally authorized Nova Labs (the company that operates Helium Mobile and negotiates the carrier offload deals) to set the price carriers pay for hotspot data without involving Helium governance. The proposal text states the goal directly: “If Nova Labs would be able to move quickly… without involving Helium governance, the authors of this HIP anticipate that the total Data Transfer of the Helium network will rise.”

The vote passed 90.53% to 9.46% on 763 million veHNT (vote-escrowed HNT, the governance token) against a 100 million quorum Helium HIP-143 Vote Results — Helium Vote - 2025-04-03. The structural detail that matters is the voter breakdown: the Nova Labs proxy controlled 26.00% of the vote, and the ferebee proxy, listed as a co-author of HIP-143, controlled 24.00%. Together, the proposing entity and one of its co-authors cast half the yes votes for the proposal authorizing the proposing entity’s pricing authority. The largest “against” vote was an anonymous proxy at 8%.

HIP-143 included a 1-year delegation provision. As of Q4 2025 State of Helium Q4 2025 — Messari, no superseding HIP had been passed. The structure auto-renewed by inaction around April 2026, weeks before this synthesis was filed. The vote that handed Nova Labs unilateral pricing authority is now in its second year, without any further operator participation having been required.

This is the structural test for any DePIN project: who holds the pricing authority over the revenue the operators are paid out of, and how is that authority changed? In Helium’s case, the answer is documented. The operators don’t, and the people who do can reauthorize themselves through votes the operators are recommended to delegate to proxies.

Supporting Evidence

The operator economics that frame the trap

Marketing once promised hundreds of dollars a month for a Helium hotspot. By August 2025, a well-placed urban hotspot was earning between $3 and $45 a month, with most operators clustered in the $4 to $8 range Helium Hotspot Earnings 2025 — AMBCrypto. A basic indoor IoT hotspot costs $249; a pro outdoor setup runs to $949. The indoor box pays back in two and a half to five years; the outdoor setup, ten to twenty Helium Operator Economics — Bytetree - 2024-03.

The three governance changes that produced the gap

The reward structure that defined what operators bought changed through a sequence of defensible-sounding proposals run over three years.

  • HIP-82 capped how much data could earn rewards: $0.50 per gigabyte up to whatever the subscriber’s plan cost divided by $0.50 allows, zero above that. Each step had a defensible logic. Caps prevent operators from earning indefinitely on subscribers who had already maxed out their plan. Run the cap for three years and it defines the ceiling.
  • HIP-138 consolidated the IOT and MOBILE subnetwork tokens into HNT in January 2025 Helium HNT Tokenomics — Tokenomist. Token consolidation simplified the accounting.
  • The August 2025 halving cut new HNT emissions from 15 million to 7.5 million per year, halving Proof of Coverage (PoC, the algorithmic reward for hotspots that prove they cover a geographic area) rewards in the same step Helium Halving 2025 — Helium Blog - 2025-07-24.

Each proposal had its own justification. Together they shifted the rewards from coverage to data traffic, then halved what could be earned on the coverage that remained. An operator who built out a rural hex in 2022 created a real public good for the network’s IoT ambitions. They were later told it was not the public good that pays.

The network revenue asymmetry

State of Helium Q4 2025 — Messari documents the structural revenue gap between the two halves of the network. The IoT side generates $124.77 per day in Data Credit burns across the entire deployed base — about $45,000 a year, the price of one Helium Mobile Air subscription per day, generated by the 385,000 hotspots that operators built to serve IoT traffic. The mobile side, which routes carrier offload from T-Mobile and AT&T, generates the rest: $56,635 per day in real utility revenue Helium Mobile Revenue and Carrier Offload — Sarson Funds - 2025. One half of the network is the revenue. The other half is the hardware that gives the project something to point at.

The proxy concentration is policy, not accident

The Helium Foundation’s official explainer on the August 2025 halving recommends operators “set a proxy as a backup to ensure you don’t miss out on rewards” Helium Halving 2025 — Helium Blog - 2025-07-24. Foundation policy normalizes delegating voting power to large proxies. The 50-percent concentration that approved HIP-143 is how the system was designed to work, not a deviation from it.

Caveats & Gaps

  • The Nova Labs / ferebee co-authorship structure is documented in the HIP-143 proposal text, but the exact ownership and decision-making relationships between the two are not public. The 26% + 24% concentration is verifiable from the on-chain vote; the inference that this represents a single coordinated bloc is reasonable but not directly proven.
  • The carrier offload deals (T-Mobile, AT&T) are confidential. Aggregate utility revenue is in State of Helium Q4 2025 — Messari, but the unit economics (what Nova Labs charges per gigabyte to T-Mobile versus what flows through to operators) are not disclosed. The HIP-143 proposal text argues this confidentiality is structurally necessary for negotiating posture; the argument is plausible but the absence of aggregate disclosure remains a structural opacity.
  • PoC reward distribution by geography (urban versus rural; dense hex versus Lone Wolf hex) is documented anecdotally in operator forums but not in aggregate. The “coverage value spreads out, data value concentrates” claim is structurally consistent with the rule changes, not directly quantified.
  • Whether operators received any private disclosure of upcoming HIP changes before public posting is not knowable from public sources.

Newsletter Application

This synthesis names a transferable analytical move that applies to multiple future pieces.

The franchise-vs-business test. When evaluating any DePIN project, or any structure where individual operators deploy capital into a shared network and earn through tokenized rewards, the question to ask is: who holds the pricing authority over the revenue the operators are paid out of? The hardware is theirs. The token may be theirs. The pricing authority over what the network charges its customers is the question that determines whether they own a business or a franchise. The Helium case is the cleanest documented example of the franchise architecture.

The proxy-concentration audit. Any DAO that uses proxy delegation for governance is vulnerable to the proposing-entity-carries-the-vote pattern. HIP-143’s voter breakdown is the worked example: 26% + 24% = 50% of yes votes carried by the entity authorizing itself and one of its co-authors. For any future DAO governance story, the audit move is to pull the voter breakdown by proxy concentration and check whether the largest blocs vote in alignment with the proposing entity. If they do, “community consensus” is descriptively wrong and the governance is a different shape than the vote percentages suggest.

The auto-renewal-by-inaction pattern. HIP-143’s 1-year delegation provision combined with no superseding HIP equals a structure that re-arms itself. Operators don’t have to be asked again because the default rule does the asking for them. For any future DePIN piece, the audit move is to check whether the project’s most consequential governance changes have sunset provisions and whether those provisions have ever been allowed to lapse. Default-rule design is governance design; the structures that survive are the ones that survive operator inattention.

The “deploy first, find out what you bought later” pattern. The structural test in the Datagram correction (see below) — that the operator pays for hardware before the documents governing what they bought are finalized — applies to Helium too. HIP-82, HIP-138, and HIP-143 were all written after operators had already deployed. The franchise architecture is partly architectural and partly temporal: governance defines the operator’s position retroactively. Any DePIN piece going forward should treat “the docs you signed before deploying” as the relevant evidence base, not the docs the project points at today.

The Datagram correction. Two earlier pieces in this newsletter cited Datagram as a DePIN counter-example doing it differently. Datagram turned out to be a rug; the project collapsed. The honest admission is that the operator due-diligence checklist that worked for Helium (who controls pricing, has governance changed rewards mid-game) was not enough to catch what Datagram actually was, which was outright fraud. The structural problems (Helium-style franchise architecture) and the fraud problems (Datagram-style nothing-to-build) share an architecture. Both require an operator who deploys capital before the documents that govern what they bought are written. The right move, given that, might be to never deploy first.

Follow-up Questions

  • How many other DePIN projects use the same authorize-the-corporate-counterparty governance pattern? Render, GEODNET, io.net, Filecoin all have variants of the operator-deploys / DAO-or-foundation-governs structure. Which of them have HIP-143-equivalent moves in their history, and which don’t?
  • Is there a DePIN project where operators do hold pricing authority? What does its governance look like, and what trade-off did the project make to keep operators in the room when commercial terms get set?
  • What does aggregate transparency on DePIN data-transfer revenue actually look like across the sector? Messari and similar research firms publish some of this; the gaps are worth mapping.
  • What is the actual ownership and operating relationship between Nova Labs and ferebee? Public sources document each as a Helium-ecosystem actor; the coordination signal in the HIP-143 vote suggests a closer relationship than the public framing implies.
  • Are there other Foundation-published documents that further institutionalize the proxy-delegation pattern? Worth a documentary audit of Foundation-published operator guidance for the same retroactive-governance-defines-what-you-bought structure.
  • Published article: Helium Operators Built the Network. Nova Labs Sets the Price. (Substack, May 22, 2026 — wiki article page to be filed in wiki/articles/ after publish)
  • Article draft: workspace/drafts/helium-operators-built-the-network.md
  • Article outline: workspace/outlines/helium-operator-incentives.md
  • Entity (created 2026-05-21): Nova Labs — the corporate counterparty at the center of the franchise architecture
  • Concept (created 2026-05-21): Franchise vs. Business — the analytical move this synthesis names; canonical concept page for future DePIN governance pieces
  • Concept (created 2026-05-21): Proxy Concentration Audit — the procedural test for any DAO governance vote using proxy delegation
  • Concept (created 2026-05-21): Auto-Renewal by Inaction — the default-rule design pattern that lets governance structures re-arm without operator participation
  • Related concept (existing): Chokepoint Control — the framework this synthesis extends to the DePIN protocol layer
  • Related concept (existing): DePIN — the broader category this synthesis sits inside
  • Related concept (existing): Operator View of Crypto Regulation — adjacent operator-perspective material

Key sources

Graph View

Backlinks