Where Your Crypto Goes During a Cross-Chain Swap

A cross-chain swap takes your crypto from one blockchain, routes it through a protocol’s settlement and liquidity system, then sends the bought asset to an address on another chain. You authorize the source-chain transaction and pay its network fee; the swap service handles the conversion and destination transfer according to its own design.

What happens after you send the crypto?

First, the swap request records the source asset, destination asset and recipient address. Some services give you a deposit address; others ask you to approve a contract or call one directly. Chainflip’s protocol documentation, for example, describes deposit channels that tell its network what to do with incoming funds.

After you send the asset, the protocol waits for enough source-chain confirmations to treat the deposit as valid. It then trades against available liquidity and arranges a transaction on the destination chain. The source and destination transactions are separate: the swap can be underway even while the recipient chain has not yet confirmed delivery.

Execution options affect the trade-off between speed and price. For a closer look at Chainflip Standard, Boost and DCA trade-offs, see the comparison of when each mode fits. In Chainflip’s documentation, Boost can use liquidity-provider collateral to start a swap before the usual deposit confirmation wait is over, while DCA divides an order into smaller trades over time.

Does a cross-chain swap use a bridge?

Sometimes, but “cross-chain swap” describes the outcome, not one fixed mechanism. A bridge route may lock or burn an asset on the source chain and issue a representation on the destination chain; a liquidity-based route can instead pay out an asset already available on the destination side. The route determines whether you receive a native token or a wrapped representation.

That distinction affects what you can do with the output. A wrapped token depends on the bridge or issuer’s redemption process, while a native asset is recorded directly on its own chain. Check the asset name and network shown in the quote: matching tickers do not guarantee that two tokens are the same asset.

What fees and delays should you expect?

You may pay a source-chain fee, a swap or liquidity fee, and a destination-chain fee; the quote should show which costs are included. The final amount can also differ from the estimate if the market moves before execution or the route applies slippage limits. Smaller pools and large orders can have a greater effect on the execution price.

Timing depends on both chains’ confirmation rules, the protocol’s processing and the destination transaction. If a deposit arrives but the swap cannot meet its stated price limits, the protocol’s rules determine whether it waits, partially fills or returns funds; check those rules before sending. A refund, where available, may still require another transaction and network fee.

What should you check before sending?

Before confirming, compare the quote’s minimum output and recipient address with your intended trade. Then check these details:

• Source and destination networks, including the exact token contract where relevant.
• Minimum output or slippage limit, and whether the quote can expire.
• All listed fees and whether the recipient chain’s fee is already deducted.
• What the service says happens if the swap fails or only partly executes.

Once the source transaction is confirmed, follow its status through processing and destination-chain confirmation. Verify the received token and network in your wallet or a destination-chain explorer before using the funds.