You see my point here? @MadFishCommunity

Based on the information provided, it appears that the issue lies in the hard-coded limitation of 30% of the pool's liquidity that can be swapped in a single transaction for Tez/Token pools. This limitation is not present in Token/Token pools, which can cause the trade to be routed through Token/Token pools which usually hold less liquidity and offer worse exchange rates when the amount of tokens to be swapped is higher than 30% of the corresponding Tez/Token pool. This explains why swapping 1 KDao to Tez goes through 3 other tokens, while swapping 10 KDao goes straight to Tez. It is possible that this issue is related to route cost validation on the frontend, which the team will investigate further on Monday.

Hello. Yes, we checked this problem. Our router doesn't calculcate correctly routs for small token ammounts. We have added this issue to our backlog to fix.

Hey Vladimir have you looked into this? I still see the same thing. Like try to swap 1 KDao to tez and it goes through 3 other tokens, try to swap 10 KDao and it goes straight to Tez 🤔

yes. It's strange. I've tried to make the same swap and I have a direct route. Maybe it was an issue with route cost validation on the frontend. We will check on Monday.

I don't think the 30% cap has something to do with that though, if swapping 10 xtz doesn't trigger it the 0.1xtz definitely shouldn't trigger that either

Hi. Tez/Token pools have hard-coded a limitation that no more than 30% of the pool's liquidity can be swapped in a single transaction. Token/Token pools do not have such a limitation. Thus if the amount of tokens to be swapped is higher than 30% of the corresponding Token/Tez pool, the trade will be routed through Token/Token pools which usually hold less liquidity and offer worse exchange rates.