-
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
HIP36: Blockheight Chainvar Activation #260
Comments
* Create 0036-blockheights-instead-of-time.md * Add HIP PR link * Add most recent halving block to HIP20 adjustments * Update statuses * Related to #260 * Add new HIP36 to README TOC Co-authored-by: Jamie Wilkinson <[email protected]>
@bfx any updates on this proposal? Seems especially relevant with ongoing conversations around on-chain voting & signaling |
Hey @jamiew, no updates yet. There was some constructive feedback in Discord and mainly evan shared having some doubts and saw a need to further refine it. He posted to share his perspective on the issue here, but I guess it must have fallen through the cracks somewhere. I'll try and see if he can do this still. |
Hi @Bx64, This HIP has been open for some time without any noticeable action. We are going to move to close this HIP. Please let us know if there is a reason not to. |
Info
#hip-36-blockheight-chainvars
on https://discord.gg/heliumRendered view
https://github.com/helium/HIP/blob/master/0036-blockheights-instead-of-time.md
Summary
At the time of writing, most (if not all) blockchain variables and implementations are activated manually by the Helium team, requiring active intervention from the team and have a time-based activation. The active intervention can, for the greatest part, be avoided by enabling auto-activation of variables at certain blockheights. This has been the standard for most blockchain projects. One example is the bi-yearly halving of HNT rewards agreed to in HIP20 which should be integrated with blockheights rather than be defined by moment in time for its activation - and in the future, hopefully any change of blockchain variables can be defined that way.
The text was updated successfully, but these errors were encountered: