Why Bridge Slippage Changes the Amount You Receive
Bridge slippage is the gap between a route’s quoted output and what arrives after execution; understand the quote, minimum received and timing before you approve.
Merkle Street Newsroom#e566c03 min read
Bridge slippage is the difference between the amount a route quotes and the amount that arrives when its transactions execute. First, the bridge estimates a route from the asset and network you choose. If that route includes a swap, a liquidity pool or order book sets an expected exchange rate. You approve the transfer, the source network processes it, and the route completes its destination-side steps. Each step takes time, so the market or available liquidity can change before the swap fills. The baseswap explainer traces what confirms a transfer before destination tokens arrive, a separate step from pricing the swap.
What causes slippage on a bridge?
Slippage usually comes from a swap in the route, not from moving tokens between networks by itself. A bridge may lock an asset on one network and release or mint a corresponding asset on another. That transfer can have fees and a wait, but it does not necessarily involve a market trade. Other routes exchange the asset before or after the transfer, and that trade can produce a different output from the quote.
Liquidity affects the fill. A larger trade can move through several pool price levels, so each unit costs slightly more than the one before it. A thin order book can also have too few orders at the quoted price. Network delays add uncertainty: the quote may be based on conditions that have changed by the time the swap executes. The bridge fee, network fee and slippage are separate costs, even when the interface presents them together.
What does minimum received mean?
Minimum received is the lowest output the swap is allowed to deliver under the settings you approve. The interface uses the quote to calculate that floor from your slippage tolerance. If the actual output falls below the floor, the swap may fail or revert; the precise result depends on the route and its contracts. If the output stays above it, execution can complete at a worse rate than the original quote.
Think of the quote as a price on a board and the minimum as the lowest price you have agreed to accept. A wider gap gives the route more room to execute as conditions move, but also permits a less favorable fill. A narrower gap limits that trade-off, while making a delay or price move more likely to stop the swap. The setting does not make the route faster or guarantee the quoted amount.
How can you judge a bridge quote?
Read the route and the expected output before confirming. Check whether it contains a swap, what asset will arrive, and whether the displayed amount is before or after fees. Then compare the quote with the minimum received and consider whether the tolerance leaves more room than you intend. For a transfer with no swap, focus on the bridge’s stated fees, destination asset and confirmation process instead of treating every difference as slippage.
- Confirm the source and destination networks, plus the exact assets being exchanged.
- Separate the bridge fee and network fees from the estimated swap output.
- Check the minimum received and the tolerance that sets it.
- If the quote changes or the route is unclear, pause and request a fresh quote before approving.
For occasional users, the better choice is usually the route whose steps and minimum output are easiest to understand, even if its quoted amount is not the highest. A quote is an estimate; the minimum received defines the boundary you accept.