Two tokens showing wrong price due to token decimals being off

[Rachel-Eichenberger]

Bug Description
Right now two tokens are giving a bad price off by 9 decimals. I believe it to be from a token list, but I have not found a list that has the wrong decimals.
Tokens that we have found as of now are
Luffy Inu -- 0xC1bfcCd4c29813eDe019D00D2179Eea838a67703
Saitama -- 0x8B3192f5eEBD8579568A2Ed41E6FEB402f93f73F

Both show the price but 9 decimals short

Steps to Reproduce

1. Go to app.uniswap.org
2. load either token
3. price is only showing wrong for x percent ( I don't see )

...

Expected Behavior
Load with correct price

Additional Context
Between clearing cookies, cache, disabling token lists, hard refresh and loading token manually with token address, seems to clear the issue.

Not 100% if this is token list or not, just been seeing a lot of these tickets

[Rachel-Eichenberger]

This seems to be showing up in other places, a users manage V2 liquidity page, with INXT token, on the swap page with ATRI

[Rachel-Eichenberger]

also add Token Luffy to the list of tokens

[Rachel-Eichenberger]

Add token HOKK to this list

Not sure why but several tokens seeing this issue and tickets in discord seem to be growing

[mykcryptodev]

I suspect that this is causing issues with my token as well.
Pawthereum: 0xAEcc217a749c2405b5ebC9857a16d58Bdc1c367F

The workaround has intermittent success for me.
Hoping we can get a solid fix.

[willhennessy]

thanks for reporting Rachel. It looks like Saitama and Luffy Inu are not on any token list. I assume the app fetches decimals from the contract or possibly assumes that decimals=18

In fact, the contract for these two tokens both shows decimals=9. That explains the off by 9, but I'm not sure where in the code base our app makes this assumption or attempts to read the contract.
https://etherscan.io/address/0xC1bfcCd4c29813eDe019D00D2179Eea838a67703#code
https://etherscan.io/address/0x8B3192f5eEBD8579568A2Ed41E6FEB402f93f73F#code

@JFrankfurt do you know?

(mykcryptodev, you token appears to be a fee-on-transfer token. those are not supported on uniswap v3.)

[Rachel-Eichenberger]

@JFrankfurt @willhennessy

Gladly. yes correct, something is loading 18 decimals somewhere. I'm wondering (although coingecko reports 9 decs) most users still search by name and coingecko list shows up when searching name

But Pretty sure something like a forced 18 decs somewhere. Doesn't happen to everyone, yet seen across various devices/browers.

Usually deleting the token and re adding via token contract address, it will pull the correct decs from the contract (sometimes needed - to disable token lists and hard refresh as well)