Routing Path
The sequence of liquidity pools a trade passes through to convert one token to another, particularly in multi-hop swaps.
Routing Path — A routing path is the specific sequence of token swaps and liquidity pools that a DEX aggregator uses to execute a trade, often passing through multiple intermediate tokens to achieve a better final price. For example, swapping Token A to Token C might route through A-to-B then B-to-C if that path offers lower price impact than a direct A-to-C swap.
How Routing Paths Work
When a trader submits a swap on a DEX aggregator, a routing algorithm evaluates all possible paths between the input and output tokens. For well-established pairs like ETH/USDC, the optimal path is usually a direct swap through a single high-liquidity pool. For less common pairs, the algorithm constructs multi-hop routes that pass through intermediate tokens to access deeper liquidity.
The routing algorithm considers: available liquidity at each hop, the swap fee charged by each pool, the gas cost of executing additional hops, and the total output after accounting for all costs. On Solana, Jupiter's routing engine evaluates pools across Raydium, Orca, Phoenix, Lifinity, and dozens of other DEXs, testing thousands of potential paths in milliseconds to find the optimal route.
Split routing adds another dimension. Instead of sending the entire order through one path, the aggregator can split the trade into portions sent through different paths simultaneously. A $50,000 swap might be split 60/40 between two different routes, with each portion choosing the path that minimizes price impact for that specific amount. The final execution combines results from all paths.
Why Routing Paths Matter
Efficient routing can mean the difference between a 0.5% and 5% cost on a swap, particularly for tokens without deep direct liquidity. A direct swap of a small-cap token to USDC through a thin $50,000 pool would cause massive price impact. But routing through that token to SOL (deeper pool) and then SOL to USDC (deepest pool) dramatically reduces total slippage.
Routing path transparency is also important for security. Traders should verify the route before confirming a swap to ensure it doesn't pass through manipulatable low-liquidity pools where sandwich attacks are more likely. Most aggregator interfaces display the routing path visually, showing each hop, the DEX used, and the expected output at each stage.
Real-World Example
A trader on Jupiter wants to swap 10,000 USDC for a new Solana gaming token called PIXEL. There is no direct USDC/PIXEL pool. Jupiter's routing engine finds the optimal path: USDC to SOL on Raydium's concentrated liquidity pool (0.02% fee, deep liquidity), then SOL to PIXEL on Orca's whirlpool (0.3% fee, moderate liquidity). An alternative path through USDC to BONK to PIXEL was evaluated but rejected because the BONK/PIXEL pool had only $20,000 in liquidity, which would cause 8% slippage on the second hop. The chosen two-hop route results in a total cost of 0.6% (fees plus price impact), compared to the 8.5% the worst path would have cost. Jupiter displays this route visually as USDC -> SOL -> PIXEL with the DEX and fee at each hop.
Related Terms
Liquidity Aggregation
Combining liquidity from multiple DEXs to execute a trade at the best composite price, as done by Jupiter and 1inch.
Read definition DeFi & AMMDEX Aggregator
A platform like Jupiter or 1inch that splits a trade across multiple DEXs simultaneously to get the best execution price.
Read definition DeFi & AMMRouter (DEX)
A smart contract that finds the optimal path through one or more liquidity pools to execute a token swap at the best price.
Read definition DeFi & AMMSlippage
The difference between the expected price of a trade and the actual execution price, caused by price movement or low liquidity.
Read definition DeFi & AMMSwap (DEX)
The act of exchanging one token for another on a decentralized exchange, executed through a smart contract.
Read definitionFrequently Asked Questions
Common questions about Routing Path in cryptocurrency and DeFi.
Multi-hop routing occurs when there is no deep direct liquidity pool between your input and output tokens. The aggregator routes through intermediate tokens (often SOL, ETH, or USDC) that have deep liquidity pools with both your input and output tokens. This multi-hop path typically results in less slippage and a better final price than forcing the trade through a thin direct pool.
Each hop charges a swap fee (typically 0.05% to 1%), and on some chains each hop adds gas cost. However, the price improvement from using deeper liquidity pools at each hop usually outweighs the additional fees. If a two-hop route saves 3% in slippage but costs an extra 0.3% in hop fees, the net benefit is still 2.7%.
Most aggregators automatically select the optimal path, but advanced interfaces allow users to specify routing preferences. On Jupiter, you can select specific DEXs to include or exclude. On 1inch, you can set maximum hop count and exclude certain tokens from routing. However, manual routing rarely outperforms the aggregator's algorithm for standard trades.
Ready to put your knowledge into practice?
Start Boosting