Description

fix(perps): add spotMeta caching to reduce API calls on HIP-3 markets

This PR adds session-based caching for HyperLiquid's global spotMeta endpoint to avoid redundant API calls during HIP-3 operations.

Context

Following a rate limiting incident where excessive API calls triggered HyperLiquid's rate limits (2000 msg/min), this is a defensive improvement to reduce unnecessary network requests.

Problem

The spotMeta API (which returns token metadata like USDC/USDH indices) was being called multiple times per trading session:

• getUsdcTokenId() - called during transfers
• isUsdhCollateralDex() - called to check collateral type
• swapUsdcToUsdh() - called during HIP-3 USDH swaps

Each call was making a fresh API request, even though the data (token indices) doesn't change during a session.

Solution

• Added cachedSpotMeta property for session-based caching (no TTL - token indices are stable)
• Added getCachedSpotMeta() method that returns cached data or fetches once
• Pre-fetch spotMeta in ensureReadyForTrading() when HIP-3 is enabled (non-blocking)
• Cache invalidated on disconnect() to ensure fresh state on reconnect/account switch

Design Decisions

• Global cache (not per-DEX): spotMeta is a global endpoint returning all tokens
• Session-based (no TTL): Token indices don't change during a session
• Graceful fallback: If pre-fetch fails, methods fetch on-demand
• Follows existing patterns: getCachedMeta(), getCachedPerpDexs()

Changelog

CHANGELOG entry: Fixed excessive API calls on HIP-3 markets by caching spot metadata

Related issues

Fixes: N/A (Defensive improvement following rate limiting incident)

Manual testing steps

Feature: SpotMeta caching for HIP-3 operations

  Scenario: User places order on HIP-3 DEX (SILVER)
    Given user has connected wallet with USDC balance
    And user is on a HIP-3 enabled DEX (e.g., SILVER)

    When user places an order
    Then order should succeed
    And spotMeta API should only be called once per session (check debug logs)

  Scenario: User disconnects and reconnects
    Given user has placed orders (spotMeta is cached)

    When user disconnects wallet
    And user reconnects wallet
    Then spotMeta cache should be cleared
    And next HIP-3 operation should fetch fresh spotMeta

Screenshots/Recordings

N/A - Internal optimization, no UI changes

Before

Multiple spotMeta API calls per session (one per HIP-3 operation)

After

Single spotMeta API call per session, cached for subsequent operations

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.