Cross-Chain Swap Status: Verify Delivery Before Reusing Funds
If you need to know whether a cross-chain swap is complete, check that the destination chain records the output transaction and that it has reached the finality standard you require. A source-chain confirmation starts the process; it does not prove the other asset has arrived and is safe to use.
Which status proves the swap finished?
A swap is complete for practical purposes when the destination chain shows the output at the intended address and the transaction has enough confirmations or finality for your task. A transaction hash is the clearest evidence: open it in the destination chain’s explorer and verify its status, token or asset, recipient, and amount.
There are several steps between your deposit and that evidence: the source chain includes the deposit, the protocol’s validators witness it, the swap executes, and the output is broadcast and included on the destination chain. In Chainflip, for example, deposit witnessing and destination broadcast are distinct stages, so a “seen” or “in progress” state is not proof of delivery.
Confirmation means a transaction has been included in a block; more blocks can make a reorganization less likely. The Bitcoin Developer Guide explains this confirmation count, while Ethereum’s documentation describes proof-of-stake finality. The right threshold depends on the destination chain and what you plan to do: checking a wallet balance is different from sending a high-value payment onward.
What should I check if the output is missing?
Start with the source transaction hash and confirm that it succeeded on the correct network and sent the intended asset and amount. Then check the swap’s progress using its transaction or swap identifier, and look for a destination transaction hash. If one exists, inspect it on the destination chain rather than relying on a wallet’s token list to refresh.
A common mistake is to see the deposit confirmed and retry the swap because the destination balance has not changed. That can create a second payment. First verify the recipient address and destination network; then check whether the output is pending, confirmed, or sent to a different token contract. If no destination transaction appears, the protocol may still be processing the deposit or handling an exception.
One edge case is a swap split into chunks: some output may arrive while the remaining input is retried or refunded. Compare the destination transfer and any source-chain refund with the original amount before deciding the task is settled. Keep both transaction hashes until the full amount is accounted for.
Does a confirmed deposit mean I can use the funds?
No. It confirms the input on its own chain, but the swap still needs to execute and the output needs to land on the destination chain. Wait for the destination transaction, check its recipient and amount, and apply the confirmation or finality standard appropriate to your next action.
What should I save before closing the swap details?
Keep the source transaction hash, swap identifier, destination transaction hash, and the intended recipient address. These let you trace each stage across the source chain, protocol, and destination chain if a wallet balance is delayed or a partial refund occurs. Before reusing the funds, ask yourself: have I verified the final asset and amount at the correct destination address?