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 112: Scaling IOT Hotspot Assert Fees #931

Closed
hiptron opened this issue Mar 5, 2024 · 1 comment
Closed

HIP 112: Scaling IOT Hotspot Assert Fees #931

hiptron opened this issue Mar 5, 2024 · 1 comment
Labels
economic Economic HIP IOT rejected HIP was rejected through voting technical Technical HIPs

Comments

@hiptron
Copy link
Collaborator

hiptron commented Mar 5, 2024

HIP 112: Scaling IOT Hotspot Assert Fees

  • Author(s): Andy Zyvoloski
  • Start Date: 2024-03-05
  • Category: Economic, Technical
  • Original HIP PR: #912
  • Tracking Issue: #931
  • Vote Requirements: veIOT Holders

Summary

This HIP proposes allowing one (1) free IOT assertion per rolling 365 epoch period, including the initial assertion. Any additional assertions conducted within the 365 epoch rolling period will be required to pay a $10 fee in IOT burn.

Rendered View

https://github.com/helium/HIP/blob/main/0112-scaling-iot-location-assert-fees.md

@waveform06 waveform06 added technical Technical HIPs economic Economic HIP IOT discussion labels Mar 5, 2024
@waveform06 waveform06 added rejected HIP was rejected through voting and removed voting now discussion rejected HIP was rejected through voting labels Apr 25, 2024
@hiptron hiptron closed this as not planned Won't fix, can't repro, duplicate, stale Apr 29, 2024
@waveform06
Copy link
Collaborator

waveform06 commented Jul 8, 2024

HIP 112 was rejected by the community on 24th April 2024 with a failing rate of 57.47%
https://heliumvote.com/iot/proposals/F7PCzKZre5bKaAX3yV9f2tWrLXMtR8J4mAY3iuCg7ejS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
economic Economic HIP IOT rejected HIP was rejected through voting technical Technical HIPs
Projects
None yet
Development

No branches or pull requests

2 participants