-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Implement new hardfork for v17 to be used in future changes #3808
Implement new hardfork for v17 to be used in future changes #3808
Conversation
Signed-off-by: pasta <pasta@dashboost.org>
Will the fork primarily be to support platform requirements? If so, the name could reflect that. |
Agree that a better name should be picked at some point (it's not even a HF atm) but we can tweak this later, it's not a blocker imo. |
Co-authored-by: UdjinM6 <UdjinM6@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
…3808) * Implement new hardfork for v17 to be used in future changes Signed-off-by: pasta <pasta@dashboost.org> * fix comment Co-authored-by: UdjinM6 <UdjinM6@users.noreply.github.com> Co-authored-by: UdjinM6 <UdjinM6@users.noreply.github.com>
Not sure I'm a huge fan of
DEPLOYMENT_V17
name, lmk if there are any suggestions