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 57: PoC Rewards Establishment Period #376

Closed
edakturk14 opened this issue Mar 18, 2022 · 6 comments
Closed

HIP 57: PoC Rewards Establishment Period #376

edakturk14 opened this issue Mar 18, 2022 · 6 comments
Labels
closed/withdrawn stale Old and needs attention

Comments

@edakturk14
Copy link
Contributor

edakturk14 commented Mar 18, 2022

HIP 57: PoC Rewards Establishment Period

Summary

In order to combat PoC rewards gaming, the process of ‘spoofing’ or ‘gaming’ a Hotspot to earn disproportionate rewards must be economically unsound. Among a range of solutions, the existing denylist and HIP-40 offer a means to remove Hotspots that don’t provide legitimate coverage. However, there is sufficient time after onboarding a Hotspot where it remains economically viable to spoof a location and game PoC rewards before a Hotspot in question can be confidently identified and added to a denylist.

If approved, this proposal would introduce a Hotspot ‘establishment period’ such that the network can better learn about a Hotspot’s deployment immediately following a location assertion. This period would be defined initially as 15 days and 10 successful witnesses, as set by a chain variable. A Hotspot’s PoC rewards and witnesses of its beacons would be throttled to 10% of what would be its normal earnings until both of these conditions are met. Data rewards would be unaffected. As the network improves its ability to understand a Hotspot’s location or as reliance on denylists are reduced, these chain variables could be adjusted.

Rendered View

https://github.com/helium/HIP/blob/main/0057-poc-rewards-establishment-period.md

@mkultr44
Copy link

mkultr44 commented Mar 26, 2022

For people with really good locations and coverage, the very things you want to incentivise, that would increase the ROI by about 50% though......

@alphaqt
Copy link

alphaqt commented Apr 3, 2022

This seems like a bandaid. The real problem is that there is no method currently to actually validate the location of a Hotspot. The companies that manufacture Helium Miners should start including a GPS receiver to accurately record a hotspots true location to keep people from asserting a location different than the physical hotspot. Once there are enough hotspots with GPS coordinates, the remaining hotspots could be easily located via triangulation of the beacons. We need to move away from bandaids and towards solutions that elevate the Miner network to one that is impervious to scamming.

@mkultr44
Copy link

mkultr44 commented Apr 5, 2022

you can spoof gps too, wouldn't change anything

@wolfenhawke
Copy link

I think the way to increase the reliability of this is to use time. With time we know which hotspots are not on a deny list, are true, and even what their average behavior is like. When a new miner comes online, a time and witness window can be used along with this historic information to validate what is being seen.
Someone being honest for 15 days then being dishonest? The algorithm can see when the change occurs that the new witness pattern is an anomaly. Someone self witnessing with a bunch in the basement? History wouldn't have the bunch in the basement.
Then the gaming is looking for those nests where maybe a spoofer was able to get many in the network and looking like normal -- but even then, it will show up because once legitimate units reach the area suddenly a whole nest is not being witnessed like they should be.
Time as in average of continuous operation is like integrating over a long period - it provides an interesting additional dimension of information.

@HansaFL
Copy link

HansaFL commented Sep 3, 2022

This is a good idea, but it needs "teeth". Proper validation using other methods will be needed to prove Hotspot locations.

@vincenzospaghetti
Copy link
Contributor

This HIP has been stale for some time. We are moving to close it, as there as been no more discussion in the community Discord. If you would like to reopen this HIP, please submit a new PR with changes. Thanks for your contribution to the Helium Community!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed/withdrawn stale Old and needs attention
Projects
None yet
Development

No branches or pull requests

6 participants