chore: update sei fallback rpc and default visibility

[khanti42]

Description

This change removes Sei from the default preloaded networks so that it no longer appears as a default entry in the networks list.
Instead, it will now be displayed under Additional Networks, allowing users to manually add it if needed.

Additionally, this update introduces a fallback RPC for Sei (QUICKNODE_SEI_URL) in customNetworks.tsx, ensuring improved redundancy and reliability when Infura is unavailable.

Changelog

CHANGELOG entry: removed Sei from default networks and added QuickNode fallback RPC.

Manual testing steps

Feature: Sei network configuration updates

  Scenario: Verify Sei is not listed as a default network
    Given the app is freshly installed or reset
    When I open the list of default networks
    Then I should NOT see "Sei" listed in the main network list
    And I should see "Sei" listed under the "Additional Networks" section

  Scenario: Verify Sei can be manually added
    Given I open the "Add Network" flow
    When I search for "Sei"
    Then I should be able to add the "Sei" network manually

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.

---

Note

Removes Sei from default networks and adds a QuickNode fallback RPC, including a migration to populate failoverUrls and associated test/snapshot updates.

• Networks:
  • Remove sei-mainnet from default NetworkController state so it appears under Additional Networks (app/core/Engine/controllers/network-controller-init.ts).
  • Add QuickNode mapping for sei-mainnet and use it as failoverRpcUrls in PopularList (app/util/networks/customNetworks.tsx).
• Migration:
  • Add migration107 to append failoverUrls to SEI RPC endpoints when missing, guarded by QUICKNODE_SEI_URL (app/store/migrations/107.ts, wired in app/store/migrations/index.ts).
  • Comprehensive tests for structure validation and behavior (app/store/migrations/107.test.ts).
• Tests/Snapshots:
  • Update AddressSelector expectations/snapshot to exclude Sei from EVM list (app/components/Views/AddressSelector/*).
  • Extend QuickNode env support to include QUICKNODE_SEI_URL in utils tests (app/core/Engine/controllers/network-controller/utils.test.ts).
  • Update logs and initial background state fixtures to remove default SEI config (app/util/logs/__snapshots__/index.test.ts.snap, app/util/test/initial-background-state.json).

^{Written by Cursor Bugbot for commit 27c61df. 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.

[cursor]

Bug: Network Configuration Desync Creates Inconsistent State

The Sei network configuration (0x531) was removed from NetworkController.networkConfigurationsByChainId, but the corresponding entry "0x531": true remains in NetworkEnablementController.enabledNetworkMap.eip155. This creates an inconsistent test state where a network is marked as enabled but doesn't exist in the network configurations, potentially causing tests to fail or pass incorrectly.

app/util/test/initial-background-state.json#L120-L130

metamask-mobile/app/util/test/initial-background-state.json

Lines 120 to 130 in 369feac

	"name": "BNB Chain",
	"nativeCurrency": "BNB",
	"rpcEndpoints": [
	{
	"failoverUrls": [],
	"networkClientId": "bsc-mainnet",
	"type": "infura",
	"url": "https://bsc-mainnet.infura.io/v3/{infuraProjectId}"
	}
	]
	},

 

---

Bug: Orphaned Preferences: Network Configuration Mismatch

The Sei network configuration (0x531) was removed from NetworkController.networkConfigurationsByChainId, but PreferencesController.showIncomingTransactions still contains "0x531": true. This creates an inconsistent test state where incoming transactions are enabled for a network that doesn't exist in the network configurations.

app/util/test/initial-background-state.json#L120-L130

metamask-mobile/app/util/test/initial-background-state.json

Lines 120 to 130 in 369feac

	"name": "BNB Chain",
	"nativeCurrency": "BNB",
	"rpcEndpoints": [
	{
	"failoverUrls": [],
	"networkClientId": "bsc-mainnet",
	"type": "infura",
	"url": "https://bsc-mainnet.infura.io/v3/{infuraProjectId}"
	}
	]
	},

 

---

[cursor]

Bug: Phantom Network: Enabled But Configuration Gone.

The Sei network (0x531) is removed from NetworkController.networkConfigurationsByChainId but remains enabled in NetworkEnablementController.enabledNetworkMap.eip155. This creates an inconsistent state where the enablement controller indicates Sei is enabled but no network configuration exists for it, potentially causing runtime errors when code tries to access the missing Sei configuration.

app/util/test/initial-background-state.json#L120-L130

metamask-mobile/app/util/test/initial-background-state.json

Lines 120 to 130 in d8c9441

	"name": "BNB Chain",
	"nativeCurrency": "BNB",
	"rpcEndpoints": [
	{
	"failoverUrls": [],
	"networkClientId": "bsc-mainnet",
	"type": "infura",
	"url": "https://bsc-mainnet.infura.io/v3/{infuraProjectId}"
	}
	]
	},

 

---

[cursor]

Bug: Phantom Network Causes Runtime Errors

Sei network (0x531) is removed from NetworkController.networkConfigurationsByChainId but remains enabled (true) in NetworkEnablementController.enabledNetworkMap.eip155. This creates an inconsistency where the enablement controller references a network that doesn't exist in the network configurations for new users, potentially causing runtime errors when the app tries to access the enabled but non-existent network.

app/util/test/initial-background-state.json#L120-L130

metamask-mobile/app/util/test/initial-background-state.json

Lines 120 to 130 in 62ef7c8

	"name": "BNB Chain",
	"nativeCurrency": "BNB",
	"rpcEndpoints": [
	{
	"failoverUrls": [],
	"networkClientId": "bsc-mainnet",
	"type": "infura",
	"url": "https://bsc-mainnet.infura.io/v3/{infuraProjectId}"
	}
	]
	},

 

---

[salimtb]

pls fix the broken unit test

[tommasini]

We should capture exceptions if the state is not structured as expected, and that means a bug on the user data structure.
If you can, please visit other migrations to see how this is handled or our migration guidelines

[tommasini]

Im not understanding the need od this delete, shouldnt this be handled by the migration?

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud