Description

Fixes a bug in the bridge token selector where Polygon's native token (POL) appeared twice in the list — once with balance at the top and once without balance at the bottom. Selecting the balance entry as a destination token caused the quote to show 0 and the rate to display "--".

Root cause: Polygon's native token uses address 0x0000000000000000000000000000000000001010 in wallet state (from getNativeTokenAddress), but the bridge API expects AddressZero (0x0000...0000) for all native assets. The bridge-controller's isNativeAddress() does not recognize 0x...1010 as native, so:

1. tokenToIncludeAsset sent the wrong asset ID (erc20:0x...1010 instead of slip44:966) to the API, which couldn't deduplicate it with its own native POL entry.
2. When the user selected POL with 0x...1010, quote matching in useBridgeQuoteData failed because the returned quote used AddressZero for destAsset.address.

Fix: Extracted the existing normalization logic from useTokenAddress into a reusable pure function normalizeTokenAddress, and applied it in useTokensWithBalance when building BridgeToken objects from wallet state. This ensures POL enters the bridge flow with AddressZero from the start, fixing both the duplicate listing and the quote/rate mismatch.

Changelog

CHANGELOG entry: Fixed a bug where Polygon's native token (POL) appeared twice in the bridge token selector and selecting it showed incorrect quote data.

Related issues

Fixes:

Manual testing steps

Feature: Bridge token selector - Polygon native token

  Scenario: user selects POL as destination token on Polygon
    Given user has a POL balance on Polygon
    And user opens the bridge token selector for destination

    When user filters by Polygon network
    Then POL appears only once in the token list with balance displayed

  Scenario: user gets a valid quote after selecting POL destination
    Given user has a source token with balance
    And user has selected POL on Polygon as the destination token

    When the quote loads
    Then the destination input shows a non-zero amount
    And the rate displays a valid exchange rate (not "--")

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.