-
Notifications
You must be signed in to change notification settings - Fork 91
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
Remove bit 2 warning. #580
Conversation
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.
Code looks fine
@blondfrogs forced pushed over what you reviewed. Added iteration over the consensus deployments to manually check if the bit has been defined. It doesn't seem like it serves a good purpose to print a warning of something that your wallet has knowledge of. On the other hand if your wallet does not have knowledge of the bit being signalled, you should be warned. |
Makes sense. I like this change |
FYI, the real reason for the warning to have appeared is very likely that you have changed The better solution for this would be to maintain these parameters per deployment so that you can vary it when needed. Look at the changes Dash did for DIP1 as an example: dashpay/dash@cd262bf#diff-bc9415451d733499187a3fe59e0fd7e6R34 (the addition of nWindowSize and nThreshold in BIP9Deployment) |
@codablock awesome reference thanks for linking it. That would be extremely useful, because (as was the case here) sometimes it is necessary to have faster than usual deployments. Will add this to the list of items to get done before we do another deployment. |
closes #563