SyncSwapSyncSwap

How does the SyncSwap Smart Router find the best route?

Quick answer

SyncSwap's Smart Router compares available swap paths across Classic, Stable and Range liquidity. The router can consider direct pools, multi-hop routes and path splitting so the app can quote a better route than a single-pool lookup. You still review the final quote before confirming the transaction.

Can the Smart Router split a trade across multiple pools?

Yes. The Smart Router can split a route when using more than one path gives a better quote than sending the whole trade through one pool.

The official Smart Router overview describes routing across pools, hops and split paths. For users, the practical point is that a single swap quote may be assembled from more than one liquidity source.

Route logicHow it helps the quote
Pool modelsCompares liquidity from Classic, Stable and Range pools instead of treating all pairs as one design.
Direct pathUses a single pool when it is already the best available path for the requested trade.
Multi-hop pathRoutes through an intermediate token when that path can improve execution.
Path splittingDivides a trade across multiple paths or pools when a split route gives a better quote.
User confirmationShows the final route and received amount before the wallet transaction is submitted.

Does it work across Classic, Stable and Range pools?

Yes. SyncSwap's router is designed around the protocol's pool set, so it can evaluate Classic, Stable and Range liquidity when finding a route.

That cross-pool behavior matters because different pool models are strong in different conditions. A pegged-asset swap may favor Stable liquidity, while a volatile pair or a concentrated-liquidity price band may produce the better route elsewhere.

  • Classic pools: general token-pair liquidity.
  • Stable pools: liquidity for assets that usually trade near a peg.
  • Range pools: concentrated liquidity around selected price ranges.
  • Smart routing: quote assembly across the available pool set.

Do I need to configure anything to use it?

No manual router setup is usually required for a standard app swap. The routing logic runs behind the quote, while the user controls the trade inputs and final confirmation.

If you are integrating directly, read the official routing documentation before assuming how a path is built. For normal users, the quote screen is the source of truth for the route, price impact and minimum received.

FAQ

Frequently asked

Route before you sign

The router finds a path; the wallet confirmation is still yours.

Quote a swap ↗

01What does the Smart Router optimize for?

The Smart Router optimizes a swap route by comparing available paths across SyncSwap liquidity. Its goal is to find the best route for the quoted trade, which can mean using different pool models, hops or route splits instead of forcing the swap through a single obvious pool.

02Can the Smart Router split a trade across multiple pools?

Yes. The Smart Router documentation describes path splitting, which lets a trade use more than one pool or path when that improves the route. Splitting is handled by the routing logic; the trader still reviews one quote before confirming the transaction.

03Does the Smart Router work across pool types?

Yes. SyncSwap's routing model is built around its liquidity system, including Classic, Stable and Range pools. That matters because a stable-pair route, a volatile-pair route and a concentrated-liquidity route may offer different execution for the same input token.

04Do I need to configure anything to use it?

For a normal swap, you usually do not need to configure the Smart Router manually. The app prepares the route in the background, while you should still review the network, output token, route, price impact, minimum received and gas before confirming.

05Where is the Smart Router documented?

SyncSwap documents the Smart Router in its official overview docs. Use that page as the primary source for routing behavior, especially if you are building integrations or trying to understand multi-hop routing, path splitting or how different pool models are considered.