0
0

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?

Which bridge categories does cBridge fit: pools or pegged tokens?

0
Posted at

For a bridge comparison table, cBridge belongs in both the liquidity-pool and lock-and-mint pegged categories, with transfers verified by an external staked validator set. The delivery label depends on the token’s transfer model. Keep delivery and verification in separate columns: they answer different questions about how an asset arrives and who authorizes its arrival.

How cBridge supplies the destination asset depends on the route

The first delivery question is whether the destination receives an existing token or a newly issued pegged one. Celer cBridge calls its pool-based model xLiquidity. A user deposits tokens into a pool on the source chain, and a pool on the destination chain supplies the payout. Destination reserves therefore matter to the amount available and, on routes that use its pricing curve, to the bridge rate.

Its xAsset model handles a different case: a token exists on its original chain but needs a mapped version elsewhere. The original token is locked in a vault, and a pegged token is minted on the destination chain. On the return trip, burning the pegged token permits release from the vault. That is a lock-and-mint, burn-and-release bridge, even though the same service also operates pools.

Hold the chain pair and transfer size constant to see the deciding condition. Suppose one token already has supported liquidity on Ethereum and BNB Chain: its destination payout can come from a pool. A second token exists originally on Ethereum and uses a mapped token on BNB Chain: its payout must be minted against locked collateral. The route’s token mapping, rather than the brand name, changes the delivery category. xAsset can also move between two mapped chains by burning on one and minting on the other, without first returning to the original chain.

What does the transfer quote reveal about the model?

A quote can expose a pool constraint, but its fee alone does not classify the bridge. In cBridge xLiquidity, an imbalanced destination pool can affect the bridge rate; some routes instead use a fixed 1:1 rate. Comparing cBridge transfer fees with the quoted output amount helps separate that pool pricing effect from the base and protocol fees. Under xAsset, the mapped token is minted at a 1:1 peg, although fees still reduce what the recipient receives.

For the table, record “pool withdrawal” or “pegged mint” from the route’s contracts and output token. A fee estimate is useful supporting evidence when pool imbalance changes the quoted amount, but similar fees across two routes do not establish that they share a delivery design.

Who attests the source-chain event?

The verification entry for both models is Celer’s State Guardian Network (SGN), an external proof-of-stake validator set. Guardians observe source-chain events, reach consensus and produce a stake-weighted multisignature attestation used on the destination chain. In an xAsset transfer, that attestation coordinates minting or release; for shared liquidity pools, the SGN also manages pool movements. “Pool-based” describes where the payout comes from, not why the destination contract accepts the transfer.

That distinction matters when comparing a canonical rollup bridge. A canonical withdrawal is executed through the rollup’s own settlement path after its state or withdrawal message is finalized and proved on the parent chain. It does not require a separate bridge validator set to attest each source event. Both designs may lock and release assets, but their verification assumptions differ.

Where do the other designs sit in the table?

Relayer and messaging-layer bridges show why the two columns must stay separate. Across relayers front destination funds from their own inventory; its later settlement bundles use optimistic verification, meaning a proposed bundle is accepted unless successfully challenged. Stargate supplies transfers through liquidity pools built atop LayerZero messaging. Its pool delivery label says nothing by itself about the messaging layer’s verification configuration.

Use “destination assets supplied by” and “source event attested by” as the column headings. The resulting entries are pool liquidity plus SGN attestation for xLiquidity, and pegged mint or vault release plus SGN attestation for xAsset. Canonical rollup bridges, relayer fills and pools on separate messaging layers then occupy distinct entries for reasons the table can show, rather than being forced into one catch-all bridge category.

0
0
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
0
0

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?