Helium After HIP-149: Can 141M HNT Buy Distribution?

HIP-149 has passed. Governance has its answer; investors still need theirs.

This article assumes familiarity with the events around HIP-149: the proposal itself, the Noble Mobile transaction, and the accompanying leadership change. Readers who need to catch up first should start with Nick Carpinito’s Helium: No Longer Inert.

The proposal gives Helium roughly 141M HNT of operating and growth runway over 36 months. The live question is what holders get for the dilution. If the HNT buys access to controlled, non-home Wi-Fi networks that carriers will pay to use, HIP-149 is distribution capital. If it buys a scattered collection of low-traffic deployments, the network will struggle to earn back what holders gave up.

Everything below is U.S.-only because the immediate underwriting problem is U.S. carrier offload: can Helium turn controlled Wi-Fi portfolios into authenticated traffic that AT&T, T-Mobile, Verizon, cable MVNOs, or another U.S. payer will buy? International expansion is upside after that mechanism works. It is not a repair kit for domestic unit economics that do not.

HIP-149 marks the network's next phase. The old model paid deployers primarily to create coverage; the new one ties their economics more directly to carrier-paid usage, creates an Advisory Council, and gives Helium roughly 141M HNT of operating and growth runway over 36 months.

Then, on June 2, 2026, Helium Mobile announced that Noble Mobile was acquiring its retail mobile business. Under the announced deal, Noble takes the subscriber-facing work—plans, billing, support, churn, SIM/eSIM operations, and fallback cellular exposure. On top of that, Helium is changing leadership: the old guard is leaving, new people are stepping in, and the full weight of proving HIP-149 now lands on HNT bagholders and the deployers expected to make it work.

With all that news landing rapid-fire, it is easy to lose the thread. But the resulting question is unusually specific for crypto: can newly minted HNT buy distribution into controlled Wi-Fi networks that carriers will pay to use? To underwrite that, we first need to clarify what counts as distribution and whether Nova Labs can deliver it for the Helium protocol.

Here, distribution means access to Wi-Fi networks that Helium can turn into paid usage—not Wi-Fi footprints for their own sake. Paid usage is narrower than Wi-Fi usage. It is traffic from a carrier or MVNO subscriber that joins an approved Wi-Fi network, passes authentication and quality checks, gets measured, and is accepted by the payer as billable offload. Finding locations with Wi-Fi is easy. Turning that capacity into traffic someone will pay Helium to authenticate, meter, and settle is the business.

The money path is simple. A carrier or MVNO pays to move eligible subscriber traffic from cellular onto trusted Wi-Fi. Helium authenticates the device, meters the traffic, and settles rewards or partner payments. Mobile data transfer is paid for in Data Credits. One DC equals $0.00001, so the public $0.10/GB benchmark equals 10,000 DC/GB. DC pay for transfer; HNT is burned when DC are created. That burn is the token's value-capture path.

The $0.10/GB figure is a benchmark, not a promise about every contract. HIP-143 allows Nova Labs to negotiate offload pricing without returning to governance for each deal, whether the contract is per-GB, flat-rate, capped, or more bespoke. HIP-149 then determines deployer rewards from the carrier revenue produced under whatever pricing arrangement Nova negotiates.

At $0.10/GB, a small site does not leave much money to negotiate over. Twenty paid GB/day produces 7,300 paid GB/year, or about $730/year of payer-side DC demand. That is $61/month of gross payer-side demand, not deployer revenue. Protocol-side, it becomes DC consumption and HNT burn as DC are created. Deployer-side, a 50% operator share leaves roughly $30/month for venue share, support, hardware, internet capacity, and overhead.

That envelope cannot absorb much one-by-one labor. One sales call, technician visit, support escalation, or venue negotiation can consume months of gross value before the site has moved enough paid traffic to matter.

The model begins to work when activation means configuring many sites that one counterparty already controls, or when one location produces hundreds of GB to multiple TB per day.

Traffic flowing through a location is not the same as billable offload. Helium does not monetize a venue because people walk through it. It monetizes a venue when carrier or MVNO devices join trusted Wi-Fi automatically, the traffic is authenticated and measured, and the payer accepts it as billable offload. Put differently, Helium can monetize a venue that is being managed by somebody. Ordinary Wi-Fi supply is not controlled Wi-Fi supply. The latter is scarce once you narrow the market to places where non-home mobile traffic recurs—and that is what Helium is now hunting, with HIP-149 dilution paying for the effort.

