Description

This PR updates Perps account resolution so compliance gated Perps flows evaluate the same EVM account the user currently has selected.

As part of the compliance work, Perps needs to reliably identify the active wallet address before allowing account specific actions such as deposits, trades, signing, and account state operations. The previous logic derived the address from the selected account group, which could pick a different EVM account than the user facing selected account when multiple EVM accounts exist in the group.

The solution adds a selected-account-first lookup across the Perps controller and related services. Perps now reads AccountsController:getSelectedAccount when it is an EVM account, and falls back to the existing selected account group behavior when needed. The PR also delegates that action through the Perps controller messenger so the selected account path works at runtime.

This keeps Perps address resolution aligned with the active wallet while preserving compatibility with the existing account group fallback path.

This also wires Perps cache invalidation to selected-account changes, so switching between EVM accounts in the same account group clears stale user data and preloads data for the newly selected account.

Changelog

CHANGELOG entry: Prefer the selected EVM account when resolving Perps account state and compliance-gated actions.

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

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.