Skip to content

fix: limit param in search is incorrect#8019

Merged
juanmigdr merged 5 commits into
mainfrom
fix/limit-in-search-is-incorrect
Feb 23, 2026
Merged

fix: limit param in search is incorrect#8019
juanmigdr merged 5 commits into
mainfrom
fix/limit-in-search-is-incorrect

Conversation

@juanmigdr

@juanmigdr juanmigdr commented Feb 23, 2026

Copy link
Copy Markdown
Member

Explanation

According to the docs, we have been passing the incorrect limits to the API since the beginning, I have updated it to pass first instead of limit and added the Ondo exception that is added on the API side

References

https://consensyssoftware.atlassian.net/browse/ASSETS-2632

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

Note

Medium Risk
Changes request construction for the Token Search API and alters effective result sizes via new clamping logic, which could affect downstream token search UX and pagination expectations.

Overview
Fixes token search pagination by switching the Token API query parameter from limit to first in getTokenSearchURL.

Adds limit clamping to avoid oversized searches: regular queries cap at 50 results, while queries containing Ondo can request up to 500 (otherwise clamped back to 50). Tests are updated/expanded to assert the new parameter and clamping behavior, and the changelog records the fix.

Written by Cursor Bugbot for commit 33d7542. This will update automatically on new commits. Configure here.

@juanmigdr juanmigdr requested a review from a team as a code owner February 23, 2026 16:41
@juanmigdr

Copy link
Copy Markdown
Member Author

@cursor update the assets-controllers changelog

@cursor

cursor Bot commented Feb 23, 2026

Copy link
Copy Markdown

I've successfully updated the assets-controllers changelog! Here's what I accomplished:

Added a proper changelog entry in the "Unreleased" section under a new "Fixed" category
Documented the token search API fix that changes the parameter from limit to first for correct pagination
Included details about the new features: limit validation (max 50 results by default) and the special Ondo exception (up to 500 results for Ondo queries)
Validated the changelog format using yarn changelog:validate to ensure it meets the project's standards
Committed and pushed the changes to the fix/limit-in-search-is-incorrect branch

The changelog entry follows the project's "Keep a Changelog" format and provides clear information about the bug fix and its implementation details for future reference.

Open in Web Open in Cursor 

- Add entry for fixing limit parameter usage in token search
- Documented change from 'limit' to 'first' parameter
- Noted addition of limit validation and Ondo exception

Co-authored-by: Juanmi <juanmigdr@users.noreply.github.com>
@cursor cursor Bot requested a review from a team as a code owner February 23, 2026 16:44
cursoragent and others added 2 commits February 23, 2026 16:48
Correct PR reference from #8008 to #8019 in assets-controllers changelog

Co-authored-by: Juanmi <juanmigdr@users.noreply.github.com>
- Update all nock mocks from 'limit=' to 'first=' parameter
- Add tests for limit validation (max 50 for regular queries)
- Add tests for Ondo exception (allowing up to 500 for Ondo queries)
- Add tests for ignoring very large limits (>500)
- Add test for default limit behavior (defaults to 10)

