Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save waveform06/0c6357d176852a93adf1811dafe9c250 to your computer and use it in GitHub Desktop.
Save waveform06/0c6357d176852a93adf1811dafe9c250 to your computer and use it in GitHub Desktop.
HIP 106 Hotspot Bidirectional Coverage Requirement - vote text
# HIP 106: Hotspot Bidirectional Coverage Requirement
## Summary
This proposal proposes to move the bidirectionality metric that is currently enforced by the denylist to the PoC pipeline. This will result in hotspot owners being signaled of the issue faster and subsequently will signal hotspot owners that the issue has been resolved without waiting until the next denylist iteration.
- Authors: [Groot](https://github.com/mawdegroot)
- Full HIP Text: [HIP 106](https://github.com/helium/HIP/blob/eaa6c9a243e71913673762273d68101744d1bf96/0106-hotspot-bidirectional-coverage-requirement.md)
## Proposal Details
Hotspots that cannot provide bidirectional coverage are not useful for the IOT network as well as posing gaming risks. These risks are currently mitigated by the denylist operated by Nova Labs. By moving the bidirectional coverage check from the denylist to the proof of coverage pipeline it will signal a hotspot owner of a problem significantly faster. And the hotspot will also be considered for rewards significantly faster after the issue has been resolved. Hotspots that were affected and resolved will not have to wait for a scheduled denylist removal update and will start participating in PoC rewards immediately.
***
## Approval Requirements:
* This HIP is considered approved if 67% of the voting power is reached.
* This HIP must reach the quorum of 100,000,000 veIOT to be considered valid.
***
## Review
Community debate on these topics can be found on the Helium Discord. Please review any necessary discussion or consult with other community members to inform your position before voting. See the #hip-106-hotspot-bidirectional-coverage-requirement channel for more details.
Additionally, these changes may have been discussed further in recent Community Calls. Video for these calls is available to review in the [community call agenda doc](https://helium.foundation/community-call).
***
## Resources
Additional information about the Governance process can be found in [Helium Docs](https://docs.helium.com/governance).
To participate in future Governance calls, please join the Community monthly on the last Wednesday of each month at 16:00 UTC.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment