A multisig wallet, short for multi-signature wallet, is a crypto wallet that moves funds only when a defined number of independent keys approve the same transaction, expressed as an M-of-N threshold such as 2-of-3. Within wallets & custody in the crypto & blockchain field, it replaces the single private key of an ordinary wallet with a shared authorization rule, so that no one device, person or location can spend the assets alone.
Organizations use multisig to enforce separation of duties over treasuries, and individuals use it to survive the loss or theft of one key without losing everything. The trade-off is added operational complexity: more devices, more backups and a stricter signing procedure.
How a multisig wallet enforces an M-of-N threshold
A multisig wallet works by encoding the approval rule directly into the spending condition that the blockchain itself verifies. Instead of checking one signature, network nodes check that at least M valid signatures from a fixed set of N public keys are attached before they accept the transaction.
On Bitcoin, this rule lives in a script, today usually a P2WSH or Taproot output that commits to all N public keys and the threshold. On Ethereum and similar networks, the rule lives in a smart contract that stores the signer list and counts approvals. In both cases the wallet software only coordinates; the consensus rules enforce the policy, which is why a compromised server or interface cannot bypass it.
Signing is a staged process. One participant drafts the transaction, often as a Partially Signed Bitcoin Transaction (PSBT) under the BIP 174 standard, and each cosigner reviews and signs it on their own device. Once the threshold is met, anyone can broadcast it.
| Threshold | Typical user | Tolerates loss of | Tolerates theft of |
|---|---|---|---|
| 2-of-2 | Two business partners | No key | One key |
| 2-of-3 | Individual or small team | One key | One key |
| 3-of-5 | Company treasury | Two keys | Two keys |
| 4-of-7 | DAO or foundation | Three keys | Three keys |
Multisig implementations on different blockchains
The mechanism differs sharply between script-based multisig on UTXO chains and contract-based multisig on account chains, and the difference affects cost, privacy and flexibility.
| Aspect | Script-based (Bitcoin) | Contract-based (Ethereum) |
|---|---|---|
| Where the rule lives | Locking script of each output | Deployed smart contract |
| Changing signers | Requires moving funds to a new address | Possible through an owner vote |
| Fee impact | Grows with signature count | Fixed deployment cost plus execution gas |
| On-chain privacy | Visible unless Taproot hides it | Signer set fully visible |
| Main risk | Lost wallet descriptor | Contract bugs or malicious upgrades |
With Taproot, a cooperative spend can appear on-chain as a single ordinary signature, which improves privacy and lowers fees, while the full multisig script remains available as a fallback path.
Multisig compared with MPC and other custody models
Multisig is one of several ways to distribute control over crypto assets, and its closest rival is the MPC wallet, which splits one private key into shares that compute a signature jointly without ever reassembling the key.
| Model | Who holds key material | Visible on-chain | Main weakness |
|---|---|---|---|
| Single-key wallet | One person or device | One signature | Single point of failure |
| Multisig wallet | N independent keys | Threshold policy visible | Coordination and backups |
| MPC wallet | Key shares across parties | Looks like one signature | Proprietary protocols, vendor reliance |
| Custodial wallet | A third-party provider | Provider’s addresses | Counterparty and insolvency risk |
The decisive difference is transparency of the policy. Multisig rules are public and verifiable by anyone, while MPC policies are enforced off-chain by software that users must trust. A multisig setup is also a form of self-custody when the holder controls at least M keys.
Designing a multisig setup that survives real failures
A robust multisig design depends less on the threshold number than on key independence. Two keys stored in the same safe, or generated on the same compromised computer, behave like one key.
- Use different hardware wallet vendors for different keys, so a single firmware flaw cannot affect every signer.
- Store keys in separate physical locations, for example home, office and a bank deposit box.
- Back up the wallet descriptor or configuration, which lists all public keys and the threshold; without it, recovery may be impossible even with enough seeds.
- Rehearse a recovery drill with a small amount before depositing significant funds.
- Document an inheritance plan that tells heirs where keys are and how signing works, without revealing secrets in one place.
For organizations, the signer list should map to roles rather than individuals, and a written procedure should state who drafts transactions, who verifies addresses and how a departing employee’s key is rotated out.
Limitations, risks and common mistakes
Multisig removes single points of failure but introduces new ones, and most real losses come from operational errors rather than broken cryptography.
| Mistake | Consequence | Prevention |
|---|---|---|
| Missing descriptor backup | Funds cannot be reconstructed | Store the descriptor with every key |
| Blind signing | Approving a malicious transaction | Verify amounts and addresses on device screens |
| Threshold equals key count | One lost key locks funds forever | Keep M lower than N |
| Correlated key storage | One incident exposes several keys | Separate vendors and locations |
| Unaudited contract wallet | Bugs drain or freeze funds | Use widely audited contracts |
High-profile incidents have shown that attackers often target the signing interface rather than the keys: if every signer approves a manipulated transaction shown by a compromised web page, the threshold offers no protection at all. Independent verification on each device is therefore essential.
Put simply
A multisig wallet works like a safe deposit box that needs several keys turned at once. If the rule is two out of three, any two keyholders together can open it, but no single person can.
This means a thief who steals one key still cannot take the money, and an owner who loses one key can still get in with the other two. The price is more effort: every payment needs several approvals, and every key must be kept safe in its own place.
In practice
A software company holds a treasury of stablecoins and bitcoin for payroll reserves. Its finance team sets up a 3-of-5 multisig wallet: the chief financial officer, the controller and the chief executive each hold one hardware key, a fourth key sits with the company’s lawyer, and a fifth is sealed in a bank deposit box for recovery.
When a monthly transfer is needed, the controller drafts the transaction and two executives review the recipient address and amount on their own device screens before signing. When the controller later leaves the company, the remaining signers move the funds to a new wallet with a replacement key, a routine operation that takes under an hour.
The outcome is that no single employee can move company funds, the loss of any two keys does not lock the treasury, and auditors can verify the signing policy directly on the blockchain.