That control point often sits somewhere other than the venue. A managed Wi-Fi operator (e.g., Single Digits in hospitality and multifamily housing) may control access points across hotels, apartment buildings, student housing, senior living, or campuses, but it also owns the network, support contract, and customer relationship; Helium must bring carrier demand or payment administration the operator does not have. A cable operator with an MVNO (e.g., Comcast/Xfinity Mobile) may control millions of broadband gateways, but most sit in homes and generate little carrier-paid public offload. A campus IT department may control a dense daily population, but procurement and security review can turn activation into a calendar problem. A stadium or airport may have exceptional traffic while the useful contract belongs to the company already running wireless service there (e.g., Boingo).

In other words, Helium's addressable market is not a count of venues. It is the aggregate revenue unlocked by offload and related services across the telecom stack, where carriers, Wi-Fi operators, and venues each need something different from the same network.

Carriers need trusted offload. Wi-Fi operators need incremental monetization. Venues need a network that still works and a contract that still makes sense. HNT captures value only if Helium makes those motives compatible and turns the resulting traffic into billable Data Credit usage.

In that regard, the new leadership's most important job is to build relationships with managed Wi-Fi operators, cable operators with MVNOs, hospitality vendors, campus operators, apartment-connectivity providers, and companies that already hold venue wireless contracts, because one relationship can activate many sites. That is the brownfield strategy: begin with installed Wi-Fi and existing commercial relationships, then add carrier demand, authentication, metering, billing, and partner payouts instead of building every site from scratch.

That strategy is a pivot, not an obvious extension of the original Helium thesis. The network was bootstrapped by individuals installing hotspots on their own initiative and earning coverage rewards. Because many hosts reused space, power, and internet connections they already paid for, their incremental return hurdle could be very low; even modest rewards could pull new supply into the market. HIP-149 marks the point at which that bootstrap story stops being the investment thesis. The question is no longer how quickly Helium can add coverage, but whether it can secure and monetize Wi-Fi that somebody already controls. Many holders still talk about Helium as though more coverage were the thesis. Under HIP-149, that is backward-looking: the new thesis is commercial distribution into managed networks. Helium can still recruit individual deployers site by site in dense districts where no managed operator exists, but then it inherits the operator's job—site acquisition, configuration, monitoring, support, troubleshooting, contract compliance, and quality control.

Helium can disintermediate an operator in some locations and partner with one in others. The economic test is the same: can someone aggregate useful Wi-Fi supply for less than a carrier would otherwise pay for comparable authenticated offload?

A stadium with 100 independently installed devices is not equivalent to a stadium network designed around 100 access points. A designed network has planned placement, wired capacity behind the radios, coordinated settings, automatic login rules, monitoring, and one support owner. Without that coordination, phones crowd the same access points while others sit idle; channels interfere, internet links saturate, sessions fail, and the failure belongs to no one.

This is why managed Wi-Fi companies exist. Hotels, apartment buildings, student housing, campuses, hospitals, malls, airports, and venues hire operators or vendors to design, monitor, patch, troubleshoot, and upgrade Wi-Fi. Helium can connect that infrastructure to carrier demand and administer the resulting payments. Eligible carrier or MVNO devices can join automatically; Helium authenticates them, meters the accepted traffic, records the resulting Data Credit usage, and uses that accounting to calculate and pay the operator's agreed share. A managed Wi-Fi company serving hundreds of hotels, for example, can turn networks built for guests into a second revenue stream without rebuilding every location. But the operator still has to keep the access points, internet connections, venue permissions, and support operation working; Helium cannot make that operating work disappear.

Helium therefore has to make ordinary Wi-Fi trusted, measurable, billable, and supportable at a carrier cost below the next-best comparable source: an incumbent managed-Wi-Fi platform, a roaming or offload broker, a venue wireless contractor, or the carrier's internal alternative.

At Helium’s public benchmark of $0.10 per paid GB, carrier revenue must cover everything required to make traffic billable—from activation and support to internet capacity, venue terms and, where applicable, site acquisition. The figures below show how much carrier-accepted traffic each route needs to cover that bill.

The model assumes an independent offload seller (a managed Wi-Fi operator, venue contractor, or local aggregator) operates without Helium, contracts directly with a carrier, receives the full ten cents, and bears the route’s costs. This is both the competitive counterfactual Helium must improve on and the partnership baseline: Helium must contribute enough carrier access, authentication, billing, or aggregation to justify sharing the ten cents.

For each route, the model annualizes equipment and integration, adds fixed and per-GB operating costs plus any venue revenue share or minimum guarantee, and solves for paid GB per active location per day. The table shows the zero-profit threshold; the read-through adds the traffic required for a 20% operating margin. Only authenticated traffic accepted by the carrier as billable offload counts.

