Contract: TransferAgent Mint Token Submission
Lock user's assets into cBridge contract, mint corresponding tokens to receiver which address can be any length
TransferAgent transfer is not recommended if receiver's wallet address is no more than 20 bytes
Implementation
Through TransferAgent's transfer function, user can specify token to be locked on source chain and receiver's address on destination chain. According to pegged_pair_config.vault_version, you should set different parameters communicating with TransferAgent contract.
Communicate with OriginalTokenVault through TransferAgent contract
Communicate with OriginalTokenVaultV2 through TransferAgent contract
Request Parameters
receiver_address
String
Receiver's address on destination chain
token_address
String
Token address on source chain
amount
UInt256
Transfer amount on source chain
nonce
UInt64
Timestamp
max_slippage
UInt32
Not required
bridgeSendType
Bridge Send Type
extensions
Not required
TransferId Generation
When you submit on-chain mint transaction through TransferAgentContract, 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.
Transfer Id Generation with OriginalTokenVault
Transfer Id Generation with OriginalTokenVaultV2
Response
Since this function is an on-chain transaction, the response is the corresponding transaction response.
Last updated