Saitama token price ratio showing up wrongly. Workaround available; not sure about root cause / fix.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Bug Description
When user tries to swap Eth for Saitama (importing from Coinmarketcap token list), the price ratio is wrong by 1e9, e.g. 1 eth ≈ 30 Saitama instead of 30e9 Saitama. Workaround is available (see below), but not sure about the root cause and potential fix.
Steps to Reproduce
- Go to https://app.uniswap.org/#/swap
- Click on "Select a token"
- Search for Saitama
- Click on Import for Saitama ("via Coinmarketcap")
- Enter 1 Eth for the "from" token
Expected Behavior
It should show around 30e9 Saitama as the "to" token, but instead it shows 30 Saitama instead.
Additional Context
Workaround to correct/refresh the price ratio: Click the Saitama token dropdown (in the "to" token part), then click "Manage Token Lists", and in the "Lists" tab switch off all the token lists. Then go to the "Tokens" tab and delete the previously-saved Saitama token address. Then the price ratio will update correctly, i.e. 1 Eth ≈ 30e9 Saitama.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Saitama import flow at app.uniswap.org and compare the imported token data with the saved token data after using the token-list workaround. Trace how the token address, decimals, and price ratio are selected during import. Done means the imported Saitama token displays approximately 30e9 tokens for 1 ETH without requiring manual list or token deletion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100