Bitcoin Multisig Planner: Choose Your m-of-n Setup
Plan your Bitcoin multisig wallet setup. Compare 2-of-3, 3-of-5, and other configurations. Understand security tradeoffs, key storage, and recovery scenarios.
All data is computed locally in your browser. No keys are generated or transmitted. This tool is for planning purposes only.
What Is Bitcoin Multisig?
Multisig (short for multi-signature) is a Bitcoin feature that requires multiple private keys to authorize a transaction. Instead of a single key controlling your funds, a multisig wallet uses an m-of-n scheme: you need m signatures out of n total keys to move bitcoin. For example, a 2-of-3 multisig requires any 2 of 3 keys to sign a transaction. The remaining key can be lost or unavailable without putting funds at risk.
Multisig is not a new concept. Bitcoin has supported it natively since 2012 through the OP_CHECKMULTISIG opcode. It is enforced at the protocol level, meaning the blockchain itself validates that the required number of signatures are present before confirming a transaction. This is fundamentally different from custodial solutions where you trust a third party to enforce access controls on your behalf.
The primary purpose of multisig is to eliminate single points of failure. With a standard single-key wallet, if your one private key is compromised, stolen, or lost, your funds are gone. Multisig distributes that risk across multiple keys, which can be stored on different devices, in different locations, and controlled by different people.
Common Multisig Configurations
The most popular multisig setup is 2-of-3. It provides a strong balance between security and usability: you can lose one key entirely and still recover your funds with the remaining two. An attacker would need to compromise two separate keys, stored in different locations, to steal anything. This is the configuration recommended for most individuals who want to self-custody significant amounts of bitcoin.
For businesses and organizations, 3-of-5 is the standard choice. It distributes key control among five parties (such as executives, board members, or department heads) while requiring only three to authorize a transaction. This allows for two keys to be lost, destroyed, or held by unavailable signers without blocking access to funds. It also means an attacker must compromise three independent keys to steal funds.
Treasury-grade setups often use 4-of-7 or similar high-threshold configurations. These are designed for organizations managing large reserves where maximum security justifies the operational overhead of coordinating four or more signers for every transaction. The tradeoff is clear: more signers means stronger security, but also slower and more complex transaction workflows.
At the simpler end, 1-of-2 functions as a backup key arrangement. Only one signature is needed, but you have two keys. If you lose your primary key, the backup can still access funds. This does not protect against theft (a single compromised key is enough), but it does protect against loss.
Key Storage Options
The security of a multisig setup depends entirely on how and where the individual keys are stored. Having three keys provides no benefit if all three sit in the same drawer.
Hardware wallets (such as Coldcard, Trezor, or Ledger) are the most common key storage devices for multisig. Each hardware wallet holds one key and signs transactions in an air-gapped or USB-connected environment. The private key never leaves the device. For a 2-of-3 setup, you might use three different hardware wallets from different manufacturers to avoid a single vendor vulnerability.
Metal seed plates provide durable, fire-resistant backup for the seed phrases that generate each key. Stamping or engraving your 12 or 24 word seed phrase onto a steel plate ensures it survives physical disasters that would destroy paper backups. Each key's seed plate should be stored in a separate location.
Geographic distribution is a core principle of multisig security. Storing keys in different physical locations (home safe, bank safe deposit box, trusted family member's location, or a secure office) means a single break-in, fire, flood, or natural disaster cannot compromise enough keys to steal funds or destroy enough keys to lose access. For a 2-of-3 setup, three different cities or at minimum three different buildings is a reasonable baseline.
Security vs Convenience
Every multisig configuration involves a tradeoff between security and convenience. Adding more keys increases the number of locations an attacker must breach but also increases the number of signers who must coordinate for every transaction.
| Configuration | Keys Lost Before Funds Lost | Keys to Steal Funds | Best For | Complexity |
|---|---|---|---|---|
| 1-of-2 | 1 | 1 | Backup key | Low |
| 2-of-3 | 1 | 2 | Personal savings | Moderate |
| 3-of-5 | 2 | 3 | Business treasury | High |
| 4-of-7 | 3 | 4 | Institutional reserve | Very high |
For most individuals, 2-of-3 hits the practical sweet spot. You get meaningful protection against both theft and loss without the operational burden of coordinating multiple signers. For organizations, the right configuration depends on how many trusted parties are available, how frequently transactions need to be signed, and how much is at stake.
Recovery Scenarios
Understanding what happens when things go wrong is the most important part of multisig planning. The whole point of the design is to survive failures.
In a 2-of-3 setup, if you lose one key (hardware wallet destroyed, seed phrase lost, or a keyholder becomes unavailable), your funds are still fully accessible with the remaining two keys. The correct response is to immediately create a new multisig wallet with fresh keys and sweep all funds from the old wallet into the new one. Running a 2-of-3 with only two surviving keys means you have temporarily become a 2-of-2, which has zero tolerance for further key loss.
In a 3-of-5 setup, you can lose up to two keys and still access funds. This provides a larger buffer for organizational turnover: if a keyholder leaves the company or a hardware wallet fails, there is time to rotate keys without an emergency. The same principle applies: once a key is lost, migrate to a fresh wallet promptly to restore the full redundancy of your intended configuration.
The recovery formula is straightforward: in any m-of-n setup, you can lose (n minus m) keys before funds become inaccessible. If you lose more than that, the bitcoin is permanently unrecoverable. There is no customer support, no password reset, and no court order that can override the protocol.
Transaction Fees and Size
Multisig transactions are larger than single-signature transactions because they contain multiple signatures and a more complex script. A standard single-sig transaction is approximately 140 to 180 virtual bytes (vBytes). A 2-of-3 multisig transaction is roughly 260 to 300 vBytes, and a 3-of-5 can reach 400 vBytes or more.
Since Bitcoin transaction fees are calculated per vByte, multisig transactions cost proportionally more. At a fee rate of 20 sat/vB, a single-sig transaction might cost around 3,200 sats, while a 2-of-3 multisig transaction would cost around 5,600 sats. At high fee rates, this difference becomes more significant.
Modern address formats help reduce this cost. Native SegWit multisig addresses (starting with bc1) discount the witness data (which includes the signatures), making multisig cheaper than it was under legacy address formats. Taproot (P2TR) can make multisig transactions appear identical to single-sig transactions on-chain when all parties cooperate, using Schnorr signature aggregation. This is a significant privacy and fee improvement, though Taproot-based multisig tooling is still maturing.
Frequently Asked Questions
What is the best multisig configuration for personal use?
A 2-of-3 setup is widely considered the best configuration for individuals. It lets you lose one key entirely (through hardware failure, misplaced backup, or any other reason) while still retaining full access to your bitcoin with the other two. An attacker would need to compromise two of your three separately stored keys to steal funds. This provides strong protection against both loss and theft without the complexity of coordinating more signers.
How do I set up a multisig wallet?
You need multiple hardware wallets (one per key) and a multisig coordinator software such as Sparrow Wallet, Nunchuk, or Caravan. First, generate a key on each hardware wallet. Then import the extended public keys (xpubs) from each device into the coordinator software, which creates the multisig wallet. The coordinator handles building transactions that you then sign on each required hardware wallet. Always test the setup with a small amount before depositing significant funds, and verify that you can successfully spend from the wallet with the required number of keys.
Can I use multisig with different hardware wallet brands?
Yes, and it is recommended. Using hardware wallets from different manufacturers (for example, one Coldcard, one Trezor, and one Ledger) means a firmware vulnerability in one brand does not compromise your entire setup. Each device generates and stores its own independent key. The multisig coordinator software handles the compatibility between devices.
What happens if I lose more keys than the threshold allows?
If you lose more than (n minus m) keys, the bitcoin is permanently inaccessible. In a 2-of-3, losing two keys means the remaining single key cannot sign a valid transaction. There is no recovery mechanism, no override, and no way to appeal to the Bitcoin network. This is why geographic distribution and durable backups (metal seed plates) are essential parts of any multisig strategy.
Are multisig transactions more expensive?
Yes. Multisig transactions include more signature data and a larger script, which increases the transaction size in vBytes. A 2-of-3 multisig transaction is roughly 1.5 to 2 times the size of a standard single-sig transaction, so fees scale accordingly. Using native SegWit (bech32) addresses reduces this overhead compared to legacy formats. Taproot-based multisig (using Schnorr signatures) can reduce fees further by making cooperative spends look like single-sig transactions on-chain.
Is multisig the same as Shamir's Secret Sharing?
No. Multisig uses multiple independent private keys where each key is a complete, standalone secret. The m-of-n policy is enforced by the Bitcoin protocol itself. Shamir's Secret Sharing (SSS) splits a single private key into shares that must be recombined to reconstruct the original key. SSS has a critical weakness: at the moment of recombination, the full private key exists in one place, creating a single point of failure. With multisig, the full private keys are never combined; each signs independently.
Can multisig protect against a $5 wrench attack?
Multisig provides partial protection. If an attacker physically coerces you, you can only provide the keys you personally hold. In a well-designed 2-of-3 setup where you hold one key and the other two are with separate parties or in separate secure locations, you genuinely cannot authorize a transaction alone. However, if you hold two or more keys or if the attacker can identify and reach your other keyholders, multisig alone does not solve this problem. Combining multisig with timelocks, geographic distribution, and operational security practices provides a more comprehensive defense.
How does Spark relate to multisig?
Spark is a Bitcoin layer that enables fast, low-cost transfers of bitcoin and stablecoins. While multisig secures your on-chain bitcoin holdings, Spark provides a complementary layer for everyday spending and receiving. You can hold your long-term savings in a multisig cold storage wallet and move smaller amounts to Spark for instant transactions. Learn more at docs.spark.money.
This tool is for educational and planning purposes only. It does not generate keys, create wallets, or interact with the Bitcoin network. Always consult current best practices and test your multisig setup with a small amount before securing significant funds.
Build with Spark
Integrate bitcoin, Lightning, and stablecoins into your app with a few lines of code.
Read the docs →