The table and exhibits below demonstrate one saved configuration of the Helium Offload Underwriting Lab. On the site, readers can select a supply route; change carrier pricing, traffic, equipment, acquisition, support, venue terms, and the required return; and watch the break-even traffic, cost per paid GB, margin, and deployment burden recalculate. There is no single sacred input. The point is to see which assumptions the economics can absorb and which ones break the case.

The ladder rises because every route adds another cost or claimant against the same ten cents. Existing controlled Wi-Fi reuses the routers, internet connection, monitoring, and venue relationship. A new SMB site adds selling, onboarding, configuration, and support. A dense overlay adds integration, equipment, internet capacity, monitoring, and enterprise procurement. A premium airport adds rights costs, a minimum guarantee, legal work, carrier coordination, and dedicated support.

The required traffic therefore rises from 7.1 GB/day to 82 GB/day, then 1.83 TB/day and finally 29.2 TB/day, because each route costs more to turn the same ten-cent gigabyte into billable supply.

Existing controlled Wi-Fi: Roughly 7.1 GB/day is the traffic of about 35 attached users at the model's 0.20 GB-per-user assumption. The row works only because the core network and venue relationship already exist: the operator is adding monetization to installed capacity, not financing a new network.

New SMB / public site: Roughly 82 GB/day requires about 274 attached users at the model's 0.30 GB-per-user assumption. That may be possible at an unusually busy gym, clinic, cafe, or retail node with repeat dwell time, but it is not a safe assumption for an ordinary storefront. At ten cents per GB, the bytes may be there while the sales and support budget is not.

Dense managed-network overlay: The model turns each daily visit into 0.10 paid GB after applying device eligibility, attachment, and usage assumptions. Zero profit therefore requires about 18,300 daily visits—roughly Madison Square Garden filling all 19,500 seats every day, Tuesday mornings included. A 20% margin requires about 27,400. The Garden is a crowd-size analogy, not the proposed venue: an arena carries an event calendar and rights costs that do not belong in the daily overlay case.

Premium airport: The model gives an Atlanta-like airport 296,000 daily passengers, 50% eligible devices, 30% attachment among eligible devices, and 0.60 GB per attached passenger. That produces 26.64 TB/day—below the 29.2 TB/day zero-profit floor and only 60% of the 44.4 TB/day 20% margin hurdle. The airport has the people, but the rights contract takes the economics.

Existing controlled Wi-Fi is a prize only where it sits under recurring non-home mobile demand. Hotels, campuses, retail sites, and transit networks can produce that traffic; suburban home gateways usually cannot. At a well-located site, the model reaches zero profit at 7.1 paid GB/day because the operator already owns and runs the network. Helium's pitch is access to carrier buyers the operator cannot reach efficiently on its own, not cheaper Wi-Fi.

New SMB is the opposite case. At 30 GB/day, a site creates only about $1.1k per year of network-level gross carrier spend before any payout split or operating cost. One sale, installation, monitoring plan, and support obligation all have to be financed from that amount. The route reaches modeled break-even near 82 GB/day, and even then the payout still has to be shared.

Helium's July 2026 restaurant data now gives that row an observed portfolio. Nearly 2,500 locations associated with 34 national brands moved more than 274,000 GB in one month: about 110 GB per site, or 3.7 GB/day on a 30-day basis. Coffee shops averaged about 7.3 GB/day; Chick-fil-A, the outlier, averaged 37.9. At ten cents, the broad restaurant average produces roughly $11 per site per month of gross carrier spend and Chick-fil-A about $114. A restaurant may still like the service because more reliable mobile ordering, loyalty, and payment flows protect its ordinary sales, but that is venue ROI rather than proof of operator economics. Against the cost screen, the portfolio average misses even brownfield zero profit, coffee shops sit on the line, and Chick-fil-A clears brownfield economics while reaching only 46% of the one-by-one SMB threshold.

Dense venues solve the traffic problem more readily than they solve the commercial one. A campus, hospital, mall, transit-adjacent property, or mixed-use site can produce enough recurring traffic to justify professional deployment. That works only if Helium, Nova, or a deployment partner can win the location without adding the premium-venue rights costs modeled in the next row.

Premium venues add a landlord to the traffic. A stadium or airport may already have a long-term wireless contractor controlling the Wi-Fi, carrier relationships, and venue contract. Helium cannot monetize those passengers or fans unless the contractor, the venue, or both let it connect to the network and the commercial arrangement. Rights fees, minimum guarantees, revenue share, support, legal work, and carrier coordination can consume the surplus before HNT sees it.

