Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HIP 106: Hotspot Bidirectional Coverage Requirement #870

Closed
hiptron opened this issue Jan 8, 2024 · 2 comments
Closed

HIP 106: Hotspot Bidirectional Coverage Requirement #870

hiptron opened this issue Jan 8, 2024 · 2 comments
Labels

Comments

@hiptron
Copy link
Collaborator

hiptron commented Jan 8, 2024

HIP 106: Hotspot Bidirectional Coverage Requirement

  • Author(s): @mawdegroot
  • Start Date: 2023-12-12
  • Category: Technical, Economic
  • Original HIP PR: #828
  • Tracking Issue: #870
  • Vote Requirements: veIOT Holders

Summary

Hotspots that can not provide bidirectional coverage are not useful for the IOT network as well as pose gaming risks. These risks are currently mitigated by the denylist operated by Nova Labs. 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.

Rendered View

https://github.com/helium/HIP/blob/main/0106-hotspot-bidirectional-coverage-requirement.md

@waveform06
Copy link
Collaborator

@waveform06
Copy link
Collaborator

HIP 106 was approved with 98% of the vote
https://heliumvote.com/iot/proposals/CBDNEgZiXqPYGpLQrMNZnJtKwbDuBDG6csAhPpBVDZNV

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants