Skip to main content
Route finds paths offchain and executes swaps onchain. You do not pay gas for the search. The signed transaction still enforces your exact input, recipient, minimum output and deadline.

​
Where liquidity comes from

Route compares its own direct search with enabled upstream aggregators. When another aggregator supplies a route, that does not mean Route has built a direct integration with each pool it uses. The Kyber source exclusion is not a blanket ban on all hooked pools. Duplicate plans share preparation work. A missing or rate-limited provider reduces coverage; it does not mean the other sources stop working.

​
Direct integrations

Kyber and 0x can reach additional liquidity. Examples observed in our September 5–6, 2026 quote records include Orvex, Metric, Hanji, Kipseli, RobinSwap and Alandale. An observed source name does not establish complete coverage, an independent audit or a direct Route adapter. SushiSwap and PancakeSwap integrations were investigated, but the additional direct adapters did not improve the selected routes in that controlled sample. They remain experimental. Some sources are available upstream when the provider supports and selects them. We add direct integrations when tests show they reach useful liquidity or improve value enough to justify the extra code and gas.

​
How a path is found

Pool listings are hints, not permission to trade. Route checks pools against supported factories and onchain state. It searches the requested pair and connector paths through WETH and USDG. The direct search has these limits:
  • Up to 96 candidate pools and 32 paths.
  • Up to three hops and three split branches.
  • Up to six discovery tokens and 360 unique pool-quote calls.
  • An 18-second target search deadline; already-running network calls can take longer to finish.
Split branches cannot reuse a pool. Their inputs must add up to the exact amount you entered; integer remainders are quoted rather than discarded. If initial discovery finds no supported path, one extra search checks a limited set of common hookless V4 pool keys. This does not cover every custom pool or guarantee a route for every pair.

​
What “best route” means

Candidate transactions are checked at a shared block and explicit positive gas price. Successful simulations take priority over unverified quotes; reverting candidates are excluded. When gas can be converted into the output token, the ranking is:
Pool and provider charges are already reflected in the assessed output. Route adds no fee. Separate approval gas is not included in this ranking. If gas conversion is unavailable, Route falls back to output before gas and discloses the limitation. “Best” means best among the candidates assessed for that request. Search limits, changing liquidity, unsupported pools and unavailable providers can leave a better route undiscovered. See route vs uniswap for measured comparisons.

​
Keep execution lean

The direct executor can settle canonical V2 and V3 legs directly, with authenticated pool callbacks where required. Other supported legs use fixed routing or adapter bindings. Kyber token-output swaps use a guard that measures delivery directly to the recipient. Native ETH output and 0x use their designated executors. A different spender always requires a fresh wallet review; old approvals do not transfer. Route refreshes and checks the route before signing. The active V2 system does not reselect Route’s paths during execution. Experimental execution-time rerouting is not an available feature.

​
Quote updates

Entering a valid amount starts a quote request straight away. Fetching prices and checking the routes still takes time. While a request is running, edits replace the next queued order; obsolete results cannot become an actionable quote. Visible quotes normally refresh about every 15 seconds. Hidden tabs stop polling; returning requests a fresh quote. Rate limits and source failures are disclosed, and a quote does not reserve liquidity. Short-lived metadata and listing hints can be shared. Executable prices are not reused across quote requests. Every route still needs current pool and transaction checks. For the full signing flow, see quotes and execution. Experimental features are not part of the active product unless explicitly stated.