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 65: Vendor HNT Lockup #437

Closed
edakturk14 opened this issue Jun 29, 2022 · 2 comments
Closed

HIP 65: Vendor HNT Lockup #437

edakturk14 opened this issue Jun 29, 2022 · 2 comments

Comments

@edakturk14
Copy link
Contributor

edakturk14 commented Jun 29, 2022

HIP 65: Vendor HNT Lockup

Addendum to HIP-19

Summary

This HIP seeks to discourage manufacturers from participating in or supporting large-scale cheating Hotspot deployments.

Manufacturers will be required to deposit Helium Network Tokens (HNT) in an escrow account in proportion to the rate at which they add new Hotspots to the network. These deposited tokens can be forfeited if the manufacturer is found to have been complicit in a scheme to receive network rewards for dishonest deployments, or returned to the manufacturer on a regular schedule after a waiting period in good standing.

*HIP-19 is the process by which manufacturers of Helium Hotspots can apply for and receive cryptographic permission to add new gateways (Hotspots) to the Helium network.

Rendered View

https://github.com/helium/HIP/blob/main/0065-vendor-token-lockup.md

@vincenzospaghetti
Copy link
Contributor

Update on HIP 65 (10/5): the most recent discussion around this HIP has concerned "shutdown economics" and the "tax" or the impacts of an economic cost on manufacturers. There's a discussion that this cost may be pushed onto consumers. Remaining questions around what happens to HNT (especially in an event where a manufacturer is gaming or has forfeited.)

@vincenzospaghetti
Copy link
Contributor

The MCC has voted to withdraw this HIP. Anyone can review the decision of the MCC through the MCC Meeting Notes here.

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

2 participants