Parse v-Value from Ledger Device
#1136
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
The Ledger device API returns the signature `v` value as a hexadecimal encoded string and **not** a number. This causes unexpected behaviour with the bitwise operations, and why the `yParity` computation would sometimes fail. This PR fixes the issue by first `parseInt`-ing the `v` value in base 16 (i.e. hexadecimal) before applying the bitwise operations.
remedcu
approved these changes
Aug 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The Ledger device API returns the signature
vvalue as a hexadecimal encoded string and not a number. This causes unexpected behaviour with the bitwise operations, and why theyParitycomputation would sometimes fail.This PR fixes the issue by first
parseInt-ing thevvalue in base 16 (i.e. hexadecimal) before applying the bitwise operations.