Prevent bid_collateral from executing through proposal before hardfork#441
Merged
Conversation
Member
|
Looks good. Although it presumes HF 429 and HF 216 will occur at same time, practically it's OK for now. |
Contributor
Author
|
Thanks. The code will be removed after the HF time anyway. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fix prevents an issue pointed out by @abitmore:
An upgraded witness could include a proposal with a bid_collateral_operation into the blockchain, which would cause block misses for nodes that haven't upgraded yet. After a majority of witnesses have upgraded, such an event would exclude all older nodes from the network.