chore(runway): cherry-pick feat(rewards): show VIP tag in referral code input at onboarding fix: cp-7.82.0

[runway-github]

• feat(rewards): show VIP tag in referral code input at onboarding fix: cp-7.82.0 (feat(rewards): show VIP tag in referral code input at onboarding fix: cp-7.82.0 #31530)

Description

• Shows a gold "VIP" tag next to a referral code when that code belongs
  to a VIP member — during onboarding, in settings, and on the referral
  details page.
• Makes it instantly clear to a user when they've been invited by a VIP.
• Puts the whole VIP experience behind a feature flag, so nothing
  VIP-related shows unless VIP is switched on.
• Fully backward-compatible: if VIP information isn't available, the app
  simply shows no tag and behaves exactly as before.

Depends on: consensys-vertical-apps/va-mmcx-rewards#636 — must be
merged before this ships.

Changelog

CHANGELOG entry: null

Related issues

Refs: consensys-vertical-apps/va-mmcx-rewards#636

Manual testing steps

1. Enter a VIP referral code in the rewards onboarding referral input →
   gold "VIP" tag appears next to the confirmation checkmark
2. Enter a non-VIP valid referral code → only the confirmation
   checkmark, no VIP tag
3. Enter an invalid referral code → only the error icon, no VIP tag
4. Backend returns no isVipCode field (old backend) → defaults to
   false, no VIP tag, no crash

Screenshots/Recordings

Before

After

• For vip referees

• For vips (in referral details page)

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
Touches rewards referral validation, controller caching, and new VIP
API paths; mitigated by feature-flag gating and tests, but incorrect
gating could leak VIP UI or stale referee state.

Overview
Adds a VIP referee experience parallel to the existing VIP member
flow: dashboard header entry (gold fox), splash → VIP Pilot stats
screen, Redux persistence for splash acceptance, and
getVipRefereeDashboard / referral-details fields (isVipReferee,
referredByVipCode) wired through RewardsController with VIP
feature-flag gating (including stripping stale VIP data from cache when
VIP is off).

Introduces a reusable RewardsVipReferralTag and shows it instead
of the success checkmark when a code is VIP—on onboarding,
settings (“referred by”), and referral details (for VIP
subscribers’ own code)—all gated on selectVipProgramEnabled. Referral
validation now consumes { valid, isVipCode } from the backend
(backward-safe when isVipCode is missing).

Also adds “Last updated” on the main VIP dashboard from
computedAt, extends CopyableField with trailingAccessory, and
ships broad unit test coverage for the new surfaces.

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

---

Co-authored-by: Claude Sonnet 4.6 noreply@anthropic.com
Co-authored-by: sophieqgu sophieqgu@gmail.com e16e696

[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 or stable branch (release/* or stable)

All E2E tests pre-selected.

View GitHub Actions results