fix: invalid rlp data for legacy transactions #212
Merged
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
legobeat
approved these changes
Dec 2, 2023
legobeat
pushed a commit
to legobeat/eth-ledger-bridge-keyring
that referenced
this pull request
Dec 2, 2023
Merged
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 commit introduced a bug with legacy transactions.
With
@ethereumjs/rlp,RLP.encode(..)returns aUint8Array, andUint8Array.toString()does not return a hex value as we expect in the code.This PR converts the returned
Uint8Arrayinto aBuffer, and then into a hex string.See MetaMask/metamask-extension#22118