Your final token amount can differ from the quote if prices move before the swap executes, and the amount you actually receive depends on the route’s minimum-output rules. From a centralised exchange, it may feel familiar to compare a quoted price with the fill; from your own wallet, the important difference is that a cross-chain swap can involve separate transactions on two networks.
A quote is an estimate, while a minimum is a limit
A quote estimates what the route can deliver at that moment; a minimum received amount sets the least the swap is allowed to deliver under its stated conditions. Slippage is the difference between the expected and executed price as the market or available liquidity changes before execution. Price impact is the effect your trade has on the pool price as it uses available liquidity.
For example, suppose a route quotes 100 destination tokens and the applicable minimum is 99. If the swap would produce only 98.7 when its protected swap step executes, that step should fail instead of completing below the limit. The 1.3-token difference is not automatically a fee: it may reflect a changed price, and the minimum does not necessarily protect every part of a multi-chain route equally.
Read the quote’s terms to see which leg the minimum covers. A route may swap on the source chain, transfer value across chains, then swap again on the destination chain; the slippage setting can apply to one swap leg or be represented by a route-level output guarantee. The route’s actual rules decide which.
Each chain adds a separate execution stage
A cross-chain swap progresses through distinct stages, so “submitted” does not mean the destination trade has finished. First, your wallet signs and sends a transaction on the source network. After that transaction is accepted, a bridge mechanism communicates the transfer to the destination network, where the assets can be delivered or used in a swap.
Wormhole’s documentation describes one example of this mechanism: tokens may be locked or burned on the sending chain, a message proves that action, and the destination chain uses the message to mint or release tokens. Other routes work differently, but the general point holds: the source transaction and destination execution are separate events, each with its own wait and possible failure.
That matters when swapping, say, USDC on Arbitrum One into SOL on Solana. quickswap bridge lets you move and exchange assets across chains in one flow, so you do not have to arrange a separate bridge transfer and destination swap yourself. The quote still depends on the route’s execution conditions, so check what amount is estimated and what amount is protected.
Recalculate the amount you can expect
Use the destination amount and the stated minimum to judge the trade, not the source amount alone. For a quote of 100 tokens with a 1% minimum-output tolerance, the arithmetic is 100 × (1 − 0.01) = 99 tokens. If the route also lists a destination conversion or other deduction, account for it according to the quote’s terms; do not assume the 99-token floor covers a separate step.
Then compare the result with the alternative of bridging first and swapping later. Include the source transaction fee, any bridge or relay cost shown in the quote, the destination swap price, and the destination network fee if you need to transact again. The single-flow option can save you from coordinating separate actions, while a two-step route can give you more control over when and where the final swap occurs.
Network congestion can change timing and fees, and a slow transfer can leave the market price different by the time the destination step runs. Ethereum.org explains that wallet transactions are broadcast and wait for network inclusion; Wormhole’s transfer-flow documentation shows why cross-chain delivery adds message processing after the source action. These are reasons to treat a quote as time-sensitive, not as a guaranteed fill price.
Check the transaction state before trying again
If the wallet says pending, look up the source transaction hash in that chain’s explorer and confirm whether it is pending, successful, or reverted. A pending source transaction has not yet established that the transfer started; a successful one may still be waiting for destination processing. Do not submit a second swap just because the destination balance has not changed yet.
If the source transaction succeeded but the destination amount has not arrived, use the transaction status or route-specific tracking information available to you and allow for the route’s processing time. The recovery action depends on the bridge and route: a destination swap may fail while transferred funds remain recoverable, or a route may require a separate completion step. Do not assume a failed destination leg means the source funds vanished or that they were automatically returned.
When the destination transaction completes, check the destination wallet and token before trading again. For quickswap users, this distinction is practical: the service coordinates movement and exchange in one flow, while the wallet and network records show whether each on-chain stage actually completed. A confirmed source transaction alone is not proof of a completed cross-chain swap.
Questions to check before you send
Can I change slippage after a transaction is sent?
Usually, changing a quote setting does not alter a transaction already signed and broadcast. Check the transaction state first. If it is still pending, wallet options to speed up or replace it depend on the chain and wallet; once confirmed, the on-chain action cannot simply be edited. A route’s destination processing may also have its own conditions.
Does a higher slippage setting guarantee the quoted amount?
No. A higher tolerance generally allows a swap step to execute despite a larger price move, but it can also permit a worse fill. It does not freeze the market price or necessarily cover every stage of a cross-chain route. Compare the minimum received amount and the route’s stated scope before accepting a more permissive setting.
What should I do if the destination token is missing?
Check the source transaction hash and its status in the source-chain explorer, then check the route’s destination status. A successful source transaction can precede delivery while the cross-chain message is processed. Follow the route’s stated recovery method if destination completion fails, and avoid sending the same amount again until you know the first transfer’s state.