How to Set Up a 2-of-3 Bitcoin Multisig Wallet

What you need before you start

To set up a 2-of-3 Bitcoin multisig wallet, you need three independent signing devices, three independent seed-phrase backups, a multisig coordinator application, and printed copies of the wallet descriptor. The whole premise of the setup is that no single piece of hardware, software, or backup location can compromise the wallet on its own.

Common device combinations that work well in 2-of-3 are Coldcard Mk4 + Trezor Model T + Blockstream Jade, or Coldcard Mk4 + Trezor Model T + Ledger Nano X. The reasoning is vendor diversity: three Coldcards is technically valid but fails the independence test if Coinkite ever ships a bad firmware update. See our Coldcard vs Trezor comparison and Blockstream Jade review for the trade-offs.

Step 1 — Choose three independent signing devices

The three signing devices in a 2-of-3 multisig should be as independent as possible: different vendors, different firmware codebases, and ideally purchased through different channels. Independence is the property that makes the quorum survive a single point of failure — if all three devices share the same vulnerability, the wallet is effectively a single-sig wallet wearing three jackets.

Vendor diversity matters

A 2-of-3 setup using three of the same model fails the moment its vendor ships a bad firmware update or has a supply-chain breach. Mixing vendors limits the blast radius of any single firmware compromise to one of the three slots, and 2-of-3 still allows a clean recovery from the remaining two.

Featured hardware wallets

Ledger

Ledger Nano X

4.5 (1,257 reviews)

Premium hardware wallet with Bluetooth connectivity and support for 5000+ cryptocurrencies.

Price

$149

2 year warranty

Secure ElementMultisig

Read ReviewBuy Now

Trezor

Trezor Model T

4.6 (892 reviews)

Premium open-source hardware wallet with touchscreen and Shamir backup support.

Price

$219

2 year warranty

Open SourceMultisig

Read Review

Coinkite

Coldcard Mk4

4.8 (634 reviews)

Bitcoin-only hardware wallet with dual secure elements and advanced air-gapped features.

Price

$148

1 year warranty

Secure ElementOpen SourceMultisig

Read Review

Step 2 — Initialize each device with its own seed

Each of the three devices must generate and store its own independent seed phrase. Reusing a seed across slots collapses the security model: losing or compromising one seed becomes a 2-of-3 compromise on its own.

On each device, run the standard initialization flow and write down the seed phrase on paper or steel. Keep each seed at a different physical location. For backup durability trade-offs (paper vs. metal, geographic separation, redundancy), see our Seed Phrase Backup Guide.

Step 3 — Install a multisig coordinator

A multisig coordinator is the software that assembles the three xpubs into a wallet, generates receive addresses, and produces PSBTs for the signing devices to sign. The coordinator never holds private keys; it only handles public keys, descriptors, and partially-signed transactions.

Coordinator options

Sparrow is the most common choice for first-time multisig setups in 2026 because it has the widest hardware-wallet support and the cleanest UI for the verification steps that come later. The remaining steps in this guide assume Sparrow, but the concepts translate one-to-one to Specter, Caravan, and Electrum.

Install the coordinator on a computer you trust and verify the installer signature if the project provides one (Sparrow does). The coordinator does not hold keys, but a tampered coordinator could show you a fake receive address — which is why the per-device address verification in Step 6 is non-negotiable.

Step 4 — Export the xpub from each device

An xpub (extended public key) is the device's public-side identity for a derivation path; the coordinator combines three of them to form the multisig wallet. The xpub never reveals the private key, but treat it with care anyway — an attacker with all three xpubs can see every address the wallet will ever generate.

For each device

1. Open the device's multisig export flow (often labelled "Export multisig", "Cosigner xpub", or similar).
2. Select the multisig derivation path. For native segwit (recommended), this is m/48'/0'/0'/2' on mainnet.
3. Export the xpub via QR, microSD, or USB — whichever the coordinator and device support in common.
4. Import the xpub into Sparrow as one of the three cosigners. Repeat for the other two devices.

Step 5 — Combine xpubs into a 2-of-3 descriptor

The wallet descriptor is the canonical record of a multisig wallet: the three xpubs, the 2-of-3 quorum policy, and the script type. Without the descriptor, the seeds alone cannot recover the wallet — you would have three loose keys with no record of which addresses they sign for.

In Sparrow, choose File → New Wallet → Multi Signature, set the policy to 2 of 3, and add the three cosigner xpubs imported in Step 4. Select Native Segwit (P2WSH) as the script type unless you have a specific reason to choose otherwise. Save the wallet.

Sparrow will generate a wallet descriptor that looks like:

