Description

Addresses two perps issues identified via Sentry analysis (branch: fix/perps/sentry-analysis).

Issue 1: HIP-3 DEX discovery not retried after transient failure

Root cause: When perpDexs() fails transiently (WS drop during init), #fetchValidatedDexsInternal was caching [null] (main DEX only). On the next #ensureReady() call, the cache hit returned the stale degraded result — HIP-3 markets stayed unavailable for the entire session.

Fix:

• On transient fetch failure, return [null] without caching so the next call retries
• Added #dexDiscoveryComplete flag: when false, #ensureReady() resets its promise after each init so every subsequent trading call (closePosition, placeOrder, etc.) retries DEX discovery
• Once discovery succeeds, HIP-3 symbols are merged into the existing map and #dexDiscoveryComplete = true — no more retries
• Trading on main DEX continues uninterrupted during degraded state
• Flag is cleared on disconnect() for clean reconnection

Note: the upstream fix preventing the permanent provider brick (commit 29d300597d, already in main) should be cherry-picked to 7.67.4. This PR adds the retry logic on top.

Issue 2: "Invalid chain ID 0xa4b1" on deposit from pay-with modal

Root cause: usePerpsBalanceTokenFilter.handlePerpsDepositPress called depositWithConfirmation() directly without first calling ensureArbitrumNetworkExists(). Users without Arbitrum in their network list hit NetworkController.findNetworkClientIdByChainId throwing on chain 0xa4b1 (Arbitrum One — HyperLiquid's bridge chain). The guard existed in usePerpsHomeActions but was missing from this second entry point.

Fix: Call ensureArbitrumNetworkExists() before depositWithConfirmation() in handlePerpsDepositPress, matching the existing pattern in usePerpsHomeActions.

This error predates 7.67 — it became visible due to improved Sentry tagging in Feb 2026 (commits 30f8e72cc4/61a2be3e9d). Not a regression, low volume (~170 users).

Changelog

CHANGELOG entry: null

Related issues

Fixes: (Sentry: METAMASK-MOBILE-5JCV, METAMASK-MOBILE-5G4T, METAMASK-MOBILE-5JGC, METAMASK-MOBILE-5H0A)

Manual testing steps

Feature: Perps DEX discovery recovery

  Scenario: user opens perps while connection is unstable
    Given the app is open on the Perps screen
    And the WebSocket connection drops during provider initialization

    When the user waits for reconnection
    Then HIP-3 DEX markets should become available once connection recovers
    And main DEX trading (closePosition, placeOrder) should work immediately

  Scenario: user without Arbitrum taps Add Funds from confirmation screen
    Given the user has no Arbitrum network configured
    And the user is on a perpsDepositAndOrder confirmation screen

    When user taps the "Add funds" button in the token selector
    Then Arbitrum should be added to their network list
    And the deposit flow should proceed normally

Screenshots/Recordings

Before

N/A — logic fix, no UI change

After

N/A — logic fix, no UI change

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.