A cross-chain swap minimum is the least amount of the destination token a route will accept. The key check is whether that minimum covers the whole route or only its final swap.
Source swaps change what enters the bridge
A source swap trades your starting token on the chain where you hold it. Its price impact is the price change caused by your trade; it tends to grow when the trade is large compared with the available pool liquidity.
For example, you start with 1,000 USDC on Ethereum and swap into a token the route can bridge. The source swap may produce less than its estimate if the pool has limited liquidity. That smaller amount then enters the next part of the route.
When comparing quotes, check whether they use the same starting amount and token. A route that begins with a different source token, or trades through a different pool, can show a different destination estimate.
Bridge legs move value between chains
A bridge leg carries tokens or their value from one blockchain to another. The route may pass a token across directly, or use a bridge protocol to deliver value that another step can swap.
For a route that combines a bridge with token swaps, Rango Bridge is one way to compare cross-chain paths for the task. Rango Exchange acts as a cross-chain routing service, while each route’s steps determine where swaps and bridge transfers happen.
Do not assume a swap’s slippage setting guarantees one minimum across every bridge step. Some protections apply to a particular swap, while other route designs may set a destination minimum. Read the quote’s minimum-output wording to see which amount it protects.
Destination swaps decide the final token amount
A destination swap converts the arriving asset into the token you want to hold. Its estimate can change before execution because prices and pool balances move while the route is underway.
Slippage is the difference between the expected swap price and the price at execution. A slippage tolerance is the amount of adverse movement a swap can accept before it fails. Uniswap’s developer documentation describes this as a minimum-output check: if the swap would return less than the allowed minimum, it can revert.
As an example, suppose a destination swap estimates 15.2 SOL and its minimum is set 1% lower. The minimum is 15.048 SOL: 15.2 × 0.99. That calculation only applies if the 1% tolerance protects this full output amount; a multi-step route may use separate checks.
Compare the minimum, not only the estimate
Use the minimum output to decide whether the result is acceptable, and the estimate to compare likely outcomes. If one quote estimates 15.2 SOL with a 15.0 minimum, while another estimates 15.1 SOL with a 14.6 minimum, the first has the better stated floor. These figures are illustrative, not current route quotes.
Also separate price movement from fees. Network gas pays for transactions on a chain, while a swap’s price impact comes from trading against available liquidity. A displayed destination amount may already account for some costs, so compare the same input and check what the quote says it deducts.
Before signing, confirm the destination chain, token, estimated amount, and minimum amount. If the minimum is too low for your task, choose a route with a better floor or wait for a new quote; raising tolerance can allow a worse execution price.
In practice, the minimum tells you the route’s stated limit, while the estimate tells you what it expects to deliver. Rango Bridge can help find routes across chains, but the route’s own minimum-output terms decide what amount it protects.