fix: migrate Sei explorer from Seitrace to Seiscan

[jeremytsng]

Description

Seitrace (https://seitrace.com), the current Sei Mainnet block
explorer, is being decommissioned. This PR swaps every hardcoded
reference to seiscan.io and adds migration 134 to rewrite existing
users' persisted NetworkController state on upgrade.

Hardcoded URL swaps:

• app/util/networks/customNetworks.tsx — Sei Mainnet blockExplorerUrl
• tests/resources/networks.e2e.js — e2e resource
• tests/api-mocking/mock-responses/tx-sentinel-networks-map.ts — mock explorer

Migration 134 rewrites
engine.backgroundState.NetworkController.networkConfigurationsByChainId['0x531'].blockExplorerUrls
from seitrace.com to seiscan.io for existing installs. It only
touches entries still pointing at seitrace.com — a user who customized
their Sei block explorer (e.g. to seistream.app) is left alone. The
migration follows mobile's current pattern (sync arrow function with
in-place state mutation), and is registered in
app/store/migrations/index.ts. Cross-repo reference for this family
of block-explorer-URL migrations is
metamask-extension/app/scripts/migrations/197.ts.

The @metamask/controller-utils bump is deliberately deferred until
the sibling PR in MetaMask/core releases; this PR stands alone.

Changelog

CHANGELOG entry: Fixed Sei Mainnet: replaced deprecated Seitrace explorer with Seiscan (https://seiscan.io). Existing installs are migrated via migration 134.

Related issues

Fixes:

Companion PRs:

• MetaMask/core#8545 — default BlockExplorerUrl[SeiMainnet]
• MetaMask/metafi-sdk#525 — shared SDK SEI_EXPLORER
• MetaMask/metamask-extension#42064 — extension migration 207

Manual testing steps

Feature: Sei Mainnet block explorer URL

  Scenario: fresh install uses Seiscan
    Given a fresh install of MetaMask Mobile
    When the user adds the Sei Mainnet network
    Then the network's block-explorer URL is "https://seiscan.io/"
    And tapping a Sei transaction's "View on block explorer" opens "https://seiscan.io/tx/<hash>"

  Scenario: existing user with Seitrace URL is migrated
    Given a build prior to this change with Sei Mainnet added
    And the stored "blockExplorerUrls" is ["https://seitrace.com"]
    When the user upgrades to this build
    Then migration 134 runs
    And the stored "blockExplorerUrls" for Sei Mainnet is ["https://seiscan.io"]

  Scenario: user-customized URL is preserved
    Given a build prior to this change with Sei Mainnet added
    And the user has customized "blockExplorerUrls" to ["https://seistream.app"]
    When the user upgrades to this build
    Then migration 134 is a no-op for this entry
    And the stored "blockExplorerUrls" for Sei Mainnet remains ["https://seistream.app"]

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.

Performance checks (if applicable)

• I've tested on Android
• I've tested with a power user scenario
• I've instrumented key operations with Sentry traces for production performance metrics

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

Medium Risk
Adds a new persisted-state migration that mutates NetworkController network configs for Sei Mainnet; while narrowly scoped, migrations run on upgrade and can affect existing user state if bugs slip through.

Overview
Updates Sei Mainnet’s default block explorer from Seitrace to Seiscan across the in-app popular network config and test fixtures.

Adds migration 134 (registered in app/store/migrations/index.ts) to rewrite persisted Sei Mainnet blockExplorerUrls entries whose URL hostname is exactly seitrace.com to seiscan.io, while leaving missing/invalid controller state and user-customized/lookalike URLs untouched; includes unit tests covering the rewrite and no-op cases.

^{Reviewed by Cursor Bugbot for commit 68e91bc. Bugbot is set up for automated code reviews on this repo. 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.

[github-actions]

AI PR Analysis

🚫 Merge safe: false | 🟠 Risk: high

Merge decision: AI analysis did not complete — manual review required before merging.

AI analysis did not complete. Manual review recommended.

View run

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeNetworkAbstractions
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 82%

click to see 🤖 AI reasoning details

E2E Test Selection:
The PR makes a narrow, targeted change: replacing the deprecated Seitrace block explorer URL (seitrace.com) with Seiscan (seiscan.io) for Sei Mainnet across four surfaces:

1. Migration 134 (app/store/migrations/134.ts): Rewrites the block explorer URL in existing users' NetworkController state. This is a safe, targeted migration with no structural changes - it only touches blockExplorerUrls for chain ID 0x531 (Sei Mainnet) and only when the URL still points to seitrace.com.

2. app/util/networks/customNetworks.tsx: Updates the PopularList entry for Sei Mainnet's blockExplorerUrl. This affects the "Add Popular Networks" flow in the Network Manager UI, which is covered by SmokeNetworkAbstractions.

3. tests/api-mocking/mock-responses/tx-sentinel-networks-map.ts: Updates the Sei Mainnet explorer URL in the TX sentinel mock used as a default mock across all E2E tests. This is a data-only change with no structural impact.

4. tests/resources/networks.e2e.js: Updates the Sei Testnet BlockExplorerUrl string. This file is imported by many test files (FixtureBuilder, network tests, ramps tests, etc.), but the Sei entry is rarely the focus of test assertions - it's used for fixture setup.

SmokeNetworkAbstractions is the most relevant tag because:

• It tests adding popular networks (including Sei) via the Network Manager UI
• It tests the network selector and network configuration flows
• The customNetworks.tsx change directly affects what URL is shown/used when adding Sei Mainnet

No other tags are warranted because:

• The migration only touches block explorer URLs, not transaction flows, confirmations, or account management
• The mock data changes are URL-only updates with no structural impact
• No confirmation flows, swap flows, or account flows are affected
• The networks.e2e.js Sei entry change is a URL string update that doesn't affect test logic

Performance Test Selection:
No performance impact expected. The changes are limited to: (1) a state migration that runs once on upgrade and only rewrites a URL string, (2) a URL string update in the popular networks list, and (3) test mock data updates. None of these affect UI rendering performance, data loading, account/network list components, or app startup/initialization in a meaningful way.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
85.2% Coverage on New Code
0.6% Duplication on New Code

See analysis details on SonarQube Cloud