What Is HIP 149?

Short answer: HIP 149 asks veHNT voters to approve a package with two especially large consequences: about 141M new HNT minted over 36 months to a Nova-administered operations and growth vault, and retirement of Proof-of-Coverage rewards on both Mobile and IoT. It also adds a Mobile data deployer target minimum near $0.05/GB at the current approximate payer rate, a 3x upside cap, and a 7-seat Advisory Council to oversee the supplement.

The controversy is not abstract. HNT holders and hotspot owners are being asked to accept dilution and possible market pressure in exchange for a funded growth plan. IoT hotspot owners are also being asked to move away from PoC rewards even though many IoT hotspots currently earn little or no data-transfer rewards.

What matters most?

What are people voting on?

HIP 149 is not one small parameter change. It is a four-part package, executed in one program upgrade after the Advisory Council is seated.

Why is HIP 149 being proposed?

HIP 149 starts from the view that Helium's original reward model was built for an earlier phase of the network. In that phase, PoC helped bootstrap coverage before there was much demand. The proposal treats the network as being in a different phase now: carrier offload demand exists, but rewards and operating resources need to follow actual usage.

The current HIP text names three core problems:

• Deployer earnings are no longer well anchored to revenue. Traffic grew, HNT issuance stayed fixed, and HNT price fell, so the old $0.50/GB target no longer reflected what deployers were actually earning or what carriers were paying.
• PoC rewards pay for existing coverage rather than user-serving traffic. Useful carrier traffic becomes the central reward signal.
• Operations and growth need multi-year resources. Carrier expansion, deployer programs, engineering, and international growth need a predictable runway rather than annual funding uncertainty.

Mario Di Dio's June 25 Discord message framed the same idea more directly: after three town halls and weeks of community feedback, the core proposal remained the same: PoC retires, deployers earn based on real carrier traffic, 141M HNT over 36 months funds expansion, and the community can halt the supplement through governance.

What changed in the recent HIP updates?

The HIP has changed materially since the early June discussions. Recent commits on June 24 and June 25 added or clarified several important mechanics:

• Voting requirements: a 67% support threshold and a 100,000,000 veHNT quorum.
• Deployer upside cap: the Mobile deployer earnings cap was raised from 2x to 3x the payer rate.
• Advisory Council design: the council structure, information rights, curtailment process, compensation, vacancies, removal rules, and confidentiality documents were expanded.
• Receiving Entity commitments: the HIP now includes a Receiving Entity Agreement covering monetization guidelines, non-compete language, DC burn alignment, and long-term alignment.
• Service Provider Rewards: the HIP clarifies that the 24% Service Provider allocation stays unchanged.
• No claim to unminted tokens: no person or entity has rights to supplement HNT that has not actually been minted and transferred.

If you read an older discussion thread or event note, check the current HIP text before voting. Some of the biggest governance details were added after the early town halls.

What happens to Mobile deployer earnings?

Mobile data deployers would earn based on rewardable data delivered, not PoC. The proposal keeps the Mobile data bucket at 70%, then adds a revenue-linked band around deployer earnings:

• Target minimum: deployer earnings target at least 50% of the carrier payer rate per GB.
• Current example: if Nova sets the payer rate near $0.10/GB, the target minimum is about $0.05/GB.
• Upside cap: if HNT appreciation makes deployer earnings exceed 300% of the payer rate, the excess is redirected to veHNT stakers.
• Burn bound: the floor top-up is capped by recent HNT burned, so Decision 1 alone is designed not to increase net HNT supply.
• Not a hard per-epoch guarantee: after a sharp HNT price drop, the target can fall short for 1 to 2 weeks until the burn average catches up.

This is the "tighter" deployer economics tradeoff. The proposed floor is lower than the historically subsidized $0.50/GB target, but it is closer to what carriers actually pay today and can rise if payer rates rise.

At current conditions, this is one of the clearest positive pieces for Mobile data deployers. As of June 24, 2026, Mobile hotspots were paid about 3.99 cents/GB, with a 7-day average near 3.89 cents/GB and a 28-day average near 5.86 cents/GB. If the floor works as designed and the burn-bound limit allows it, useful Mobile data deployments should receive support toward the target minimum.

Does the $0.05/GB floor set a floor for HNT price?

No. The $0.05/GB figure is about deployer payout per GB at the current approximate payer rate. It is not a guarantee that HNT itself will trade above any price.

