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.
thirashapw
commented
1 year ago
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.