chore(runway): cherry-pick fix(perps): enforce geo-block and compliance gate on Market Insights Long/Short actions

[runway-github]

• fix(perps): enforce geo-block and compliance gate on Market Insights Long/Short actions cp-7.72.1 (fix(perps): enforce geo-block and compliance gate on Market Insights Long/Short actions cp-7.72.1 #28678)

Description

The MarketInsightsView (AI summaries page) Long/Short buttons
navigated directly to PerpsOrderRedirect without checking
geo-eligibility or running the compliance gate. This allowed users in
restricted regions to bypass restrictions and open perps positions from
the Market Insights entry point, even though every other entry point
(Market Details, Order Book, Token Details) correctly blocked them.

Changes:

• Wrapped handlePerpsDirectionPress in the compliance gate() and
  added the isEligible geo-check before navigation, matching the pattern
  in PerpsMarketDetailsView and AssetOverviewContent
• Renders the PerpsBottomSheetTooltip geo-block modal ("Perps
  unavailable in your region") when the user is ineligible
• Added MARKET_INSIGHTS to PERPS_EVENT_VALUE.SOURCE for proper
  geo-block analytics attribution
• Updated existing tests and added a new test case for the ineligible
  scenario

Changelog

CHANGELOG entry: Fixed a bug where users in restricted regions could
open perps positions from the Market Insights page

Related issues

Fixes:

Manual testing steps

Feature: Perps geo-block enforcement on Market Insights

  Scenario: Restricted user taps Long on Market Insights
    Given the user is in a geo-restricted region
    And the user navigates to Market Insights for a perps asset (e.g. ETH)

    When the user taps the "Long" button
    Then the "Perps unavailable in your region" modal is shown
    And the user is NOT navigated to the order screen

  Scenario: Restricted user taps Short on Market Insights
    Given the user is in a geo-restricted region
    And the user navigates to Market Insights for a perps asset

    When the user taps the "Short" button
    Then the "Perps unavailable in your region" modal is shown
    And the user is NOT navigated to the order screen

  Scenario: Eligible user taps Long on Market Insights
    Given the user is NOT in a geo-restricted region
    And the user navigates to Market Insights for a perps asset

    When the user taps the "Long" button
    Then the user is navigated to the order screen as expected

Screenshots/Recordings

N/A — behavior matches existing geo-block modal shown on other Perps
entry points.

Before

Tapping Long/Short on Market Insights in a restricted region navigated
to the order screen (bypassing restrictions).

After

Tapping Long/Short on Market Insights in a restricted region shows the
geo-block modal and blocks navigation.

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.

---

Note

Medium Risk
Touches Perps eligibility/compliance gating and navigation from
MarketInsightsView, so mistakes could reintroduce a restriction bypass
or block eligible users; changes are localized and covered by updated
tests.

Overview
Prevents the Market Insights Perps Long/Short CTAs from navigating
directly to order flow without restrictions by wrapping the action in
the compliance gate() and checking selectPerpsEligibility first.

When ineligible, it now tracks a geo-block screen view with source
PERPS_EVENT_VALUE.SOURCE.MARKET_INSIGHTS and shows the
PerpsBottomSheetTooltip in a modal instead of navigating. Tests were
updated to handle async gated presses and a new test asserts the
ineligible geo-block behavior; the Perps view test renderer also ensures
extra routes get the same Perps providers.

^{Reviewed by Cursor Bugbot for commit
8ed8908. Bugbot is set up for automated
code reviews on this repo. Configure
here.}

---

Co-authored-by: Javier Garcia Vera javier.vera@consensys.net
Co-authored-by: javiergarciavera 76975121+javiergarciavera@users.noreply.github.com
Co-authored-by: Alejandro Garcia alejandro.garcia@consensys.net
Co-authored-by: Nicholas Gambino nicholas.gambino@consensys.net 90f34c6

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[gambinish]

Tested on Android and LGTM ✅

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokePerps, SmokeWalletPlatform, SmokeConfirmations
• Selected Performance tags: None (no tests recommended)
• Risk Level: medium
• AI Confidence: 85%

click to see 🤖 AI reasoning details

E2E Test Selection:
The changes introduce geo-eligibility gating on the Perps Long/Short buttons in MarketInsightsView. When a user is not eligible (geo-blocked), a PerpsBottomSheetTooltip modal is shown instead of navigating to the Perps order flow. Key impacts:

1. SmokePerps (primary): MarketInsightsView is navigated to from PerpsMarketDetailsView (confirmed via grep). The geo-block modal is a new UI path in the Perps flow. The existing perps-add-funds.spec.ts E2E test exercises the Perps feature and should validate the overall Perps flow still works correctly.

2. SmokeWalletPlatform (required by SmokePerps tag description): Perps is a section inside the Trending tab. Changes to Perps views affect Trending, so SmokeWalletPlatform must be included per the tag dependency rules.

3. SmokeConfirmations (required by SmokePerps tag description): Add Funds deposits are on-chain transactions, so SmokeConfirmations must be included per the tag dependency rules.

The changes are scoped to:

• A new analytics event source constant (MARKET_INSIGHTS in eventNames.ts)
• Geo-eligibility check + modal in MarketInsightsView
• Test renderer infrastructure for component-view tests (not Detox E2E)
• Unit tests for the new behavior

No changes to navigation infrastructure, Engine, controllers, or shared components that would affect other test suites (SmokeAccounts, SmokeIdentity, SmokeTrade, SmokeNetworkAbstractions, etc.).

Performance Test Selection:
The changes add a Redux selector call (selectPerpsEligibility) and a conditional modal render to MarketInsightsView. These are lightweight operations triggered only on user interaction (button press), not on initial render or data loading. No performance-sensitive paths (list rendering, app startup, balance loading, swap flows) are affected. Performance tests are not warranted.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
92.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

✅ E2E Fixture Validation — Schema is up to date
17 value mismatches detected (expected — fixture represents an existing user).
View details