chore: Core controllers v300

[tommasini]

Description

• Update accounts controller (^24), assets controller(^50) and transaction controller(^46)
• Handle breaking changes of assets controllers
• Update the patch of assets controllers to be on v50
• Add MultichainNetworkController v0.1.1 (Although only added and not used at this PR, setActiveNetwork will be refactored in a follow up PR)

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Before

After

Screen.Recording.2025-02-17.at.15.50.13.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.

[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]

New and updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/[email protected] 🔁 npm/@metamask/[email protected]	None	0	301 kB	metamaskbot
npm/@metamask/[email protected] 🔁 npm/@metamask/[email protected]	None	+1	2.77 MB	metamaskbot
npm/@metamask/[email protected] 🔁 npm/@metamask/[email protected]	None	0	76.2 kB	gudahtt
npm/@metamask/[email protected] 🔁 npm/@metamask/[email protected]	None	+1	348 kB	mcmire
npm/@metamask/[email protected] 🔁 npm/@metamask/[email protected]	None	+1	82.1 kB	danfinlay, gudahtt, kumavis, ...6 more
npm/@metamask/[email protected]	None	0	110 kB	metamaskbot
npm/@metamask/[email protected] 🔁 npm/@metamask/[email protected]	None	0	812 kB	metamaskbot
npm/@metamask/[email protected] 🔁 npm/@metamask/[email protected]	None	+2	3.66 MB	metamaskbot

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

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

Ignoring: npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected], npm/@metamask/[email protected]

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: b0dda1b
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/790b1a31-239d-4dbe-a455-5267585b74b2

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[tommasini]

@SocketSecurity ignore-all
All those packages are internal and we trust those

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 2bce9c0
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/b382b07a-80a8-4b3a-b069-68f9a2a7276a

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[salimtb]

Assets changes LGTM

[gantunesr]

Reviewed,

• app/components/Views/AddAccountActions/AddAccountActions.tsx
• app/core/Engine/Engine.ts
• app/core/Engine/controllers/AccountsController/constants.ts
• app/core/Engine/controllers/AccountsController/utils.test.ts
• app/core/Engine/controllers/MultichainNetworkController/index.test.ts
• app/core/Engine/controllers/MultichainNetworkController/index.ts
• app/core/Engine/types.ts
• app/selectors/multichain/multichain.test.ts
• app/core/Multichain/constants.ts
• app/selectors/multichain/multichain.ts
• e2e/fixtures/fixture-builder.js

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 6397f1c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/5caba08e-ea6f-4599-9d56-7f0209475270

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[gantunesr]

lgtm!

[sonarqubecloud]

Quality Gate passed

Issues
13 New issues
0 Accepted issues

Measures
0 Security Hotspots
80.6% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud