---
title: "Prepare the activation of a multisig wallet"
method: POST
path: "/v1/treasury/wallets/{chain}/multisig/activation"
tags: ["Key Custody"]
---

# Prepare the activation of a multisig wallet

`POST /v1/treasury/wallets/{chain}/multisig/activation`

## Request

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

Once the wallet is backed up (a passkey holds D and the kit is
confirmed) and its address holds at least 101 TRX
(`activation_min_sun`), builds the AccountPermissionUpdate that installs
owner = 2-of-3 and active = 2-of-3 (transfers and contract calls only)
over V, D and R, from a reference block, and returns its raw bytes. The
network burns a 100 TRX fee when it lands. The device decodes and checks
the raw itself, then signs it with D (the account's sole owner until
then) and calls `activation/complete`. 409 when already active or not
funded.

## Response `200`

The raw permission update to sign

- MultisigPreparedRaw
  - `key_id` string, uuid, required
  - `chain` string, required
  - `raw` string, required: Base64 `Transaction.raw` protobuf bytes, built by the vault in canonical form. Decode and check them before signing.
  - `txid` string, required: Hex sha256(raw), the digest each key signs and the passkey binds.
  - `kind` 'activation' | 'transfer', required
  - `to` string: Transfers only.
  - `value_base_units` string: Transfers only; sun.
  - `expires_at_ms` integer, required: When the raw expires (10 minutes after its reference block).

## Other responses

- `400`: Invalid request
- `401`: Authentication required or invalid
- `404`: Resource not found
- `409`: Resource already exists or conflict

---

[API](https://skmtc.dev/1claw/apis/1claw-api.md) · [All operations](https://skmtc.dev/1claw/apis/1claw-api/llms.txt) · [OpenAPI document](https://skmtc.dev/1claw/apis/1claw-api/revisions/5fa0918f3b41?raw)