quickswap routes should be chosen by output asset, net quote, and settlement state. If an attempt to swap crypto across chains is pending, quickswap can handle the exchange and transfer in one flow once you know where your funds are. Check the existing transaction before sending anything again.
Which criteria decide the route?
Five checks decide whether a route delivers the asset you need on acceptable terms.
- Destination asset: Confirm its chain and token identity.
- Route mechanism: Identify who or what provides the destination liquidity.
- Net output: Compare the amount received after every fee and swap.
- Settlement time: Account for source finality and destination execution.
- Recovery path: Find out what happens if the destination leg fails.
A ticker alone is insufficient. “ETH” on Ethereum and ETH on Arbitrum One are usable on different networks; a token labelled “BTC” on an EVM chain is a representation, not native Bitcoin. Check the destination chain, token contract where applicable, and whether the recipient can use that version of the asset.
A same-chain swap uses liquidity on one network. A bridge moves value between networks, while a cross-chain swap also changes the asset. If you need to swap Bitcoin to Ethereum’s ETH on Arbitrum One, a transfer that delivers a BTC representation leaves you with another swap to make.
The mechanism sets the risks behind the quoted speed. A canonical bridge may lock or burn on the source and release or mint on the destination after verification; a liquidity route may pay from a destination pool and settle its inventory later. Check the route’s bridge or liquidity provider and any temporary asset it uses, especially for a large transfer.
Compare routes using the same input amount and recipient network. Record the quoted output, minimum received, estimated arrival time, and any separate destination transaction you must fund. A faster quote is less useful if its recipient gets the wrong token or cannot afford gas to use it.
Finally, read the failure terms before committing. Ask where value remains if the destination swap cannot execute: in a claimable destination asset, a refund on the source chain, or a pending message requiring execution. Those outcomes have different costs and may require access to different wallets.
What happens after you submit?
A cross-chain swap has separate source and destination events, so a confirmed send does not prove delivery. On an EVM source, approval may occur first; that transaction only authorizes spending. The subsequent swap or transfer consumes the asset and emits the event that the bridge or liquidity route tracks.
For a Bitcoin-to-Arbitrum example, the Bitcoin payment must enter a block and reach the route’s required confirmation depth. The route then verifies or accounts for that payment, sources ETH on Arbitrum One, and pays the specified recipient. A quote can appear to stall between those stages without either chain having failed.
The pricing rule matters during that wait. Determine whether the BTC-to-ETH rate is fixed when you accept the quote, when the Bitcoin deposit confirms, or when the destination trade executes. A long confirmation wait can change the delivered ETH if the route uses a floating rate; a fixed-rate route may instead have an expiry or deposit window.
What determines the amount you receive?
The useful comparison is destination value after trading costs, bridge charges, network fees, and price impact. Some quotes include destination gas and provider fees in the displayed output; others itemize them separately. Compare the final amount in the exact token and chain you need, rather than comparing headline exchange rates.
Slippage tolerance controls how far an execution price may move before a swap leg rejects it. For example, if a quoted 0.18 ETH output is already net of stated fees, a 0.5% tolerance implies 0.1791 ETH for that leg. It does not automatically guarantee the same floor across every stage of a multi-leg route; check which amount the minimum received field protects.
For quickswap, a 0.5% setting may suit a liquid pair, while thin pools can require more room and expose you to a worse fill. Raising tolerance to force a stuck trade through also increases the price you may pay. If the quote is poor, reduce the trade size or compare another route before changing the tolerance.
How long should settlement take?
Settlement time is the source confirmation period plus route verification and destination execution. Bitcoin targets roughly ten minutes per block, so a requirement of several confirmations can mean tens of minutes before the destination stage begins. Congestion, a low source fee, liquidity shortages, or a paused route can extend that estimate.
Direction changes the timing trade-off. An Arbitrum One withdrawal through its canonical bridge to Ethereum has a challenge period of at least seven days; a liquidity route can pay sooner if destination liquidity is available, with different fees and trust assumptions. When you move crypto between blockchains, compare the route’s stated timing with the mechanism it uses, not with the block time alone.
What should you do when a transfer is pending or failed?
Locate the last completed stage before retrying. Save the source transaction hash or Bitcoin transaction ID, the source and destination addresses, and any route or message ID. Check the source transaction in its own chain explorer first: an unconfirmed Bitcoin payment is a different problem from a confirmed payment awaiting destination execution.
If an EVM source transaction reverted, the assets generally remain in the wallet, although gas was spent; an approval that succeeded is not evidence that a transfer began. If the source transfer succeeded, sending a second one can create a second order. Trace the route or message status and the destination recipient’s balance before initiating another payment.
A confirmed source with no payout may still be waiting for finality, liquidity, or destination execution. Some messaging routes permit a failed destination execution to be retried after its cause, such as insufficient callback gas, is resolved; others provide a claim or refund process. Use the recovery path for the route that actually received the funds, and verify the asset and chain on which recovery pays out.
At quickswap.dev, you can start a fresh cross-chain exchange once the earlier transfer’s location is clear. If the earlier funds are already on the destination chain, use that confirmed balance as the starting point; if they are still committed to a pending route, resolve that route first.
- Confirm where the existing funds are and whether the source transfer succeeded.
- Choose the exact destination token and network, then compare net output and timing.
- Check the rate rule, minimum received, and recovery path before sending again.
Top comments (0)