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 42: Beacon/Witness Ratio - Witness Reward Limit #303

Closed
jamiew opened this issue Oct 27, 2021 · 2 comments
Closed

HIP 42: Beacon/Witness Ratio - Witness Reward Limit #303

jamiew opened this issue Oct 27, 2021 · 2 comments

Comments

@jamiew
Copy link
Contributor

jamiew commented Oct 27, 2021

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.

@disk91
Copy link
Contributor

disk91 commented Jan 9, 2022

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.
In a such situation, we have a double pain, beaconing + witnessing
This also touch Hotspot when resync or touched by helium issues are we have currently manys: they are down, so they not beaconning so once back, they won't witness before a while.
How do you manage these situations ?

jamiew referenced this issue Jan 10, 2022
* HIP-42 revision

* revision 3
@vincenzospaghetti
Copy link
Contributor

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.

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

No branches or pull requests

3 participants