DEV Community

Milton Altenwerth
Milton Altenwerth

Posted on

How Can Fraxswap Swap Tokens Without a Direct Pool?

If a Fraxswap quote shows an unfamiliar token between the one you hold and the one you want, it can connect pools through that token even without a direct pool for your pair. The middle token is an intermediary asset: one swap produces it, and the next uses it as input. Both legs execute as one spot trade on the same network. What matters is connected liquidity, not a dedicated pool for every token combination.

How Fraxswap Routes a Spot Swap

Fraxswap's spot routes move input through one or more Pair contracts, which hold the tokens and liquidity used for each swap. In a quote on Fraxswap, an intermediary token between input and output names a stop along that route. You are choosing a path through pools, not taking delivery of the middle token as the final result. The selected router or interface must support the path; connected pools alone do not guarantee that every interface will quote it.

A token selector can blur three distinct things. A token contract identifies an asset, such as token A. An A/B pair is a pool holding liquidity for swaps between A and B. A route is the ordered sequence of pairs that takes input A to output B. Listing A and B does not establish an A/B pair or another sequence that can carry the trade.

Direct and Multihop Routes

A direct route takes A to B through one A/B pool, with no intermediary token. A multihop route takes A to C in an A/C pool, then C to B in a C/B pool. The output of the first swap becomes the input of the second. Both swaps occur within one transaction on one network. A multihop spot route therefore uses connected pools; it does not require you to place two separate orders.

The path in a quote makes the distinction visible: A → B uses one pool; A → C → B uses two. More intermediaries mean more pools to traverse, and each pool needs usable liquidity for the amount routed through it. The middle token may be unfamiliar, but its role is specific: it connects pools that share that asset.

What Changes When a Quote Adds a Hop

Adding a hop adds another pool fee and another liquidity dependency, but it does not necessarily reduce the amount received. Compare two quotes with the same A input, B output, trade amount, network, and router. Keep the A/C and C/B pools the same too. In the first case, the A/B pool has ample liquidity, so the one-pool route may give more B after its fee. In the second, only the A/B pool's liquidity is thin. The direct trade can move its price enough that the A/C/B route gives more B even after two pool fees. The decisive change is liquidity in the direct pool.

Pool count is a clue, not a ranking. For your intended amount, compare the quoted output, the assets in the path, and the minimum received after your slippage setting. A small trade may fit a direct pool comfortably, while a larger one may face more price impact there. The result depends on current pool liquidity and fees. Path selection matters too: one interface may show a supported route that another does not offer.

When No Route Is Available

A route is unavailable when the selected router or interface cannot find a supported path with usable liquidity at every hop for your amount. Seeing both token contracts in a selector does not establish a pool, a connected path, or enough liquidity for a useful quote. A path with poor quoted output is different from no route at all. Look at the amount and path before submitting the trade. Moving assets between networks requires bridging, which is separate from a spot route.

A multihop spot quote also says nothing about whether the same path works for a Fraxswap TWAMM order. TWAMM spreads an order over time, so its supported paths and execution rules must be considered separately from a spot router's path.

The quoted path lets you distinguish a listed token, an existing pool, and a usable route for the amount you want to trade.

Top comments (0)