If you send 1,000 USDC from Ethereum to Arbitrum, the destination pool’s available liquidity helps determine how much ETH you can receive. You are comparing routes, so focus on the amount you would actually get after the route’s swaps and costs.
What does destination liquidity decide?
Destination liquidity is the supply of tokens available for a trade on the network where you want to receive funds. A route can only deliver an output token if it can access that token there, directly or through other trades.
For example, a service might move your USDC to Arbitrum, then trade it for ETH in a pool. A pool is a shared supply of two tokens that people trade against. If the pool has little ETH, your trade uses up more of the available supply and the price moves against you.
Some bridge designs instead have a provider send you the requested token from funds already on the destination network, then settle the cross-chain transfer later. Across Protocol’s documentation describes this kind of destination-side fulfillment. Either way, available funds and trading depth on the destination shape what a route can offer.
How does pool depth change your output?
A deeper pool usually gives you more output for the same input because your trade has less effect on its price. Uniswap’s documentation explains that pool reserves help determine swap prices; the same principle applies when a cross-chain route includes a destination swap.
Say a destination pool holds 100 ETH and 250,000 USDC. Ignoring fees, a 1,000 USDC trade against that pool returns about 0.3984 ETH under a simple constant-product model, where the product of the two token reserves stays roughly constant. A pool with ten times those reserves would return about 0.3998 ETH for the same trade, before fees.
Those figures are examples, not quotes. The trade also changes the pool, so the next person may get a different price. A route may split a large trade across pools or trade through an intermediate token, but each extra step can add costs and another source of price movement.
What should you compare in a route quote?
Compare the estimated output and the minimum amount the route promises under its slippage setting. Slippage means the amount the price can move before the trade fails or completes at a worse rate. A quote can change while it waits because other trades alter pool balances.
Check whether the destination asset is the exact token you want. Tokens can share a name or ticker while being different assets, and a route may offer a wrapped version, which represents another asset on that network. Also account for bridge charges, swap fees, and network fees; their amounts vary by route and network activity.
- Compare the same input amount and the same destination token.
- Look at the expected output after fees, plus the minimum received.
- For a large transfer, see whether the quote changes when you try a smaller amount.
That last check reveals a useful edge case: a route may exist for a small trade but offer much worse output for a larger one. The route’s token routing—the choice of pools and intermediate assets—can change as the amount grows. If a route only works by using thin pools, splitting the trade, or accepting a different token, its headline availability may hide a poor fit.
How do you choose between one flow and separate steps?
A cross-chain swap combines moving funds between networks and exchanging them into the destination token. It can save you from arranging those tasks separately, but the combined route still depends on destination liquidity. Knowing why Biswap suits a first swap helps you weigh that one-flow convenience against checking a bridge and destination swap as separate choices.
Biswap is a cross-chain bridge and swap service, so it can help you move and exchange assets across networks in one flow. Before choosing any route, compare its final output with the token you need and the costs you would face if you handled the transfer and swap separately.
Ask yourself: is the destination amount acceptable after fees, and does the route deliver the exact asset you intend to hold?