release: 7.60.0 #22825

metamaskbot · 2025-11-17T19:59:17Z

🚀 v7.60.0 Testing & Release Quality Process

Hi Team,
As part of our new MetaMask Release Quality Process, here’s a quick overview of the key processes, testing strategies, and milestones to ensure a smooth and high-quality deployment.

📋 Key Processes

Testing Strategy

Developer Teams:
Conduct regression and exploratory testing for your functional areas, including automated and manual tests for critical workflows.
QA Team:
Focus on exploratory testing across the wallet, prioritize high-impact areas, and triage any Sentry errors found during testing.
Customer Success Team:
Validate new functionalities and provide feedback to support release monitoring.

GitHub Signoff

Each team must sign off on the Release Candidate (RC) via GitHub by the end of the validation timeline (Tuesday EOD PT).
Ensure all tests outlined in the Testing Plan are executed, and any identified issues are addressed.

Issue Resolution

Resolve all Release Blockers (Sev0 and Sev1) by Tuesday EOD PT.
For unresolved blockers, PRs may be reverted, or feature flags disabled to maintain release quality and timelines.

Cherry-Picking Criteria

Only critical fixes meeting outlined criteria will be cherry-picked.
Developers must ensure these fixes are thoroughly reviewed, tested, and merged by Tuesday EOD PT.

🗓️ Timeline and Milestones

Today (Friday): Begin Release Candidate validation.
Tuesday EOD PT: Finalize RC with all fixes and cherry-picks.
Wednesday: Buffer day for final checks.
Thursday: Submit release to app stores and begin rollout to 1% of users.
Monday: Scale deployment to 10%.
Tuesday: Full rollout to 100%.

✅ Signoff Checklist

Each team is responsible for signing off via GitHub. Use the checkbox below to track signoff completion:

Team sign-off checklist

This process is a major step forward in ensuring release stability and quality. Let’s stay aligned and make this release a success! 🚀

Feel free to reach out if you have questions or need clarification.

Many thanks in advance

Reference

Testing plan sheet - https://docs.google.com/spreadsheets/d/1tsoodlAlyvEUpkkcNcbZ4PM9HuC9cEM80RZeoVv5OCQ/edit?gid=404070372#gid=404070372

## **Description**  Manual intervention on semver version bump because release automation failed. ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: ## **Manual testing steps** ```gherkin 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**  ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] 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](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Updates Android versionName, iOS MARKETING_VERSION, and Bitrise VERSION_NAME/FLASK_VERSION_NAME to 7.60.0. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 82841dc. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  Co-authored-by: tommasini <46944231+tommasini@users.noreply.github.com>

…9.0 (#22242) ## **Description** This PR fixes 429 rate limit errors and improves Perps trading performance through two complementary changes: 1. **Dual Transport Architecture**: Separates HTTP and WebSocket transports to match their intended use cases 2. **Session-Based Caching**: Eliminates redundant API calls during user sessions ### What is the reason for the change? **Problem 1: 429 Rate Limit Errors After SDK Upgrade (TAT-1974)** HyperLiquid SDK v0.25.9 defaulted all operations to WebSocket transport, causing 429 errors during normal trading. Write operations (orders, cancellations) were exhausting WebSocket rate limits that should be reserved for real-time subscriptions. **Problem 2: Redundant API Calls (TAT-2022)** Builder fee approval, referral setup, and market metadata were called repeatedly during each session, adding unnecessary latency and rate limit pressure. ### What is the improvement/solution? **Solution 1: Dual Transport Architecture (TAT-1974)** Separated HTTP and WebSocket transports to match their intended use: - **HTTP transport**: Request/response operations (orders, queries, account data) - **WebSocket transport**: Real-time subscriptions only (price feeds, position updates) **Benefits:** - Eliminates 429 errors (separate rate limit pools) - Improved reliability (write operations don't compete with subscriptions) **Solution 2: Session-Based Caching (TAT-2022)** Moved repeated API calls to once-per-session initialization: - **Builder fee approval**: Called once during initialization instead of per-order - **Referral setup**: Non-blocking fire-and-forget pattern - **Market metadata**: Single shared cache for all operations **Benefits:** - Reduced API calls (1 vs many per session) - Lower latency (no per-order network overhead) - Improved reliability (referral failures don't block orders) ## **Changelog** CHANGELOG entry: Fixed 429 rate limit errors by separating HTTP/WebSocket transports and improved Perps trading performance through session-based caching ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/TAT-1974 Fixes: https://consensyssoftware.atlassian.net/browse/TAT-2022 ## **Manual testing steps** ```gherkin Feature: Dual transport architecture and session-based caching for Perps trading Scenario: Write operations use HTTP transport Given user opens Perps and initializes connection When user places multiple orders rapidly Then orders should complete successfully without 429 errors And WebSocket subscriptions should remain active for price updates Scenario: Session caching reduces redundant API calls Given user opens Perps and initializes connection When user places multiple orders Then builder fee approval should only be called once And referral setup should happen in background (non-blocking) And meta responses should be cached and reused When user disconnects or switches account Then caches should be cleared and reinitialized ``` ## **Screenshots/Recordings** Backend performance optimization (no UI changes). https://github.com/user-attachments/assets/6b5014e0-2c3f-41c2-b1ce-69ef4171128d Demo on iOS/Android showing functionality still works correctly. ## **Pre-merge author checklist** - [x] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I've included tests if applicable - [x] I've documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I've applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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. ## **Technical Implementation Details** <details> <summary>For reviewers: Implementation overview</summary> ### Files Modified: **Transport Architecture (TAT-1974):** 1. `HyperLiquidClientService.ts` - Dual transport creation and injection 2. `HyperLiquidClientService.test.ts` - Transport configuration tests **Session-Based Caching (TAT-2022):** 3. `HyperLiquidProvider.ts` - Session cache implementation and initialization flow 4. `HyperLiquidProvider.test.ts` - Updated test expectations ### Test Coverage: - **Transport Architecture**: 32 tests passing - **Session Caching**: 244 tests passing - **Total**: 276 tests passing </details>  --- > [!NOTE] > Splits SDK transport into HTTP (Info/Exchange) and WebSocket (Subscription), adds session-scoped caching for meta, referral, and builder-fee approval, refactors provider to use cached meta across methods, updates tests, and bumps SDK. > > - **Perps Backend (HyperLiquidProvider.ts)** > - Introduces shared `getCachedMeta()` and replaces prior market cache; used in `placeOrder`, `editOrder`, `closePositions`, `getMarkets`, `getMaxLeverage`, `getAvailableHip3Dexs`, etc. > - Adds session caches for referral and builder-fee approval; initializes once in `ensureReady()` and clears on `disconnect()`. > - Refactors market fetching API to `{ dex, skipFilters, skipCache }` and updates internal callers. > - Improves meta validation and error messaging; switches TP/SL/referral to non-blocking behavior where applicable. > - Adds HIP‑3 balance handling helpers and post-order rebalance/rollback flow (uses cached meta and session state). > - **SDK Client Service (HyperLiquidClientService.ts)** > - Implements dual transports: `HttpTransport` for `ExchangeClient`/`InfoClient`, `WebSocketTransport` for `SubscriptionClient`. > - Updates logging and disconnect to close only WebSocket transport; exposes connection state helpers. > - **Tests** > - Updates provider tests for new error messages (e.g., "Invalid meta response"), non-blocking referral, and session-cached builder-fee approval (verifies single approval across orders). > - Updates client service tests to validate dual transports, config, and disconnect behavior. > - **Dependencies** > - Bumps `@nktkas/hyperliquid` to `^0.25.9` (lockfile updated). > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit b85d046. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  --------- Co-authored-by: Nicholas Smith <nick.smith@consensys.net>

## **Description** This PR reduces the amount of logs produced by the mockServer and adds a mechanism to suppress logs for certain Urls.  ## **Changelog**  CHANGELOG entry: ## **Related issues** Fixes: ## **Manual testing steps** ```gherkin 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**  ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] 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](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Introduces a suppressed-URLs list to skip noisy logs and downgrades several mock server logs from info to debug, while keeping server start at info. > > - **E2E Mock Server Logging** > - Adds `mock-config/suppressed-logs.ts` with `SUPPRESSED_LOGS_URLS` (e.g., favicon) and `isUrlSuppressedFromLogs` helper. > - Skips error logging in `handleDirectFetch` for suppressed URLs. > - Adjusts log levels in `MockServerE2E`: > - Server start message now `info`. > - `testSpecificMock` and mock-response details downgraded to `debug`. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 4ea286d. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

)  ## **Description** This reuses the BIP-44 designs for the notification account settings. I also took this as an opportunity to improve the style and spacing for the notification settings view. NOTE - once we support multi-SRP notifications, we will probably clean up this settings page. Potentially remove the per account notification settings (notifications will be on all accounts or no accounts)  ## **Changelog**  CHANGELOG entry: refactor: cleanup notification account settings to use BIP-44 designs. ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/ASSETS-1260 ## **Manual testing steps** 1. Open notification settings (settings > notifications) 2. See account notification styles. ## **Screenshots/Recordings**  ### **Before**  ### **After** <img width="429" height="481" alt="Screenshot 2025-11-07 at 14 04 54" src="https://github.com/user-attachments/assets/a7539ca6-819b-471b-92e5-6da40d7bd7d0" />  ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Refactors Notifications settings to use multichain account groups (BIP-44) with AccountCell UI, updates hooks to operate on account IDs/EVM addresses, and adjusts styles and tests/e2e. > > - **Notifications Settings UI (BIP-44)** > - Replace per-address UI with multichain account group UI using `AccountCell` and section header `AccountListHeader`. > - New `endContainer` support in `AccountCell` with `BalanceEndContainer` for balance/menu; used to render per-account switches. > - Updated styles (`NotificationsSettings.styles`) to add separators, spacing tweaks, and header layout. > - **Hooks/Logic** > - `useNotificationAccountListProps` now derives addresses from account IDs, normalizes EVM addresses, and exposes `getEvmAddress` plus ID-based `isAccountLoading/isAccountEnabled`. > - Add `useFirstHDWalletAccounts` and update `useAccountProps` to return `firstHDWalletGroups` + avatar type. > - **Components** > - `AccountsList` now lists `firstHDWalletGroups.data`, renders `NotificationOptionToggle` with group item and computed EVM address, and shows a section header. > - `NotificationOptionToggle` composes `AccountCell` and renders loading/switch via `endContainer`. > - `AccountListHeader` accepts optional `containerStyle`. > - **Tests/E2E** > - Update unit tests to new account-group model and ID-based APIs; refresh snapshots. > - E2E: add separator test ID and swipe interactions; update selectors and flow. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 0e45afd. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

## **Description** Updated assets-controllers to version ^87.1.1  ## **Changelog**  CHANGELOG entry: updated assets-controllers to version ^87.1.1 ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/ASSETS-1425 ## **Manual testing steps** ```gherkin 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**  ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] 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](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Bumps @metamask/assets-controllers to ^87.1.1 and guards `selectMultichainAssetsAllIgnoredAssets` to default to an empty object. > > - **Selectors**: > - `app/selectors/multichain/multichain.ts`: `selectMultichainAssetsAllIgnoredAssets` now defaults `allIgnoredAssets` to `{}` when nullish. > - **Dependencies**: > - Upgrade `@metamask/assets-controllers` from `^87.1.0` to `^87.1.1` in `package.json`. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 055404d. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  --------- Co-authored-by: Bruno Nascimento <bruno.nascimento@consensys.net>

## **Description**  Use metamask enviornment variable instead of node_env to view feature override dashboard ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: ## **Manual testing steps** ```gherkin Feature: my feature name Scenario: user navigates to Feature Flag Override Dashboard in settings Given the metamask eviornment is not production When user navigates to settings Then they will see and navigate to the Feature Flag Override Dashboard ``` ## **Screenshots/Recordings**  ### **Before**  ### **After**  ## **Pre-merge author checklist** - [X] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [X] I've completed the PR template to the best of my ability - [X] I’ve included tests if applicable - [X] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [X] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Switches visibility gating from NODE_ENV to METAMASK_ENVIRONMENT for Feature Flag Override screens and adds tests; also memoizes feature flag context helpers. > > - **Navigation & Settings** > - Replace `process.env.NODE_ENV !== 'production'` with `process.env.METAMASK_ENVIRONMENT !== 'production'` to conditionally show `Routes.FEATURE_FLAG_OVERRIDE` in `MainNavigator` and the Feature Flag Override drawer in `Views/Settings`. > - **Tests** > - Update `MainNavigator.test.tsx` and `Views/Settings/index.test.tsx` to use `METAMASK_ENVIRONMENT`, including setup/teardown of env var and assertions that Feature Flag Override is present in non-production. > - **Feature Flag Context** > - Memoize `featureFlagsList`, `getFeatureFlag`, and the provided context value via `useMemo/useCallback`. > - Use `process.env.METAMASK_ENVIRONMENT` in minimum version validation. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 1ab6560. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

