Contract: Mint Canonical Token(OriginalTokenVaultV2)
Lock user's assets into cBridge and mint corresponding token on the destination chain
Implementation
There is no big difference between originalTokenVault and originalTokenVaultV2. However, you should use different parameters to generate transfer id.
Request Parameters
Name | Type | Description |
---|---|---|
token | String | Token's address |
amount | UInt256 | locked token amount |
mint_chain_id | UInt64 | destination chainId to mint tokens |
nonce | UInt64 | Current timestamp |
mint_account | String | User's wallet address |
If the mint_account
is a smart contract and the token you are sending is a wrapped native gas token on the destination chain, make sure the contract can receive native gas token by implementing fallback
/ receive
functions.
TransferId Generation
When you submit on-chain deposit transaction, you can also generate a transfer id for future reference. For example, it is used for getTransferStatus. It should be the same as transferId inside on-chain transaction log.
Response
Since this function is an Ethereum on-chain transaction, the response is the corresponding transaction response.
Last updated