Why Cross-Chain Swaps Wait for Deposit Confirmations

A cross-chain swap waits for deposit confirmations so the service can check that your funds reached the source chain before it routes the trade or sends assets elsewhere. A wallet may show that a transaction was sent, but that does not mean the swap service can safely act on it yet.

Why does a swap need deposit confirmations?

A confirmation means a transaction has been included in a block, a batch of recorded transactions on a blockchain. Each new block after it adds another confirmation. Services wait because a transaction that looks settled can still be replaced if the chain reorganizes, or briefly changes which blocks it treats as valid.

Waiting lowers the chance that a service releases destination funds for a deposit that later disappears from the source chain. The trade-off is time: block intervals and network delays differ, so there is no single wait that fits every chain. A fuller walkthrough of routing and verification appears in thor swap.

What happens after the deposit is confirmed?

Once the service accepts the deposit, it can arrange the exchange and destination payout. A route may use one or more liquidity pools, which hold assets for trades. Some systems use a relayer, a service that carries messages or submits transactions between chains. The destination transaction then needs to be recorded on its own chain.

That makes a cross-chain swap a sequence of steps, rather than one transaction that moves between networks. A delay can happen while the source deposit gains confirmations, while the trade is arranged, or while the payout waits for destination-chain inclusion. A status page or transaction record may show which stage is pending.

What should you check while you wait?

Use the deposit details supplied for that swap and check the transaction on the source chain. The transaction hash is its public identifier. Match the asset and network, since the same token name can exist on different chains. Then check whether the service has detected the deposit and whether it is still waiting for confirmations.

• Compare the deposit address and network with the swap instructions before sending.
• Keep the transaction hash so you can check whether the source chain recorded the transfer.
• Wait for the service’s status to update before sending again; a second deposit may create a separate swap.

The confirmation wait is a security step, not a promise of a fixed arrival time. For most readers, the useful measure is the service’s stated status and the source-chain record, rather than the wallet’s initial “sent” message.