Description

Adds Predict order placement support for Polymarket Deposit Wallet accounts on top of the Deposit Wallet deposit foundation.

This PR:

• Adds the POLY_1271 Polymarket signature type.
• Adds Deposit Wallet / ERC-1271 order signing via the TypedDataSign wrapper.
• Routes order maker/signer fields from active Predict account state.
• Uses Deposit Wallet maker/signer for Deposit Wallet users.
• Preserves legacy Safe order signing for grandfathered Safe users.
• Runs Deposit Wallet create/setup preflight before submitting Deposit Wallet orders.
• Passes an optional signed legacy Safe migration sweep as allowancesTx for Deposit Wallet orders, so stranded pUSD/USDC.e can be swept before the backend relays the order.
• Skips Safe trade allowance and Permit2 fee preflight for Deposit Wallet orders.
• Continues signing CLOB L2 headers with the EOA owner address.

This PR is temporarily stacked on predict/dw-deposit-foundation while PRs 1 and 2 are under review, and should be rebased/retargeted after those merge.

Validation run locally:

yarn jest app/components/UI/Predict/providers/polymarket/protocol/orderCodec.test.ts app/components/UI/Predict/providers/polymarket/PolymarketProvider.test.ts --runInBand
yarn lint:tsc

Changelog

CHANGELOG entry: Fixed Predict order placement for Polymarket Deposit Wallet accounts

Related issues

Fixes: PRED-860

Manual testing steps

Feature: Predict Deposit Wallet order flow

  Scenario: Deposit Wallet user places a Predict order
    Given a Predict user is routed to a Polymarket Deposit Wallet
      And the Deposit Wallet has enough pUSD balance and required setup from the deposit flow
    When the user places a Predict buy or sell order
    Then the order is signed with POLY_1271 semantics
      And the order is submitted successfully to the Polymarket CLOB

  Scenario: Deposit Wallet user places first order before wallet setup
    Given a Predict user is routed to a Polymarket Deposit Wallet
      And the Deposit Wallet still needs creation or allowance setup
    When the user places a Predict buy or sell order
    Then the app creates/sets up the Deposit Wallet before order submission
      And the order is submitted successfully to the Polymarket CLOB

  Scenario: Deposit Wallet user has funds stranded in legacy Safe
    Given a Predict user is routed to a Polymarket Deposit Wallet
      And the deterministic legacy Safe has sweepable pUSD or USDC.e
    When the user places a Predict buy or sell order
    Then the signed legacy Safe sweep is included as allowancesTx
      And the backend can submit the sweep before relaying the order

  Scenario: Legacy Safe user places a Predict order
    Given a Predict user is grandfathered to the legacy Safe wallet
    When the user places a Predict buy or sell order
    Then the order continues to use legacy Safe signing and preflight behavior

Screenshots/Recordings

Before

N/A - provider/order-signing change only.

After

N/A - provider/order-signing change only.

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.