> ## Documentation Index
> Fetch the complete documentation index at: https://help.bitcoincontrolcenter.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Multisig wallets

> Track a multisig wallet and verify it with your signing keys.

Track a multisig wallet from its **descriptor**. No funds move. Your custody does not change.

## What you need

* Your wallet's descriptor file, or the descriptor text.
* Enough signing devices to meet your quorum. A 2-of-3 wallet needs 2 keys.
* Supported signing devices: Ledger, Trezor, COLDCARD, Keystone.

### Why only these devices

Most wallets can't yet sign a message for a multisig address. The standard for that is called BIP-322.

So Control Center verifies multisig its own way. Each key signs the message separately, from its own single-key address. Control Center then checks that each signing key belongs to your multisig wallet.

This only works with devices Control Center can connect to directly: Ledger, Trezor, COLDCARD, and Keystone. We're working to add more.

> [!NOTE]
>
> A key held in another device or app can still be part of your wallet. You just need enough supported devices among your keys to meet your quorum.

### Where to get the descriptor

Control Center reads these formats:

| Format | Comes from |
| - | - |
| A single descriptor line, such as `wsh(sortedmulti(2,…))` | Sparrow, Nunchuk, and most coordinators. Copy and paste it. |
| Wallet configuration `.json` | Unchained / Caravan, Specter Desktop, Electrum |
| Generic multisig setup `.txt` (Name, Policy, Derivation, Format) | COLDCARD, BlueWallet, Sparrow |
| Descriptor export `.txt` | Bitcoin Core |

Not sure? Find "descriptor" or "export" in your coordinator's wallet settings, and paste the descriptor text.

Supported script types: `wsh(...)`, `sh(wsh(...))`, and `sh(...)` with `multi` or `sortedmulti`. Mainnet only.

> [!WARNING]
>
> Never upload a file that contains a seed phrase. Control Center rejects it with "Seed phrase found in wallet export file."

## Add a multisig wallet

**1. Start**

Select **Add Account** → **Multisig**. Select **Next**.

![Connect Your Multisig Wallet introduction screen](https://mintcdn.com/hoseki-corp/UfUbkRUza9CJFqpH/images/accounts-multisig-intro.png?fit=max\&auto=format\&n=UfUbkRUza9CJFqpH\&q=85\&s=e32965fd56ac3353ce2f7f818cf06ef9)

What the multisig setup involves.

**2. Upload the descriptor**

Drop the `.txt` or `.json` file. Or open **Paste Your Multisig Descriptor**, paste it, and select **Verify Descriptor**.

![Upload Your Multisig Descriptor screen with a file drop zone](https://mintcdn.com/hoseki-corp/UfUbkRUza9CJFqpH/images/accounts-multisig-upload.png?fit=max\&auto=format\&n=UfUbkRUza9CJFqpH\&q=85\&s=e5897bf152932b83d6d5a24e670bbf78)

Upload a file or paste the descriptor.

**3. Name it**

Control Center shows the quorum it found, such as "2 of 3". Enter a name. Select **Next**.

**4. Connect and sign with each key**

Pick a key. Choose its device. Control Center checks the device is part of this wallet. Then sign the message on it.

Repeat until you meet your quorum. You can use the keys in any order.

## Key statuses

Each key has an avatar at the top of the wallet page.

| Status | Meaning |
| - | - |
| Pending | No device connected yet. |
| Identified | Device matched, not signed yet. Select **Continue**. |
| Verified | Signed. |

When enough keys are verified, the wallet becomes **verified**.

## Device notes

* **"Not a match"** means the device's key isn't in this descriptor. Check you picked the right device, passphrase, and account.
* **"Unusual derivation path"** warnings on the device are normal. Each key signs with its own simple address.
* **Trezor** can't sign for keys on `m/45'` or custom paths. Use another device for those keys.
* **Replace a device:** on an identified key, select **Replace this device?** → **Connect New Device**.

After it's verified, select any key avatar to see its details or rename it.

> [!TIP]
>
> Delete the descriptor file from your computer when you finish. It reveals all your addresses.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.