Internal Transfer Signature Guide
To create a valid internal transfer request, you need to generate two different signatures - an EIP 712 signature and a Poseidon signaturePoseidon Signature Guide. Here's how you can do it:Generate the EIP 712 Signature:#
Construct the EIP 712 message parameters, including the domain, message, primary type, and types.
Use the ethers.js library to sign the EIP 712 message using your private key.
The resulting eip712Signature will be used in the final request body.Generate the Poseidon Hash Signature:#
Use the circomlibjs library to build the Poseidon hash calculator.
Fetch the asset information (including the on-chain decimal) from the /api/v1/public/assetInfo endpoint using the provided assetId.
Calculate the Poseidon hash using the following parameters:assetId: The unique identifier of the asset in Vessel.
toAddress: The user address you want to transfer.
assetAmount: The amount you want to transfer.
feeAmount: The fee amount charged by Vessel(Currently, the fee is 0).
timestamp: Unix timestamp in milliseconds when transfered.
nonce: An arbitrary number that can be used just once in a cryptographic communication.
The resulting signature will be used in the final request body.JavaScript Example#
Here's an example implementation in JavaScript:To use this function, you would need to provide the required parameters, such as chainId, assetId, toAddress, assetAmount, feeAmount, timestamp, nonce, address, and privateKey.Important Notes#
Keep Your vesselPrivateKey Secure#
Never share your vesselPrivateKey with anyone. It's crucial for generating signature for order placement.Timestamp Usage#
The timestamp in the signature cannot be earlier than the order placement request timestamp by more than 60 seconds. Ensure synchronization for accurate results. Modified at 2024-11-07 09:08:39
