fix: when validating a block, clone the blocks version #5539
+5
−0
Conversation
This file contains 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
jcnelson
approved these changes
Dec 8, 2024
obycode
approved these changes
Dec 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When nodes change their
NAKAMOTO_BLOCK_VERSION, unupgraded signers reject the block, because the unupgraded signers use the old version when trying to clone (and compare the block hash) of the proposed block.This change has the block validation endpoint clone the version of the proposed block to the local block, so that the block hash will match.
We may need more validation here about what a valid block version is - for example, I believe it needs to be <128, or it is treated as a shadow block. Thus, opening as a draft.