Skip to the article
Chainvane

Crypto markets, protocols and policy

Cross-chain swaps: how one trade moves between chains

How do cross-chain swaps work? Your token moves through a source-chain swap, a bridge or messaging step, and a destination-chain swap in one signed flow.

The Chainvane Desk5 min read

Cross-chain swaps: how one trade moves between chains

A cross-chain swap trades your token on its source chain, carries a bridgeable asset across chains, then trades it for the target token on the destination chain, with one signature when the route supports it.

What happens during a cross-chain swap?

A cross-chain swap has three stages: a source-chain swap, a bridge or messaging step, and a destination-chain swap. You start with a token in your wallet on chain A and end with a different token in your wallet on chain B.

The two blockchains cannot read each other directly. A bridge or messaging protocol relays proof that an action happened, or uses liquidity to make the corresponding funds available on the destination chain. The exact mechanism depends on the route.

A route may swap your starting token into an asset the bridge can move, transfer that asset across, then swap it into your target token. KyberSwap Cross-chain Swap routes swaps between supported networks such as Arbitrum and Base. Its quote brings the route’s swaps, bridge fee, and gas together, so the amount you receive is generally lower than a single-chain swap would return from the same starting amount.

That route is different from swapping on one chain and bridging separately: the cross-chain route coordinates both swaps and the transfer as one flow. If you provide liquidity instead of swapping, impermanent loss changes how you compare an LP position with simply holding the same tokens as their prices move. KyberSwap is an aggregator for finding swap routes across supported liquidity sources; the swap route and the risks of supplying liquidity are separate decisions.

Bridges use different ways to make funds available across chains. A lock-and-release bridge locks tokens on the source chain and releases corresponding tokens on the destination. A burn-and-mint route destroys tokens on the source and creates the same amount on the destination. Circle CCTP, for instance, burns USDC on the source chain and mints the same amount on the destination. A liquidity-based bridge can instead pay out from its own destination-chain liquidity.

Take USDC on Arbitrum and ETH on Base. Illustrative example: before the swap, your wallet holds USDC on Arbitrum and no ETH on Base. You choose the destination token and network, review the quoted amount and fees, and sign the source-chain transaction. After the route completes, the USDC has been spent and ETH has arrived on Base. The tokens and their networks changed; your wallet address can stay the same because the destination leg sends the output to that address.

The source transaction can confirm while the destination leg is still pending. That means a confirmed source transaction is not, by itself, proof that the full swap has finished. Track the route using its source transaction hash and watch for the destination transaction or completed status. The total time depends on source-chain finality and the bridge, so it can take seconds or many minutes.

People use cross-chain swaps to reach a token or application on another network without manually arranging each leg. For instance, a trader with USDC on Arbitrum can route toward ETH on Base, where they want to use that asset. The convenience comes with trade-offs: fees across both chains, the route’s exchange rates, and waiting for the bridge or messaging step. Before signing, compare the quoted output with what you need on the destination chain.

Related

Are cross-chain bridges safe?

Bridge safety depends on the route’s contracts, verification or messaging design, and liquidity arrangements. A lock-and-release bridge, a burn-and-mint system such as Circle CCTP, and a bridge that pays from its own liquidity rely on different mechanisms. A quote does not remove those risks. Check which bridge or messaging route the swap uses, and avoid committing funds you cannot afford to have delayed or exposed to a route failure.

How long does a cross-chain swap take?

A cross-chain swap can take seconds or many minutes, depending on source-chain finality and the bridge. The source transaction may confirm first, with the destination swap still pending. Keep the source transaction hash so you can follow the transfer and confirm when the target token reaches your wallet.

Before signing, check the destination network, target token, quoted output, and status tracking method; after signing, follow the source hash until the destination leg completes.

What should you know before using a cross-chain swap?

What happens if a cross-chain swap gets stuck?

A stuck swap means the source transaction may have confirmed while a later bridge or destination step has not completed. Use the source transaction hash in the swap interface or the relevant chain explorer to check its status. Follow the route’s stated recovery or support steps before retrying: submitting a second swap can spend additional funds.

Do I need gas on the destination chain?

You generally need gas on the source chain to sign and submit the swap. The route may account for destination-chain gas in its fees, but you may still need the destination chain’s native token for later transactions there. Check the quote and keep some destination gas if you plan to use the received token immediately.

Can I swap to a different wallet address on another chain?

Some routes let you specify a destination address, while others send to the connected wallet address. Before signing, check the recipient field and confirm that the address can receive the target token on the destination chain. In the illustrative Arbitrum-to-Base example, changing the recipient would change where the ETH arrives; the source USDC and route would otherwise be the same.