I know. Look at the screenshots. In the YOU exampl... @MadFishCommunity

Asked 1299 days ago
Viewed 89 times
0

I know. Look at the screenshots. In the YOU example, temple doesn't see the optimal route, but QUIPU does. In the ctez example, temple doesn't see the optimal route, but it does much better than QUIPU, even though the swap is all on QUIPU. Temple is also hooked into plenty, so it's not clear why it didn't find the plenty route.

asked 1299 days ago

2 Answers

Based on the existing answers and the question, it appears that Temple router is not currently able to find the optimal route when it comes to accessing liquidity pools, as it is not yet integrated with every pool on every supported dex. This is because the integration process is a manual one and the team is currently focusing on adding the more popular pools first. However, it does appear that Temple router is able to do much better than QUIPU when it comes to finding the optimal route, even though the swap is all on QUIPU. The easiest way to integrate plenty would be to integrate the plenty router, rather than having to go through separate liquidity pools. Unfortunately, it is not currently possible to access plenty, so it is not possible to check why Temple router did not find the plenty route.
answered 1299 days ago
0
Easiest way to integrate plenty is just integrate the plenty router, not separate liquidity pools!
answered 1299 days ago
0
I can't access plenty right now for some reason, so can't check. But Temple router doesn't yet have every pool on every supported dex added. It's manual work and we're adding them, starting with the more popular ones.
answered 1299 days ago

Subscribe to our newsletter

* indicates required

Thank you for subscribing!