πŸŒ‰
πŸŒ‰
πŸŒ‰
πŸŒ‰
Celer cBridge
Search…
πŸ‘‹
Welcome to cBridge
Introduction
Architectural Benefits
State Guardian Network
SGN and cBridge
Fungible Token Bridging Models
cBridge Security
Tutorial
Cross-chain Transfer
LP Guide
SGN V2 Staking Guide
SGN V1 Unbonding Guide
Smart Contract as LP
Ape Chain Bridge Guides
Rewards
Fee Rebate
Developer
cBridge SDK
cBridge Pool-Based Transfer (xLiquidity)
cBridge Canonical Mapping Transfer (xAsset)
Mint
Mint Refund
Burn
Burn Refund
cBridge Transfer Web Widget
API Reference
Custom Transfer URL Schemes
Referral Specific Transfer
NFT Bridge
Introduction
NFT Bridge Fee
List Your Tokens
Simple Listing Process
Reference
FAQ
Audit Reports
Contract Addresses
Powered By GitBook
Mint
To mint pegged token for user on pegged chain, FE(front-end) needs to do the following things:
  1. 1.
    Get basic pegged configs through cBridge gateway. The same api as general token transfer
  2. 2.
    After collecting all needed information, always get updated estimation for the mint. The same estimation api as general token transfer
  3. 3.
    Check user's on-chain token allowance for cBridge contract. If the allowance is not enough for mint, trigger the corresponding on-chain approve flow
  4. 4.
    Submit on-chain deposit/mint request to cBridge OriginalTokenVault contract on source chain
  5. 5.
    Get transfer status repeatedly to check whether the mint is complete.
Mint/Burn flow are quite similar to pool-based token transfer flow. However, it is simpler because there is no slippage-related transfer failure scenario. If user's original token could be moved into OriginalTokenVault, peggedTokenBridge will mint and send corresponding pegged tokens to user's wallet address on pegged chain.
Developer - Previous
cBridge Canonical Mapping Transfer (xAsset)
Next
Mint Refund
Last modified 7mo ago
Copy link