Jump to content
Chain Times

Markets, protocols, policy and people

cBridge Pool Transfers and Destination Liquidity

When a bridge pool does not have enough liquidity, cBridge blocks the quote or refunds a transfer it cannot pay from the destination pool in full.

The Chain Times Desk3 min read

cBridge Pool Transfers and Destination Liquidity

A cBridge pool transfer is usually blocked before you send when the destination pool cannot cover it; if liquidity drops after you deposit, the transfer is refunded on the source chain. The payout comes from tokens already held in the destination pool, so the transfer is paid in full or refunded.

What happens when destination liquidity is short?

With xLiquidity, tokens are paid out from a liquidity pool on the destination network. The pool must hold enough of the requested asset when the payout is due. The cBridge documentation says a transfer that cannot be relayed is marked for a source-chain refund.

The usual sign of a shortfall is an error in the quote, which blocks the send. For a wider view of the route and its pool payouts, read cbridge cross-chain; that context helps explain how cBridge moves assets between networks.

A pool transfer does not pay out part of the amount and leave the rest waiting. It also does not sit in a queue until liquidity returns. The outcome is all or nothing: a full payout from available destination liquidity, or a refund on the source chain if the transfer cannot be relayed.

This is why the quote is useful but not a guarantee that the pool will still have the same balance later. Other transfers can draw tokens from the pool. Liquidity providers can also withdraw tokens. Either can reduce the balance between your quote and the payout.

What does a shortfall look like in practice?

Say you want to send 10,000 USDC from Ethereum to an Arbitrum pool holding 6,000 USDC. At quote time, the pool cannot cover the requested amount, so the quote returns an error and the send is blocked. You do not get a partial 6,000 USDC payout.

Now suppose the pool had enough liquidity when you quoted, but other transfers or LP withdrawals reduced it before your payout. If the transfer can no longer be relayed, it becomes a refund on the source chain. The refund is claimed there; it is not a delayed payout from Arbitrum.

In everyday use, this matters when choosing an amount for a pool-based route between networks such as Ethereum and Arbitrum. A smaller amount may fit the available pool. If it does not, consider a mint-based route where one is available. For a pool transfer, expect either the full payout or a source-chain refund, then choose a smaller amount or another route.

More stories

  1. 01DBS and Circle open 24/7 USDC access for Asian institutions
  2. 02Is bridging crypto between networks a taxable event? Swap cases
  3. 03ETH for DEX Token Swaps: How Gas Works
  4. 04Token Approval Revocation: Checking the Allowance