The HIP's formula uses HNT price to calculate how much HNT is needed to meet a dollar-denominated deployer target. That means lower HNT prices can require more HNT to deliver the same dollar value, subject to the burn-bound limit.

What happens to Proof-of-Coverage?

HIP 149 retires PoC on both Mobile and IoT.

For Mobile, the practical shock is smaller than on IoT because Mobile rewards have already been mostly about carrier data, and many Mobile deployments have not seen meaningful PoC rewards for months. Hotspots that carry useful carrier traffic can still participate in the 70% Mobile data deployer bucket, with the new target-minimum mechanism described above.

For IoT, the impact is much sharper. Data transfer continues at the existing $/DC peg, but PoC is retired. Since real IoT usage has not taken off at the same scale, many IoT hotspots still live mostly on PoC rewards. In the June 24 UTC epoch, ending June 25, 2026 at 00:00 UTC, 114,267 of 163,607 rewarded IoT hotspots received only PoC rewards and no data rewards. If HIP 149 had already been live and the same usage profile applied, those 114,267 hotspots would have received no rewards for that reward period.

What is the 141M HNT supplement?

Decision 2 authorizes a new HNT mint for operations and growth: about 141M HNT over 36 months.

• about 70.6M HNT over the first 12 months, at a flat rate near 196,000 HNT per day;
• about 70.6M HNT over the next 24 months, tapering linearly to zero;
• a fully bounded schedule set at deploy, with hardcoded end points;
• an effective max supply increase from about 206M HNT to about 347M HNT;
• a public on-chain vault whose balance and outflows should be visible.

The supplement does not flow to hotspot rewards. The stated uses are international carrier expansion, deployer programs, engineering, ecosystem grants, regulatory work, and core operating costs.

Does the 141M HNT mint happen all at once?

No. It is a scheduled 36-month supplement. It also does not start immediately after a yes vote. The Council is seated first, then there is a two-week pre-mint diligence window. If the Council objects during that window, it can recommend a curtailment vote before minting starts.

This does not remove dilution risk. The supply path is still large and explicit, which is why HNT holders are paying close attention. It means the dilution is scheduled rather than immediate.

Can Nova sell the HNT?

The Receiving Entity Agreement allows the possibility of supplement HNT sales. The Receiving Entity commits, in good faith and where commercially practical, to prefer OTC sales over open-market or exchange sales, seek reasonable lockups on OTC purchasers, and report supplement sales activity to the Council in an aggregated way when legal and commercial limits allow.

That is an important distinction. The HIP adds oversight and reporting commitments, but it does not give the public a live, fully detailed operating treasury plan. The Council is the mechanism proposed to inspect sensitive details without requiring every carrier or treasury detail to be public.

What is the Advisory Council?

The Council is the proposed oversight body for the operations and growth supplement. It has 7 seats:

• 5 community-nominated seats, confirmed by veHNT-weighted vote;
• 2 Receiving-Entity-appointed seats, appointed by the Receiving Entity, currently Nova Labs;
• public member identities, with no anonymous members;
• community-seat compensation totaling 1.25% of the supplement, minted directly to community members' wallets over time;
• confidential information rights, including category-level financials and insight into payer-rate negotiations;
• the ability to demand disclosure, publish dissent, recommend course correction, and escalate to a community curtailment vote;
• a vacancy guardrail: if fewer than two community-nominated members are seated, the Council cannot act and the supplement mint pauses until at least three community-nominated members are seated.

The Council cannot directly spend funds, block individual transactions, or override Nova's HIP 143 payer-rate authority. Its strongest tool is escalation: it can trigger a community vote to reduce, pause, or halt the supplement.

Can the community stop the supplement later?

Yes, but not by a single Council action. The Council can recommend curtailment, which then triggers a community vote. A Council-raised curtailment vote can reduce, pause, or halt the supplement with a simple majority of voted veHNT and a 100,000,000 veHNT quorum.

This is intentionally asymmetric: approving HIP 149 requires a 66.67% supermajority, while a Council-escalated vote to reduce or halt the mint requires a simple majority. Any increase, restart, acceleration, or expansion would still require a normal community HIP and higher authorization.

Why is the vote bundled?

The four decisions are linked. The Council exists to oversee the supplement; the supplement funds operations and growth; PoC retirement and revenue-linked deployer rewards are part of the same program upgrade. A single yes/no vote means voters cannot approve only the deployer floor while rejecting the supplement, or approve the supplement while rejecting the Council.

