Simple Base SwapSimple Base SwapOpen app
← All articles
Nov 13, 2026·5 min read

Why Your Swap Sometimes Goes Through Another Token First

baseswapsguides
base

You ask your wallet to swap one token for another, and the quote shows your trade passing through a second token on the way. You wanted USDC for your WBTC, but the route shows WBTC going to ETH first, then ETH going to USDC. Nothing is broken. This is called multi hop routing, and it is one of the most common things a swap interface does behind the scenes.

What a hop actually is

Every swap on a decentralized exchange happens inside a liquidity pool, a pot of two tokens that traders swap against. A direct swap is one hop: your token goes into the pool, the other token comes out. A multi hop swap chains two or more of these pools together in a single transaction. Your first token goes in, an intermediate token comes out of the first pool and goes straight into a second pool, and the final token comes out at the end. From your wallet's point of view it still looks like one swap. Under the hood it is a sequence of pool interactions bundled into one transaction.

Why a direct pool is not always the best path

In an ideal world every pair of tokens would have a deep, well funded pool and you could always swap directly. In practice, liquidity is spread thin across thousands of token pairs, and most of it concentrates around a handful of widely held assets such as ETH, WETH, and major stablecoins like USDC. If you want to swap a smaller or newer token for another smaller or newer token, a direct pool between the two may not exist at all, or it may exist but hold very little liquidity.

Routing through a popular intermediate token solves this. A route like Token A to WETH to Token B can use two deep, liquid pools instead of one shallow one. Even when a direct pool does exist, a multi hop path can sometimes offer a better final price if the direct pool has less liquidity than the combined depth of an indirect path.

How your wallet or aggregator finds the route

Most swap interfaces on Base, including Simple Base Swap, rely on a routing engine that treats this as a search problem. It looks at the pools available across one or more decentralized exchanges, estimates the price and available depth of each, and compares a direct path against multi hop alternatives. Some routers go further and split a single trade across several paths at once, sending part of it through one route and part through another, then recombining the output. The goal in every case is the same: find the path, or combination of paths, that gets you the most of the token you want after accounting for fees along the way.

This comparison also has to account for gas. Every additional hop is an additional pool interaction, and each one adds to the gas cost of the transaction. A route that technically offers a slightly better price is not worth it if the extra gas spent to achieve it is larger than the improvement. A well built router weighs the price improvement against the added gas before recommending a multi hop path, which is why you will sometimes see a router choose a direct, single hop route even when a multi hop one offers a marginally better rate on paper.

What this means for slippage and price impact

A multi hop route does not eliminate slippage, it distributes it. Each pool in the chain has its own price impact based on how much liquidity it holds relative to your trade size. When you set a slippage tolerance in your wallet before confirming a swap, that tolerance applies to the entire route from start to finish, not to each individual hop. If prices move between the moment you get a quote and the moment your transaction confirms, a longer route has more individual pools where that movement could show up, which is one reason multi hop trades can be a little more sensitive to timing than a single pool swap. This is normal and expected. It is also exactly what swap fees and slippage are designed to protect you against: your transaction will revert rather than complete at a worse price than the limit you set.

Reading a route before you confirm

Most swap interfaces that show you a route will display it as a simple chain, for example Token A, then WETH, then Token B. A few things are worth glancing at before you confirm:

  • The intermediate token. Routing through a well known asset like WETH or a major stablecoin is routine. Routing through an obscure token you have never heard of is worth a second look, since it suggests the router found liquidity in an unusual place.
  • The number of hops. More hops generally means more gas. If the price difference between a one hop and a two hop route is small, the extra gas may not be worth it, and a good router will usually already reflect that in the quote it shows you first.
  • The final quoted amount, not just the path. The route is a means, not the goal. What matters is the amount you actually receive after fees, gas, and any price impact, which is the number your wallet shows you right before you sign.

The short version

Multi hop routing lets a swap move through one or more intermediate tokens instead of requiring a single deep pool between the exact two tokens you want to trade. It exists because liquidity on any chain, including Base, concentrates around a small set of popular assets rather than spreading evenly across every possible pair. A good router compares direct and indirect paths, weighs the price difference against the extra gas each hop adds, and settles on whichever route gets you the best result after costs. You do not need to manage any of this yourself, but understanding why your route sometimes takes a detour makes the quote you are looking at a lot less mysterious.

Ready to try it yourself?

Create a non-custodial wallet on Base in seconds. No account, no sign-up.

Open the web app