Key Custody

Broadcast a multisig wallet's signed activation

raw must be exactly what activation prepared and device_signature D's signature over sha256(raw). Needs X-Passkey-Token from a passkey assertion bound to action tss_sign and the hex sha256 of raw. The vault re-checks the raw, broadcasts it with D's signature alone, and waits a few blocks for the permissions to appear; poll activation/status if it answers pending_activation. A second submit of the same prepared raw is 409. Audited treasury_wallet.multisig_activation_sent then treasury_wallet.multisig_activated.

post/v1/treasury/wallets/{chain}/multisig/activation/complete

Request

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

Headers

X-Passkey-Tokenstring required

Request body

rawstring required

Base64 raw bytes exactly as prepared.

device_signaturestring required

Hex 65-byte recoverable ECDSA signature (r ‖ s ‖ v, low-S) by D over sha256(raw).

Response

The wallet after broadcasting

key_idstring uuid required
chainstring required
addressstring required

The account address (D's).

custody'client_multisig' required
status'pending_activation' | 'active' required
activation_min_suninteger required

What the account must hold before activation (101 TRX), in sun.

Changes

No recorded changes to this operation across all 1 revision of this API.