chore(runway): cherry-pick fix(predict): update Polymarket adapter contract addresses

[runway-github]

• fix(predict): update Polymarket adapter contract addresses (fix(predict): update Polymarket adapter contract addresses #29573)

Description

Updates the Polymarket adapter contract addresses used by Predict to the
new CtfCollateralAdapter and NegRiskCtfCollateralAdapter values
shared by Polymarket.

Polymarket added new events on these adapters and will stop accepting
relayed transactions through the old adapters on May 1 at 3pm UTC.
Without this change, Polymarket transactions routed through the old
adapters will start failing.

Changelog

CHANGELOG entry: Updated Polymarket adapter contracts so Polymarket
prediction transactions continue working after the relayer migration.

Related issues

Fixes:

• PRED-853
• https://consensyssoftware.atlassian.net/browse/PRED-853

Manual testing steps

Feature: Polymarket adapter migration

  Scenario: user submits a Polymarket transaction after the adapter migration
    Given the app is running a build from this branch
    And the user has access to the Predict/Polymarket experience

    When the user submits a Polymarket transaction that uses the collateral adapters
    Then the app should use the updated adapter addresses
    And the transaction should be accepted by the relayer after the migration cutoff

Not run locally; constants-only configuration update.

Screenshots/Recordings

Not applicable.

Before

Not applicable.

After

Not applicable.

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.

---

Note

Medium Risk
Low code complexity, but changes production on-chain contract targets
for Polymarket claim/relay flows; incorrect addresses would cause
transactions to fail.

Overview
Updates Predict’s Polymarket configuration to use new
CtfCollateralAdapter and NegRiskCtfCollateralAdapter contract
addresses in polymarket/constants.ts.

This shifts v2 claim/relay routing (as referenced by protocol
claim.standardTarget/claim.negRiskTarget) to the new adapter
contracts to maintain compatibility with Polymarket’s relayer migration.

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

[ad31020](https://github.com/MetaMask/metamask-mobile/commit/ad31020baf93f1254dabfcc0a237c93de26d5979)

[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