This PR will fix #25144 which constantly popup QR signing transaction.

Root clause

The cause of this issue is little bit complicate,
The issue is that the Explorer/Trending tab has a Perps section that automatically initializes when the tab is clicked. This initialization:

1. Creates a wallet adapter (createWalletAdapter() in HyperLiquidWalletService.ts)
2. Prepares signing methods that require hardware wallet interaction
3. Monitors account changes via Redux subscription in PerpsConnectionManager.ts (lines 81-163)
4. Repeatedly reconnects when account changes are detected, creating new wallet adapters each time

The whole flow like below

Explorer Tab Click
  → PerpsSection renders (sections.config.tsx)
    → usePerpsMarkets() hook
      → streamManager.marketData.subscribe()
        → PerpsConnectionManager.connect()
          → setupStateMonitoring() - subscribes to Redux
            → reconnectWithNewContext() on account change
              → createWalletAdapter()
                → signTypedData method created
                  → QR POPUP TRIGGERED (for hardware wallets)

solution

implement global signing cache for DEX abstraction and referral setup

• Introduces a global singleton cache to manage signing operations for DEX abstraction, builder fee approval, and referral code setup, preventing repeated signing requests across provider reconnections.
• Updates HyperLiquidProvider to utilize the new cache for checking and setting DEX abstraction status, ensuring critical operations for hardware wallets are streamlined.
• Adds methods in PerpsConnectionManager to clear cache entries, enhancing debugging and user experience after signature rejections.
• Refactors existing logic to improve handling of concurrent signing attempts and cache state management.

This change enhances the user experience by reducing unnecessary signing prompts and improving the efficiency of the DEX abstraction process.

Description

Changelog

CHANGELOG entry: implement global signing cache for DEX abstraction and referral setup to fix the issue #25144

Related issues

Fixes: #25144

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.

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.