wsh(sortedmulti(2,
  [fingerprint1/48'/0'/0'/2']xpub1.../<0;1>/*,
  [fingerprint2/48'/0'/0'/2']xpub2.../<0;1>/*,
  [fingerprint3/48'/0'/0'/2']xpub3.../<0;1>/*
))

Copy this descriptor verbatim. It is what you will print and back up alongside each seed in Step 9.

Step 6 — Verify the receive address on every device

Generate a receive address in the coordinator and confirm that all three hardware wallets display the same address before sending any bitcoin. This is the single most important step in the entire setup. If a device disagrees, the wallet is misconfigured on that device, and a deposit could land in an address you cannot recover.

Verification flow

1. In Sparrow, register the multisig wallet on each device (most devices have a "register multisig" or "import wallet config" flow that imports the descriptor).
2. In Sparrow, generate the first receive address.
3. On each device, navigate to the multisig wallet and display the receive address for the same derivation index. The device should ask you to confirm the address against the coordinator.
4. Compare every character. They must match.

Step 7 — Send a small test deposit

Send a small amount of bitcoin to the verified receive address. "Small" here means an amount you would not lose sleep over — a few dollars worth is plenty. The point is to confirm the wallet receives correctly before any meaningful balance lands in it.

Wait for one confirmation before proceeding. Confirm the deposit appears in the coordinator with the correct amount and receive address. If anything looks off, do not move on to signing — investigate first.

Step 8 — Sign a test transaction with two of the three keys

Build a small test transaction back to a wallet you control, sign it with two of the three keys, broadcast, and confirm. This is the first time the wallet has actually authorized a spend. If anything is wrong, this is when you find out.

Signing flow

1. In Sparrow, build the transaction. Select a small output amount and a destination address you control (e.g. a single-sig wallet on a different device).
2. Sparrow will produce a PSBT. Save it to microSD, scan it as a QR, or send it to the device via USB.
3. Open the PSBT on the first signing device. Verify the destination address and amount on the device screen. Approve.
4. Bring the partially-signed PSBT back to Sparrow. Sparrow will show that one signature has been collected.
5. Repeat with a second device. After two signatures, Sparrow can finalize and broadcast the transaction.
6. Wait for one confirmation. Verify on a block explorer that the transaction landed where you expected.

For more on PSBT workflows and air-gapped signing variants, see our Air-Gapped Bitcoin Signing Guide.

Step 9 — Back up the wallet descriptor

Print the wallet descriptor and store a copy alongside each seed backup. The descriptor is not secret in the same way a seed is, but it is just as critical for recovery. Without it, the seeds alone cannot recover the wallet — you would have three loose keys with no record of how they combine.

• Export the wallet descriptor from Sparrow (File → Export → Wallet Output Descriptors).
• Save a digital copy in encrypted storage and print at least two paper copies.
• Store one paper copy with each seed backup — that way, any seed-recovery scenario is also a descriptor-recovery scenario.
• Optionally, store one additional copy with a trusted attorney or in a safe-deposit box. The descriptor leaks visibility into the wallet's addresses, but not spending power, so the threshold for "trusted enough" is lower than for a seed.

Step 10 — Rehearse recovery on a clean machine

Before depositing meaningful funds, install the coordinator on a different computer and recover the wallet using only the descriptor and any two of the three seeds. If you can sign a transaction from that recovered wallet, the setup is real. If not, fix the gap before scaling up.

1. On a different computer (or a fresh OS install), install Sparrow.
2. Import the wallet from the descriptor backup. Confirm the receive address matches the original wallet.
3. Connect any two of the three devices. Build a small test transaction back to yourself.
4. Sign with two devices. Broadcast. Confirm.

If the rehearsal succeeds, the setup is operationally ready. Move funds in gradually, not all at once. If the rehearsal fails, the gap is almost always one of: missing descriptor backup, lost seed, wrong derivation path, or coordinator version mismatch — all fixable, but only if you discover them now rather than under pressure.

How to spend from a 2-of-3 multisig wallet

Spending from a 2-of-3 multisig wallet is the same flow as the test transaction in Step 8: build a PSBT in the coordinator, sign with any two of the three keys, combine, and broadcast. The third key is never required for a normal spend — it is the recovery margin.

1. Open the multisig wallet in the coordinator and build the transaction.
2. Save the unsigned PSBT.
3. Sign on the first device. Verify the destination and amount on the device screen.
4. Bring the partially-signed PSBT back to the coordinator.
5. Sign on the second device. Verify again.
6. Combine the two signatures in the coordinator. Broadcast.

For larger transfers, consider doing the verification + signing on an air-gapped machine to limit exposure. The coordinator does not need to be online to build the PSBT — only to broadcast the final transaction.

Common multisig setup mistakes

Frequently asked questions