Description

https://consensyssoftware.atlassian.net/browse/RWDS-1163

Leaderboard tier selector

• Replaced TabsBar with a Pressable trigger that opens a RewardsSelectSheet bottom sheet for tier selection
• Created RewardsSelectSheet -- a generic, reusable select bottom sheet registered as a transparentModal in MainNavigator.js at Routes.MODAL.REWARDS_SELECT_SHEET. Accepts title, options, selectedValue, and onSelect callback
• Default tier is the user's projected tier (from leaderboard position) when available, otherwise the top tier (last in list)

Stats summary

• Added CampaignStatsSummary component displaying Return, Market Value, Rank, and Tier in a 2x2 grid with loading skeletons and error banners

Leaderboard neighbor display (preview mode)

• When maxEntries is set and the user's tier matches the selected tier:
• If user rank is within visible range: highlights their row with bg-background-muted
• If user rank is outside visible range: shows top 3 entries + dot separator + neighbor entries (rank-1, user, rank+1)
• Handles edge cases: first/last in tier (1-2 neighbors), tier mismatch, no position data

Pending tag / Qualified tag

• Add qualified and qualifiedDays to CampaignLeaderboardEntry and CampaignLeaderboardPositionDto
• Display Pending Tag if qualified: false, Qualified tag if true

Activity view

• Group activity rows by date

Prize pool

• Add prize pool progress bar according to hardcoded breakpoints given by PRD
• Fetch total deposit volume from new endpoint Get(':campaignId/stats/deposits')

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

*After

Pending

Qualified

Activity view

Prize pool

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.

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.