Base

rolling out search improvements on coinbase wallet

should help people find tokens faster and make sure that they are interacting with the right ones.

That’s a great update, but there are still some issues with price lag, which can cause warnings when trying to make transactions. The warning usually mentions a high price impact. For example, let’s say the price on Uniswap spikes due to a big buy, increasing to 0.101. However, the price in Coinbase Wallet remains stuck at the old rate of 0.091 for hours. This mismatch triggers the high price impact warning, making it difficult to complete transactions smoothly. It's something that definitely needs to be addressed

@base builder #001; onchain cities w/ OAK & city3

Proud member of the Lordy community. Riding high with $LORDY, the top memecoin on Base.  Here to make waves and share the excitement. 

Website: lordy.meme

Core team @base • Former maintainer: bitcoin.org • Editor: Mastering Bitcoin & Mastering Ethereum • Builder, full stack developer: github.com/wbnns

It's not just $Lordy. CB have a problem with lagging prices. Let me explain this easier:

It's all due to the price difference between CB and whatever platform they use to extract the data:

$1 on Uniswap = 9614 Lordy
$1 on CB = 9544 Lordy
Both with 1% slippage

Price of Lordy:
Uniswap: $0.000103
CB: $0.000091
Difference: 12.3%

The impact price on CB shows 12.3%.

So, CB is lagging to update the price, which is causing the price impact which is a false error that might stop investors from buying a token. For example there is a big buy on uniswap which send the token up the chart for 20% then if another person would like to buy the same token in CB wallet the chart would continue to display the old price hance the information about high price impact, in this case it would be 20%. It's kind of bad that such big wallet like CB have this kind of issue with updating the price on time. It takes sometimes a couple of hours!

Thanks for sharing this feedback; how could this be updated to be more helpful to you?