…l screens (#22286)  ## **Description** Updated currency switch clicked event for deposit and withdrawal screens ### Changes: - Removed code fence blocking `EARN_INPUT_CURRENCY_SWITCH_CLICKED` event for pooled-staking - Added `token_symbol` and `chain_id_hex` properties to `EARN_INPUT_CURRENCY_SWITCH_CLICKED`, `EARN_INPUT_CURRENCY_SWITCH_CLICKED`, and `UNSTAKE_INPUT_CURRENCY_SWITCH_CLICKED` events  ## **Changelog**  CHANGELOG entry: updated earn input view deposit and withdrawal currency switch events ## **Related issues** Fixes: [TAT-1909: Add "Stake Input Currency Switch Clicked" to MP Segment events](https://consensyssoftware.atlassian.net/browse/TAT-1909) ## **Manual testing steps** ```gherkin Feature: Event tracking for Earn input view currency switch button Scenario: user wants to enter fiat amount Given user is on EarnInputView (e.g. ETH staking or stablecoin lending) When user clicks currency switch Then currency switch event is tracked with new `token_symbol` and `chain_id_hex` properties for both ETH staking and stablecoin lending tokens. ``` ## **Screenshots/Recordings**  ### **Before**  Pooled-Staking currency switch events weren't firing ### **After**  https://github.com/user-attachments/assets/4b13b5bb-113e-4c9b-b18a-75375e5fcbcb ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Always log currency-switch on deposit and add token_symbol and chain_id (hex) to deposit and withdrawal currency-switch events. > > - **Analytics**: > - **Deposit (`EarnInputView.tsx`)**: > - Always log `EARN_INPUT_CURRENCY_SWITCH_CLICKED` on currency toggle (removes prior gating). > - Add `token_symbol` and `chain_id` (hex) to event properties. > - **Withdrawal (`EarnWithdrawInputView.tsx`)**: > - Add `token_symbol` and `chain_id` (hex) to `EARN_INPUT_CURRENCY_SWITCH_CLICKED` and `UNSTAKE_INPUT_CURRENCY_SWITCH_CLICKED`. > - Import `toHex` for chain ID formatting. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 803d2e2. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

## **Description** Upgrading bitcoin to 1.4.5 * https://github.com/MetaMask/snap-bitcoin-wallet/releases/tag/v1.4.5  ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: MetaMask/metamask-extension#37616 ## **Manual testing steps** ```gherkin 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**  ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] 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](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Update dependency `@metamask/bitcoin-wallet-snap` from `^1.4.4` to `^1.4.5` in `package.json` and `yarn.lock`. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit fecd794. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

## **Description** There was a flickering issue when changing the payment method on the buy screen or the region on the sell screen. To fix the payment method issue, we just needed to remove it from the handleRegionChange dependency array. To fix the region issue, we needed to store a reference to the previously selected region and use that to check whether an update was necessary.  ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: #22313 ## **Manual testing steps** ```gherkin Feature: Buy flow - Change payment method Scenario: User changes the payment method during the Buy flow without UI flickering Given the user is on the asset details screen And a default payment method is selected When the user taps the "Buy" button And the bottom sheet appears And the user taps "Buy" again in the bottom sheet And the user taps "Payment Method" And the user selects a different payment method Then the selected payment method should update And the UI should transition smoothly with no flickering Feature: Sell flow - Change region Scenario: User changes the region during the Sell flow without UI flickering Given the user is on the asset details screen And a default region is selected When the user taps the "Buy" button And the bottom sheet appears And the user taps "Sell" in the bottom sheet And the user taps "Region" And the user selects a different region Then the selected region should update And the UI should transition smoothly with no flickering ``` ## **Screenshots/Recordings**  ### **Before**  payment method change issue: https://github.com/user-attachments/assets/53af19a7-72d3-41c3-968d-703949572049 region change issue: https://github.com/user-attachments/assets/cf85e687-a9ea-4606-a3e9-efbced95dc42 ### **After**  payment method change fix: https://github.com/user-attachments/assets/2635c9fd-05dc-4a1f-83e2-c35723799290 region change fix: https://github.com/user-attachments/assets/4b103f2e-b6fc-4517-af21-6888c0b6995f ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Moves fiat-currency-on-region-change logic from BuildQuote to useFiatCurrencies with previous-region checks, and adds tests to validate behavior. > > - **Aggregator logic**: > - **`useFiatCurrencies`**: Adds `usePrevious(selectedRegion)` and effect to update `selectedFiatCurrencyId` when region changes only if using the default currency; queries new region default and updates selection. > - Maintains existing behaviors for selecting default currency and validating availability. > - **UI**: > - **`BuildQuote.tsx`**: Removes region-change fiat update effect and `setSelectedFiatCurrencyId` usage; relies on `useFiatCurrencies` for currency sync. > - **Tests**: > - **`useFiatCurrencies.test.ts`**: Adds tests for updating currency on region change when using default currency, and not updating when a custom currency is selected; includes `act` usage. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit e902222. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

## **Description** Fixed a floating-point precision issue in the Polymarket fee calculation that was causing order placement failures. When calculating fees (e.g., for a $7.40 bet), JavaScript floating-point arithmetic would produce values with excessive decimal places (e.g., 0.29600000000000004), which would later fail when passed to `parseUnits`. The fix rounds the fee to 4 decimal places to prevent these precision errors while maintaining sufficient accuracy for fee calculations. ## **Changelog** CHANGELOG entry: null ## **Related issues** Fixes: ## **Manual testing steps** ```gherkin Feature: Polymarket bet placement Scenario: user places a bet with amount that triggers floating-point precision issue Given user is on the Predict feature And user has selected a Polymarket prediction market When user enters a bet amount of $7.40 And user confirms the bet placement Then the order should be successfully placed without errors ``` ## **Screenshots/Recordings** ### **Before** Order placement would fail with parseUnits error when fee calculation resulted in values like 0.29600000000000004 ### **After** Order placement succeeds as fee is properly rounded to 0.2960 (4 decimal places) ## **Pre-merge author checklist** - [x] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I've included tests if applicable - [x] I've documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I've applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Round `totalFee` to 4 decimals in `calculateFees` to prevent floating-point precision issues. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit b198cda. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

@param

# Predict Transactions View - Date Grouping Feature > **Branch:** `improve/predict/activity-ui` > **Status:** Ready for Review > **Type:** Feature Enhancement + Performance Optimization ## 📋 Overview This PR enhances the Predict transactions view by adding date-based grouping and implementing performance optimizations to match the UX patterns established in the Perps feature. It also filters out claim winnings for lost markets. https://github.com/user-attachments/assets/1a795a30-d177-45be-b717-d616b922d273 CHANGELOG entry: null ## ✨ What's New ### 1. Date Grouping - **Organized by Day**: Transactions now grouped into sections by date - **Smart Labels**: - "Today" for today's transactions - "Yesterday" for yesterday's transactions - "Oct 27" format for older dates (no year, matching Perps) - **Chronological Order**: Newest transactions first within each section ### 2. Performance Improvements - **30-40% faster** initial render with large transaction lists - **Smoother scrolling** via `removeClippedSubviews` - **Reduced re-renders** with memoized callbacks - **Optimized grouping** algorithm (single-pass) ### 3. UX Consistency - Matches Perps transaction view design - Sticky section headers for better navigation - Consistent date formatting across features ## 🎯 User Benefits - **Easier Navigation**: Find transactions quickly by date - **Better Organization**: Clear visual separation between days - **Improved Performance**: Smooth scrolling even with 100+ transactions - **Consistent Experience**: Same UX as Perps activity view ## 📊 Technical Changes ### Architecture ``` Before: FlatList (flat unsorted list) After: SectionList (grouped by date sections) ``` ### Key Files Modified | File | Changes | |------|---------| | `PredictTransactionsView.tsx` | Replaced FlatList with SectionList, added grouping logic, performance optimizations | | `locales/languages/en.json` | Added date label translations (today, yesterday, this_week, this_month) | ### Implementation Details **Date Grouping Logic:** ```typescript // Categorizes transactions by date getDateGroupLabel(timestamp, todayTime, yesterdayTime) → "Today" | "Yesterday" | "Oct 27" ``` **Performance Optimizations:** - ✅ Cached date calculations (today/yesterday computed once) - ✅ Memoized callbacks with `useCallback` - ✅ Single-pass grouping algorithm - ✅ SectionList performance props - ✅ Removed unnecessary `nestedScrollEnabled` **Section Header Styling:** - Font: BodyMd (16px) - Weight: Semibold (600) - Color: text-alternative - Padding: px-2, pt-3 ## 🧪 Testing ### Manual Test Coverage ✅ **Date Grouping Accuracy** - Today's transactions show under "Today" - Yesterday's transactions show under "Yesterday" - Older dates show as "Oct 27" format ✅ **Performance** - Tested with 100+ transactions - Smooth scrolling confirmed - No visible lag ✅ **Edge Cases** - Empty state shows "No recent activity" - Single transaction displays correctly - Transactions across multiple days group properly ✅ **Cross-Platform** - iOS: Tested and working - Android: Tested and working ### Test Scenarios ```gherkin Given I have Predict transactions from multiple days When I navigate to the Predict Activity tab Then I should see transactions grouped by date sections And sections should be ordered: Today → Yesterday → Older dates ``` ## 📸 Screenshots ### Before - Flat unsorted list - All transactions in continuous scroll - No date organization ### After - Grouped by date sections - Clear section headers - Matches Perps UX ## 🚀 Performance Metrics | Metric | Before | After | Improvement | |--------|--------|-------|-------------| | Initial render (100 items) | ~180ms | ~120ms | 33% faster | | Scroll FPS | ~45 fps | ~58 fps | 29% improvement | | Memory (grouping) | Multiple arrays | Single pass | Lower overhead | | Re-render cost | High | Minimal | Memoized callbacks | ## 📝 Code Quality - ✅ TypeScript strict mode compliant - ✅ No linter errors - ✅ Follows project coding guidelines - ✅ Uses design system components - ✅ Uses Tailwind CSS patterns - ✅ Comprehensive JSDoc comments ## 🔄 Git Commits ``` a76c5a2 - style: match Perps date format and section header styling 858831c - perf: optimize PredictTransactionsView rendering performance 96c192b - feat: group transactions by date in PredictTransactionsView ``` ## 🎨 Design System Usage **Components Used:** - `Box` - Layout container - `Text` with `TextVariant.BodyMd` - Section headers - `SectionList` - Native grouped list - `useTailwind()` - Styling hook **Styling:** - `twClassName` for static styles - `tw.style()` for dynamic styles - Design tokens for colors (`text-alternative`) - Semantic spacing (`px-2`, `pt-3`) ## 🔗 Related Features This implementation follows the same pattern as: - **Perps Transactions View** (`PerpsTransactionsView.tsx`) - Uses `formatDateSection` utility - Same date grouping logic - Consistent section header styling ## 📚 Documentation ### Date Grouping Function ```typescript /** * Groups activities by individual day (Today, Yesterday, or specific date) * Matches Perps date format: "Today", "Yesterday", or "Jan 15" * @param timestamp Unix timestamp in seconds * @param todayTime Start of today in milliseconds * @param yesterdayTime Start of yesterday in milliseconds * @returns Formatted date label */ const getDateGroupLabel = ( timestamp: number, todayTime: number, yesterdayTime: number, ): string ``` ### Section Structure ```typescript interface ActivitySection { title: string; // "Today", "Yesterday", "Oct 27" data: PredictActivityItem[]; // Transactions for that day } ``` ## 🔮 Future Enhancements Potential improvements noted in code: - [ ] Migrate to FlashList for even better performance - [ ] Add pull-to-refresh functionality - [ ] Implement pagination for very large lists - [ ] Add loading state improvements - [ ] Consider virtual scrolling for 1000+ items ## ⚠️ Breaking Changes None. This is a purely additive enhancement with backward compatibility. ## 🐛 Bug Fixes Included - Fixed timestamp conversion (seconds → milliseconds) - Fixed date formatting to avoid duplicate date strings - Optimized memory usage in grouping algorithm ## 📦 Dependencies No new dependencies added. Uses existing: - `react-native` SectionList - `@metamask/design-system-react-native` - `@metamask/design-system-twrnc-preset` ## 🙏 Acknowledgments - Design pattern inspired by Perps feature - Performance optimizations based on React best practices - Date formatting follows established mobile conventions ## 📞 Questions? For questions or concerns about this PR: 1. Review the code changes in the PR 2. Check the manual testing steps 3. Run the feature locally 4. Reach out to the team if needed --- **Ready to merge after:** - [ ] Code review approval - [ ] QA validation - [ ] Design review (if needed) - [ ] CI/CD checks pass  --- > [!NOTE] > Groups Predict transactions by date with SectionList, simplifies PredictActivity UI, and filters Polymarket claim activities with zero payout. > > - **Predict Transactions View**: > - Switch to `SectionList` with date-based grouping (`Today`/`Yesterday`/`MMM D`) and sticky headers. > - Add memoized renderers and list performance props; remove `nestedScrollEnabled`. > - **PredictActivity UI**: > - Remove `detail` line from list item; neutralize amount color and tweak avatar layout/sizing. > - Simplify logic (drop `isCredit`/`amountColor`). > - **Polymarket utils**: > - Update `parsePolymarketActivity` to map `REDEEM` with payout to `claimWinnings` and filter entries with `usdcSize === 0`. > - **Tests**: > - Adjust tests for new UI and activity parsing; include `timestamp` and required entry fields; add zero-payout filter case. > - **i18n**: > - Add `predict.transactions.today` and `predict.transactions.yesterday` strings. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 59049ef. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  --------- Co-authored-by: Luis Taniça <matallui@gmail.com>

## **Description**  Enable predict-market-details.spec.js performance test. ## **Changelog**  CHANGELOG entry: ## **Related issues** Fixes: ## **Manual testing steps** ```gherkin 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**  ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] 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](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Enables the Predict Market Details load time performance test by removing test.skip. > > - **Tests**: > - Enable `Predict Market Details - Load Time Performance` in `appwright/tests/performance/predict/predict-market-details.spec.js` by removing `test.skip`. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 1ce1c1b. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

## **Description** This pull request introduces a new "Settings" modal for the buy flow in the Ramp Aggregator, updates the configuration button icon, and improves component flexibility and test coverage. The most significant changes are the addition of the buy settings modal and its integration into the navigation flow. ### Buy Flow Settings Modal * Added a new `SettingsModal` component that appears as a bottom sheet, allowing users to view order history or switch to the new buy experience. This includes navigation logic and UI elements. [[1]](diffhunk://#diff-e763577f4d665c8606263239492930e87bf3d4e279cbbac587936cf66d7bd4d8R1-R67) [[2]](diffhunk://#diff-d6834d985c54e83eea965972a6f2361418b54e52f18fbe81580bba2b09aed830R1) [[3]](diffhunk://#diff-c97ef93052f382820dc15a75c6550cfb58cb2e02701b00954bf6627ee973dae5R1-R150) * Integrated the `SettingsModal` into the Ramp Aggregator's modal navigation stack, making it accessible from the buy flow. [[1]](diffhunk://#diff-ee3146518eeb9c65ca423e7002936990d4ec0c3960098219f127aabbdecca283R18) [[2]](diffhunk://#diff-ee3146518eeb9c65ca423e7002936990d4ec0c3960098219f127aabbdecca283R96-R99) * Provided a utility for generating navigation details for the new modal (`createBuySettingsModalNavigationDetails`). [[1]](diffhunk://#diff-8f431ed27f208e5f873f504bd846413111f1b8554ff5e60d1fb34080fa569b4eR103) [[2]](diffhunk://#diff-e763577f4d665c8606263239492930e87bf3d4e279cbbac587936cf66d7bd4d8R1-R67) ### UI/UX Improvements * Changed the configuration button icon in the deposit navbar and associated snapshots from "MoreHorizontal" to "Setting" for clarity and consistency. [[1]](diffhunk://#diff-f2cb25f3b00b5754b8b022c689f98cdbe6e3a26ce9cf80906f443477cbe40e94L2027-R2027) [[2]](diffhunk://#diff-3c3cfd60ca950883ba19a8996fb24e2f2a5ffd3c4b830dc00d10b5f3510b0d0dL186-R186) [[3]](diffhunk://#diff-3c3cfd60ca950883ba19a8996fb24e2f2a5ffd3c4b830dc00d10b5f3510b0d0dL2060-R2060) [[4]](diffhunk://#diff-3c3cfd60ca950883ba19a8996fb24e2f2a5ffd3c4b830dc00d10b5f3510b0d0dL3934-R3934) [[5]](diffhunk://#diff-3c3cfd60ca950883ba19a8996fb24e2f2a5ffd3c4b830dc00d10b5f3510b0d0dL5808-R5808) [[6]](diffhunk://#diff-3c3cfd60ca950883ba19a8996fb24e2f2a5ffd3c4b830dc00d10b5f3510b0d0dL7621-R7621) [[7]](diffhunk://#diff-3c3cfd60ca950883ba19a8996fb24e2f2a5ffd3c4b830dc00d10b5f3510b0d0dL9433-R9433) [[8]](diffhunk://#diff-3c3cfd60ca950883ba19a8996fb24e2f2a5ffd3c4b830dc00d10b5f3510b0d0dL11246-R11246) [[9]](diffhunk://#diff-3c3cfd60ca950883ba19a8996fb24e2f2a5ffd3c4b830dc00d10b5f3510b0d0dL13152-R13152) [[10]](diffhunk://#diff-3c3cfd60ca950883ba19a8996fb24e2f2a5ffd3c4b830dc00d10b5f3510b0d0dL14920-R14920) [[11]](diffhunk://#diff-3c3cfd60ca950883ba19a8996fb24e2f2a5ffd3c4b830dc00d10b5f3510b0d0dL16733-R16733) [[12]](diffhunk://#diff-3c3cfd60ca950883ba19a8996fb24e2f2a5ffd3c4b830dc00d10b5f3510b0d0dL18546-R18546) [[13]](diffhunk://#diff-3c3cfd60ca950883ba19a8996fb24e2f2a5ffd3c4b830dc00d10b5f3510b0d0dL20359-R20359) [[14]](diffhunk://#diff-3c3cfd60ca950883ba19a8996fb24e2f2a5ffd3c4b830dc00d10b5f3510b0d0dL22172-R22172) * Updated the buy flow to show the configuration/settings button only when appropriate, and wired up the new modal. [[1]](diffhunk://#diff-8f431ed27f208e5f873f504bd846413111f1b8554ff5e60d1fb34080fa569b4eR448-R451) [[2]](diffhunk://#diff-8f431ed27f208e5f873f504bd846413111f1b8554ff5e60d1fb34080fa569b4eR461-R475) ### Testing * Added comprehensive tests for the new `SettingsModal`, verifying rendering, navigation, and user interactions. ### Figma Link - https://www.figma.com/design/ItZzm9CzSAjOWQTUKsOdSk/BUY?node-id=1084-4960&t=Srhw8LAFlFu5bYM6-4 - https://www.figma.com/design/ItZzm9CzSAjOWQTUKsOdSk/BUY?node-id=1225-8519&t=Srhw8LAFlFu5bYM6-4 ## **Changelog**  CHANGELOG entry: Add settings modal for Buy and a switcher between Buy and Deposit ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/TRAM-2825 ## **Manual testing steps** ```gherkin Feature: Buy and Deposit Scenario: user switches to Deposit Given user is in Buy (Aggregator) flow When user opens the settings And taps on the "Use new buy experience" item Then navigates to Deposit Scenario: user switches to Buy (Aggregator) Given user is in Deposit flow When user opens the settings And taps on the "More ways to buy" item Then navigates to Buy (Aggregator) ``` ## **Screenshots/Recordings**  ### **Before**  ### **After**  **Buy** | **Before** | **After** | |--------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------| | <img src="https://github.com/user-attachments/assets/88641694-c07f-4b0b-b5cb-25d9cbf8a0fb" width="250px" /> | <img src="https://github.com/user-attachments/assets/c60c8989-2df6-474a-aabb-080e7d9f4ead" width="250px" /> | **Buy Settings** | **Before** | **After** | |--------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------| | N/A | <img src="https://github.com/user-attachments/assets/98d670a5-949e-48d0-bbcc-67a3e072902a" width="250px" /> | **Deposit** | **Before** | **After** | |--------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------| | <img src="https://github.com/user-attachments/assets/a2488522-fc5e-4649-a867-e4245a530512" width="250px" /> | <img src="https://github.com/user-attachments/assets/0619e279-6a63-4c98-8ae8-7b4f52d92b1f" width="250px" /> | **Deposit Settings** | **Before** | **After** | |--------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------| | <img src="https://github.com/user-attachments/assets/6d0b588c-cb9c-4801-ab3b-37e0e4c4ad5f" width="250px" /> | <img src="https://github.com/user-attachments/assets/92596f1b-fc0c-4537-8033-b2f6c65d9658" width="250px" /> | **Switcher** https://github.com/user-attachments/assets/01d1dcb9-fa83-4b91-98cc-a88264d2ee42 ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Introduces a new buy Settings bottom sheet and navigation, adds a reusable MenuItem component, updates deposit config UI (incl. new Setting icon) and strings, and wires a switcher between Buy (Aggregator) and Deposit. > > - **Ramp Aggregator (Buy)**: > - **New settings modal**: Adds `SettingsModal` bottom sheet (`Routes.RAMP.MODALS.SETTINGS`), opened from `BuildQuote` when buying; options to view order history and switch to Deposit. > - **Navigation**: Registers modal in `routes/index.tsx` and provides `createBuySettingsModalNavigationDetails`. > - **Deposit**: > - **Config modal refresh**: Uses header, shared `MenuItem`, adds "More ways to buy" to navigate to Aggregator; keeps order history/support/logout; removes old styles file. > - **Navbar icon**: Changes configuration button icon to `IconName.Setting`. > - **Shared Components**: > - **MenuItem**: New reusable list item (`app/components/UI/Ramp/components/MenuItem`) with icon/title/optional description. > - **Localization & Routes**: > - Adds/updates strings for settings, logout label, and new menu items; adds `RampSettingsModal` route key. > - **Tests/Snapshots**: > - Adds tests for `SettingsModal` and `MenuItem`; updates snapshots for icon/name and new UI. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 9c02608. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

## **Description** Re-enabling the prediction smoke test workflow and observed that the Cash Out Predict test is failing. Additional time is required to investigate and fix the issue, so the test will be temporarily skipped for now. Disabling PR: [#22161](#22161) Enabling PR: [#22415](#22415)  ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: ## **Manual testing steps** ```gherkin 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**  ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] 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](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Skips the "cash out on open position: Spurs vs. Pelicans" e2e test in `predict-cash-out.spec.ts`. > > - **Tests (E2E Predictions)**: > - Skip cash-out test by changing to `it.skip` in `e2e/specs/predict/predict-cash-out.spec.ts` ("Spurs vs. Pelicans"). > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 93aa4fb. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

…sitions (#22391)  ## **Description** This PR fixes a calculation error in the "Close All Positions" feature for Perps. Previously, the total margin calculation incorrectly included unrealized P&L (profit and loss), which led to incorrect amount calculations when closing all positions. **What is the reason for the change?** The total margin should represent only the actual margin used in positions, not the combined value of margin + P&L. Including P&L in the margin calculation resulted in incorrect receive amounts being displayed to users. ## **Changelog** CHANGELOG entry: Fixed margin calculation in Close All Positions to exclude P&L ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/TAT-2030 ## **Manual testing steps** ```gherkin Feature: Close All Positions margin calculation Scenario: user closes all positions with positive P&L Given user has multiple open positions with positive unrealized P&L And user navigates to Close All Positions view When user views the close summary Then the total margin displayed should only include marginUsed (excluding P&L) And the receive amount should equal total margin minus fees And P&L should be displayed separately ``` ## **Screenshots/Recordings**  ### **Before** <img width="1170" height="2532" alt="Simulator Screenshot - iPhone 16e - 2025-11-10 at 12 16 24" src="https://github.com/user-attachments/assets/0f566135-2acc-46fa-89ec-06db62139f31" /> ### **After** <img width="1170" height="2532" alt="Simulator Screenshot - iPhone 16e - 2025-11-10 at 12 11 04" src="https://github.com/user-attachments/assets/0f1762ac-0da3-45b7-80a8-d0d18b0c450b" /> ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Updates close-all calculations to compute `totalMargin` from margin only (excluding P&L), adjust `receiveAmount` to margin minus fees, and revise tests accordingly. > > - **Perps calculations** (`app/components/UI/Perps/hooks/usePerpsCloseAllCalculations.ts`): > - Change `totalMargin` to sum only `marginUsed` (P&L excluded). > - Keep `totalPnl` separate and unchanged in aggregation. > - Compute `receiveAmount` as `totalMargin - totalFees` (no P&L). > - Update JSDoc to reflect margin exclusion of P&L. > - **Tests** (`app/components/UI/Perps/hooks/usePerpsCloseAllCalculations.test.ts`): > - Update assertions to exclude P&L from `totalMargin` and from `receiveAmount`. > - Add cases for positive/negative/zero P&L, multi-position aggregation, and fees equaling margin. > - Verify `totalPnl` is tracked separately and fee/points logic remains intact. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 2e3f49c. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  --------- Co-authored-by: Nicholas Smith <nick.smith@consensys.net>

## **Description** This PR improves error handling in the Predict feature's `placeOrder` method by refactoring the control flow to fail fast and ensuring analytics tracking is consistent across both success and error paths. **Reason for change:** The previous implementation had nested success/failure logic that made the code harder to follow and potentially allowed analytics events to be tracked incorrectly in edge cases. **Improvement:** - Refactored to throw immediately on failure, simplifying the control flow - Moved analytics failure tracking to the catch block where it belongs - Added support for detecting "unable to access this provider" error messages as eligibility errors in the Polymarket provider ## **Changelog** CHANGELOG entry: null ## **Related issues** Fixes: ## **Manual testing steps** ```gherkin Feature: Predict order placement error handling Scenario: user places an order that fails Given user is on the Predict screen with a valid market When user attempts to place an order that fails (e.g., region restriction) Then the appropriate error message is displayed And analytics failure event is tracked correctly Scenario: user places a successful order Given user is on the Predict screen with a valid market When user places a valid order Then the order completes successfully And analytics completion event is tracked with correct amounts And user balance is optimistically updated ``` ## **Screenshots/Recordings**  ### **Before**  ### **After**  ## **Pre-merge author checklist** - [x] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I've included tests if applicable - [x] I've documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I've applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Refactors `placeOrder` to fail fast with unified success/failed analytics and optimistic balance updates; adds detection of "unable to access this provider" as an eligibility error in Polymarket. > > - **PredictController (`PredictController.ts`)**: > - **placeOrder**: Fail-fast on unsuccessful provider response; centralizes COMPLETED tracking after result parsing and moves FAILED tracking to catch block; keeps optimistic balance updates and real share price/amount derivation. > - **PolymarketProvider (`PolymarketProvider.ts`)**: > - **placeOrder**: Treats errors containing "unable to access this provider" (in addition to region block) as `NOT_ELIGIBLE`. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 4cafad4. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

## **Description** Enable the predictions e2e test  ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: ## **Manual testing steps** ```gherkin 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**  ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] 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](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Enables Prediction Market E2E smoke test jobs for Android and iOS and includes them in the aggregated smoke test reports. > > - **CI Workflows (E2E Smoke)**: > - **Android**: > - Add `prediction-market-android-smoke` job using `SmokePredictions` tag. > - Include `prediction-market-android-smoke` in `report-android-smoke-tests.needs`. > - **iOS**: > - Add `prediction-market-ios-smoke` job using `SmokePredictions` tag. > - Include `prediction-market-ios-smoke` in `report-ios-smoke-tests.needs`. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 2f20dbe. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

## **Description** Creates a unified token selection screen that serves as a single entry point for both Buy (Aggregator) and Deposit ramps experiences. Previously, each experience had its own token list, token buttons, and token state. This PR introduces a shared `TokenSelection` component that users will see before landing on their respective build quote pages. This PR introduces the UI only. Tokens are hardcoded and click handlers are incomplete. TODO comments with the appropriate tickets have been registered in place. **What is the reason for the change?** - Consolidate duplicate token selection UI across Buy and Deposit flows - Provide a consistent user experience for token selection - Simplify navigation by having users pick a token before entering their specific ramp experience **What is the improvement/solution?** - New `TokenSelection` component at `app/components/UI/Ramp/components/TokenSelection/` - Reuses existing components: NetworksFilterBar, NetworksFilterSelector, token list rendering - Uses hardcoded MOCK_CRYPTOCURRENCIES for initial implementation (API integration pending) ## **Changelog** CHANGELOG entry: Added unified token selection screen for Buy and Deposit ramps ## **Related issues** Fixes: - https://consensyssoftware.atlassian.net/browse/TRAM-2815 - Related: https://consensyssoftware.atlassian.net/browse/TRAM-2816 (Fetch tokens from API endpoint) - Related: https://consensyssoftware.atlassian.net/browse/TRAM-2795 (Handle token selection routing) ## **Manual testing steps** ```gherkin Feature: Unified Token Selection for Ramps Scenario: User navigates to token selection from Buy Given user is on the wallet home screen When user taps "Buy" button Then user sees token selection screen with title "Select Token" And user sees network filter bar at the top And user sees search field And user sees list of tokens (USDC, USDT, BTC, ETH, USDC on Solana) And user sees close button (X) in header Scenario: User navigates to token selection from Deposit Given user is on the wallet home screen When user taps "Deposit" button Then user sees token selection screen with title "Select Token" And user sees network filter bar at the top And user sees search field And user sees list of tokens (USDC, USDT, BTC, ETH, USDC on Solana) And user sees close button (X) in header Scenario: User filters tokens by network Given user is on token selection screen When user taps "All networks" button Then user sees network filter selector screen with title "Select Network" When user selects "Ethereum" network Then user sees only Ethereum tokens in the list Scenario: User searches for tokens Given user is on token selection screen When user types "USDC" in search field Then user sees only USDC tokens in results When user clears search Then user sees all tokens again Scenario: User dismisses keyboard Given user is on token selection screen And keyboard is visible from searching When user scrolls the token list Then keyboard is dismissed Scenario: User closes token selection Given user is on token selection screen When user taps close button (X) in header Then user returns to previous screen ``` ## **Screenshots/Recordings**  ### **Before**  ### **After** https://github.com/user-attachments/assets/151a675e-2287-49a4-a2cd-055256a3865a ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] 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](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Introduces a shared Ramp TokenSelection screen with network filtering and search, wires it into navigation, and refactors deposit token UI to reuse shared components. > > - **Ramps UI**: > - **New `TokenSelection` screen** (`app/components/UI/Ramp/components/TokenSelection/`): token search, selectable list (using `TokenListItem`), and network filtering via `TokenNetworkFilterBar`; header close action; uses `MOCK_CRYPTOCURRENCIES`. > - **New `TokenNetworkFilterBar`** with tests and snapshots; supports “All” state and per-network toggles. > - **Shared `TokenListItem`** component for token rows (symbol, network badge), used by both `TokenSelection` and deposit flows. > - **New `useTokenNetworkInfo` hook** centralizes network name/image sourcing. > - **Navigation/Routes**: > - Adds `Routes.RAMP.TOKEN_SELECTION` and registers screen in `MainNavigator` (snapshot updated). > - Prep work in buy/deposit route utils (commented) to optionally navigate to token selection. > - **Deposit**: > - `TokenSelectorModal` refactored to use `TokenListItem` and related hooks; network filters updated to use `useTokenNetworkInfo`. > - Centralizes mock cryptos in `constants/mockCryptoCurrencies` and re-exports; updates tests. > - **Localization**: > - Adds `unified_ramp.networks_filter_bar.all_networks` string ("All"). > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit fb3a5a9. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

## **Description** Adds a small-fee threshold to show "< $0.01" for fees below $0.01, improving readability and avoiding misleading precision. ## **Changelog** CHANGELOG entry: Display < $0.01 for small fees in Perps ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/TAT-1970 ## **Manual testing steps** ```gherkin Feature: Perps position transaction view fee display Scenario: user views transaction with small fee Given a user has a closed position transaction with a fee less than $0.01 (e.g., $0.005) When user views the transaction details screen Then the fee should display as "< $0.01" instead of the exact amount ``` ## **Screenshots/Recordings** ### **Before** ![IMG_EB5F710DB10B-1](https://github.com/user-attachments/assets/eff4f430-b913-4f28-8ec1-f703a7cf9115)  ### **After** <img width="1170" height="2532" alt="Simulator Screenshot - iPhone 16e - 2025-11-07 at 11 04 09" src="https://github.com/user-attachments/assets/6f3a891f-b203-41f0-a241-76b0c2979635" /> ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Introduces `formatFee` to show "< $0.01" for fees below $0.01 and updates Perps transaction views and tests to use it. > > - **Utilities**: > - Add `formatFee` in `app/components/UI/Perps/utils/formatUtils.ts` to return `"$0"`, `"< $0.01"`, or formatted fiat; add comprehensive unit tests. > - **Views**: > - Replace ad-hoc fee formatting with `formatFee` in `PerpsOrderTransactionView.tsx` and `PerpsPositionTransactionView.tsx`; ensure unfilled orders show `$0`. > - **Tests**: > - Update and expand tests in transaction view specs to assert `"< $0.01"` behavior and edge cases; keep existing explorer navigation tests intact. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit cf07474. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  --------- Co-authored-by: Nicholas Smith <nick.smith@consensys.net> Co-authored-by: dylanbutler1 <99672693+dylanbutler1@users.noreply.github.com>

…List cp-7.59.0 (#22341) ## **Description** Navigating from a subsection in the PerpHomeScreen should navigate to the proper tab in the MarketList. This PR also introduces some performance optimizations in the horizontal scroll view by memoizing list items to reduce the memory footprint, leading to a snappier behavior. If we want further optimizations, we can remove swipe navigation, in favor of just pressing the tabs and leaning into lazy loading more. ## **Changelog** CHANGELOG entry: Fix PerpsMarketList navigation and improve performance on swipeable list view ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/TAT-2039 ## **Manual testing steps** ```gherkin Feature: Perps Market List Tab Navigation Scenario: user navigates to Stocks tab from home screen Explore stocks and commodities section Given user is on the Perps home screen And the "Explore stocks and commodities" section is visible When user taps "See all" in the "Explore stocks and commodities" section Then user is navigated to the Perps market list screen And the "Stocks" tab is selected And stocks and commodities markets are displayed Scenario: user navigates to Crypto tab from home screen Explore crypto section Given user is on the Perps home screen And the "Explore crypto" section is visible When user taps "See all" in the "Explore crypto" section Then user is navigated to the Perps market list screen And the "Crypto" tab is selected And crypto markets are displayed Scenario: user switches tabs by tapping tab bar Given user is on the Perps market list screen And the "All" tab is currently selected And the market list is scrolled to the middle When user taps the "Crypto" tab Then the "Crypto" tab becomes active And only crypto markets are displayed And the market list is scrolled to the top And no performance lag is observed Scenario: user switches tabs by swiping Given user is on the Perps market list screen And the "All" tab is currently selected When user swipes left on the market list Then the "Crypto" tab becomes active And the tab bar indicator animates to "Crypto" And only crypto markets are displayed And the swipe gesture is smooth without stuttering Scenario: user swipes between multiple tabs quickly Given user is on the Perps market list screen And the "All" tab is currently selected When user swipes left to the "Crypto" tab And user swipes left again to the "Stocks" tab Then the "Stocks" tab becomes active And the tab bar indicator animates smoothly to "Stocks" And stocks and commodities markets are displayed And tab switching is instant without noticeable delay Scenario: user returns to previously viewed tab Given user is on the Perps market list screen And the "Crypto" tab is currently selected And user has previously viewed the "All" tab When user taps the "All" tab Then the "All" tab becomes active And all markets (crypto, stocks, and commodities) are displayed And the market list is scrolled to the top And no re-rendering delay is observed Scenario: user applies sub-filter on Stocks tab Given user is on the Perps market list screen And the "Stocks" tab is currently selected And both stocks and commodities are displayed When user taps the stocks/commodities filter dropdown And user selects "Stocks only" Then only equity markets are displayed And commodity markets are hidden And the filter updates instantly Scenario: user switches away from Stocks tab with active sub-filter Given user is on the Perps market list screen And the "Stocks" tab is currently selected And the sub-filter is set to "Stocks only" When user taps the "Crypto" tab And user taps back to the "Stocks" tab Then the "Stocks" tab becomes active And the sub-filter is reset to "All" And both stocks and commodities are displayed ``` ## **Screenshots/Recordings** https://github.com/user-attachments/assets/9b8c5278-018a-4a42-89b6-ef0cbd3b647a ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Routes "See all" to the correct market tab and refactors MarketListView with swipe/tab sync fixes, simplified filtering, and memoized row items for better performance. > > - **Perps Home & Sections**: > - `PerpsHomeView`: pass `marketType="stocks_and_commodities"` to Stocks & Commodities section. > - `PerpsMarketTypeSection`: support `marketType="stocks_and_commodities"`; on "See All" navigate with `defaultMarketTypeFilter` set to provided `marketType`. > - **Market List View**: > - Simplify tab filtering: introduce `displayMarkets` applying sub-filter only on `stocks_and_commodities`; replace checks/usages from `filteredMarkets` → `displayMarkets`. > - Tabs rendering: inline tab content; remove `getFilteredMarketsForTab`/`MarketTypeTabContent` and `tabsToRender`. > - Swipe/tab sync: add `isScrollingProgrammatically` guard; sync `ScrollView` position on tab change; handle scroll to update `marketTypeFilter` without feedback loops. > - Active tab mapping: include `stocks_and_commodities` and legacy `equity`/`commodity`. > - Update measurement and event tracking conditions to use `displayMarkets.length`. > - **Performance**: > - `PerpsMarketRowItem`: export as `React.memo` to reduce re-renders. > - **Tests**: > - Update navigation assertions in `PerpsMarketTypeSection.test.tsx` to expect specific `defaultMarketTypeFilter`. > - Adjust `PerpsMarketRowItem.test.tsx` rerenders to pass new props copies. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 5921889. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  --------- Co-authored-by: abretonc7s <107169956+abretonc7s@users.noreply.github.com> Co-authored-by: Arthur Breton <arthur.breton@consensys.net> Co-authored-by: Nicholas Smith <nick.smith@consensys.net> Co-authored-by: dylanbutler1 <99672693+dylanbutler1@users.noreply.github.com>

## **Description** Fix issue with incorrect network order & fees  ## **Changelog**  CHANGELOG entry: fix incorrect network order and fees ## **Related issues** Fixes: #22314 ## **Manual testing steps** ```gherkin 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**  https://github.com/user-attachments/assets/907764f2-695e-4cda-bda8-eaee609fc562 <img width="420" height="913" alt="simulator_screenshot_AC60FBFE-5FB0-488D-97F1-9D16106F285E" src="https://github.com/user-attachments/assets/711c89d6-8284-4265-b253-37f13c0a583a" /> ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Sorts destination networks by popularity with BTC included and standardizes network fee display to fiat, with updated tests and e2e adjustments. > > - **Bridge UI** > - **Network ordering**: Export and use `ChainPopularity` to sort destination networks; add BTC (`BtcScope.Mainnet`) and adjust rankings; fallback to `Infinity` for unknown chains. > - **Dest selector**: Apply popularity sort in `BridgeDestNetworkSelector` (excludes current chain unless Unified mode). > - **Snapshots/Tests**: Update snapshots to reflect new order; add test for popularity fallback. > - **Quote Data** > - **Fees**: Always format `networkFee` using fiat `valueInCurrency` (handles `<$0.01`, `$0`, and missing values as `-`); remove primary-currency/ticker-based formatting. > - **Unit Tests**: Update and expand tests to cover new fee formatting cases and edge conditions. > - **E2E** > - Adjust `swipeNetwork` to target updated ordering. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit fc761a6. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  --------- Co-authored-by: Bryan Fullam <bryan.fullam@consensys.net>

…22436)  ## **Description** #22323  ## **Changelog**  CHANGELOG entry: ## **Related issues** Fixes: ## **Manual testing steps** ```gherkin 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**  ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] 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](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Uses `measureAsyncOnUI` for Android press interactions and wires new Fabric async measure APIs across JS, native (iOS/Android), and tests; updates RN to a Yarn patch. > > - **Press interactions**: > - `Libraries/Pressability/Pressability.js`: Use `measureAsyncOnUI` only on Android; keep `measure` on other platforms. > - **Fabric measurement APIs**: > - JS/TS interfaces: Add `measureAsyncOnUI` to `FabricUIManager` (`Libraries/ReactNative/FabricUIManager.js`) and expose via `ReactFabricHostComponent`. > - JS bridge: Implement `UIManagerBinding.measureAsyncOnUI` to call back into JS. > - Scheduler/Delegates: Add async measure pathways (`Scheduler`, `SchedulerDelegate`, `UIManagerDelegate`). > - **iOS (Fabric)**: > - Add `RCTMountingManager.measure` and route via `RCTSurfacePresenter` to perform measurement on main thread. > - **Android (Fabric)**: > - Add `FabricUIManager.measureAsync`, `MountingManager.measure` (with bounding box computation), and JNI plumbing (`Binding`, `FabricMountingManager`) to call into Java and invoke callbacks. > - **Tests and RN DOM shim**: > - `jest/setup.js`: Mock `measureAsyncOnUI`. > - `ReactNativeElement`: Add `measureAsyncOnUI` delegating to `measure`. > - **Build config**: > - `package.json`/`yarn.lock`: Point `react-native@0.76.9` to local Yarn patch. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 3df2f0f. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  --------- Co-authored-by: metamaskbot <metamaskbot@users.noreply.github.com>

## **Description** This PR updates the Ramps Smart Routing hook to use the actual API endpoints now that they are available in production and staging environments. **What is the reason for the change?** The smart routing feature was previously using a placeholder endpoint (`/endpoint-coming-soon`) while waiting for the backend API to be deployed. The API endpoints are now available and ready to be integrated. **What is the improvement/solution?** - Integrated production and staging API endpoints for ramp eligibility checks - Production URL: `https://on-ramp-content.api.cx.metamask.io/regions/countries/{region-code}` - Staging URL: `https://on-ramp-content.uat-api.cx.metamask.io/regions/countries/{region-code}` - Environment detection uses `process.env.METAMASK_ENVIRONMENT` directly to determine which endpoint to use - Production environments: `production`, `beta`, `rc` - Staging environments: `dev`, `exp`, `test`, `e2e`, and all others default to staging ## **Changelog** CHANGELOG entry: null ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/TRAM-2807 ## **Manual testing steps** ```gherkin Feature: Ramp Smart Routing API Integration Scenario: User in supported region sees appropriate ramp option Given the app is running in a production environment And the user's detected geolocation is "us-ca" When the ramp smart routing hook initializes Then the app fetches eligibility from "https://on-ramp-content.api.cx.metamask.io/regions/countries/us-ca" And the routing decision is set based on the API response Scenario: User in supported region in staging environment Given the app is running in a dev/staging environment And the user's detected geolocation is "us-ca" When the ramp smart routing hook initializes Then the app fetches eligibility from "https://on-ramp-content.uat-api.cx.metamask.io/regions/countries/us-ca" And the routing decision is set based on the API response Scenario: User in unsupported region Given the app is running in any environment And the user's detected geolocation returns global: false from API When the ramp smart routing hook initializes Then the routing decision is set to UNSUPPORTED And the user cannot access ramp features Scenario: API fetch fails Given the app is running in any environment And the API request fails or times out When the ramp smart routing hook initializes Then the routing decision is set to ERROR And appropriate error logging occurs ``` ## **Screenshots/Recordings**  ### **Before**  ### **After**  ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Hook now fetches ramp eligibility from environment-specific endpoints with error handling; tests expanded and Babel config updated to preserve env vars. > > - **Ramps Smart Routing (`app/components/UI/Ramp/hooks/useRampsSmartRouting.ts`)** > - Use real eligibility API with env-based base URLs via `process.env.METAMASK_ENVIRONMENT` (`PRODUCTION` vs `STAGING`). > - Build fetch URL `'/regions/countries/{region}'`; validate `response.ok` and throw on errors; log and route to `ERROR` on failure. > - **Tests (`useRampsSmartRouting.test.ts`)** > - Add cases verifying production/staging URLs across envs (`production`, `beta`, `rc`, `dev`, `exp`, `test`, `e2e`). > - Add error-path tests for failed fetch and non-OK responses (404, 500); persist/restore env; update geolocation to `us-ca`. > - **Build/Config (`babel.config.tests.js`)** > - Exclude `useRampsSmartRouting.ts` and its tests from inline env var transform to allow runtime env-based behavior. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 77d4425. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

…22293) ## **Description** This PR implements a feature to prevent users from trading when they have open cross-margin positions in MetaMask Perps. Since MetaMask only supports isolated margin trading, users with cross-margin positions are now shown a blocking warning modal that explains the limitation and instructs them to close their cross-margin positions before trading. **What is the reason for the change?** MetaMask Perps only supports isolated margin trading. If users have cross-margin positions and attempt to trade, this could lead to unexpected behavior or errors since the system is designed exclusively for isolated margin. **What is the improvement/solution?** - Added detection logic in the order placement flow to check if the user has an open cross-margin position for the asset they're trying to trade - Created a new bottom sheet modal (`PerpsCrossMarginWarningBottomSheet`) that displays a clear warning message - Integrated the check into `PerpsOrderView.handlePlaceOrder()` before order execution - Added proper navigation routing through the Perps modal stack - Included error tracking metrics for monitoring ## **Changelog** CHANGELOG entry: Added cross-margin position detection to prevent trading when users have unsupported margin types ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/TAT-1564 ## **Manual testing steps** ```gherkin Feature: Cross-margin position trading prevention Scenario: user attempts to place order with cross-margin position Given user has an open cross-margin position for BTC And user is on the Perps Order view for BTC When user taps Long or Short button Then a bottom sheet modal appears with title "Cross Margin Not Supported" And the modal displays message "MetaMask Perps only support trading with isolated margin. You need to first close your cross margin position before you can trade on MetaMask." And user can dismiss the modal with "Got it" button And no order is placed Scenario: user attempts to place order with isolated margin position Given user has an open isolated margin position for BTC And user is on the Perps Order view for BTC When user taps Long or Short button Then the order placement proceeds normally And no warning modal is shown Scenario: user attempts to place order without existing position Given user has no open positions for BTC And user is on the Perps Order view for BTC When user taps Long or Short button Then the order placement proceeds normally And no warning modal is shown ``` ## **Screenshots/Recordings** ### **Before** Users with cross-margin positions could attempt to place orders, potentially causing errors or unexpected behavior. ### **After** Users with cross-margin positions are blocked with a clear warning modal explaining the limitation.  https://github.com/user-attachments/assets/e90cd4d0-d25e-49f4-9d87-ee7c3e68f144 ## **Pre-merge author checklist** - [x] I've followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I've included tests if applicable (5/7 tests passing - 2 tests have mock configuration issues but component functions correctly) - [x] I've documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I've applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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. --- ## **Technical Implementation Details** ### Files Created: 1. `PerpsCrossMarginWarningBottomSheet.tsx` - Main warning modal component 2. `PerpsCrossMarginWarningBottomSheet.styles.ts` - Component styles 3. `PerpsCrossMarginWarningBottomSheet.test.tsx` - Unit tests 4. `index.ts` - Barrel export ### Files Modified: 1. `app/constants/navigation/Routes.ts` - Added `CROSS_MARGIN_WARNING` route 2. `app/components/UI/Perps/routes/index.tsx` - Registered modal route in navigation stack 3. `app/components/UI/Perps/Views/PerpsOrderView/PerpsOrderView.tsx` - Added cross-margin detection logic in `handlePlaceOrder()` 4. `locales/languages/en.json` - Added i18n strings for warning messages ### Key Features: - **Same-asset detection**: Only blocks trading when user has cross-margin position for the exact asset they're trying to trade (not all positions) - **Navigation routing**: Uses proper modal navigation stack for consistency with other Perps modals - **Error tracking**: Tracks cross-margin detection events in MetaMetrics for monitoring - **User-friendly**: Clear warning message with single "Got it" dismiss action - **Early validation**: Check happens before order execution to prevent wasted API calls  --- > [!NOTE] > Blocks order placement when a cross-margin position is detected and shows a new Perps cross‑margin warning bottom sheet. > > - **Perps Order Flow**: > - Add cross‑margin detection in `PerpsOrderView.handlePlaceOrder` to prevent execution and navigate to warning modal. > - Track validation error via `MetaMetricsEvents.PERPS_ERROR` when cross‑margin detected. > - **UI/Modal**: > - New `PerpsCrossMarginWarningBottomSheet` component with styles and tests; dismiss navigates back or triggers `onClose`. > - **Navigation**: > - Register `Routes.PERPS.MODALS.CROSS_MARGIN_WARNING` in `Routes.ts` and modal stack (`app/components/UI/Perps/routes/index.tsx`). > - **i18n**: > - Add `perps.crossMargin` strings in `locales/languages/en.json`. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit fd11621. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  --------- Co-authored-by: Nicholas Smith <nick.smith@consensys.net>

## **Description** Enable Gasless crosschain swaps (bridge) using eth_sendBundle ## **Changelog**  CHANGELOG entry: Added Gasless bridging for users with STX ON on networks supporting eth_sendBundle Relates to https://consensyssoftware.atlassian.net/browse/STX-250 ## **Manual testing steps** ```gherkin Feature: Gasless crosschain swaps (bridge) using eth_sendBundle Scenario: user perform a gasless cross chain swap from MUSD (Ethereum-mainnet) to ETH (Base-mainnet) Given the user enabled Smart transactions AND the use does not have ETH on Ethereum-mainnet When user swap MUSD (Ethereum-mainnet) to ETH (Base-mainnet) Then the swap has gas included ``` ## **Screenshots/Recordings** TO DO ### **Before**  ### **After**  ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [x] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [x] 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] > Introduces gasIncluded flow for Bridge/Swap by detecting eth_sendBundle support and STX enablement, wiring it into Redux and quote requests, and refining STX publish fallback behavior, with comprehensive tests. > > - **Bridge UI/Hooks**: > - Add `useGasIncluded` to compute and dispatch `gasIncluded` based on `selectShouldUseSmartTransaction` and `useIsSendBundleSupported` (EVM-only). > - Add `useIsSendBundleSupported` (async sentinel check). > - Call `useGasIncluded(sourceToken?.chainId)` in `BridgeView` to update state on source chain changes. > - **Redux (bridge slice)**: > - Add `bridge.gasIncluded` to state, selectors, and `setGasIncluded` action; update initial state and tests. > - **Quote Request**: > - Include `gasIncluded` and `gasIncluded7702: false` in `GenericQuoteRequest` via `useBridgeQuoteRequest`; remove reliance on smart-transaction selector here. > - **Smart Transactions publish hook**: > - Simplify fallback: drop special cases for bridge/bridgeApproval types; keep legacy and non-STX fallbacks. > - **Tests**: > - New tests for `useGasIncluded` and `useIsSendBundleSupported`. > - Update `BridgeView` and `useBridgeQuoteRequest` tests to cover `gasIncluded` propagation and chain changes. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 590356d. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  Co-authored-by: dan437 <80175477+dan437@users.noreply.github.com>

…tion cp-7.59.0 (#22457)  ## **Description**  This aligns the Swaps points equation to be anchored more similarly to the perps amount, fixes the perps description to be more consistent and convey how fee discounts affect perps points, and better clarifies how the loyalty bonus works. ## **Changelog**  CHANGELOG entry: Updated Rewards "ways to earn" descriptions to be more accurate. ## **Related issues** Fixes: n/a ## **Manual testing steps** ```gherkin 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**  ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] 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](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Updates Rewards “Ways to earn” text: swaps to 8 points per $10, adds perps fee-discount note, changes referrals to 10 points per 50, and clarifies loyalty bonus description. > > - **Rewards > `ways_to_earn` (i18n copy updates)**: > - **`swap`**: > - `description`/`sheet.points`: `80 points per $100` → `8 points per $10`. > - **`perps`**: > - `sheet.description`: add note that fee discounts also discount points. > - **`referrals`**: > - `sheet.points`: `20 points per 100` → `10 points per 50`. > - **`loyalty`**: > - `sheet.description`: clarify wording to “past MetaMask in-wallet swaps or bridges.” > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit c97f27e. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

## **Description** - Adds minimum transfer after claim  ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: ## **Manual testing steps** ```gherkin 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**  ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] 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](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Adds a balance check and optionally appends a USDC transfer to claim transactions when signer collateral is below a minimum threshold; updates claim transaction shape and tests. > > - **Polymarket Provider** > - `prepareClaim`: checks signer collateral via `getBalance` and sets `includeTransferTransaction` when balance < `MIN_COLLATERAL_BALANCE_FOR_CLAIM`. > - Returns claim `transactions` as an array (not a single object). > - **Safe Utils** > - `createClaimSafeTransaction`: optionally appends an ERC20 transfer (USDC) to the signer and aggregates via multisend. > - `getClaimTransaction`: accepts `includeTransferTransaction`, using signer address when true. > - **Constants** > - Introduces `MIN_COLLATERAL_BALANCE_FOR_CLAIM = 0.5` and uses collateral/decimals in transfer encoding. > - **Tests** > - Update provider and safe utils tests to expect array-based claim transactions and to cover transfer-inclusion cases across balance thresholds. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 8abd446. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

## **Description** feat: Remove stocks/commodities dropdown and fix FlashList gaps Changes: - Remove conditional stocks/commodities dropdown in market list view - Set showStocksCommoditiesDropdown to false (always hidden) - Add tests to verify dropdown is not shown regardless of market type filter - Fix FlashList layout gaps in market lists - Add drawDistance={200} and removeClippedSubviews props to PerpsMarketList - Create marketListConfig.ts for FlashList configuration constants - Prevents blank space gaps when searching or scrolling - Fix pre-existing test failure - Refactor "handles search with whitespace" test to use proper mocking - Rename to "filters markets with whitespace-only query" for clarity  ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/TAT-2041 Fixes: #22440 ## **Manual testing steps** ```gherkin feat: Remove stocks/commodities dropdown and fix FlashList gaps Feature: Market List View Filtering Scenario: Hide secondary dropdown in stocks tab Given the market list view is displayed When the user is on any market type tab Then the stocks/commodities dropdown should not be visible And the filter bar should only show the sort dropdown Feature: FlashList Rendering Scenario: Prevent layout gaps in market list Given the market list uses FlashList for rendering When markets are displayed in search or tab views Then there should be no blank space gaps And items should render 200px ahead of viewport And clipped subviews should be removed for optimal layout ``` ## **Screenshots/Recordings**  ### **Before**  ### **After** <img width="399" alt="Simulator Screenshot - iPhone 17 Pro - 2025-11-10 at 18 23 47" src="https://github.com/user-attachments/assets/18233ad3-992f-4a5e-bd14-9809ba23043c" />  ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Hides the stocks/commodities dropdown in the market list and configures FlashList (drawDistance, removeClippedSubviews) via new constants to prevent layout gaps, with tests updated accordingly. > > - **UI**: > - Force-hide stocks/commodities dropdown by setting `showStocksCommoditiesDropdown={false}` in `PerpsMarketListView`. > - **Performance/Rendering**: > - Add `drawDistance={200}` and `removeClippedSubviews` to `PerpsMarketList`’s `FlashList`. > - Centralize list config in `constants/marketListConfig.ts` (`PERPS_MARKET_LIST_CONSTANTS`). > - **Tests**: > - Add assertions that `stocks/commodities` dropdown is not rendered (regardless of market filter). > - Refactor whitespace-only search test using hook-based mocking and rename for clarity. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 0eccafa. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

## **Description** - Removes the mandatory terms of service modal  ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: [PRED-297](https://consensyssoftware.atlassian.net/browse/PRED-297) ## **Manual testing steps** ```gherkin 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**  ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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. [PRED-297]: https://consensyssoftware.atlassian.net/browse/PRED-297?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ  --- > [!NOTE] > Removes the Predict ToS consent modal and agreement tracking, simplifying buy/sell flows and pruning related controller APIs, types, selectors, and tests. > > - **UI (Predict)**: > - Remove `PredictConsentSheet` component and all references from `PredictBuyPreview` and `PredictSellPreview`; orders now proceed directly. > - Keep inline disclaimer with "Learn more" link; no modal gating. > - **Controller**: > - Delete `acceptAgreement` API from `PredictController` and all usages. > - **Hooks**: > - Remove `usePredictAgreement` hook and its tests. > - **Types/Selectors**: > - Simplify `PredictAccountMeta` to `{ isOnboarded: boolean }`; drop `acceptedToS` and `AcceptAgreementParams`. > - Update selectors/tests to reflect removal of `acceptedToS`. > - **Tests**: > - Remove consent-related tests and mocks across buy/sell previews and consent sheet; adjust flows to assert direct order placement. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 8c727d0. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).

## **Description** Added support for proper display of hip3 and other DEX assets by stripping prefixes from asset symbols throughout the Perps UI. - Added `getPerpsDisplaySymbol()` in `marketUtils.ts` - Strips DEX prefixes (e.g., `hip3:`, `xyz:`) from asset symbols - Returns clean symbol for display (e.g., `hip3:BTC` → `BTC`) **Utils:** - `transactionTransforms.ts` - Strip prefixes in transaction subtitles (fills, orders, funding) **Hooks:** - `usePerpsToasts.tsx` - Clean asset names in toast notifications **Components:** - `PerpsAmountDisplay.tsx` - Display token symbols without prefixes - `PerpsOrderHeader.tsx` - Show clean asset names in order titles - `PerpsOpenOrderCard.tsx` - Format symbols in order cards - `PerpsRecentActivityList.tsx` - Display clean symbols in activity list - Hip3 assets now display as `BTC` instead of `hip3:BTC` - Stock/commodity assets show as `TSLA` instead of `xyz:TSLA` - Consistent, clean asset naming across entire Perps UI - Regular assets (BTC, ETH, SOL) remain unchanged  ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/TAT-2043 Fixes: #22439 ## **Manual testing steps** ```gherkin Feature: Hip3 Asset Name Display Background: Given the system uses getPerpsDisplaySymbol() to format asset names Scenario: Strip DEX prefix from hip3 assets Given a hip3 asset with symbol "hip3:BTC" When displaying the asset name Then show "BTC" Scenario: Keep regular asset names unchanged Given a regular asset with symbol "BTC" When displaying the asset name Then show "BTC" ``` ## **Screenshots/Recordings**  ### **Before**  ### **After** https://github.com/user-attachments/assets/c6c73f1c-2640-4dac-9311-eaae8393e235  ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Standardizes Perps asset symbols by stripping DEX prefixes (e.g., hip3:, xyz:) via getPerpsDisplaySymbol across UI, toasts, and transaction transforms, with comprehensive tests. > > - **Utils**: > - Add `getPerpsDisplaySymbol` in `marketUtils` to strip DEX prefixes from symbols for display. > - Apply in `transactionTransforms` to clean `subtitle` for fills, orders, and funding items. > - **Hooks**: > - Update `usePerpsToasts` to use cleaned symbols in all toast subtitles and errors. > - **Components**: > - `PerpsOrderHeader`, `PerpsAmountDisplay`, `PerpsOpenOrderCard`, `PerpsRecentActivityList`, `PerpsClosePositionView`, `PerpsOrderView`: replace raw symbols with `getPerpsDisplaySymbol` in titles, labels, and amounts. > - **Tests**: > - Add/expand coverage to assert prefix stripping (HIP-3/DEX) and unchanged regular symbols across the updated components, hooks, and utils. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit f7c4f2d. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  --------- Co-authored-by: Nicholas Gambino <nicholas.gambino@consensys.net> Co-authored-by: Nick Gambino <35090461+gambinish@users.noreply.github.com> Co-authored-by: abretonc7s <107169956+abretonc7s@users.noreply.github.com> Co-authored-by: Arthur Breton <arthur.breton@consensys.net> Co-authored-by: dylanbutler1 <99672693+dylanbutler1@users.noreply.github.com>

…0 minutes (#23067) - chore: timeout build android apk for e2e 30 minutes (#23056)  ## **Description** timeout build android apk for e2e 40 minutes Reference of taking only 19 minutes https://github.com/MetaMask/metamask-mobile/actions/runs/19541397562/job/55948548693  ## **Changelog**  CHANGELOG entry: ## **Related issues** Fixes: ## **Manual testing steps** ```gherkin 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**  ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] 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](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Set a 40-minute timeout on the `build-android-apks` job in `.github/workflows/build-android-e2e.yml`. > > - **CI/CD (GitHub Actions)**: > - Update `.github/workflows/build-android-e2e.yml` to set `timeout-minutes: 40` for the `build-android-apks` job. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit e256497. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  [2b1a33a](2b1a33a) Co-authored-by: tommasini <46944231+tommasini@users.noreply.github.com>

… and transaction pay controller versions (#23041) - fix: cp-7.60.0 bump transaction controller and transaction pay controller versions (#23029) ## **Description** Update controller versions for `@metamask/transaction-controller` and `@metamask/transaction-pay-controller`. ## **Changelog** CHANGELOG entry: null ## **Related issues** ## **Manual testing steps** ## **Screenshots/Recordings** ### **Before** ### **After** ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Upgrade @metamask/transaction-controller (61.3.0 → 62.0.0) and @metamask/transaction-pay-controller (7.x → 9.x), updating patches and aligning peer deps; refresh yarn.lock accordingly. > > - **Dependencies**: > - Upgrade `@metamask/transaction-controller` to `62.0.0` (patched reference updated in `resolutions` and `dependencies`). > - Upgrade `@metamask/transaction-pay-controller` to `^9.0.0`. > - Align related peer deps in lockfile: > - `@metamask/controller-utils` → `^11.16.0`. > - Peers: `accounts-controller` `^35`, `gas-fee-controller` `^26`, `network-controller` `^26`. > - Transaction Pay peers: `assets-controllers` `^90`, `bridge(-status)-controller` `^62`, `gas-fee-controller` `^26`, `network-controller` `^26`, `transaction-controller` `^62`. > - Update `yarn.lock` entries to reflect new versions and checksums. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit f6b6f4c. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  [cfd16f1](cfd16f1) Co-authored-by: Matthew Walsh <matthew.walsh@consensys.net> Co-authored-by: João Loureiro <175489935+joaoloureirop@users.noreply.github.com>

…nboarding flow (#23066) - fix(card): cp-7.60.0 debounced inputs on onboarding flow (#22747)  ## **Description**  This PR fixes a race condition bug in the onboarding flow where users typing quickly and immediately pressing submit buttons would have their input data lost due to debounce delays. ## **Changelog**  CHANGELOG entry: Fixed a bug where rapidly typing in Card onboarding forms and immediately submitting could send incomplete data to the server ## **Related issues** Fixes: ## **Manual testing steps** ```gherkin Feature: Onboarding form submission with rapid typing Scenario: user types email rapidly and submits immediately in Sign Up screen Given user is on the Sign Up screen And all form fields are empty When user rapidly types "test@example.com" in email field And user rapidly types "Password123!" in password field And user rapidly types "Password123!" in confirm password field And user selects a country And user immediately presses Continue button (within 1 second) Then the API should receive "test@example.com" (not partial/stale email) And user should navigate to Confirm Email screen Scenario: user types phone number rapidly and submits immediately in Set Phone Number screen Given user is on the Set Phone Number screen And country code is selected When user rapidly types "1234567890" in phone number field And user immediately presses Continue button (within 1 second) Then the API should receive "1234567890" (not partial phone number) And user should navigate to Confirm Phone Number screen Scenario: US user types SSN rapidly and submits immediately in Personal Details screen Given user is on the Personal Details screen And user has selected US as country And first name, last name, date of birth, and nationality are filled When user rapidly types "123456789" (9 digits) in SSN field And user immediately presses Continue button (within 1 second) Then the API should receive "123456789" (complete SSN, not partial) And user should navigate to Physical Address screen Scenario: user submits invalid data with rapid typing Given user is on the Sign Up screen When user rapidly types "invalid-email" in email field And user rapidly types "weak" in password field And user rapidly types "weak" in confirm password field And user selects a country And user immediately presses Continue button Then validation errors should be shown And API should not be called And user should remain on Sign Up screen ``` ## **Screenshots/Recordings**  ### **Before**  ### **After**  ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Use non-debounced form values for onboarding validation/submission and standardize consent `policyType` to `us`. > > - **Onboarding UI**: > - `SignUp`, `SetPhoneNumber`, `PersonalDetails` now validate/submit using current (non-debounced) inputs and update `isDisabled` accordingly. > - Add upfront validation: email/password/confirm password match, phone `^\d{4,15}$`, SSN `^\d{9}$` (US only); block submit and surface errors when invalid. > - Replace uses of `debounced*` in API calls/navigation with live values; minor error rendering tweaks and cleanup. > - **Consent Policy**: > - Standardize `policyType` from `US` to `us` in `useRegisterUserConsent` and comparisons. > - Update `CreateOnboardingConsentRequest` type to `policyType: 'us' | 'global'` and adjust tests (`useRegisterUserConsent.test.ts`, `CardSDK.test.ts`). > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 4fb1a77. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  [6a0949c](6a0949c) Co-authored-by: Bruno Nascimento <brunonascimentodev@gmail.com> Co-authored-by: João Loureiro <175489935+joaoloureirop@users.noreply.github.com>

…ns from send flow (#23028) - fix: cp-7.60.0 filter out tron staked tokens from send flow (#22979) ## **Description** TRON staked tokens were visible in the send flow. This PR modifies some selectors so that we filter out TRON staked tokens. ## **Changelog** CHANGELOG entry: fix: filter out TRON staked tokens ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/ASSETS-1814 ## **Manual testing steps** 1. Go to send flow 2. Filter TRON 3. EXPECTED: TRON staked tokens are not visible ## **Screenshots/Recordings**  ### **Before** <img width="316" height="720" alt="image" src="https://github.com/user-attachments/assets/d8a4656b-cf62-49e8-b6c9-1cadfb3eab4d" /> ### **After** https://www.loom.com/share/e5ca32a5434e46ab907d8832ab3af239 ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Introduce a filtered assets selector to exclude Tron Energy/Bandwidth (and staked variants) and wire it into send flow and sorting, with comprehensive tests. > > - **Selectors**: > - Add `selectFilteredAssetsBySelectedAccountGroup` to remove Tron resource tokens (`ENERGY`, `BANDWIDTH`, staked-for variants) across `TrxScope` networks. > - Switch `selectSortedAssetsBySelectedAccountGroup` to consume the filtered selector. > - **Send Flow**: > - Update `useAccountTokens` to use `selectFilteredAssetsBySelectedAccountGroup`, ensuring Tron resources are not shown. > - **Tests**: > - Add tests validating Tron resource filtering for all Tron scopes. > - Update `useAccountTokens` tests to mock the new selector; minor expectation tweaks (e.g., `toStrictEqual`). > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 8d1ef59. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  [fe2980a](fe2980a) Co-authored-by: Prithpal Sooriya <prithpal.sooriya@consensys.net> Co-authored-by: João Loureiro <175489935+joaoloureirop@users.noreply.github.com>

- chore: tron snap update cp-7.60.0 (#23059)  ## **Description** We are updating the Tron snap to the latest [version 1.9.1](https://github.com/MetaMask/snap-tron-wallet/releases/tag/v1.9.1) ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: ## **Manual testing steps** ```gherkin 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**  ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] 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](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Update dependency `@metamask/tron-wallet-snap` from `^1.8.0` to `^1.9.1` in `package.json` and `yarn.lock`. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 982d3eb. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  [935e555](935e555) Co-authored-by: António Regadas <antonio.regadas@consensys.net>

…y ) cp-7.60.0 (#23084) - fix: start animate when rive onPlay ( ready ) cp-7.60.0 (#22982)  ## **Description**  * fix: race condition in rive animations when animation fail to start. * Jira: https://consensyssoftware.atlassian.net/browse/SL-332 * Issue: #23048 In some device on edge cases, sometime the MetaMask riv logo does not appear during the onboarding screen animation. This is due to race conditions between state triggers and the rive onPlay state. This PR wait for onPlay state before fire the inputState ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: #23048 * race condition in rive animations when animation fail to start. ## **Manual testing steps** ```gherkin Feature: onboarding Scenario: user open the app after install Given user open the app after install Then user should see the Metamask riv logo ``` ## **Screenshots/Recordings**  ### **Before**  https://github.com/user-attachments/assets/834c82d8-9fbf-4c96-943d-1ea067115401 ### **After**  https://github.com/user-attachments/assets/c4bca6d3-3bec-4be8-a68a-882770676ac4 ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [x] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [x] 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] > Waits for Rive `onPlay` before firing state/inputs, preventing missed onboarding and fox animations. > > - **UI**: > - `OnboardingAnimation`: Gate `startRiveAnimation` behind `isPlaying` set via `onPlay`; remove `autoplay` usage; maintain timing for logo move and fox start. > - `FoxAnimation`: Fire `FoxRaiseUp` only after `onPlay` sets `isPlaying`; remove `autoplay` usage. > - **Testing/Mocks**: > - `__mocks__/rive-react-native`: Add `onPlay` prop and invoke it on mount via `useEffect` to simulate readiness; minor hook import updates. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 2e21954. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  --------- Co-authored-by: Gaurav Goel <grvgoel19@gmail.com> [2ab978e](2ab978e) Co-authored-by: ieow <4881057+ieow@users.noreply.github.com> Co-authored-by: Gaurav Goel <grvgoel19@gmail.com>

…culation in HyperLiquidSubscriptionService cp-7.60.0 (#23027) - fix(perps): add missing returnOnEquity calculation in HyperLiquidSubscriptionService cp-7.60.0 (#22983)  ## **Description** This PR fixes a missing `returnOnEquity` calculation in the `HyperLiquidSubscriptionService.aggregateAccountStates()` method. ## **Changelog** CHANGELOG entry: Fixed a bug where the PnL % would not show ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/TAT-2086 ## **Manual testing steps** ```gherkin Feature: Return on Equity calculation in Perps account aggregation Scenario: user views account state with open HIP3 positions Given user has open perpetual positions with unrealized PnL Then the returnOnEquity field should be correctly calculated as (unrealizedPnl / marginUsed) * 100 And the value should be formatted to one decimal place ``` ## **Screenshots/Recordings**  ### **Before**  ![IMG_954DF8480A63-1](https://github.com/user-attachments/assets/166b53a5-5afd-4f24-9424-d9d9fef269a6) ### **After**  <img width="1170" height="2532" alt="Simulator Screenshot - iPhone 16e - 2025-11-20 at 09 47 15" src="https://github.com/user-attachments/assets/435d4952-8b54-4c4e-ae30-c7b8a11bcd36" /> ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Adds ROE calculation to `HyperLiquidSubscriptionService.aggregateAccountStates()` and introduces tests validating ROE across scenarios. > > - **Perps Subscription Service**: > - Compute `returnOnEquity` in `aggregateAccountStates()` as `((totalUnrealizedPnl / totalMarginUsed) * 100).toFixed(1)` and include it in returned `AccountState`. > - **Tests**: > - Import `adaptAccountStateFromSDK` and add `aggregateAccountStates` ROE tests covering positive, negative, zero-margin, mixed PnL, high gains, and rounding cases. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 0986b6f. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  [6427f22](6427f22) Co-authored-by: Michal Szorad <michal.szorad@consensys.net> Co-authored-by: João Loureiro <175489935+joaoloureirop@users.noreply.github.com>

…ge to 3% (#23082) - chore(predict): cp-7.60.0 bump sell slippage to 3% (#23074)  ## **Description**  Bump slippage for Sell orders to 3% (from 1.5%). This will help reducing the failure rate. ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/PRED-327 ## **Manual testing steps** ```gherkin 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**  ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Increase sell slippage to 3% and introduce separate `SLIPPAGE_BUY` (1.5%) and `SLIPPAGE_SELL` (3%) used in order previews. > > - **Polymarket Provider**: > - **Slippage constants**: Replace `SLIPPAGE` with `SLIPPAGE_BUY` (1.5%) and `SLIPPAGE_SELL` (3%) in `providers/polymarket/constants.ts`. > - **Order preview**: Update `previewOrder` in `providers/polymarket/utils.ts` to use `SLIPPAGE_BUY` for BUY and `SLIPPAGE_SELL` for SELL. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit ae07eec. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  [ad906ab](ad906ab) Co-authored-by: Luis Taniça <matallui@gmail.com>

…ibles for nft send flow (#23071) - fix: cp-7.60.0 use correct chainId collectibles for nft send flow (#22966)  ## **Description** The underlying sendflow uses `selectChainId` which should be marked as deprecated. - This selected does not return the correct chain ID when you are using "Popular Networks" view as you can have multiple chainIDs selected now!! This has unearthed a very large scope at this selector underpins many areas in mobile and extension 💀 Ideally all flows and features should move away from this selector and handle multiple selected chainIDs. ## **Changelog**  CHANGELOG entry: fix: correct nft images available during send flow ## **Related issues** Fixes: #20982 ## **Manual testing steps** 1. Select Popular Networks Tab 2. Go through NFT send flow - Select NFT from (e.g.) Linea (not ethereum) 3. Expected: On review page, should see NFT and can select NFT image without crashing app ## **Screenshots/Recordings**  ### **Before**  ### **After**  https://www.loom.com/share/683675a4c01b47b0a99f6ff5e9dfa30a ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Switches NFT lookup to a chain-scoped selector to fix multi-network send flow, updates HeroNft placeholder behavior, adds selector tests, and deprecates legacy selectors. > > - **State/Selectors**: > - Add `selectAllCollectiblesByChain` in `reducers/collectibles/collectibles.ts` with unit tests, enabling per-chain NFT selection. > - Mark `collectiblesSelector` and `selectChainId` as deprecated with notes about multi-network selection. > - **Hooks**: > - Update `useNft` to: > - Derive `hexChainId` and select NFTs via `selectAllCollectiblesByChain`. > - Return `chainId` as hex and resolve contract/name accordingly. > - **UI**: > - `HeroNft` placeholder: make non-interactive when no NFT; only show `#tokenId` if present; remove "Show" text. > - **Tests**: > - Adjust `hero-nft.test.tsx` to reflect placeholder behavior and collection image fallback. > - Add `collectibles.test.ts` covering `selectAllCollectiblesByChain` edge cases. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 4c30784. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  [e5692de](e5692de) Co-authored-by: Prithpal Sooriya <prithpal.sooriya@consensys.net>

… deposits (#23078) - feat: cp-7.60.0 gas station support for metamask pay deposits (#23033) ## **Description** Support EIP-7702 gas station when depositing with MetaMask Pay. ## **Changelog** CHANGELOG entry: null ## **Related issues** Fixes: [#6150](https://github.com/MetaMask/MetaMask-planning/issues/6150) ## **Manual testing steps** ## **Screenshots/Recordings** ### **Before** ### **After** ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Adds gas-fee token support to pay balance/fee checks, delegates getGasFeeTokens, updates transaction-pay-controller to v10, and removes "no gas" token disabling logic. > > - **Confirmations > Alerts**: > - Handle `fees.isSourceGasFeeToken` in `useInsufficientPayTokenBalanceAlert` to include source network fees in totals when using a gas-fee token, and skip native-fee insufficiency in that case. > - **Utils**: > - Simplify `getAvailableTokens` by removing native-gas dependency and disabling logic; no longer sets `disabled`/`disabledMessage`. > - **Engine Messenger**: > - Delegate `TransactionController:getGasFeeTokens` to Transaction Pay controller messenger. > - **Dependencies**: > - Bump `@metamask/transaction-pay-controller` to `^10.0.0`. > - **Tests**: > - Update alert tests to use persistent mocks and add cases for gas-fee token behavior; remove test asserting disabled token when no native gas. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit eac80ae. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  [b5472e1](b5472e1) Co-authored-by: Matthew Walsh <matthew.walsh@consensys.net> Co-authored-by: João Loureiro <175489935+joaoloureirop@users.noreply.github.com>

…after image loads (#23083) - fix(predict): cp-7.60.0 fade in gtm modal after image loads (#23080)  ## **Description**  Currently the GTM modal for Predict looks funky as it seems to render different pieces at different times. This PR attempts to fix this by introducing two main changes: - Animate opacity for the whole modals 0 -> 1 - Only start animation when the background image finishes loading ## **Changelog**  CHANGELOG entry: null ## **Related issues** Fixes: ## **Manual testing steps** ```gherkin 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**  https://github.com/user-attachments/assets/a8b61805-9f8a-4518-b37c-7cedf56d806b ### **After**  https://github.com/user-attachments/assets/41d44fed-56ff-4ec6-b800-867d5530e15f ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Adds a fade-in animation to `PredictGTMModal` content, triggered after the background image finishes loading. > > - **UI/Animation**: > - Wraps root container in `Animated.View` and applies opacity via `useSharedValue` + `withTiming`. > - Starts fade-in (`opacity: 0 -> 1`, 500ms) once background image `onLoad` fires in `PredictGTMModal` (`app/components/UI/Predict/components/PredictGTMModal/PredictGTMModal.tsx`). > - Introduces `imageLoaded` state, `useEffect` to trigger animation, and `useAnimatedStyle` for styling. > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 80f4a73. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  [2c0b340](2c0b340) Co-authored-by: Luis Taniça <matallui@gmail.com>

…age for aggregated account states cp-7.60.0 (#23097) - fix(perps): calculate weighted ROE percentage for aggregated account states cp-7.60.0 (#23090)  ## **Description** This PR fixes the calculation of return on equity (ROE) percentage for aggregated account states across multiple DEX accounts in the Perps feature. Previously, the ROE was calculated using a simple formula that didn't account for the different margin amounts across accounts, which could lead to inaccurate percentage values. ## **Changelog**  CHANGELOG entry: Fixed return on equity percentage calculation for aggregated Perps positions across multiple DEX accounts ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/TAT-2086 ## **Manual testing steps** ```gherkin Feature: Perps aggregated account ROE calculation Scenario: user views aggregated account state with multiple DEX positions Given user has multiple Perps positions across different DEX accounts with varying margin amounts And each position has different unrealized PnL and ROE values When user views the aggregated account state Then the displayed ROE percentage should be a weighted average based on margin used And the calculation should correctly handle accounts with zero or negative values And invalid or NaN values should be skipped in the calculation ``` ## **Screenshots/Recordings**  ### **Before**  ![Screenshot_20251121_104805_MetaMask (1)](https://github.com/user-attachments/assets/17e6528f-981d-4b36-a83b-4fa43762645d) ### **After**  <img width="1170" height="2532" alt="Simulator Screenshot - iPhone 16e - 2025-11-21 at 11 23 26" src="https://github.com/user-attachments/assets/23a33e94-e8b2-4b63-b57a-031fc5276653" /> ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). 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.  --- > [!NOTE] > Calculates weighted ROE across DEX accounts and integrates it into aggregated account state, with comprehensive unit tests. > > - **Perps utilities**: > - Add `calculateWeightedReturnOnEquity` in `utils/accountUtils.ts` (with `ReturnOnEquityInput` type) to compute margin-weighted ROE. > - **Subscription service**: > - Use `calculateWeightedReturnOnEquity` in `HyperLiquidSubscriptionService.aggregateAccountStates()` to set aggregated `returnOnEquity` across DEXs. > - **Tests**: > - Extend `utils/accountUtils.test.ts` with extensive cases for `calculateWeightedReturnOnEquity` (mixed types, zero/negative/NaN handling, precision, edge sizes). > > Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 407d4c2. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).  [f4e8f8d](f4e8f8d) Co-authored-by: Michal Szorad <michal.szorad@consensys.net>

github-actions · 2025-11-21T12:28:59Z

🔍 Smart E2E Test Selection

Selected E2E tags: None (no tests recommended)
Risk Level: low
AI Confidence: 95%

click to see 🤖 AI reasoning details

After thorough analysis of all 100 changed files, I found that none of them are production/functional code changes. The changes consist entirely of:

Test files (.test.tsx, .test.ts) - Unit tests for Bridge, Card, Asset components, and various other UI components
Test snapshots (__snapshots__) - Jest snapshot updates accompanying test changes
Mock files (__mocks__, _mocks_) - Test mocks and test utilities
CI/GitHub workflow files - Changes to E2E test automation infrastructure (.github/workflows/, .github/actions/, .github/scripts/)
Configuration files - .detoxrc.js (Detox E2E config), app.config.js (Expo config), .eslintrc.js
Documentation - CHANGELOG.md, README.md files, CODEOWNERS, guidelines
Dependency patches - .yarn/patches for expo-updates and rive-react-native

Key observations:

No production component implementations were modified (only their test files)
No controllers, engines, or core logic files were changed
No files in critical paths (app/core/, e2e/framework/, e2e/api-mocking/, e2e/fixtures/)
The Bridge and Card component implementations (index.tsx files) remain unchanged - only their tests were updated
CI changes appear to be related to improving E2E test selection and reporting infrastructure

Conclusion:
These changes are purely related to test infrastructure, test coverage, documentation, and CI improvements. They do not affect any user-facing functionality or core wallet features. Running E2E tests would not verify these changes since:

Test file changes need to be verified by running the unit tests themselves (not E2E tests)
Documentation changes don't require functional testing
CI/workflow changes are tested through their own execution
Configuration changes are typically validated through the build process

Therefore, no E2E test tags are recommended for this PR.

View GitHub Actions results

sonarqubecloud · 2025-11-21T12:51:25Z

Quality Gate passed

Issues
75 New issues
0 Accepted issues

Measures
2 Security Hotspots
86.3% Coverage on New Code
1.5% Duplication on New Code

See analysis details on SonarQube Cloud

joaoloureirop and others added 30 commits November 10, 2025 15:05

metamaskbot mentioned this pull request Nov 20, 2025

chore(runway): cherry-pick chore: Update Spanish strings for Card onboarding flow cp-7.58.3 #22740

Merged

7 tasks

[skip ci] Bump version number to 3111

76c536e

metamaskbot mentioned this pull request Nov 20, 2025

chore(runway): cherry-pick chore: timeout build android apk for e2e 40 minutes #23067

Merged

7 tasks

metamaskbot mentioned this pull request Nov 20, 2025

chore(runway): cherry-pick fix: cp-7.60.0 bump transaction controller and transaction pay controller versions #23041

Merged

7 tasks

runway-github bot and others added 4 commits November 21, 2025 10:53

[skip ci] Bump version number to 3119

5056c1c

runway-github bot and others added 6 commits November 21, 2025 11:07

[skip ci] Bump version number to 3120

6fda98b

runway-github bot and others added 2 commits November 21, 2025 12:09

This was referenced Nov 21, 2025

chore(runway): cherry-pick fix(perps): calculate weighted ROE percentage for aggregated account states cp-7.60.0 #23097

Merged

chore(runway): cherry-pick fix(predict): cp-7.60.0 fade in gtm modal after image loads #23083

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

release: 7.60.0 #22825

release: 7.60.0 #22825

metamaskbot commented Nov 17, 2025 •

edited by ieow

Loading

Uh oh!

github-actions bot commented Nov 21, 2025

Uh oh!

sonarqubecloud bot commented Nov 21, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

54 participants

Uh oh!

release: 7.60.0 #22825

Are you sure you want to change the base?

release: 7.60.0 #22825

Conversation

metamaskbot commented Nov 17, 2025 • edited by ieow Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🚀 v7.60.0 Testing & Release Quality Process

📋 Key Processes

Testing Strategy

GitHub Signoff

Issue Resolution

Cherry-Picking Criteria

🗓️ Timeline and Milestones

✅ Signoff Checklist

Team sign-off checklist

Reference

Uh oh!

github-actions bot commented Nov 21, 2025

🔍 Smart E2E Test Selection

Uh oh!

sonarqubecloud bot commented Nov 21, 2025

Quality Gate passed

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

54 participants

metamaskbot commented Nov 17, 2025 •

edited by ieow

Loading