-
Notifications
You must be signed in to change notification settings - Fork 407
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 42: Beacon/Witness Ratio - Witness Reward Limit #303
Comments
I have some remark on this, my hotspot are not currently Beaconing on regular basis, I mean I have some hotspot working normally with 8 days w/o beaconing. This is realated to the beacon distribution and the relayed challenger not able to receive witnesses information. |
Summary of this HIP - We are closing this HIP for now. The proposal went through a temperature check but will come back as an IOT subDAO proposal since oracles and off-chain POC will be implemented. |
Rendered view
https://github.com/helium/HIP/blob/master/0042-beacon-witness-ratio-witness-reward-limit.md
Summary
This proposal intends to enforce a hard limit on the number of witness receipts a hotspot is capable of claiming based on how well the hotspot is able to perform all functions related to Proof of Coverage (PoC). The two major componets to PoC, is the hotspots ability to beacon and witness. Beaconing is the mechanism used by the blockchain to determine if a hotspot has the capability to perform downlinks and also provides a means to determine coverage without the need for devices. Downlinks are integral for a LoRa based Internet of Things (IoT) network since they wouldn't be able to join if they couldn't receive downlinks for example.
The primary function of this proposal is to tie beacons to witnesses to ensure that setups benefit the network and not just the individual hotspot.
A secondary function of this proposal is to combat the most recent gaming associated to the following #poc-discussion on Discord.
The text was updated successfully, but these errors were encountered: