# multisig-threshold-1 (/docs/tx/multisig-threshold-1)

For multisig accounts with threshold 1, where any single member may act
alone: the call executes in this same extrinsic, with no approval round,
no timepoint, and no deposit. The multisig account is derived from the
signer plus `other_signatories`, so the full member set must still be
supplied even though nobody else signs. For thresholds above 1 use
`multisig_execute` / `multisig_approve` instead.

| Signer    | Origin                                 | Pallet   | Wraps                           |
| --------- | -------------------------------------- | -------- | ------------------------------- |
| `coldkey` | signed account (pallet role may apply) | Multisig | `Multisig.as_multi_threshold_1` |

## Parameters [#parameters]

| Parameter           | Type   | Required | Description                                                                                                                                                                                                                                                                            |
| ------------------- | ------ | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `other_signatories` | array  | yes      | The other members of the multisig (every signatory except the signer), as a JSON list of addresses. The same set must be given on every approval; order does not matter (sorted automatically).                                                                                        |
| `call`              | object | yes      | The inner call to dispatch from the multisig account, as a JSON object \{"op": \<intent name>, ...args}. All approvals must describe the identical call — it is matched by hash. Its arguments must be fully explicit, since it runs as the multisig account, not the signer's wallet. |

Address parameters (`--hotkey`, `--coldkey`, `--dest`, ...) accept a raw ss58
address, an address-book or proxy-book name, or a local wallet/hotkey name.

## CLI [#cli]

Preview with `--dry-run` (shows fee, effects, and policy result without
submitting), then submit:

```bash
btcli tx multisig-threshold-1 \
  --other-signatories <a,b,c> \
  --call '<json>' --dry-run
btcli tx multisig-threshold-1 \
  --other-signatories <a,b,c> \
  --call '<json>' -w my_coldkey
```

## Python [#python]

```python
import bittensor as bt
from bittensor.wallet import Wallet

wallet = Wallet(name="my_coldkey", hotkey="my_hotkey")
intent = bt.MultisigThreshold1(other_signatories=[...], call={...})

sub = bt.Subtensor()
plan = sub.plan(intent, wallet)   # fee, effects, policy — no submission
result = sub.execute(intent, wallet)
if not result.success:
    print(result.error.code, result.error.remediation)
```

(`bt.Subtensor` is also the async client — `async with bt.Subtensor() as client:`
— see [The client](/docs/concepts/client).) Or build the intent by op name, as
an agent would:

```python
result = sub.execute_tool("multisig_threshold_1", {...}, wallet)
```

## On-chain implementation [#on-chain-implementation]

`Multisig.as_multi_threshold_1` is implemented by Substrate's `pallet_multisig`, outside this repository's pallets.

Every file is browsable under [/code](/code) exactly as built into the runtime, or as plain text under `/code/raw/<path>` (index: [`/code/index.json`](/code/index.json)).