cBridge is reasonably safe for typical transfers when you use the real site, limit token approvals to the amount you will send, and accept reliance on the State Guardian Network validator quorum.
What are the main risks when using cBridge?
The Celer bridge’s main risks are a compromised frontend, an unsafe token approval, and the validator trust assumption while funds move between chains. A successful source-chain transaction alone does not mean the destination transfer is complete.
In August 2022, a DNS hijack affected the bridge’s frontend and presented some users with malicious approval requests. The bridge contracts were not the target of that incident. This distinction matters: even a correct-looking website can ask a wallet to approve the wrong spender. A bookmark helps you avoid lookalike links in ads or messages; reading the approval in MetaMask addresses the risk at the wallet prompt.
A token approval gives a named contract permission to spend a specified token from your wallet. An unlimited allowance can remain useful to that spender after this transfer. If the spender is malicious, the amount at risk can exceed the amount you meant to bridge.
The State Guardian Network, or SGN, observes source-chain activity and coordinates destination-chain transfers. Its validators reach consensus and produce a stake-weighted attestation, as Celer’s security model explains. That signing process is the trust assumption to consider when choosing how much value to have in transit at once.
Which checks should you run before sending?
The Celer bridge is ready for your transfer only when the route, receiving asset, wallet address, and wallet permissions match what you intend. Run this checklist each time:
- Open your saved bookmark. Avoid ads and links in direct messages, which can lead to lookalike sites. Then inspect the wallet prompts independently: the 2022 frontend incident showed why arriving at a familiar address is not the last safety check.
- Confirm the route and receiving token. Verify the source chain, destination chain, token, and expected output before signing. An xLiquidity transfer uses pooled liquidity; an xAsset transfer can deliver a pegged token minted against an original token locked elsewhere. A pegged xAsset is not the destination chain’s native asset.
- Read the approval’s spender and amount. Compare the spender shown in MetaMask with Celer’s published contract address for that chain and transfer type. Approve only the amount being sent. Reject an unfamiliar spender, especially when the prompt requests a much larger allowance.
- Wait for any required approval to confirm. The source-chain transfer can spend the token only after its allowance exists on-chain. A confirmed approval transaction, or a sufficient allowance already in place, tells you this prerequisite is complete. An approval confirmation is not a bridge-transfer confirmation.
- Verify the destination wallet can receive the asset. A smart-contract wallet may have an address on the destination chain without having been deployed there. Confirm that its contract exists and can handle the token before naming it as the receiver; otherwise, receiving funds may be difficult or impossible to access.
- Set a slippage tolerance you can accept. For a pooled xLiquidity route, the destination amount depends on available liquidity and the bridge rate. If the transfer cannot meet your tolerance, it can enter a refund state. The source-chain funds return after you request and submit the refund, rather than appearing back automatically.
- Allow for safeguards on a large transfer. A transfer above an on-chain delay threshold can wait in a release queue. A volume cap can also restrict when a transfer is accepted or released. A delayed transfer is being held for the safeguard period, not necessarily lost; inspect its status before sending again.
- Size the transfer for the SGN risk. While the transfer is in progress, destination execution depends on the validator quorum. For a sum that would be painful to have pending, consider smaller transfers and avoid leaving more value in transit than necessary. Splitting may add fees and does not remove the shared validator assumption.
Take a transfer that shows a successful source-chain transaction but no destination balance. The sender may expect an immediate arrival; the transfer may actually be waiting under a delay threshold or for SGN confirmation. The source transaction proves the funds were sent into the bridge, while the transfer status tells you what must happen next.
Once the checks pass and your route is supported, you can send the asset between networks. Use cbridge.finance for that Celer bridge transfer.
Related questions
Can cBridge transfers be reversed?
A confirmed source-chain transfer cannot simply be reversed like a cancelled bank payment. A refund is available for certain failed bridge transfers, including ones that cannot complete within the chosen slippage tolerance. First establish whether the transfer is pending, completed, or marked for refund; sending a second transfer before doing so can create a separate problem.
What is a token approval and why does cBridge ask for one?
A token approval authorizes a spender contract to move a token from your wallet. The bridge needs sufficient allowance to take an ERC-20 token for the transfer. MetaMask may show the approval as a separate transaction before the bridge transaction. Read its spender and allowance because confirming the approval grants permission even if you never complete the transfer.
Are cross-chain bridges riskier than exchanges?
Cross-chain bridges expose users to source and destination chains, smart contracts, and a cross-chain verification mechanism. An exchange instead asks users to trust its custody and withdrawal operations. Neither choice has one universal risk ranking; for this bridge, the practical question is whether you accept SGN validation and can verify the approval and receiving asset.
What should you do after a transfer needs attention?
How do I request a refund on cBridge?
Request a refund when the transfer status says it is eligible, then submit the required source-chain refund transaction. A failed pooled transfer may need time for the refund transaction details to become available. Keep the original transaction hash and transfer identifier so you can distinguish a refundable failure from a transfer still waiting for release.
How do I revoke token approvals?
Use Revoke.cash to review approvals on the relevant chain, identify the token and spender, and submit a revocation transaction. Its documentation covers reviewing and revoking allowances. Revoke an unfamiliar approval promptly; reducing or revoking an old legitimate allowance also limits what that spender can use later.
How long does a cBridge transfer take?
Transfer time varies with source-chain confirmation, SGN processing, destination-chain conditions, liquidity, and safeguards. A large transfer can take longer because of a deliberate delay, while a cap may temporarily restrict capacity. Use the individual transfer’s status rather than assuming that a successful source transaction sets an arrival deadline.
What should I do if bridged tokens don't arrive?
Find the transfer status and source-chain transaction first. If the transfer is pending or delayed, wait for the stated stage to finish. If it is complete, switch MetaMask to the destination chain and check the received token’s contract address; an xAsset may need to be added to the wallet before its balance appears. If the status calls for a refund, request it instead of repeating the send.
Top comments (0)