chore: bump network controller 21.0.0

[salimtb]

Description

This PR updates the network-controller from version 20.0.0 to 21.0.0. The migration introduces changes in the handling of network configurations, particularly regarding how network data is structured and referenced.

Key Changes:
Consolidation of Network Configurations:

Network configurations in v21 are now organized by chainId in a new networkConfigurationsByChainId structure, replacing the networkConfigurations section in v20.
The new structure supports multiple RPC endpoints per network, as seen in the list of rpcEndpoints, with support for Infura-based connections (e.g., https://mainnet.infura.io/v3/{infuraProjectId}).

Remark

As part of the update to version 21 (v21) of the network controller, we are making a key change in how networks are handled. Previously, networks could have the same chain ID but different RPC URLs. With v21, each network will now have a unique chain ID that can include multiple RPC URLs.

To support this, the UI will also be updated—for example, the RPC URL field in the network form will become a dropdown menu instead of a simple text input.

These changes have been implemented behind a feature flag, which will remain in place until the v21 upgrade is finalized.

To complete this migration, we have 3 PRs that need to be reviewed and merged together:

The first PR upgrades the network controller to v21.
The second PR adds the migration script and the necessary UI for migration.
The third PR removes the feature flag, making the v21 changes active.
For the review process, it's recommended to start with the third PR (removing the feature flag), then proceed to the > second and first PRs. This order ensures a smooth transition and proper implementation of the changes.

Related PRS

• feat: network Controller Migration + UI #11622 ( contain the migration script + modal )
• feat: bump network controller 21.0.0 remove feature flag #11436 ( contain the remove of the feature flag , the new UI is visible )

Related issues

Fixes: #11229

Manual testing steps

• Verify that networkConfigurations has been replaced by networkConfigurationsByChainId.
• Check that each network in networkConfigurationsByChainId is identified by its chainId.
• Ensure that all rpcEndpoints are correctly listed for each network in networkConfigurationsByChainId.
• Validate that the defaultRpcEndpointIndex points to a valid and functional RPC endpoint for each network.
• Check that Infura-based RPC URLs (e.g., Mainnet, Goerli, Sepolia, Linea networks) are properly formatted with the correct {infuraProjectId}.
• Verify that networks like Linea Goerli, Linea Sepolia, and Linea Mainnet are listed under networkConfigurationsByChainId with their correct chainId values.
• Ensure that any unused or outdated custom network configurations (e.g., BNB Chain from v20) have been removed.
• Check that all network names (e.g., "Mainnet", "Goerli", "Sepolia") in networkConfigurationsByChainId match their respective chainId values.
• Validate that nativeCurrency fields are correctly set for each network in networkConfigurationsByChainId (e.g., ETH for Mainnet, SepoliaETH for Sepolia).
• Ensure that each network's blockExplorerUrls is present and correctly configured where applicable.

Screenshots/Recordings

Before

After

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]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: dbf808b
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/42668c05-bf0a-468e-baf2-8efa1d234112

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

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 0a56a68
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/b9218208-db83-49e5-983e-a004776e9b6f

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

[sonarcloud]

Quality Gate passed

Issues
37 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[legobeat]

Why is renderRpcNetworks skipped except for this set of hardcoded known chains? Is there any difference in functionality between the two cases?

[salimtb]

We skip rendering certain networks in the if block because we need to handle them separately to manage their order and display settings. Specifically, test networks (testnets) need to appear at the bottom of the list, and their visibility should be controlled by a toggle option (whether to show or hide them).

For the primary networks, Mainnet and Linea, they should always appear as the first and second items in the network list by default.

• Mainnet is rendered using the renderMainnet function.
• Linea is rendered with the renderLineaMainnet function.
• All other networks are rendered through the renderRpcNetworks function.
• Test networks (testnets) are rendered using the renderOtherNetworks function.

To manage the display order and ensure proper handling, we exclude these specific networks from the networkConfiguration state, allowing us to render them with greater control in the desired order.

[github-actions]

Bitrise

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

Commit hash: 0a76ef0
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/df452b65-2acf-443d-ae06-05250066aa20

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

[metamaskbot]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 0a76ef0
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/df452b65-2acf-443d-ae06-05250066aa20

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]

This pull request was merged into this feature branch, so I need approval on that feature branch. I'm keeping the PR open to make the review process easier.