Description

Sei has updated their brand logo. This updates the Sei logo used in the network selector and for the Sei native token to the new brand mark.

The asset is swapped in place at app/images/sei.png (same filename), so every consumer that already resolves to it picks up the new mark automatically:

• Network selector / network image — customNetworks.tsx
• Native token icon — image-icons.js

The icon uses Sei's new symbol in black on a white background (Sei's primary brand presentation), keeping the existing full-bleed square convention used by the other network icons (masked to a circle in the UI), exported at 512×512. This bundled asset is the network image and is also reused for the Sei native token icon in-wallet.

Changelog

CHANGELOG entry: Updated the Sei network and token logo to Sei's new brand mark.

Related issues

Fixes:

Manual testing steps

Feature: Sei logo update

  Scenario: user views the updated Sei logo
    Given the user has the Sei network available

    When the user opens the network selector and locates Sei
    Then the new Sei logo is displayed

    When the user switches to Sei and views the assets list
    Then the Sei native token uses the new logo

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
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

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.