Co-authored-by: Juanmi <juanmigdr@users.noreply.github.com>
@juanmigdr juanmigdr enabled auto-merge February 23, 2026 17:49

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Comment thread packages/assets-controllers/src/token-service.ts
Comment thread packages/assets-controllers/src/token-service.ts
@juanmigdr juanmigdr added this pull request to the merge queue Feb 23, 2026
@juanmigdr juanmigdr removed this pull request from the merge queue due to a manual request Feb 23, 2026
@juanmigdr juanmigdr added this pull request to the merge queue Feb 23, 2026
Merged via the queue into main with commit f22dd27 Feb 23, 2026
310 checks passed
@juanmigdr juanmigdr deleted the fix/limit-in-search-is-incorrect branch February 23, 2026 18:15
github-merge-queue Bot pushed a commit to MetaMask/metamask-mobile that referenced this pull request Mar 2, 2026
<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**
This PR aims to add the stocks section in the explore page. In order to
get this PR to the finish line, I have:
- Updated the core package
[here](MetaMask/core#8019) to fix an issue with
the `limit` param in the search endpoint request and support for a
higher limit when calling with the QueryString `Ondo`
- Asked the design team to add the corporate icon
[here](#26492)
- Raised the following issues in api-platform and got a fix
  - https://consensys.slack.com/archives/C03MLR70YSK/p1771489684959419
  - https://consensys.slack.com/archives/C03MLR70YSK/p1771850443811719
- Added Geo-blocking (hardcoded for now but it should live on the API at
some point)
- Modified order of sections in explore page following @chaoticgoodpanda
guidance
- Modified predictions section to not be a carousel

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: added stocks section to explore page

## **Related issues**

Fixes: https://consensyssoftware.atlassian.net/browse/ASSETS-2635 &
https://consensyssoftware.atlassian.net/browse/ASSETS-2632

## **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**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

[Here](https://consensys.slack.com/archives/C07NF2K42LE/p1771849520486939)
is a full video explaining the e2e functionality.




https://github.com/user-attachments/assets/ac8c7c52-30c6-4913-9e69-7b8fe8e0db52





<!-- [screenshots/recordings] -->

## **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.


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Adds a new Explore section and full-screen view backed by a new search
hook with geo-restriction logic and new navigation routes, which could
affect what data users see and how filtering/refetch behaves. Refactors
Trending Tokens full view into shared layout/components, so regressions
could impact existing trending-token filtering UI and bottom sheets.
> 
> **Overview**
> Adds a new **Stocks** section to Explore, including a new
`RWATokensFullView` screen/route and `useRwaTokens` hook that queries
Ondo RWA assets (with production geo-blocking) and supports search,
network, and sort filters.
> 
> Refactors `TrendingTokensFullView` into the `UI/Trending` area and
introduces shared `TokenListPageLayout`, `FilterBar`, and
`useTokenListFilters` to unify header/search/filter behavior across
token list full views; updates the network bottom sheet to take an
explicit `networks` prop and adjusts token sorting to push missing
market data to the end. Explore/QuickActions/predictions presentation,
navigation, mocks, and smoke tests are updated to include the new Stocks
section and new predictions row rendering.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
2be0c5a. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
runway-github Bot added a commit to MetaMask/metamask-mobile that referenced this pull request Mar 2, 2026
<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**
This PR aims to add the stocks section in the explore page. In order to
get this PR to the finish line, I have:
- Updated the core package
[here](MetaMask/core#8019) to fix an issue with
the `limit` param in the search endpoint request and support for a
higher limit when calling with the QueryString `Ondo`
- Asked the design team to add the corporate icon
[here](#26492)
- Raised the following issues in api-platform and got a fix
  - https://consensys.slack.com/archives/C03MLR70YSK/p1771489684959419
  - https://consensys.slack.com/archives/C03MLR70YSK/p1771850443811719
- Added Geo-blocking (hardcoded for now but it should live on the API at
some point)
- Modified order of sections in explore page following @chaoticgoodpanda
guidance
- Modified predictions section to not be a carousel

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: added stocks section to explore page

## **Related issues**

Fixes: https://consensyssoftware.atlassian.net/browse/ASSETS-2635 &
https://consensyssoftware.atlassian.net/browse/ASSETS-2632

## **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**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

[Here](https://consensys.slack.com/archives/C07NF2K42LE/p1771849520486939)
is a full video explaining the e2e functionality.




https://github.com/user-attachments/assets/ac8c7c52-30c6-4913-9e69-7b8fe8e0db52





<!-- [screenshots/recordings] -->

## **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.


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Adds a new Explore section and full-screen view backed by a new search
hook with geo-restriction logic and new navigation routes, which could
affect what data users see and how filtering/refetch behaves. Refactors
Trending Tokens full view into shared layout/components, so regressions
could impact existing trending-token filtering UI and bottom sheets.
> 
> **Overview**
> Adds a new **Stocks** section to Explore, including a new
`RWATokensFullView` screen/route and `useRwaTokens` hook that queries
Ondo RWA assets (with production geo-blocking) and supports search,
network, and sort filters.
> 
> Refactors `TrendingTokensFullView` into the `UI/Trending` area and
introduces shared `TokenListPageLayout`, `FilterBar`, and
`useTokenListFilters` to unify header/search/filter behavior across
token list full views; updates the network bottom sheet to take an
explicit `networks` prop and adjusts token sorting to push missing
market data to the end. Explore/QuickActions/predictions presentation,
navigation, mocks, and smoke tests are updated to include the new Stocks
section and new predictions row rendering.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
2be0c5a. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
runway-github Bot added a commit to MetaMask/metamask-mobile that referenced this pull request Mar 2, 2026
<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**
This PR aims to add the stocks section in the explore page. In order to
get this PR to the finish line, I have:
- Updated the core package
[here](MetaMask/core#8019) to fix an issue with
the `limit` param in the search endpoint request and support for a
higher limit when calling with the QueryString `Ondo`
- Asked the design team to add the corporate icon
[here](#26492)
- Raised the following issues in api-platform and got a fix
  - https://consensys.slack.com/archives/C03MLR70YSK/p1771489684959419
  - https://consensys.slack.com/archives/C03MLR70YSK/p1771850443811719
- Added Geo-blocking (hardcoded for now but it should live on the API at
some point)
- Modified order of sections in explore page following @chaoticgoodpanda
guidance
- Modified predictions section to not be a carousel

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: added stocks section to explore page

## **Related issues**

Fixes: https://consensyssoftware.atlassian.net/browse/ASSETS-2635 &
https://consensyssoftware.atlassian.net/browse/ASSETS-2632

## **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**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

[Here](https://consensys.slack.com/archives/C07NF2K42LE/p1771849520486939)
is a full video explaining the e2e functionality.

https://github.com/user-attachments/assets/ac8c7c52-30c6-4913-9e69-7b8fe8e0db52

<!-- [screenshots/recordings] -->

## **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.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Adds a new Explore section and full-screen view backed by a new search
hook with geo-restriction logic and new navigation routes, which could
affect what data users see and how filtering/refetch behaves. Refactors
Trending Tokens full view into shared layout/components, so regressions
could impact existing trending-token filtering UI and bottom sheets.
>
> **Overview**
> Adds a new **Stocks** section to Explore, including a new
`RWATokensFullView` screen/route and `useRwaTokens` hook that queries
Ondo RWA assets (with production geo-blocking) and supports search,
network, and sort filters.
>
> Refactors `TrendingTokensFullView` into the `UI/Trending` area and
introduces shared `TokenListPageLayout`, `FilterBar`, and
`useTokenListFilters` to unify header/search/filter behavior across
token list full views; updates the network bottom sheet to take an
explicit `networks` prop and adjusts token sorting to push missing
market data to the end. Explore/QuickActions/predictions presentation,
navigation, mocks, and smoke tests are updated to include the new Stocks
section and new predictions row rendering.
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
2be0c5a. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
runway-github Bot pushed a commit to MetaMask/metamask-mobile that referenced this pull request Mar 2, 2026
…26426)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**
This PR aims to add the stocks section in the explore page. In order to
get this PR to the finish line, I have:
- Updated the core package
[here](MetaMask/core#8019) to fix an issue with
the `limit` param in the search endpoint request and support for a
higher limit when calling with the QueryString `Ondo`
- Asked the design team to add the corporate icon
[here](#26492)
- Raised the following issues in api-platform and got a fix
  - https://consensys.slack.com/archives/C03MLR70YSK/p1771489684959419
  - https://consensys.slack.com/archives/C03MLR70YSK/p1771850443811719
- Added Geo-blocking (hardcoded for now but it should live on the API at
some point)
- Modified order of sections in explore page following @chaoticgoodpanda
guidance
- Modified predictions section to not be a carousel

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: added stocks section to explore page

## **Related issues**

Fixes: https://consensyssoftware.atlassian.net/browse/ASSETS-2635 &
https://consensyssoftware.atlassian.net/browse/ASSETS-2632

## **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**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

[Here](https://consensys.slack.com/archives/C07NF2K42LE/p1771849520486939)
is a full video explaining the e2e functionality.




https://github.com/user-attachments/assets/ac8c7c52-30c6-4913-9e69-7b8fe8e0db52





<!-- [screenshots/recordings] -->

## **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.


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Adds a new Explore section and full-screen view backed by a new search
hook with geo-restriction logic and new navigation routes, which could
affect what data users see and how filtering/refetch behaves. Refactors
Trending Tokens full view into shared layout/components, so regressions
could impact existing trending-token filtering UI and bottom sheets.
> 
> **Overview**
> Adds a new **Stocks** section to Explore, including a new
`RWATokensFullView` screen/route and `useRwaTokens` hook that queries
Ondo RWA assets (with production geo-blocking) and supports search,
network, and sort filters.
> 
> Refactors `TrendingTokensFullView` into the `UI/Trending` area and
introduces shared `TokenListPageLayout`, `FilterBar`, and
`useTokenListFilters` to unify header/search/filter behavior across
token list full views; updates the network bottom sheet to take an
explicit `networks` prop and adjusts token sorting to push missing
market data to the end. Explore/QuickActions/predictions presentation,
navigation, mocks, and smoke tests are updated to include the new Stocks
section and new predictions row rendering.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
2be0c5a. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
joaoloureirop pushed a commit to MetaMask/metamask-mobile that referenced this pull request Mar 3, 2026
…26768)

- feat: stocks section in explore cp-7.68.0 (#26426)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**
This PR aims to add the stocks section in the explore page. In order to
get this PR to the finish line, I have:
- Updated the core package
[here](MetaMask/core#8019) to fix an issue with
the `limit` param in the search endpoint request and support for a
higher limit when calling with the QueryString `Ondo`
- Asked the design team to add the corporate icon
[here](#26492)
- Raised the following issues in api-platform and got a fix
  - https://consensys.slack.com/archives/C03MLR70YSK/p1771489684959419
  - https://consensys.slack.com/archives/C03MLR70YSK/p1771850443811719
- Added Geo-blocking (hardcoded for now but it should live on the API at
some point)
- Modified order of sections in explore page following @chaoticgoodpanda
guidance
- Modified predictions section to not be a carousel

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: added stocks section to explore page

## **Related issues**

Fixes: https://consensyssoftware.atlassian.net/browse/ASSETS-2635 &
https://consensyssoftware.atlassian.net/browse/ASSETS-2632

## **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**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**


[Here](https://consensys.slack.com/archives/C07NF2K42LE/p1771849520486939)
is a full video explaining the e2e functionality.





https://github.com/user-attachments/assets/ac8c7c52-30c6-4913-9e69-7b8fe8e0db52





<!-- [screenshots/recordings] -->

## **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.


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Adds a new Explore section and full-screen view backed by a new search
hook with geo-restriction logic and new navigation routes, which could
affect what data users see and how filtering/refetch behaves. Refactors
Trending Tokens full view into shared layout/components, so regressions
could impact existing trending-token filtering UI and bottom sheets.
> 
> **Overview**
> Adds a new **Stocks** section to Explore, including a new
`RWATokensFullView` screen/route and `useRwaTokens` hook that queries
Ondo RWA assets (with production geo-blocking) and supports search,
network, and sort filters.
> 
> Refactors `TrendingTokensFullView` into the `UI/Trending` area and
introduces shared `TokenListPageLayout`, `FilterBar`, and
`useTokenListFilters` to unify header/search/filter behavior across
token list full views; updates the network bottom sheet to take an
explicit `networks` prop and adjusts token sorting to push missing
market data to the end. Explore/QuickActions/predictions presentation,
navigation, mocks, and smoke tests are updated to include the new Stocks
section and new predictions row rendering.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
2be0c5a. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
[f8c1bda](f8c1bda)

Co-authored-by: Juanmi <95381763+juanmigdr@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants