Fix getting parity from keypair in fuzzing #451
Merged
Conversation
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
This also enables a test that was failung due to the parity bug.
tcharding
approved these changes
Jun 16, 2022
|
Could you explain why in other places it does check the 32'nd byte but here the 64? |
|
Or are you saying there's another place where it should be changed to 64? Do you want me to add a comment or change the commit message to explain this? |
|
That was exactly the context I've missed, Thanks! |
elichai
approved these changes
Jun 16, 2022
apoelstra
approved these changes
Jun 16, 2022
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.
This also enables a test that was failung due to the parity bug.