Surfaced during #879 (Swap to new token) but kept out of scope to keep that PR shorter.
The discovery logic in useSwapTokenLookup already produces a held-excluded "Popular tokens" array (top 50 stellar.expert assets by volume7d intersected with the runtime verified-tokens lists). The Add-Token picker could benefit from a similar section.
What to do
- Try reusing the discovery primitives (
computeTrendingIntersection, useStellarExpertTopTokensStore, useVerifiedTokensStore, Blockaid bulk-scan) inside the Add-Token flow.
- Unlike the swap flow, the Add-Token picker should also surface custom Soroban tokens (the swap-only classic-only filter shouldn't carry over).
- Mirror the section header + (i) info treatment used in
SwapToScreen for consistency.
Notes
- The pre-warm hook (
useSwapTokenListsPrewarm in TabNavigator) already populates the shared caches on Home mount, so Add-Token could benefit from instant first paint without doing its own pre-warm work.
Surfaced during #879 (Swap to new token) but kept out of scope to keep that PR shorter.
The discovery logic in
useSwapTokenLookupalready produces a held-excluded "Popular tokens" array (top 50 stellar.expert assets byvolume7dintersected with the runtime verified-tokens lists). The Add-Token picker could benefit from a similar section.What to do
computeTrendingIntersection,useStellarExpertTopTokensStore,useVerifiedTokensStore, Blockaid bulk-scan) inside the Add-Token flow.SwapToScreenfor consistency.Notes
useSwapTokenListsPrewarminTabNavigator) already populates the shared caches on Home mount, so Add-Token could benefit from instant first paint without doing its own pre-warm work.