feat: add destinationChainId to support cross chain txs#4988
Merged
infiniteflower merged 2 commits intomainfrom Nov 27, 2024
Merged
feat: add destinationChainId to support cross chain txs#4988infiniteflower merged 2 commits intomainfrom
infiniteflower merged 2 commits intomainfrom
Conversation
4 tasks
matthewwalsh0
approved these changes
Nov 27, 2024
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
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.
Explanation
This PR adds a new field to the
TransactionMetatype to facilitate Bridge transactions.The primary purpose is to ensure that
destinationTokenAddressrefers to the correct token on the correct chain.References
A slimmed down version of #4918
Related to MetaMask/metamask-extension#28460
Changelog
@metamask/transaction-controllerdestinationChainIdto theTransactionMetatypeChecklist