UniSwap Dapp cannot find the right router path
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
There is a Uniswap V3 liquidity pool on Polygon mainnet, which is the pair of two tokens: USDC.e and AKRE.
The Pool link is: https://polygonscan.com/address/0x65906dbdfca73c67cf35744864d2f3f9f71a8c44
The AKRE token link is: https://polygonscan.com/address/0xe9c21de62c5c5d0ceacce2762bf655afdceb7ab3
There are more than 30K USDC.e of liquidity in this pool. It works well while user selects USDC.e and AKRE directly to exchange. But if user selects any tokens other than USDC.e to buy/sell AKRE, the UI always prompt: "Insufficient liquidity for this trade."
I have checked this problem on some old releases, and found that all the releases before v4.255.4 has no this preblem. This problem only happens on all the releases after v.4.255.5 (included).
Here are some screen copy, please help check this problem, Thanks!
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
Reproduce the swap on Polygon with AKRE and compare behavior between v4.255.4 and v4.255.5, using the linked pool and token addresses. Trace the router-path selection entry point and verify that trades routed through tokens other than USDC.e can find the AKRE pool; done means the UI selects a valid route instead of reporting insufficient liquidity.
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