Description

Enables the live BTC 5-minute up/down row in the Predict homepage discovery section (HomepagePredictWorldCupDiscovery).

The row was previously gated behind a temporary SHOW_BTC_UP_DOWN_5M_ROW kill switch while waiting on the shared useCurrentCryptoUpDownMarketData hook. That hook is now wired up, so the row shows live BTC spot price, price-to-beat, and a countdown. Tapping the row opens the active BTC market details when available; otherwise it falls back to the crypto category market list.

Why: Surface live crypto up/down markets on the homepage discovery treatment and remove dead placeholder/TODO wiring.

Changes:

• Remove SHOW_BTC_UP_DOWN_5M_ROW from btcUpDown5mSeries.ts
• Wire useCurrentCryptoUpDownMarketData + usePredictNavigation in HomepagePredictWorldCupDiscovery
• Always render BtcLiveRow (no longer conditional on kill switch)
• Navigate to live market on row tap when btcMarketId is available

Changelog

CHANGELOG entry: Added a live BTC up/down row to the Predict homepage discovery section with real-time price, price-to-beat, and countdown.

Related issues

Fixes:

Manual testing steps

Feature: Predict homepage discovery BTC live row

  Scenario: BTC row displays live data when Predict is enabled
    Given Predict is enabled
    And the user is in the homepage discovery treatment (world cup discovery layout)
    When the user views the Predict section on the homepage
    Then the BTC live row is visible
    And it shows BTC spot price, price-to-beat, and a live countdown

  Scenario: Tapping BTC row opens the active market
    Given Predict is enabled
    And a live BTC 5-minute up/down market is available
    When the user taps the BTC live row
    Then the app navigates to that market's details screen
    And the entry point is HOME_SECTION

  Scenario: Tapping BTC row falls back when no live market
    Given Predict is enabled
    And no live BTC market is available
    When the user taps the BTC live row
    Then the app navigates to the Predict crypto category market list

Screenshots/Recordings

Before

After

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.