Description

Adds FIFA World Cup (fifwc) as a supported sports league in the Predict feature, enabling users to browse and bet on World Cup match markets with live game data.

Changes:

• Added fifwc to the PredictSportsLeague union type
• Registered fifwc in SUPPORTED_SPORTS_LEAGUES so World Cup markets appear in the sports feed
• Added fifwc to DRAW_CAPABLE_LEAGUES since soccer matches can end in draws
• Added slug config in gameParser.ts with:
  • Pattern: fifwc-{team1}-{team2}-{date}
  • Team order: home-away
  • Tag slug: fifa-world-cup

This follows the existing pattern for adding new leagues as documented in sports.ts.

Changelog

CHANGELOG entry: Added FIFA World Cup support to live sports predictions

Related issues

Fixes: N/A — feature enablement for FIFA World Cup 2026

Manual testing steps

Feature: FIFA World Cup prediction markets

  Scenario: user views World Cup markets in the sports feed
    Given the user has the Predict feature enabled
    And FIFA World Cup markets are available from the provider

    When user navigates to the Predict tab
    And user browses sports markets
    Then World Cup match markets appear in the list
    And each market displays home and away teams with logos and scores

  Scenario: user places a prediction on a World Cup match
    Given the user is viewing a FIFA World Cup match market
    And the market status is "open"

    When user selects an outcome (home win, draw, or away win)
    And user enters a bet amount
    And user confirms the prediction
    Then the order is placed successfully
    And the position appears in the user's positions list

Screenshots/Recordings

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.