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 Jade Core and Jade Plus guide 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

Using the same model for every signer creates a shared exposure to that model's vulnerabilities. Vendor diversity reduces this correlated risk, but does not protect against every attack or replace independent backups and verification.

Featured hardware wallets

Ledger

Ledger Nano X

Bluetooth-enabled hardware wallet with a CC EAL5+ secure element, USB-C, and broad multi-asset support.

Status

Available

Proprietary firmware

Secure ElementProprietary firmwareMultisig

Official product page

Coinkite

Coldcard Mk4

Bitcoin-only hardware wallet with dual secure elements, source-available firmware, and microSD-based air-gapped signing.

Status

Available

Source-available firmware

Secure ElementSource-available firmwareMultisig

Official product page

Blockstream

Blockstream Jade

Open-source Bitcoin and Liquid hardware wallet with USB-C, Bluetooth, camera-based QR signing, and an optional blind-oracle security model.

Status

Available

Open-source hardware and firmware

Open-source hardware and firmwareMultisig

Official product page

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. In this hardware-wallet setup, import public keys only. Desktop software can also support software keys, so do not import your hardware seeds.

Coordinator options

The examples below use Sparrow. Check the current documentation for your exact devices and coordinator; menus and supported transfer methods differ.

Install the coordinator on a computer you trust and verify the installer signature if the project provides one (Sparrow does). This setup keeps private keys on hardware, 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. Preserve derivation paths and key fingerprints too. Back up the original configuration instead of relying on reconstruction during a recovery.

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>/*
))

This is an illustrative template, not a usable wallet backup. Export your own complete descriptor from the coordinator, including any checksum. Back it up before the test deposit; Step 9 explains storage.

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. Losing the file does not automatically mean the funds are lost: another coordinator backup or registered device may retain the configuration. Recovery can fail if missing public keys or policy details cannot be reconstructed.

• 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

Keep hardware-wallet seed phrases off the coordinator computer. First rebuild the watch-only wallet from its public configuration and sign with hardware devices. This tests the coordinator backup, not the seed backups.

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. Verify the destination, amount and fee on each device before broadcasting.
5. Test seed backups separately on spare hardware using the manufacturer's recovery instructions, including any required passphrase. Do not erase your only working signer to rehearse.

If the rehearsal fails, stop and identify the missing configuration, key or passphrase. Do not assume every recovery failure can be fixed. A successful coordinator rebuild does not prove that every seed backup is correct.

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

Recovery references

Descriptor and recovery guidance checked September 7, 2026. This is a documentation review, not a hands-on test of every device combination.

• COLDCARD configuration and reconstruction requirements
• Jade configuration backup and export
• Blockstream guidance on keeping recovery phrases off computers
• Sparrow storage and signer-separation guidance