Boingo's 2020 10-K is a reminder of what that permission can cost. Premium-venue wireless contracts can last up to 25 years and may include revenue share, minimum payment guarantees, financial security guaranteeing performance, and substantial network build-out commitments. Stadiums and airports are not unclaimed sites waiting for Helium. The relevant question is not whether the building contains enough people; it is who already owns the right to monetize their traffic.

The arithmetic gets severe quickly. Every $100k per year of fixed venue rent, minimum guarantee, or rights cost consumes the gross revenue from 1M paid GB per year—about 2.7 TB/day—before support, internet or fiber capacity, partner payout, or operator margin. A $500k annual guarantee consumes 13.7 TB/day. A $1M guarantee consumes 27.4 TB/day.

Now scale that arithmetic to Helium. Generating $100M per year of gross carrier-offload spend at $0.10/GB requires about 1,000 PB per year, or 2.74 PB every day. The Hartsfield-Jackson traffic example produces less than $1M per year of gross carrier spend at that rate before premium-venue contract costs. One Atlanta-sized traffic case contributes less than 1% of the target.

Helium therefore needs large portfolios whose owners will accept terms that leave enough of the ten cents to keep each site operating; only then can the paid traffic appear on Helium and generate Data Credit usage and the associated HNT burn.

Put into deployment units, 2.74 PB/day equals about 295,000 existing controlled sites at the 9.3 GB/day 20% margin hurdle, 23,800 new small sites at 115 GB/day, 1,000 dense managed-network overlays at 2.74 TB/day, or 62 airports at 44.4 TB/day. Divide the first three routes among 50 partners and the average is still roughly 5,900 controlled sites, 476 new small sites, or 20 dense overlays per partner. The network can mix the routes. It cannot escape the need for portfolios.

One thousand dense overlays is not merely a deployment target. It asks Helium to capture a startling share of the plausible U.S. inventory.

Our market screen found about 1,000-2,250 core candidates—large campuses, major medical centers, malls and high-traffic retail centers, and transit hubs. Stretch the definition to include lower-confidence mixed-use and office districts and the range reaches 1,500-3,750. The $100M target therefore asks Helium to recruit roughly 44-100% of the core pool, or 27-67% of the expanded one. At the generous end, Helium still needs more than one in four candidates. At the constrained end, it needs essentially every core venue on the list.

And that comparison is still too kind. The 2.74 TB/day case assumes a managed-network overlay reaches a 20% modeled margin; the market count identifies candidates, not sites proven to have eligible traffic, reusable Wi-Fi, or workable commercial terms.

Dense venues can prove that controlled Wi-Fi produces paid carrier traffic. They cannot, by themselves, carry the scale thesis.

The cost screen therefore ends as a sales strategy. Helium will not reach petabyte-scale offload through isolated venue wins. It needs counterparties that can authorize dozens, hundreds, or thousands of locations in one decision. The next question is what those counterparties would need in return.

Why would Helium have a carrier relationship that an established Wi-Fi operator does not? Not because Helium runs Wi-Fi more cheaply. The cost screen says the opposite: a manager reusing an installed, well-used network can show a modeled cost below $0.10/GB. What that manager may lack is enough geographic reach or contract volume to justify a direct carrier integration. A carrier may not want a separate authentication system, billing process, and support relationship for every regional hotel, campus, or retail network.

Helium's proposed role is to pool those portfolios behind one carrier-facing system. The manager contributes controlled Wi-Fi, venue relationships, and day-to-day operations; Helium contributes aggregated carrier demand, authentication, metering, billing, and payout administration. The carrier gets one integration spanning many locations. The manager gets access to revenue it could not efficiently reach alone.

The ten-cent rate is the clearing constraint on that bargain, not the reason Helium uniquely has the carrier. The model above gives an independent operator the full $0.10/GB, while an actual partnership must divide that amount among Helium, the operator, possibly the venue, support costs, and required returns. If the split pays both layers, cooperation works. If it does not, adding Helium merely adds another claimant to the same ten cents.

Helium therefore has to aggregate twice: first individual sites into operator portfolios, then those portfolios into one carrier interface.

The reason to say yes differs by actor:

Companies that already know how to run Wi-Fi do not need lessons in Wi-Fi from Helium. They need a way to turn installed capacity into carrier-paid traffic without rebuilding the network or renegotiating every venue from scratch.

The underwriting question is whether the new leadership can sell each participant the specific thing it lacks: carriers need trusted offload, operators need incremental monetization, property owners need better economics or connectivity, and HNT holders need the resulting paid traffic to accrue to the token rather than only to Nova, vendors, or partners.

