fix: hide HIP-3 provider prefix and gate Trade to supported xyz markets

[joaosantos15]

Description

HIP-3 perpetual markets were surfacing in the social leaderboard with their raw provider prefix (xyz:, cash:, kv: …), e.g. cash:SPCX, and the perp Trade button always linked straight to the position's symbol — even for HIP-3 providers we don't support trading.

This PR:

1. Hides the HIP-3 provider prefix everywhere a perp symbol is displayed (position detail header + profile position rows), using the controller's getPerpsDisplaySymbol (strips everything up to and including the first :). Non-HIP-3 symbols pass through unchanged.
2. Gates the Trade CTA to supported xyz markets. We only support trading xyz HIP-3 markets:
   • xyz: and non-HIP-3 symbols link directly.
   • Other HIP-3 providers are remapped to their xyz equivalent (cash:SPCX → xyz:SPCX) and linked only when that market exists in the tradable market set (checked via useTradablePerpsMarketSymbols).
   • When no corresponding xyz market exists, the button is disabled and reads "Unsupported asset".

The xyz resolution and its backing market-data subscription are scoped to a new PerpsTradeButton component (wrapped in its own PerpsStreamProvider), so spot positions never mount the provider and the subscription is limited to perp positions only. PerpsStreamProvider itself only shares the app-wide stream singleton (no connection side effects); the sole effect is subscribing to the public market-data channel, which the homepage already warms.

Changelog

CHANGELOG entry: Fixed Hyperliquid HIP-3 perp markets showing their provider prefix (e.g. cash:) in the social leaderboard, and disabled the Trade button for assets without a supported xyz market.

Related issues

Fixes: TSA-785

Manual testing steps

Feature: HIP-3 perp markets in the social leaderboard

  Scenario: Provider prefix is hidden
    Given a trader holds a HIP-3 perp position (e.g. "cash:SPCX")
    When I open their profile and the position detail
    Then the asset is shown as "SPCX" without the "cash:" prefix

  Scenario: xyz market links directly
    Given a perp position on an "xyz:" market with a tradable market
    When I tap the Trade button
    Then I land on that market's Perps detail page

  Scenario: Non-xyz HIP-3 with an equivalent xyz market
    Given a "cash:SPCX" perp position and an existing "xyz:SPCX" market
    When I tap the Trade button
    Then I land on the "xyz:SPCX" Perps detail page

  Scenario: Unsupported asset
    Given a HIP-3 perp position whose xyz equivalent does not exist
    Then the Trade button is disabled and reads "Unsupported asset"

Screenshots/Recordings

Before

After

N/A — behavioral change covered by unit tests; UI screenshots to be attached on the PR.

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

Low Risk
Social leaderboard UI and perp navigation only; no auth or payment paths, with broad unit test coverage.

Overview
HIP-3 perp symbols in the social leaderboard no longer show provider prefixes (cash:SPCX → SPCX) via getPerpsDisplaySymbol on position detail and profile rows.

Perp Trade is replaced by PerpsTradeButton, which maps symbols to tradable xyz HIP-3 markets (getSupportedXyzPerpMarketSymbol), checks the tradable set from useTradablePerpsMarketSymbols, and either navigates to Perps market details or shows a disabled Unsupported market label. Non-xyz HIP-3 positions stay enabled optimistically while the market list is empty or loading.

Unit tests cover display, navigation, gating, and optimistic behavior; copy adds unsupported_market.

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

[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.

[metamask-ci]

PR template — items to address before "Ready for review"

Warnings — informational, address before merging:

• Pre-merge author checklist has only 5 of the required 8 items. Every checklist row must be present and consciously checked — do not delete rows.

See docs/readme/ready-for-review.md for the full Definition of Ready for Review.

[metamask-ci]

PR template — items to address before "Ready for review"

Warnings — informational, address before merging:

• Pre-merge author checklist has only 5 of the required 8 items. Every checklist row must be present and consciously checked — do not delete rows.

See docs/readme/ready-for-review.md for the full Definition of Ready for Review.

[aganglada]

market instead of asset?

[xavier-brochard]

I would hide the CTA completely, otherwise the user might not have enough context to know what the button should do it asset was supported, causing confusion.

"I see this disabled button, but I have no idea what it would do if it was enabled"

[joaosantos15]

@xavier-brochard this would only happen if this was the first time you were seeing the page, right? Low probability imo

[xavier-brochard]

I think we can't just assume the user will remember what is the CTA is supposed to be doing when disabled, at any time. UI in general should be explicit, IMO.

[joaosantos15]

Fair enough. For this PR I'd rather leave it as is to avoid the design rabbit hole of where to put the "unsupported market" message. Happy to follow up on a ticket and see what/where to put it.

[xavier-brochard]

Excellent

[github-actions]

🔍 Smart E2E Test Selection

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

click to see 🤖 AI reasoning details

E2E Test Selection:
The PR modifies the Social Leaderboard's perps-related UI components:

1. New PerpsTradeButton component: Wraps the trade CTA with HIP-3 market existence checking via PerpsStreamProvider and useTradablePerpsMarketSymbols. The button is now disabled (showing "Unsupported market") when the resolved xyz market doesn't exist in the tradable list.

2. getSupportedXyzPerpMarketSymbol utility: New function that maps non-xyz HIP-3 provider symbols (e.g., cash:SPCX) to their xyz equivalent (xyz:SPCX) for routing.

3. Display symbol stripping: getPerpsDisplaySymbol is now used in useTraderPositionData, PositionRow, and TraderPositionView to strip HIP-3 prefixes (e.g., xyz:SPCX → SPCX) for display.

4. Navigation change: handlePerpTrade now receives the resolved targetSymbol from PerpsTradeButton instead of using the raw tokenSymbol, affecting which market details screen is opened.

Tag selection rationale:

• SmokePerps: Directly tests perps flows including market navigation and position management. The trade button behavior change (disabled state for unsupported markets, symbol resolution) could affect perps navigation from the social leaderboard.
• SmokeWalletPlatform: Required by SmokePerps tag description (Perps is a section inside Trending tab). Social Leaderboard is also part of the wallet platform.
• SmokeConfirmations: Required by SmokePerps tag description (Add Funds deposits are on-chain transactions).

No E2E specs directly test the Social Leaderboard trader position/profile views, so these are the closest coverage available. The changes are medium risk — they affect UI behavior and navigation logic but are scoped to the social leaderboard perps feature.

Performance Test Selection:
The changes are UI-level modifications to the Social Leaderboard's perps trade button and symbol display logic. No performance-sensitive code paths are affected: no new data fetching loops, no controller changes, no rendering-heavy operations. The PerpsStreamProvider wrapping merely shares an existing singleton stream subscription. No performance test tags are warranted.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarQube Cloud

[gauthierpetetin]

No release label on PR. Adding release label release-8.1.0 on PR, as PR was added to branch 8.1.0 when release was cut.