How cBridge Works: Deposit, Validation, and Delivery

How cBridge Works: Deposit, Validation, and Delivery


cBridge moves value when State Guardian Network validators observe and sign a source-chain deposit, then a separate destination-chain transaction releases tokens from an xLiquidity pool or mints an xAsset pegged token; no asset physically crosses chains.

A Signed Deposit Determines Destination Delivery

The signed source event authorizes a destination contract to pay or mint for the recorded recipient. The Celer bridge uses two models based on where destination value comes from. In cBridge, xLiquidity draws on pooled tokens, while xAsset creates a pegged token against locked supply.

  • Source contract: records the deposit or lock.
  • State Guardian Network (SGN): observes, agrees on and signs the event.
  • Destination contract: verifies the attestation and pays or mints.

A relayer submits the SGN’s signed instruction on the destination chain. The SGN is a proof-of-stake validator network backed by staked CELR. Its attestation links the source event to the destination transaction.

In xLiquidity, the user deposits into the source liquidity pool and liquidity providers’ funds in the destination pool pay the recipient. Available destination pool depth caps what can settle: a transfer larger than that liquidity cannot be paid out. Pool imbalance can change the bridge rate, so compare the quoted receipt with the deposited amount.

In xAsset, the original token is locked in a source vault and a pegged token is minted on the destination chain. Say a supported route starts with a token native to Ethereum: the original stays in its Ethereum vault while a mapped token reaches the recipient. Returning it to Ethereum burns the pegged units and releases the original. Verify the destination token contract, not just its ticker. Celer describes both models in its bridging architecture.

Delivery is a separate destination-chain transaction. A confirmed source hash proves deposit, not payout. Between the two, SGN validators must observe the source event, reach consensus and sign; a relayer then submits that attestation for destination execution. This intermediate state explains why a confirmed send can coexist with an unchanged destination balance.

Use cBridge’s transfer history to follow that gap. Read the transfer status and destination transaction hash, then inspect that hash on the destination chain. Without a destination hash, determine whether validator confirmation, fund release or refund is pending. If delivery is recorded but the balance looks empty, verify the recipient and token contract; an xAsset mint may appear under a different contract.

MessageBus applies SGN attestation to arbitrary cross-chain messages for dapps: a source message is signed, relayed and checked before destination logic runs. For an asset route, identify the model first, then weigh destination liquidity or pegged-token exposure alongside validator risk.

Questions That Affect a Transfer

What Happens If SGN Validators Sign a Wrong Event?

A false attestation accepted on the destination could authorize an improper release or mint. Staked CELR creates an economic penalty for validator misconduct, but a penalty cannot reverse a completed payout. Celer also describes a delayed mode that lets a guardian challenge a bad message before execution; whether it applies depends on the route’s configuration.

How Do Fees Split Between LPs and Validators?

In xLiquidity, the protocol fee compensates both liquidity providers whose funds pay the recipient and SGN participants who validate the transfer. In xAsset, no destination LP supplies the minted token, so its protocol fee compensates SGN participants. A separate base component covers destination gas. Compare a route’s quoted net receipt when judging its cost.

Can I Bridge to a Different Recipient Address?

Yes, when the route accepts a separate receiver. The recipient is encoded in the source transfer instruction, so verify the destination address before signing. Once confirmed, the transfer targets that recorded address; changing it requires a new transfer.

How Does cBridge Compare With Across or Stargate Finance?

Across uses relayers to front destination funds and optimistic verification for later settlement. Stargate Finance uses liquidity pools with LayerZero messaging. The Celer bridge uses pooled release or pegged minting under SGN attestations. Compare token contracts, destination liquidity, net receipt and verification for the route you need.

Report Page