chore: fetch currencyRates with price api

[sahar-fehri]

Description

PR to upgrade @metamask/assets-controllers package. It introduces multiple breaking changes:

• Fetching exchangeRates from price api and fallback to crypto compare.
• Changes to selector calls to ignore manually selected non-evm assets.
• Changes to the number of networks enabled by default from @metamask/controller-utils.
  • This one makes a significant amount of changes to initial state and onboarding.
• New events added to AccountTrackerController.

Changelog

CHANGELOG entry: Fetch currency rates using price api and fallback to crypto compare

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

Screen.Recording.2025-10-22.at.14.19.13.mov

After

Screen.Recording.2025-10-22.at.14.00.22.mov

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

Switches currency rates to the Price API (with normalization), enables more EVM mainnets by default, and updates selectors/tests and configs accordingly.

• Engine/Controllers:
  • CurrencyRateController: initialize with tokenPricesService (Price API) and normalize persisted currencyRates.
  • NetworkController defaults: add Infura failovers and names for arbitrum-mainnet, bsc-mainnet, optimism-mainnet, polygon-mainnet, sei-mainnet.
  • NetworkEnablementController (patched): default-enable Arbitrum, BNB Chain, OP, Polygon, Sei.
  • AccountTrackerController messenger: listen to NetworkController:networkAdded and KeyringController:unlock.
• Selectors:
  • Balances/Assets: include MultichainAssetsController.allIgnoredAssets in calculations; wire through in selectors; convert multichain asset selectors to memoized selectors.
• UI/Tests:
  • AddressSelector tests/snapshots: expect new EVM networks in list/order.
  • OnboardingSuccess: remove network auto-add side effects; drop associated test.
• E2E/Config:
  • Allowlist price.api.cx.metamask.io; add Infura mock for sei-mainnet; update initial background state and snapshots with new networks and enabled map.
• Dependencies:
  • Bump @metamask/assets-controllers to ^86.0.0; use patched @metamask/network-enablement-controller.

^{Written by Cursor Bugbot for commit 5ab6311. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​metamask/​controller-utils@​11.14.1 ⏵ 11.15.0	+1		+1	+3
	npm/​@​metamask/​assets-controllers@​84.0.0 ⏵ 86.0.0	+1		+1

View full report

[socket-security]

All alerts resolved. Learn more about Socket for GitHub.

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report

[bergarces]

Not even one of the SonarCloud "issues" (they aren't) is new.

[tommasini]

Not even one of the SonarCloud "issues" (they aren't) is new.

We need to ignore them on the sonar cloud then, will talk with the team! Thanks @bergarces

[bergarces]

Not even one of the SonarCloud "issues" (they aren't) is new.

We need to ignore them on the sonar cloud then, will talk with the team! Thanks @bergarces

The arrow function being too large warning is ok in general (better to use an object bag than too many arguments), but in this case it is the only reasonable way of doing it, since that's the interface for selectors.

The one about the useless assignment is also good in general, but that's because SonarCloud is not aware of our code fencing comments.

The rest are the usual "please complete your TODOs" (which sometimes makes sense, but other times they are there to split the PR in smaller ones) and one about a type assignment, which is not really part of this PR either.

My main beef with SonarCloud is that it adds issues as "New" when they were already there.

In general, I think it's best to let SonarCloud report freely, we can then make the call as to whether we want to ignore it or not.

[sonarqubecloud]

Quality Gate passed

Issues
10 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
9.0% Duplication on New Code

See analysis details on SonarQube Cloud

[grvgoel81]

LGTM