defi-blog

How to use Celer cBridge for an EVM token transfer

cBridge moves tokens between EVM chains: connect a wallet, choose the source and destination chains, token, and amount, approve the token, confirm the transfer, and wait for Completed before checking the destination balance. Use cBridge to move a supported asset and get a quote for the Celer bridge route you choose. State Guardian Network validators attest to the source-chain deposit so the destination contract can release or mint the tokens.

Run a cBridge transfer and read the quote

Have an EVM wallet, the token on your source chain, and enough of that chain’s native token to pay for approval and transfer transactions. Know which token you need to receive: the route determines whether you get a token already held in a destination pool or a pegged token minted there.

  1. Connect your wallet. Confirm that it shows the address holding the source-chain tokens; this is also the address that will receive them on the destination chain.
  2. Select the source chain, destination chain, token, and amount. A route and estimated received amount should appear. Confirm the destination token’s identity before treating the quote as interchangeable with another bridge route.
  3. Review estimated received, the base and protocol fees, the bridge rate, and slippage tolerance. The received estimate already deducts both fees; on a pool route, the bridge rate can also change the token amount. Requote if you change the amount.
  4. Approve the token for spending and confirm that transaction in your wallet. Once the approval succeeds, the token can be used for this transfer. An existing sufficient approval may let you proceed without another approval transaction.
  5. Confirm the transfer in the app and sign the source-chain transaction in your wallet. Its transaction hash shows that you submitted the deposit; it does not yet mean the destination payment has arrived.
  6. Watch History until the transfer shows Completed, then switch your wallet to the destination chain. The task is done when its token balance shows the received amount. If Completed appears first, make sure the destination token is added to your wallet’s token display.

Route type changes what you receive. xLiquidity uses pooled liquidity on both chains: your source-chain deposit is matched by a payout of the destination chain’s token. xAsset locks the source token and mints a pegged token on the destination chain. A pegged token may require a different exit route from the token you expected to use in DeFi, so compare token identities as well as quoted amounts. Celer’s model description explains the distinction.

Destination liquidity sets the practical size of an xLiquidity transfer. Say, illustratively, you want to move 1,500 units while the destination pool can release only 1,000. The larger transfer can be rejected; a pool imbalance can also worsen the bridge rate or protocol fee. Try a smaller amount and read its new estimate. Split the transfer only when each part has an acceptable quote and liquidity is available for it; splitting cannot create missing pool funds. For the remainder, wait for liquidity or compare an available xAsset or canonical route.

For an Arbitrum-to-Ethereum withdrawal, the Celer bridge can deliver through its route in minutes, while the canonical optimistic-rollup withdrawal has a roughly seven-day challenge period before claiming on Ethereum. That speed adds reliance on State Guardian Network attestations and, for xLiquidity, destination liquidity. Arbitrum’s withdrawal explanation describes the canonical wait.

How long does a cbridge transfer take?

A Celer bridge transfer commonly takes minutes after the source transaction confirms, but chain confirmations, State Guardian Network processing, and destination release affect the actual time. Use the transfer status for your transaction. If it remains at an SGN confirmation or fund-release stage, keep the source transaction hash so you can distinguish a pending transfer from one that requires a refund.

Cbridge slippage tolerance setting

Slippage tolerance sets how far an xLiquidity route’s execution may move from its quoted rate. A tight setting protects the minimum received amount but can cause the transfer to fail when the pool rate changes. Celer’s transfer instructions describe 0.1% to 0.5% as a usual range. Read the minimum received amount before signing; increasing tolerance permits a worse payout.

Once the destination balance appears, compare the amount and token contract with the quote you accepted. That gives you a usable reference for deciding whether to repeat the route.

Questions to consider before another transfer

Is cBridge safe to use for large transfers?

For a large transfer, assess the route’s token identity, current pool depth, quoted minimum received, and the State Guardian Network trust assumption before signing. A small test transfer can verify that your wallet receives the intended asset. Requote the larger amount afterward: its rate and available liquidity may differ from the test.

How do I add liquidity to a cBridge pool?

To add xLiquidity pool liquidity, supply a supported token on a supported chain and approve its deposit into the pool. The position can earn a share of transfer fees, while transfers can shift where your liquidity sits across chains. Review the pool’s current terms and the effect of an imbalance before depositing; supplying liquidity is a separate decision from making one transfer.