Discord6 months ago

Helium Network Update: New HIPs for MOBILE and IOT Governance

  • HIP 98 introduces quality of service standards and an "Acceptable" speed tier for the Helium MOBILE Network.
  • HIP 103 proposes a new MOBILE Oracle framework and adds three new Oracles for hotspot rewards.
  • HIP 105 amends HIP 85 by creating separate Hex Limits for Outdoor Wi-Fi and Outdoor CBRS in MOBILE.

@Community, @veMOBILE Voter, @veIOT Voter, Your Voice Matters! 📣

After several exciting votes last week, the Helium Network continues to iterate. New HIPs 98, 103, 105, and 106 are now ready for your vote.👇

HIP 98: MOBILE SubDAO Quality of Service (QoS) Requirements

This HIP formalizes quality of service standards (QoS) requirements for the Helium MOBILE Network. Previous QoS requirements were implemented for the MOBILE network without community input and vote.

It also introduces an "Acceptable" speed tier with a 0.75X multiplier, aiming to reward moderate internet speeds of 5G hotspots. Speed test results will be categorized into one of four tiers - Good, Acceptable, Degraded, Poor, and Fail.


HIP 103: MOBILE Oracle Hex Boosting

This HIP establishes a new MOBILE Oracle framework for Hotspot rewards and adds three (3) new Oracles.

  • Footfall Oracle: incentives deployments in areas that have heavy footfall traffic
  • Land Type Oracle: discourages deployments that cover empty fields and bodies of water
  • Urbanization Oracle: encourages deployments in urbanized areas

If passed, this HIP proposes that Service Providers & Subscribers can benefit from a coverage map of more useful radio/wi-fi coverage. Radio/Wi-Fi Deployers can benefit from increased rewards for providing coverage in areas where this type of coverage is needed.


HIP 105: Modification of MOBILE subDAO Hex Limits

This HIP is an amendment to HIP 85, the author of this HIP proposes to create separate Hex Limits for both Outdoor Wi-Fi and Outdoor CBRS.

HIP 85 aimed to restrict Modeled Coverage Points (MCP) for outdoor radios, without specifying whether they were CBRS or Wi-Fi. As a result, it counted the top three signals from any source within each res12 hex. HIP 105 intends to modify this approach by allowing up to three CBRS and three Wi-Fi signals to earn MCP within each res12 hex.


HIP 106: Hotspot Bidirectional Coverage Requirement

This IOT HIP proposal proposes to move the bidirectionality metric that is currently enforced by the denylist to the PoC pipeline.

This implementation also carries the added benefit of a more responsive system for Hotspot owners to be able to deploy coverage and participate in PoC rewards sooner.


If you can participate in MOBILE or IOT governance, you can cast your votes using the governance icon in the Helium Wallet App or at https://heliumvote.com/. If you don't already have veMOBILE or veIOT, you can lock your MOBILE or IOT using the governance icon in the Helium Wallet App. 🗳️


📣 Related news

Loading news...

💼 DePIN Hub Newsletter

We bring you real world use cases of web3 through DePIN. And btw, you can generate passive income along the way!