A delayed cross-chain swap is often waiting for a destination-chain step, so check the original transaction before trying again. A route may confirm the send, then wait for proof and destination execution; a service such as quickswap lets you move and swap assets across chains in one flow. The same checks apply whether you are moving ETH to Arbitrum One or swapping it there.
Keep these three checks in order:
- Did the source transaction confirm?
- Has the cross-chain message been created and delivered?
- Did the destination swap complete into the token you expected?
1. Did the source transaction confirm?
First, look up the transaction on the explorer for the chain you sent from. An explorer is a public page that shows a transaction’s status. “Pending” means the chain has not finished processing it; “failed” means the send did not complete. If it is still pending, wait. Do not start a second swap with the same funds.
A confirmed send only proves that the source chain accepted the first step. It does not prove the other chain has received the assets. For a quickswap route, keep the source transaction hash—the unique transaction ID—so you can distinguish a slow transfer from one that never started.
2. Has the message reached the destination?
After the source transaction confirms, a bridge may need to pass proof of that event to the destination chain. For example, Wormhole uses a signed message called a VAA; its Guardians verify the source event, and the message must then be submitted on the destination chain to complete the transfer. Wormhole’s VAA documentation explains this sequence.
This separate step is why a successful source transaction can sit without a destination balance. Check the route’s transaction status using the original hash. If it says the message is ready but not completed, follow the originating service’s recovery instructions. Do not paste a recovery phrase into a site or pay someone who contacts you privately.
3. Did the destination swap finish?
Check the destination chain’s explorer and your wallet for the received token. A bridge transfer and a token swap can be separate actions: the assets may arrive, while the final exchange fails. For example, a route may deliver a bridge token but fail to trade it because the price moved beyond the allowed slippage—the maximum price change you accepted.
Check the destination transaction’s result and token address, since similarly named tokens can be different assets. If the bridge arrived but the swap failed, you may need to swap the received token separately. A quickswap cross-chain swap is useful when you want those two jobs handled in one route; still, verify the final token and amount on the destination chain. A practical tip: save the source transaction hash until you have confirmed the expected asset arrived.
Top comments (0)