Contract: Mint Canonical Token(OriginalTokenVaultV2)
Lock user's assets into cBridge and mint corresponding token on the destination chain
There is no big difference between originalTokenVault and originalTokenVaultV2. However, you should use different parameters to generate transfer id.
originalTokenVaultV2!.deposit(
pegConfig.config.org_token.token.address,
value,
pegConfig.config.pegged_chain_id,
address,
nonce,
)
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.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.
/// Example transaction:
/// https://testnet.bscscan.com/tx/0x5a4a0b50a74c9671f39694a506f1117bdfda2fbd001fe853c0494ca542d7687f#eventlog
const deposit_id = ethers.utils.solidityKeccak256(
[
"address",
"address",
"uint256",
"uint64",
"address",
"uint64",
"uint64",
"address",
],
[
"0x51d36e18e3d32d121a3cfe2f3e5771a6fd53274e", /// User's wallet address,
"0x0368ba12d5b0fc5cd2e17199f8074fbac9abb7aa", /// selectedTokenAddress,
"50000000000000000000", /// Mint amount in String
"65", /// Pegged Chain Id
"0x51d36e18e3d32d121a3cfe2f3e5771a6fd53274e", /// User's wallet address,
"....", /// Nonce
"...", /// Original chain id
"...", /// Original Token Vault V2 contract address
],
)
Since this function is an Ethereum on-chain transaction, the response is the corresponding transaction response.