That bundling is one of the drawbacks. A voter who likes three parts but dislikes one still has to vote on the entire package.

What does HIP 149 not change?

• HIP 20's halving emission schedule continues, although the supplement raises the effective maximum supply path.
• The Mobile and IoT sub-DAO structure remains.
• veHNT lockups, multipliers, and voting mechanics remain.
• The 6% delegator allocation remains.
• HIP 143's commercial payer-rate authority remains with Nova.
• The IoT $/DC peg for data transfer remains.

Potential impact by group

What are the main potential benefits?

• Rewards move toward actual usage. Deployers carrying real carrier traffic become the focus.
• Mobile deployers get a dollar-linked target minimum. Recent Mobile earnings per GB have been below the proposed target, so useful deployments get a clearer support mechanism than a purely fixed HNT pool if the burn-bound limit allows it.
• HNT holders get an upside-sharing path through veHNT. Above the 3x deployer cap, excess deployer-pool value flows to stakers rather than being minted or burned.
• Growth funding becomes explicit. The proposal creates a bounded, visible funding schedule instead of recurring ad hoc requests.
• Community oversight becomes formalized. The Council gets information rights and a curtailment path.

What are the main risks?

• Dilution and price pressure: the supplement is large, raises the effective HNT supply ceiling by about 141M HNT, and HNT has already seen a sharp post-announcement decline before any supplement tokens have been minted or sold.
• Execution risk: carrier growth, useful coverage, payer-rate improvement, and international expansion still have to happen.
• Confidentiality risk: some carrier and treasury details will not be public, which means the Council has to earn trust.
• Payer-rate dependence: deployer economics follow the payer rate Nova sets under HIP 143; the Council gets insight but not direct authority.
• IoT reward cliff: PoC retirement is especially important for IoT, where a large share of rewarded hotspots still earn from PoC and many would receive no rewards in periods where they have no data usage.
• Bundling: voters cannot split the four decisions.

What did the recent events clarify?

The public calls and AMAs help explain why the proposal exists and what the community challenged:

• The June 4 announcement introduced the shift from bootstrap coverage toward useful carrier traffic, the deployer floor, and the governance plan.
• The June 4 Discord Q&A focused on funding, trust, why token funding was chosen over equity, and how the Council could inspect details under confidentiality.
• The June 10 town hall expanded the carrier pipeline case, including brownfield deployments, offload demand, advisory council transparency, and community questions.
• The June 17 Blockworks fireside chat framed Nova as an infrastructure and protocol company after the Helium Mobile transition, with carrier-grade Wi-Fi, quality telemetry, international expansion, and HIP 149 as the focus.
• The June 18 town hall covered HIP revisions, the Helium Mobile sale, council representation, HNT and deployer economics, carrier offload rates, Mexico expansion, IoT operations, and the Blockworks report reference around pricing stability.

What should voters read before deciding?

Start with the official HIP text. Then read the vote summary, the official proposal page, and the event notes if you want the community Q&A context.

For voting, the key question is not only whether Helium needs to move from PoC to useful carrier traffic. It is whether this specific package is the right tradeoff: 141M HNT of bounded growth funding, current Nova payer-rate authority, a 7-seat Council, a deployer floor and cap, and PoC retirement all approved together.

HeliumGeek is not telling you how to vote. The goal of this page is to help you read the proposal with the major mechanics, benefits, and risks in one place.

FAQ

Sources and related reading

• HIP 149: Helium Utility and Emissions Realignment
• Recent HIP 149 commit history
• HIP 149 vote summary
• Helium Vote PR for HIP 149
• Official Helium proposal page
• HIP 149 proposal on Helium Vote
• The Next Era of Helium
• Blockworks Q1 2026 Helium Token Holder Report PDF
• HeliumGeek IoT reward stats and IoT data reward distribution for the June 24 UTC epoch ending June 25, 2026 at 00:00 UTC, and Mobile earnings per GB chart through June 24, 2026
• HeliumGeek Event Notes
• Related FAQ: Why is HNT price going down after HIP 149?
• Official Helium Discord

Last updated June 25, 2026, using the current HIP 149 text, recent GitHub commits, official proposal page, vote summary, HeliumGeek event notes, and Mario Di Dio's June 25 Discord message.