feat: add multichain support to bridge-controller #5486
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
micaelae
commented
Mar 15, 2025
micaelae
force-pushed
the
mms2100-bridge-multichain-support
branch
from
9817317 to
1a23d2d
Compare
micaelae
force-pushed
the
mms2100-bridge-multichain-support
branch
from
1a23d2d to
42b9e6c
Compare
micaelae
commented
Mar 18, 2025
micaelae
commented
Mar 18, 2025
|
New dependencies detected. Learn more about Socket for GitHub ↗︎
|
|
@metamaskbot publish-preview |
|
Preview builds have been published. See these instructions for more information about preview builds. Expand for full list of packages and versions. |
|
@metamaskbot publish-preview |
|
Preview builds have been published. See these instructions for more information about preview builds. Expand for full list of packages and versions. |
GustavoRSSilva
approved these changes
Mar 21, 2025
infiniteflower
approved these changes
Mar 21, 2025
|
@metamaskbot publish-preview |
|
Preview builds have been published. See these instructions for more information about preview builds. Expand for full list of packages and versions. |
Merged
micaelae
added a commit
that referenced
this pull request
Mar 21, 2025
## Explanation Releasing @metamask/bridge-controller 11.0.0 to include multichain network support implemented in [5486](#5486) <!-- Thanks for your contribution! Take a moment to answer these questions so that reviewers have the information they need to properly understand your changes: * What is the current state of things and why does it need to change? * What is the solution your changes offer and how does it work? * Are there any changes whose purpose might not obvious to those unfamiliar with the domain? * If your primary goal was to update one package but you found you had to update another one along the way, why did you do so? * If you had to upgrade a dependency, why did you do so? --> ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> ### `@metamask/bridge-controller` ### Added - BREAKING: Bump dependency @metamask/keyring-api to ^17.2.0 ([#5486](#5486)) - BREAKING: Bump dependency @metamask/multichain-network-controller to ^0.3.0 ([#5486](#5486)) - BREAKING: Bump dependency @metamask/snaps-utils to ^8.10.0 ([#5486](#5486)) - BREAKING: Bump peer dependency @metamask/snaps-controllers to ^9.19.0 ([#5486](#5486)) - Solana constants, utils, quote and token support ([#5486](#5486)) - Utilities to convert chainIds between `ChainId`, `Hex`, `string` and `CaipChainId` ([#5486](#5486)) - Add `refreshRate` feature flag to enable chain-specific quote refresh intervals ([#5486](#5486)) - `isNativeAddress` and `isSolanaChainId` utilities that can be used by both the controller and clients ([#5486](#5486)) ### Changed - Replace QuoteRequest usages with `GenericQuoteRequest` to support both EVM and multichain input parameters ([#5486](#5486)) - Make `QuoteRequest.slippage` optional ([#5486](#5486)) - Deprecate `SwapsTokenObject` and replace usages with multichain BridgeAsset ([#5486](#5486)) - Changed `bridgeFeatureFlags.extensionConfig.chains` to key configs by CAIP chainIds ([#5486](#5486)) ## Checklist N/A
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.
Explanation
The
BridgeControllercurrently only works with EVM networks and addresses. In order to support Solana integration into mobile, this PR adds the multichain compatibility updates implemented in extension.Specific changes
Notes for upgrading mobile to this version
AllowedActionstype update)References
Bridge{,Status}Controllerstate metamask-extension#29443Changelog
@metamask/bridge-controller 8.0.0ADDED
CHANGED
fetchFncan propagate parameters to the underlying fetch functionbridgeFeatureFlags.chainskeys from Hex to CAIP-formatted chainIdsChecklist