The easy part was selling HIP-149 to the people still holding locked HNT—the constituency Helium has left to call a community. Their vote secured roughly 141M HNT and 36 months to sign venues, activate hotspots, and announce partnerships. The hard part begins now: making the HNT leaving the vault produce more carrier-paid GB at places where subscribers repeatedly need offload.

Nick Carpinito's Blockworks Research article on HIP-149 proposes a useful accountability metric: incremental carrier burn per HNT drawn from the HIP-149 vault. Divide carrier-attributable HNT burn during the period by the HNT released from the vault. If the ratio rises, each HNT of dilution is buying more payer-funded network use; if it falls, the vault is spending faster than carrier demand is arriving.

Two further checks tell us whether the burn behind that ratio comes from real commercial partners and whether it can continue after subsidies expire: named traffic and unsubsidized retention.

First, named traffic. A partnership becomes evidence when Helium can attribute billable traffic to a partner that controls a real portfolio. The early names at least fit the profile. Ameriband connects enterprise Wi-Fi to carrier networks; in 2024 Helium announced plans to integrate more than 100,000 Ameriband-linked access points across retailers, grocery chains, venues, and other commercial sites. Talus builds city, campus, school, and private-wireless networks; its Redondo Beach conversion was reported to serve more than 2,000 users a day over the city's existing Wi-Fi. Mambo is the international example: it supplies the software that logs guests onto Wi-Fi, authenticates them, and lets Brazilian businesses and ISPs manage those networks; its reported 40,000-access-point footprint is intended to seed Helium's entry into the country. Each could open many controlled sites through one relationship, but paid GB/day by partner remains undisclosed. Until Helium publishes it, these names describe potential distribution rather than named traffic.

The restaurant release illustrates the distinction. Chick-fil-A, Starbucks, KFC, and Taco Bell identify where Helium traffic appeared, but the post does not say who opened those networks, whether the deployments came through chain-level contracts or individual franchisees, or which operator controls them. Thirty-four venue logos provide useful traffic context, but they do not necessarily represent thirty-four distribution relationships.

Second, unsubsidized retention. This diagnostic requires disclosure: HIP-149 calls for quarterly reporting of supplement-vault outflows, but that alone will not show whether a deployment works. For each named operator—or at least each comparable partner cohort—Helium should report active locations, carrier-paid GB, HNT or cash paid to the operator, vault-funded launch subsidies, and the share of locations still active after six and twelve months. Those figures produce two usable ratios: total partner compensation per paid GB and per active location, with subsidies included rather than parked elsewhere. Traffic and on-chain HNT rewards can verify part of the calculation; private contract terms and support costs cannot. If independent Wi-Fi managers renew and expand after the launch money expires, Helium has a commercial distribution pitch. Until then, investors are watching traffic, not partner economics.

Milestones should therefore be denominated in burn, not activity. Hotspots, throughput, and deployer count are operating statistics; they become investment evidence only when they produce paid GB/day and incremental carrier burn per HNT drawn from the vault. Taper and continuation reviews should be tied to those ratios. If carrier burn per HNT does not rise, HNT is funding activity rather than buying demand.

The bear case does not require the network to fail. It only requires the economics to accrue somewhere else. A controlled Wi-Fi operator may already sell offload directly. Residential gateways may add millions of theoretical locations and almost no useful non-home traffic. Premium venues may produce traffic but hand the surplus to whoever owns the rights. Carriers may push the price below $0.10/GB or bury it in flat-rate bundles. Under any of those outcomes, Helium can report more deployments while tokenholders finance software, services, and partner margins that accrue off-token.

HIP-149 is therefore not a coverage program. It is a roughly 141M-HNT attempt to buy contractual distribution into Wi-Fi networks Helium does not own through companies that can authorize, configure, or operate many networks at once: managed Wi-Fi operators, cable operators with MVNOs, hospitality and apartment-connectivity vendors, campus network managers, wireless-rights incumbents, chain-level Wi-Fi vendors, business ISPs, and local aggregators.

The partnership route works when those companies lack something Helium can supply—carrier demand, authentication, metering, billing, or payout administration—and when the ten-cent gross payment can still support both layers. Helium can also skip portfolio operators and recruit small sites itself, but that route works only where a district generates enough billable traffic for each location to clear roughly 82 GB/day at zero profit and about 115 GB/day before the model grants the operator a 20% margin.

If incumbent operators already monetize offload themselves, or Helium can recruit only low-traffic fragments, the ten-cent model fails for one of two ordinary reasons: the operator does not need Helium, or the site cannot afford another claimant.