So far you have protected your bitcoin with a single seed. For most people, that works very well. But a single seed has one clear limit: it is a single point of failure. If someone finds those words, they take everything. If you lose them, you lose everything.
When the amount you hold starts to matter in your overall net worth, there is a way to remove that single point of failure: multisig, short for multi-signature. It is the right tool for a specific problem, not a mandatory next step. I will explain when it is worth it and when it just gets in the way.
What multisig is: the m-of-n concept
In a regular wallet, one key signs and the money moves. In a multisig wallet, the address is built so that spending requires m signatures out of a total of n keys.
The most common example is 2-of-3: there are three keys, each with its own seed, and any two of them are enough to sign a transaction. That gives you two protections at once:
- Against theft: whoever gets a single key cannot move anything. They would need two.
- Against loss: if you lose one key (the device broke, the seed got wet, the house burned down), the other two can still move everything. Then you create a new wallet and move the balance calmly.
This rule does not depend on a company or a server. It is written into Bitcoin's own script, and the network only accepts the transaction if the required signatures are there.
There are other setups, like 2-of-2 (lose one key, lose access) or 3-of-5 (more common in companies). For an individual, 2-of-3 is the balance that makes the most sense.
Each key is a complete wallet
Each of the three keys is created the way you learned in the previous chapters: a BIP39 seed of 12 or 24 words, generated inside a hardware wallet, written on paper or metal, and tested.
Ideally, each key lives on a device from a different manufacturer. For example, one on a Coldcard, one on a Trezor and one on a Jade, or any mix of BitBox02, Ledger, SeedSigner or Krux. The reason is simple: if a serious firmware bug ever shows up in one brand, or a tampered batch enters the supply chain, that problem hits only one of your keys. On its own, it is not enough to spend.
The buying rule stays the same: straight from the manufacturer or an official reseller, never used, checking the seal and the firmware.
And it is worth repeating: no legitimate person or company will ever ask for your seed. That applies to all three. Not me, not wallet support, not an exchange.
The coordinator: the software that builds the wallet
The devices hold the private keys. But something has to bring the three parts together and build the multisig wallet. That job belongs to a program called the coordinator. Examples: Sparrow, Nunchuk and Electrum.
In any serious coordinator, the process follows these steps:
- Each hardware wallet exports its xpub (extended public key), along with the key fingerprint and the derivation path (BIP32). The xpub lets you generate addresses and see the balance, but it cannot spend.
- The coordinator combines the three xpubs with the 2-of-3 rule and generates the wallet's addresses.
- You register this multisig wallet on every device that supports it. That way the device itself can confirm, on its own screen, that an address belongs to the right set and that the change from a transaction comes back to you.
No seed ever touches the computer. It only sees public information.
If any of the keys uses a passphrase, the passphrase becomes part of that key. The xpub has to be exported with the passphrase already applied on the device, and the passphrase needs a backup just like the seed. Without it, that seed produces a different key, one that does not belong to your multisig.
The backup almost everyone forgets: the descriptor
This is the most common mistake, and it is a serious one. Many people believe that in a 2-of-3, having two seeds is enough to recover everything. It is not.
To rebuild the addresses of a multisig, you need to know all three public keys, plus the rule (2-of-3), the script type and the derivation paths. With two seeds you can recreate two xpubs. The third xpub cannot be derived from your two seeds. Without it, the software does not know which addresses to look for.
That is why the output descriptor exists. It is a piece of text that describes the entire wallet. It usually looks something like wsh(sortedmulti(2,[fingerprint/path]xpub...,...,...)). Coordinators export this file, often also as a QR code or PDF.
What you need to know about the descriptor:
- It cannot move money. Without two private keys, nobody can spend anything with it.
- It reveals everything. Whoever has the descriptor can see all your addresses, balance and history. Treat it as sensitive privacy information.
- Keep a copy with each seed. That way, any combination of two locations lets you recover the complete wallet.
Without the descriptor (or all three xpubs), two seeds may not be enough to recover a multisig. Back up the descriptor the same day you create the wallet, in more than one place.
How to spend: PSBT
To sign with two keys sitting on different devices, Bitcoin uses the PSBT standard (Partially Signed Bitcoin Transaction, defined in BIP174). It works like this:
- The coordinator builds the transaction: destination, amount and fee.
- You take that PSBT to the first device, by USB cable, microSD card or QR code. You check the destination address and amount on its screen, and sign.
- You take the PSBT, now carrying one signature, to the second device. Check again and sign.
- Back in the coordinator, it finalizes the transaction and broadcasts it to the network.
Devices that sign by microSD or QR never touch the computer. This is called offline (air-gapped) signing, and it reduces the attack surface.
The most important point in this flow: check the address on each device's screen, never only on the computer screen. Malware on the computer can swap the destination. The device screen is where the truth is.
Multisig transactions take up more space, so they pay a bit more in fees. For larger holdings, that is a minor detail.
Where to keep each part
The logic is to never keep two keys in the same place. If two sit in the same drawer, a single burglar or a single fire defeats the whole setup.
A common 2-of-3 arrangement:
| Location | What stays there |
|---|---|
| Your home | Device A, seed A, copy of the descriptor |
| Second secure location (another property of yours, a safe deposit box) | Seed B, copy of the descriptor |
| Third location (trusted person or collaborative custody service) | Seed C or device C, copy of the descriptor |
Some companies offer to hold one of the three keys (collaborative custody). On their own, they cannot move anything. Before using one, understand what happens if the company shuts down: with the descriptor and two seeds, you need to remain independent.
Test before you move a large amount
Before you transfer your holdings, run a full rehearsal:
- Send a small amount to the multisig.
- Spend it by signing with the A + B combination.
- Make another spend with B + C.
- On another computer, ideally in a different coordinator, import only the descriptor. Check that the addresses and balance match. Then sign a test spend there with two of the keys.
If everything worked, the plan is proven in practice.
When it is worth it and when it is too much
It is worth it when the amount is something you could not accept losing under any circumstances, when you already master a single-key wallet, and when you are willing to keep three locations organized. Multisig also helps a lot with inheritance planning, the topic of the last chapter.
It is too much when you are still learning, when the amount is small, or when you do not have three separate locations. A badly done multisig is worse than a well done single key. In self-custody, many people lose bitcoin through their own mistakes, not through attacks: incomplete backup, lost descriptor, untested seed.
If in doubt, start with a well protected seed and a passphrase. When the amount grows and you feel comfortable, migrate.
Checklist
- I understand that in a 2-of-3 any two keys can spend and one alone moves nothing
- I generated each seed on its own device, ideally from different manufacturers, bought through official channels
- I saved the wallet descriptor and keep a copy with each seed
- I registered the multisig on the devices and checked a receive address on each screen
- I made test spends with two different key combinations
- I rebuilt the wallet on another computer from the descriptor and signed a spend there
- No location holds two keys at the same time