Key Custody
Build the unsigned message for a send from a client_tss wallet
Changed onRuns 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
Response
Unsigned message
Changes
- info
added the new optional request property
- info
added the success response with the status
- info