fix: assign mainnetAddress correctly in token search (#1734)

Co-authored-by: brdy <[email protected]>
rainbow-me · Oct 21, 2024 · c56dbbe · c56dbbe
1 parent ff500fd
commit c56dbbe
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/src/core/resources/search/parseTokenSearch.ts b/src/core/resources/search/parseTokenSearch.ts
@@ -8,14 +8,15 @@ export function parseTokenSearch(
   chainId: ChainId,
 ): SearchAsset {
   const networkInfo = asset.networks[chainId];
+  const mainnetInfo = asset.networks[ChainId.mainnet];
 
   return {
     ...asset,
     address: networkInfo ? networkInfo.address : asset.address,
     chainId,
     decimals: networkInfo ? networkInfo.decimals : asset.decimals,
     isNativeAsset: isNativeAsset(asset.address, chainId),
-    mainnetAddress: asset.uniqueId as AddressOrEth,
+    mainnetAddress: mainnetInfo?.address as AddressOrEth,
     uniqueId: `${networkInfo?.address || asset.uniqueId}_${chainId}`,
   };
 }