Description

Follow-up to #30892 (which updated the Sei network logo to the new black mark).

Per Sei's brand guidelines the network/brand mark is black, but the token mark is maroon. Today the Sei native token reuses the network image, so it renders black. This splits the native token icon into its own asset so it shows the maroon token mark while the network keeps the black mark.

• Adds app/images/sei-native.png — Sei's token mark in maroon (#600014) on a white background, 512×512 (matching the network logo treatment, so it stays legible in light and dark mode).
• image-icons.js now imports SEI from it, so the token avatar (Base/TokenIcon when symbol === 'SEI', plus Bridge/Ramp token icons) renders maroon.
• The network image stays on sei.png (black) via customNetworks.tsx → getNetworkImageSource — network selector / network badge unchanged.

Changelog

CHANGELOG entry: Updated the Sei native token icon to Sei's maroon token mark.

Related issues

Fixes:

Manual testing steps

Feature: Sei token logo

  Scenario: user views the Sei token and network icons
    Given the user has the Sei network available

    When the user switches to Sei and views the assets list
    Then the Sei native token shows the maroon mark

    When the user opens the network selector
    Then the Sei network shows the black mark

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.