What Is HIP 150? Mobile Deployer Rewards Explained

Short answer: HIP 150 passed and is active. It directs more Mobile emissions to data deployers, raises the target minimum from 50% to 80% of the payer rate, and creates optional reward multipliers from 1x to 5x for approved high-value locations. The changes that affect all Mobile data deployers were active for the August 31, 2026 UTC reward epoch.

Highlights for deployers

Executive summary

• All Mobile data rewards draw from a larger baseline pool. Nova Labs contributes its 24% Service Provider allocation to deployers, moving the Mobile data bucket from 70% to 94% of the Mobile sub-DAO slice. That is a 24-point move and a 34.3% relative increase in the scheduled baseline allocation. It does not guarantee that every hotspot's total earnings will rise.
• The deployer target minimum rises from 50% to 80% of what the payer pays. At the $0.10/GB base payer rate used in the HIP's examples, the target is $0.08 per rewardable GB. The ceiling remains three times the payer rate, or $0.30/GB at 1x.
• The Backstop now mints directly to the Deployer Data Reward Pool. HNT minted to support the target no longer passes through allocations for IoT, veHNT delegation, and the Service Provider bucket before reaching deployers.
• Selected high-value locations can receive a multiplier. The permitted range is 1x to 5x. Nova expects 1.5x and 5x as initial standard values, but eligibility requires Helium Plus enrollment, custodial ownership, commercial approval, and an issued multiplier ticket.
• A multiplier raises both sides of the transaction. The payer burns proportionally more Data Credits for that hotspot's rewardable traffic, and the deployer receives proportionally more reward weight. Rewardable byte counts themselves do not change.
• HIP 150 does not create traffic. It raises the target and scheduled allocation for rewardable data, but a hotspot with no rewardable data still earns no Mobile data rewards. Total earnings can fall if traffic disappears even while earnings per GB rise.
• The higher target and Service Provider contribution are time-limited. Deployers should not model them as permanent economics.

What did HIP 150 change?

What changes for a normal Mobile deployer?

A normal Mobile hotspot remains at 1x. It does not need to enroll in Helium Plus or apply for anything to participate in the changes that affect all deployers.

A ticketed hotspot carries more reward weight per rewardable byte than a 1x hotspot. While the 80% target binds, the additional payer burn raises target support in the same proportion, which is why the HIP describes a multiplier as self-funding in that condition. When the target does not bind, the shared deployer pool and total multiplied Data Credits determine the final rate, so HIP 150 does not promise a fixed uplift or haircut for a normal 1x deployer.

Its rewardable data now competes for a larger scheduled reward pool, and the Backstop target is higher and delivered more efficiently. At the $0.10/GB base payer rate used in the HIP:

• the target minimum is $0.08 per rewardable GB, up from $0.05;
• the ceiling remains $0.30 per rewardable GB;
• the actual epoch rate is not fixed at $0.08: the target can be missed when the Backstop's burn bound constrains the top-up, and the rate can also be higher;
• total earnings still depend on how many rewardable bytes the hotspot serves.

How does a hotspot get a multiplier?

The vote created the mechanism and allowed range. It did not grant 1.5x or 5x to every airport, stadium, convention center, or other self-declared venue.

A hotspot needs all of the following before it can operate above 1x:

• Helium Plus enrollment with a deployer agreement;
• custodial ownership of the on-chain hotspot and its rewards, so contractual remedies can be enforced;
• commercial and location approval by Nova Labs;
• a signed multiplier ticket accepted by the reward oracles.

Nova decides which locations are candidates and what multiplier they receive. A location move resets the hotspot to 1x until it is approved again. A normal reduction or return to 1x requires 30 days' notice, while abuse can result in rewards being withheld or clawed back and the multiplier being removed without notice.

Why does the move from 70% to 94% matter?

The Mobile data reward bucket receives 94% of the Mobile sub-DAO slice instead of 70%. This is not a 24% relative increase; it is a 24 percentage-point move, which makes the scheduled data pool approximately 34.3% larger than before:

94 / 70 - 1 = 34.3%

All else equal, a larger pool raises the HNT reward per unit of rewardable data. In a real epoch, however, all else is not equal. The rate per GB also depends on total rewardable traffic, the HNT price used to value rewards, and whether a Backstop top-up is needed and permitted by the burn bound.

Why did earnings reach 25.57 cents per GB?

