feat: Transition from Multiple Networks with Same ChainID to Unique Networks with Distinct ChainIDs and Multiple RPC URLs

[salimtb]

Description

This PR refactors our network configuration to eliminate the use of multiple networks with the same ChainID but different RPC URLs. Instead, we are moving towards a setup where each network is uniquely identified by a distinct ChainID and can have multiple RPC URLs associated with it.

This PR includes three merge commits. The first primarily addresses the Network Controller upgrade, as outlined in issue #11229. The second commit contains the script for migrating the state to v21, and the third commit includes all the UI changes along with the fix for the e2e tests.

For more details, please refer to this .

related PRs:

• chore: bump network controller 21.0.0 #11292
• feat: network Controller Migration + UI #11622
• feat: bump network controller 21.0.0 remove feature flag #11436

Related issues

Fixes: #11229 #11232 #11234 #11233

Manual testing steps

1. Go to add network flow and test

Screenshots/Recordings

Before

After

https://drive.google.com/drive/folders/149Xji42k5of5Vl8nBlI0pFYFgPnWqILH?usp=drive_link

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 removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/json-rpc-engine@9.0.3	None	0	177 kB	metamaskbot
npm/reselect@5.1.1	None	0	646 kB	acemarke

🚮 Removed packages: npm/@metamask/json-rpc-engine@9.0.2

View full report↗︎

[legobeat]

patch-package is failing.

 **ERROR** Failed to apply patch for package @metamask/preferences-controller
    
  This happened because the patch file patches/@metamask+preferences-controller+11.0.0.patch could not be parsed.
   
  If you just upgraded patch-package, you can try running:
  
    patch -p1 -i patches/@metamask+preferences-controller+11.0.0.patch
    npx patch-package @metamask/preferences-controller
    
  Otherwise, try manually creating the patch file again.
  
  If the problem persists, please submit a bug report:
  
    https://github.com/ds300/patch-package/issues/new?title=Patch+file+parse+error&body=%3CPlease+attach+the+patch+file+in+question%3E

[salimtb]

patch-package is failing.

 **ERROR** Failed to apply patch for package @metamask/preferences-controller
    
  This happened because the patch file patches/@metamask+preferences-controller+11.0.0.patch could not be parsed.
   
  If you just upgraded patch-package, you can try running:
  
    patch -p1 -i patches/@metamask+preferences-controller+11.0.0.patch
    npx patch-package @metamask/preferences-controller
    
  Otherwise, try manually creating the patch file again.
  
  If the problem persists, please submit a bug report:
  
    https://github.com/ds300/patch-package/issues/new?title=Patch+file+parse+error&body=%3CPlease+attach+the+patch+file+in+question%3E

rsolved cc @legobeat

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 0920582
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/b20b0ee1-548f-4c96-b839-24b3b85a3afb

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

[github-actions]

Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: 28ca838
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/a1ecebf7-2d94-4838-b561-1cf54922f333

Note

• This comment will auto-update when build completes
• 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

[github-actions]

Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: 963f438
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/7ffec7ef-3411-4086-97cf-5e54097f658f

Note

• This comment will auto-update when build completes
• 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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 54af1c4
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/106a6675-5592-4857-9864-82231f06ac7c

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

[andreahaku]

LGTM

[brianacnguyen]

Approved with DS changes

[wachunei]

ramp changes lgtm

[sonarqubecloud]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

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

See analysis details on SonarCloud