Multisig

Multisig, short for multi-signature, is a Bitcoin wallet arrangement that requires more than one key to authorize a spend. It is described as m-of-n: there are n keys total, and any m of them must sign before funds move. A 2-of-3, for example, has three keys and needs any two to spend. This contrasts with a single-sig wallet, where one private key controls everything — and that one key is a single point of failure for both loss and theft.

Why distribute the keys

In single-sig, whoever holds the key holds the coins, so one mistake, theft, fire, or coerced disclosure can mean total loss. Multisig spreads the risk across keys you can store in different locations and on different devices — ideally different hardware wallet models, so no single vendor bug compromises the quorum. An attacker must now compromise multiple keys in multiple places at once, and you can lose one key entirely without losing access, since the remaining keys still meet the threshold. A 2-of-3 with keys at home, at a second property, and in a bank box survives a house fire, a stolen device, or a forgotten PIN — events that would each be fatal to a single-sig setup. The cost is complexity: setup, backup, and recovery all have more moving parts, and more parts means more ways to make a quiet mistake that only surfaces years later at recovery time.

What you must actually back up

The classic multisig failure is not losing keys — it is losing the wallet's description. To reconstruct an m-of-n wallet you need not just m seeds but the full set of public keys and the policy that binds them, which is why every multisig should be captured as a descriptor (or a wallet configuration file) and stored with each key backup. Each cosigner's seed phrase alone is not enough. Store the descriptor with every share; unlike a seed, it does not enable spending by itself, so it can be copied liberally. Note the privacy nuance, though: while the descriptor cannot move funds, it does reveal every address the wallet will ever use, so treat it as confidential even if not as critical as the seeds themselves.

Collaborative custody

A popular pattern is collaborative custody, often a 2-of-3 where you hold two keys and a service holds the third as a recovery key. You remain the only party able to spend, since the provider's single key cannot reach the threshold alone — so this is still genuine self-custody. The provider helps you recover if you lose one of your own keys, without ever being able to take your bitcoin. The trade-off is privacy: the collaborative custodian typically learns your balances and addresses, which matters if your threat model includes data leaks rather than only theft.

Signing and the road ahead

Day to day, a multisig spend is coordinated through the PSBT workflow: the wallet drafts an unsigned transaction, each device adds its partial signature — often via air-gapped signing over QR codes or SD cards — and the final assembled transaction is broadcast. Since Taproot, Schnorr signatures make it possible for aggregated multisig spends to look identical to ordinary single-sig payments on-chain, improving both fees and privacy as wallet support matures.

The practical guidance: multisig earns its complexity when the value at stake exceeds what you would be comfortable losing to a single point of failure. Start with a well-drilled single-sig-plus-passphrase setup, graduate to 2-of-3 when the stakes justify it, document everything for your heirs, and rehearse recovery before you need it. Distributed keys are the wallet-level expression of the same principle that drives everything D-Central builds toward: no single point of failure, no single point of control.