Description

This is PR 2 for the Predict Deposit Wallet migration and is temporarily opened against predict/dw-confirmation-hooks to accelerate review while PR 1 is reviewed. Once PR 1 merges, this PR should be rebased/retargeted to main.

Polymarket migrated new API users from the legacy Safe/proxy wallet model to deterministic Deposit Wallets. This PR adds the shared Predict Deposit Wallet foundation and enables the deposit flow while preserving legacy Safe behavior for users with existing Polymarket activity.

Included changes:

• Adds walletType to Predict account state and routes users by legacy Safe activity:
  • legacy Safe with raw Polymarket activity stays on Safe
  • legacy Safe without activity routes to Deposit Wallet
  • deployed legacy Safe + Activity API failure fails closed
• Adds Deposit Wallet helper utilities for deterministic address derivation, relayer proxy calls, polling, EIP-712 batch execution, and CLOB balance-allowance sync.
• Adds Deposit Wallet deposit preflight to deploy/setup allowances in beforePublish.
• Adds legacy Safe migration sweep planning for zero-activity users with stranded pUSD/USDC.e.
• Updates deposit preparation so Deposit Wallet users receive pUSD transfers to their Deposit Wallet.
• Updates balance/position lookup to use the active Predict wallet.
• Adds post-confirm best-effort CLOB balance-allowance sync for Deposit Wallet deposits and deposit-and-order deposits.
• Keeps order and claim execution support out of scope for this PR; those follow in separate PRs.

Validation performed:

• yarn jest app/components/UI/Predict/providers/polymarket/depositWallet.test.ts app/components/UI/Predict/providers/polymarket/preflight/legacySafeMigration.test.ts app/components/UI/Predict/providers/polymarket/preflight/depositWallet.test.ts app/components/UI/Predict/providers/polymarket/preflight/v2AllowanceRequirements.test.ts app/components/UI/Predict/providers/polymarket/PolymarketProvider.test.ts app/components/UI/Predict/controllers/PredictController.test.ts app/components/UI/Predict/hooks/usePredictAccountState.test.ts --runInBand --forceExit
• yarn lint:tsc

Changelog

CHANGELOG entry: Added support for Polymarket Deposit Wallet deposits in Predict

Related issues

Fixes: PRED-858

Manual testing steps

Feature: Predict Deposit Wallet deposits

  Scenario: new Predict user deposits to a Polymarket Deposit Wallet
    Given the selected wallet has no legacy Safe Polymarket activity
    And the user opens Predict deposit

    When user confirms a Predict deposit
    Then the Deposit Wallet setup preflight runs through the relayer
    And the pUSD deposit transaction transfers funds to the derived Deposit Wallet
    And the deposit completes without changing legacy Safe users' behavior

Feature: Legacy Safe compatibility

  Scenario: existing Predict user with legacy Safe activity deposits
    Given the selected wallet has a deployed legacy Safe with Polymarket activity

    When user prepares a Predict deposit
    Then Predict keeps using the legacy Safe path
    And no Deposit Wallet relayer preflight is run

Screenshots/Recordings

N/A — core/provider flow changes covered by tests and manual wallet-flow validation.

Before

N/A

After

N/A

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.