Skip to main content
Chain Media

Protocols, chains and markets, reported

cBridge Chain Support and Its Live Transfer List

Which chains does cBridge support? It connects major networks including Ethereum, Arbitrum, Optimism, BNB Chain, Polygon and Avalanche; the live list changes.

The Chain Media Editors5 min read

cBridge Chain Support and Its Live Transfer List

cBridge connects dozens of mostly EVM networks, including Ethereum, Arbitrum, Optimism, BNB Chain, Polygon and Avalanche, when each network is currently enabled for transfers. For a transfer you are planning now, open cBridge to check the source and destination in its current chain selector. Celer bridge support changes as liquidity and demand shift, so a saved list can go stale.

Which chains does cBridge support?

cBridge supports major EVM networks, with availability determined by the live transfer configuration. Commonly named networks include:

  • Ethereum
  • Arbitrum and Optimism
  • BNB Chain and Polygon
  • Avalanche

These names describe broad coverage, not a guarantee that every route between them is active at the moment you need it. A chain can be supported while a particular token or transfer direction is unavailable. The transfer also depends on the relevant token mapping or pooled liquidity for that route.

The Celer bridge uses pooled liquidity for some transfers and token mappings for others. Those mechanisms affect which assets can move between which networks; the chain name alone does not settle whether your intended transfer is available. Confirm both the source and destination, then verify the specific asset.

How can I check whether cBridge supports a chain now?

The transfer-config API gives the live chain and token configuration; the app’s chain selector shows the chains currently enabled there. Use those current records instead of relying on an older article or remembered network list.

The API response includes supported chain information and a token list for each chain. That makes it useful when you need to check a chain programmatically or compare current token coverage across networks. The Celer documentation describes this endpoint as the source for chains and corresponding tokens supported by the bridge. DefiLlama’s Bridges dashboard can provide another view of cBridge chain coverage, but the transfer configuration is the more direct check for whether a route is enabled now.

Say you want to move an asset from Ethereum to Arbitrum. Confirm that both networks appear in the current configuration, then look up the asset on each side and verify that the intended direction is available. A chain appearing in a broad coverage list is not enough to establish that a specific token transfer will work.

What happens when cBridge retires a chain?

A retired chain disappears from the current chain selector, while records of completed transfers remain viewable in History. That distinction matters when you are checking an old transaction: past activity can still be accessible even when the chain is no longer offered for a new transfer.

Network support can change as liquidity and demand shift. A saved list may therefore include a chain that is no longer enabled, or omit one added since the list was written. When a network vanishes from the selector, treat that as a sign to recheck the current configuration rather than assume that a previous route is still available.

For an in-progress or completed transfer, use the transaction record to follow that transfer’s status. For a new transfer, check current chain and token availability again before submitting it. Those are separate checks: History helps you review past activity, while the live selector and configuration answer whether you can start a supported transfer now.

What tokens can I bridge with cbridge?

The tokens available through cBridge depend on the token list for the selected chain and the route you intend to use. The API returns token information by chain, so check the asset on both ends rather than assuming that a familiar ticker represents the same supported transfer everywhere.

Token mappings can connect an original asset with a corresponding token on another network. A pooled-liquidity route instead depends on available liquidity for that asset and direction. These are different ways to facilitate a cross-chain transfer; neither means that every token on a supported chain can be bridged to every other chain.

Before acting, match the token and network in your wallet to the entries in the live configuration. Confirm that transfers are enabled for the token and that the destination route is available. If either side is missing or disabled, choose another supported route or wait until the configuration changes.

cbridge vs canonical bridge for layer 2

A canonical bridge is the bridge associated with a Layer 2 network’s own protocol, while the Celer bridge is a separate cross-chain option that uses its configured liquidity or token mappings. The practical difference is the route and mechanism your transfer relies on.

For a Layer 2 transfer, compare whether the specific asset and direction are supported, which bridge mechanism handles the transfer, and whether your wallet supports both networks. A canonical route and a third-party bridge can have different availability and requirements; the right fit depends on the transfer you need to make, not on a general ranking.

Your wallet must support the source and destination chains so you can select the correct network and interact with the transfer. Once the live list confirms both chains and the token, proceed only if the wallet can connect to the required networks. Use the current selector or transfer configuration to make that decision.