Key Custody

Build the unsigned message for a send from a client_tss wallet

Changed on

Runs wallet access, the sanctions screen and spend policies on the declared destination, fetches a recent blockhash and returns the unsigned transaction message. Sign it with /v1/keys/{key_id}/tss/sign/* and submit with …/tss/broadcast. It then runs the same Cedar/OPA transaction policy (action submit) and treasury_send M-of-N consensus a server-custody treasury send runs; the vault co-signs this send, so an org rule that would stop a server send stops it too.

post/v1/treasury/wallets/{chain}/tss/prepare

Request

  • Base URL: https://api.1claw.co
  • URL: https://api.1claw.co/v1/treasury/wallets/{chain}/tss/prepare
  • Auth: HTTP bearer

Request body

tostring required
valuestring required

Major units, e.g. "0.5".

memostring
approval_idstring uuid

An approved treasury_send M-of-N consensus approval for this exact send (the pending_approval_id of an earlier 202).

Response

Unsigned message

key_idstring uuid
chainstring
fromstring
tostring
value_base_unitsstring
recent_blockhashstring
messagestring
message_digeststring

Changes

    • info

      added the new optional request property

    • info

      added the success response with the status