-
Notifications
You must be signed in to change notification settings - Fork 408
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
HIP23: Decouple Consensus From Gateways #101
Comments
CG is currently the only incentive for lone wolf gateways to be on the network - they dont earn otherwise. this hip would kill that incentive. hips should attempt to solve one of two core problems for the network: 1- increase # of gateways / supply of network coverage or 2- increase demand for data usage. i think this hip does the opposite. while it might be an improvement, current net effect is likely negative. it is something to revisit when the network is more mature. |
With the merger of #111, is this HIP still relevant? Should this be rolled into a "validators phase 2" proposal? |
Yes @jamiew it needs to be renamed / reformed. It would be helpful if some of the more "finalized" concepts around validators could be updated accordingly as well. |
Propose closing this as stale @jamiew? |
Author(s): @cvolkernick
Initial PR: #97
Start Date: 2020-12-15
Category: Technical
Rendered view:
https://github.com/helium/HIP/blob/master/0023-decouple-consensus-from-gateways.md
Summary:
This proposal changes the structure & process involved in forming consensus on the network, primarily by separating concerns of miners (providing verifiable coverage) and the consensus group (securing the network and forming blocks).
The text was updated successfully, but these errors were encountered: