Insufficient liquidity error with Auto Router API
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
Upon trying to purchase $MLK we find that with auto router API on, insufficient liquidity for trade is shown.
When turning the auto router API off, the trade route is fine.
The legacy router appears to not be being used anymore.
Steps to Reproduce
Go to the main swap app with Auto Router API on, 0xf87C4B9C0c1528147CAc4E05b7aC349A9Ab23A12
Attempt to trade $MLK token for contract address
Expected Behavior
The V2 liquidity pool to be found and trades executed in that.
Additional Context
This has been reported by multiple buyers attempting to purchase across mobile and desktop. I found the Auto Router API determines "no route found" when queried for the above contract address, and as the fallback behaviour should be to use the legacy router, this is not occuring or the trade would still show up.
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 MLK swap in the main swap app with Auto Router API enabled, then trace the Auto Router API response and the fallback to the legacy router. Done means the V2 liquidity pool is found and the trade executes instead of showing insufficient liquidity or no route found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, blockchain, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100