Swap between chains

Start a cross-chain swap

1. Under You pay, pick the network and token you send.
2. Under You receive, pick a different network and the token you want.
3. Type an amount.

Cleave can swap on either side, so the tokens do not need to match. The bridged token can be USDC, USDT, WETH or WBTC, depending on the route.

Choose a route

When more than one route can carry your trade, Choose a bridge lists them. Each card shows:

• the route's time, with may take longer when it can run slower
• the amount you receive
• how it is delivered (see below)
• price impact, when the quote reports it

Tap Details on a card for the full picture:

Cleave's fees are inside the amount you receive. Some routes also show the smallest or largest amount they can carry.

Delivery

Each route says how your tokens reach the destination:

• Delivery included or Free delivery: tokens arrive with nothing more to do.
• You'll claim on the destination: you finish there yourself. The card shows about how long it takes and the gas you pay there.
• Connect to get delivery: connect a wallet to see the delivery option.

Some routes let you pick between Delivery included and claiming yourself.

Free delivery needs a quick human check before it is arranged. Paid delivery does not.

Delivery fee

When delivery has a fee, choose where it comes from:

• Take from amount: the fee comes out of what you send.
• Add from wallet: you send a little more, so the amount you typed is sent in full. This needs enough of the token in your wallet.

Timing

The route card shows the expected time before you send. After you send, the transfer shows its stage and about how many minutes are left:

1. Sending on the source network
2. Sent
3. Bridging
4. Received on the destination, or Claim on the destination

If a transfer runs slower than usual, it says so.

If the swap on arrival can't run

When the route swaps again on the destination, Review shows an extra line: what you get if that swap stops, as If the swap stops: at least … with an amount of the bridged token. That token is USDC, USDT, WETH or WBTC, depending on the route.

If it happens, the recipient gets the bridged token instead. The transfer shows how much arrived, and Now swap opens the swap from that token to the one you wanted on the destination network.

On some routes the bridged token is held for the recipient on the destination instead. Activity then shows Release, which sends it to the recipient's address. See Activity.

When a route needs two steps

Some pairs cannot cross in one go. Cleave then offers two steps:

1. Send to USDC on the destination network.
2. Swap USDC to your token there.

When a token cannot arrive at all, the swap button can offer Get USDC instead.

Part of the amount bridges

A route can carry less than you typed. Review then says Only x will bridge and the rest returns to you on the source network, in the token you paid or as the native coin.

Native coins

You can pay with a network's native coin directly, with no wrapping. You can also receive the native coin on arrival. A route that delivers the native coin instead of its wrapped token says so before you send.

Recipients on another chain

You can send to another address on the destination. Cleave checks it on both networks:

• If the address is a contract on the source network but not on the destination, as a smart account or multisig wallet often is, Cleave stops. Tick I control it on the destination only if you can use that address there.
• When the native coin arrives, Cleave checks that the address can receive it.

If it does not arrive

If no bridge fills the transfer before it expires, the refund goes back to the sender on the source network. Timing varies, and some refunds need a claim on the source network. Track all of this, and claim, in Activity.