feat: migrate BSC network RPC to bsc-mainnet.infura.io

[salimtb]

Description

This PR introduces a migration to replace the Base network RPC URL (https://bsc-dataseed.binance.org/) with the new Infura RPC URL (https://bsc-mainnet.infura.io/v3/{infuraProjectId}) in the MetaMask state.

Acceptance Criteria:

• Migrate BSC Mainnet to Infura only if users are using an Infura RPC as the default on at least one added network, excluding testnets and Linea Mainnet.

same PR was opened on extension

Related issues

Fixes:

Manual testing steps

1. run a build on main
2. switch to this branch
3. check the rpc url used by bsc mainnet

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]

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.

[github-actions]

Bitrise

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

Commit hash: 7971e48
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/39597161-7a59-4478-a271-3ead85c985db

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 failed on Bitrise! ❌❌❌

Commit hash: 93a95a6
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f9a71675-ad7e-43b1-b18c-91449d46ad84

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 failed on Bitrise! ❌❌❌

Commit hash: eae360e
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/d5474939-222c-44b6-b9c6-08ff2ef3f219

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 passed on Bitrise! ✅✅✅

Commit hash: 3249521
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/c989afed-54ac-4deb-9e2c-5690d7071341

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: 95ab626
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/333ea6d5-add4-4a8b-be5f-8ae460722888

Note

• You can rerun any failed steps by opening the Bitrise build, tapping Rebuild on the upper right then Rebuild unsuccessful Workflows
• 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

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
87.7% Coverage on New Code
1.4% Duplication on New Code

See analysis details on SonarQube Cloud