chore(runway): cherry-pick fix(predict): fix unregistered wallet issue on first deposit cp-7.77.0 cp-7.78.0

[runway-github]

• fix(predict): fix unregistered wallet issue on first deposit cp-7.77.0 cp-7.78.0 (fix(predict): fix unregistered wallet issue on first deposit cp-7.77.0 cp-7.78.0 #30267)

Description

Fixes the first-deposit flow for new Predict users whose Polymarket
deposit wallet has been created but is not fully registered yet.

Polymarket advised that STATE_MINED can happen before the wallet is
usable on their side, so the deposit wallet relayer polling now treats
only STATE_CONFIRMED as a successful completion state. This keeps
polling through mined responses until Polymarket confirms the wallet,
preventing the follow-up batch transaction from failing with "wallet is
not registered".

Changelog

CHANGELOG entry: Fixed a bug that caused a user's first Predict deposit
to fail while their deposit wallet was still registering.

Related issues

Fixes: PRED-886

Manual testing steps

Feature: Predict first deposit wallet registration

  Scenario: user makes their first Predict deposit
    Given a new Predict user does not have a registered Polymarket deposit wallet

    When user starts their first deposit
    Then the app creates the deposit wallet
    And waits until the relayer reports STATE_CONFIRMED
    And proceeds with the wallet batch transaction without a "wallet is not registered" error

Screenshots/Recordings

N/A - logic-only relayer polling change.

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.

Testing

• yarn jest app/components/UI/Predict/providers/polymarket/depositWallet.test.ts --runInBand

---

Note

Medium Risk
Changes deposit-wallet relayer polling completion criteria, which can
affect first-deposit transaction flow timing and success. Low code
surface area but touches user-critical deposit execution behavior.

Overview
Fixes Predict first-deposit failures by tightening Polymarket relayer
success detection: waitForDepositWalletTransaction now treats only
STATE_CONFIRMED (not STATE_MINED) as a completion state before
proceeding.

Updates the related unit test to expect continued polling through
STATE_MINED/no-hash responses until a STATE_CONFIRMED transaction
hash is returned.

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

[dafc42c](https://github.com/MetaMask/metamask-mobile/commit/dafc42c6db046d4dd858209e93fca3888104dad3)

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

[github-actions]

🔍 Smart E2E Test Selection

⏭️ Smart E2E selection skipped - PR targets a release branch (release/*)

All E2E tests pre-selected.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud