Request a deposit into a vault
Submits a signed deposit action from the user’s source subaccount and enqueues it in the vault’s pending-deposit queue for the curator to settle. Inputs are the target vault subaccount, the deposit asset, and the amount as a decimal string. Returns an acknowledgement with the queued request; requires the user-deposit permission.
Body
Fields common to every signed vault action. They appear alongside each endpoint's action-specific parameters in the same request object.
Deposit amount in the vault's deposit asset, as a decimal string (e.g. "1").
20-byte Ethereum address as a 0x-prefixed lowercase hex string.
42^0x[0-9a-fA-F]{40}$x >= 00x-prefixed hex of the 65-byte EOA signature.
x >= 020-byte Ethereum address as a 0x-prefixed lowercase hex string.
42^0x[0-9a-fA-F]{40}$The subaccount the action is signed on; which subaccount applies depends on the specific method — see that method's reference.
x >= 0x >= 0Response
Success
Returned by request_vault_deposit / request_vault_withdraw: the id the queued request was assigned (the user's handle for polling / cancelling).
Composite vault request id: (vault_subaccount_id, wallet, vault_nonce)
Useful as a stable dedup key across off-chain and on-chain vault events.
Related topics
Reject a pending vault deposit requestPage a vault's pending deposit requestsSettle a queued vault deposit