The August 31 UTC epoch was the first reward result with HIP 150 active and T-Mobile offload removed network-wide. The 25.57 cents per rewardable GB result had at least three important drivers:

1. HIP 150 increased the scheduled deployer pool. The 70% to 94% move contributed directly to the increase.
2. Fewer rewardable bytes shared the pool. T-Mobile had represented 47.29% of rewardable Mobile traffic bytes over the 30 complete UTC days before the disconnect.
3. HNT appreciated. The dollar value of each HNT reward rose, pushing the reported dollar-denominated rate per rewardable GB higher.

The network-wide jump should not be attributed to 1.5x or 5x multipliers without evidence that multiplier tickets were active. Hotspots without a ticket remain at 1x.

Read Why did Helium Mobile earnings per GB jump to 25.57 cents? for the measured contribution of each driver, and the August 28 carrier-offload event notes and August 31 follow-up for the underlying traffic change.

Is the 80% target guaranteed?

No. It is a target minimum inside a bounded mechanism, not an unconditional promise of a fixed dollar rate.

• The target is a percentage of the payer rate, so it falls if the base payer rate falls.
• Only rewardable data counts. No rewardable traffic means no data reward.
• The Backstop may not exceed recent HNT destruction.
• The final observed network-wide rate can sit above the target; it was 25.57 cents per rewardable GB for the August 31 epoch.
• The earnings ceiling remains three times the payer rate at each hotspot's multiplier.

Does a higher rate per GB guarantee higher total earnings?

No. A deployer's total data earnings are driven by both rate and volume. A hotspot can earn more per rewardable GB but less in total if it serves substantially fewer rewardable gigabytes.

This distinction matters after the T-Mobile offload removal. The remaining pool was shared across fewer rewardable bytes, raising the network-wide rate per GB, but hotspots that lost a large amount of T-Mobile traffic may still see lower total earnings.

How long do these changes last?

• 80% target minimum: one year from activation, with a second year pre-authorized unless it is cut short. After the applicable period, the target returns to 50% unless another HIP changes it.
• Nova's Service Provider contribution: runs through July 31, 2027. Nova may extend it once for another year. Ending it earlier or otherwise changing it requires another HIP.
• Per-hotspot multipliers: remain governed by each hotspot's active ticket, location status, agreement, and the 1x to 5x range.

The step from an 80% target back to 50% would be a 37.5% reduction in the target. Long-term deployment models should account for the planned step-down instead of assuming current support continues indefinitely.

Who funds the higher deployer support?

The package redirects value rather than treating the higher target as free:

• Nova Labs contributes its Service Provider rewards. That 24% allocation moves to Mobile data deployers while the contribution is active.
• The Backstop is delivered directly. IoT and veHNT holders keep their shares of the normal emission schedule but no longer receive shares of Backstop HNT minted specifically to support Mobile deployers.
• Nova pays the additional Data Credit burn for multiplied traffic. That is why the multiplier raises both payer cost and deployer reward weight.
• The higher Backstop target can re-emit more recently burned HNT when a top-up is needed. The Backstop is capped so this mechanism cannot increase net supply by itself, but it can reduce how much HNT is net burned. HIP 149's separate operations and growth supplement is unchanged.

What does HIP 150 not change?

• The base payer rate remains a commercial parameter set by Nova Labs under HIP 143.
• The rules determining whether data is rewardable do not change.
• The earnings ceiling remains three times the payer rate.
• The 6% veHNT allocation from the normal emission schedule remains.
• IoT's share of the normal emission schedule and its internal allocations remain.
• HIP 149's operations and growth supplement and Advisory Council oversight remain separate and unchanged.

FAQ

Sources and related reading

• HIP 150: Mobile Deployer Prioritization
• Official HIP 150 vote summary
• HIP 150 vote result on Helium Vote
• Helium Mobile oracle 4.6.0: HIP 150 implementation
• Helium sub-DAO 0.2.47: HIP 150 on-chain implementation
• HIP 82: Mobile service-provider rewardable data limits
• What is HIP 149?
• Why did Helium Mobile earnings per GB jump to 25.57 cents?
• Demand Sampling and unrewarded data
• T-Mobile Offload via Ameriband Is Ending: event notes and outcome
• Official Helium Discord

Last updated September 2, 2026, using the final HIP 150 text, vote result, implementation outcome, and the first active reward epoch.