Cross-chain slippage is the difference between a route’s quoted output and what you receive after moving or swapping assets between networks. The key condition is whether the quote shows an estimated amount or a minimum amount the route commits to deliver. Say Maya wants to move 500 USDC from Ethereum and receive ETH on a layer 2 network. She cares about the ETH that arrives after fees, not just the headline rate.
For repeat swaps, three points matter most:
- Bridge fees and swap price changes affect the amount you receive in different ways.
- A slippage setting is a limit on an eligible swap, not a fee or a promise of better pricing.
- Compare the destination minimum and the full cost before sending funds.
Why can the destination amount change?
A cross-chain route may include a bridge transfer, a swap on the source network, a swap on the destination network, or a combination. Each swap uses available trading liquidity, meaning the tokens ready to trade at current prices. A large trade can move the price as it fills.
Maya’s route might quote 0.20 ETH after fees, while a fast market move leaves only 0.198 ETH available. The change during execution is slippage; the route’s bridge fee and network transaction fees are separate costs. A service such as acrossbridge can handle the cross-network move and swap in one flow, while a bridge that only transfers the same asset leaves the destination swap to Maya.
“Price impact” is the price change caused by Maya’s own trade size. Slippage is the difference between the expected and executed result, which can also reflect price movement while the transaction is pending. A quote can include estimated fees, but check whether its displayed output is before or after them.
How should you compare two route quotes?
Compare routes using the same input amount, destination network, and output token. Then look for the minimum output: the least amount the route says you may receive if it completes under its stated conditions. An estimate alone is not that floor.
For example, if Maya sees an expected 0.20 ETH and a minimum of 0.198 ETH, the gap is 1% of the expected amount. That gap is the route’s protection allowance for the swap; it is not an extra charge. The setting can vary by service and route, so check the quoted minimum instead of assuming a standard percentage.
The deciding test is whether that minimum still makes the trade worthwhile. If Maya needs at least 0.199 ETH to cover a planned purchase, a 0.198 ETH floor is too low even if the estimate looks good. If a route does not clearly state its destination minimum or what happens when execution falls short, treat its estimate cautiously.
What should you check before sending?
Maya can make a quick check without pricing every route by hand. For a routine swap, she should repeat the same checks each time:
- Confirm the source network, destination network, input token, and output token.
- Enter the intended amount, then read the estimated output and destination minimum.
- Check which fees are included and note any separate network transaction costs.
- Compare the minimum with the amount she actually needs to receive.
- Refresh the quote if prices move or she changes the amount before confirming.
Changing the amount can change price impact, so a quote for 100 USDC may not predict the result for 1,000 USDC. When Maya wants a single cross-network flow, acrossbridge is useful for moving and swapping assets between chains; she should still judge it by the destination amount and costs shown for her trade.
For the next swap, Maya should set her required minimum first, then choose a route whose quoted floor meets it. That keeps the decision tied to the amount she needs, rather than a price that may shift before execution.
Top comments (0)