What Is a Multi-Signature Wallet?

TL;DR: A multi-signature wallet (multisig) is a cryptocurrency wallet that requires more than one private key to authorize a transaction. Rather than a single key controlling a wallet, multisig distributes control across multiple keys — and requires a predefined minimum number of those keys to sign before any transaction can be executed. This eliminates the single-point-of-failure risk inherent in single-key wallets and is the standard security model for high-value custody, protocol treasuries, and enterprise crypto asset management.

How Multi-Signature Wallets Work

Standard cryptocurrency wallets operate on a simple model: one private key, full control. Whoever holds the private key can sign and broadcast transactions. Lose the key, lose the funds. Have the key stolen, lose the funds.

Multi-signature wallets replace this with an m-of-n scheme: n keys are generated and distributed, and any m of them must sign a transaction for it to be valid. The values of m and n are set when the wallet is created and define the signing policy.

Common configurations:

2-of-3: Three keys exist, any two must sign. Useful for individual users who want a backup key stored separately — losing one key doesn't mean losing access.
3-of-5: Five keys exist, any three must sign. Used by organizations where multiple officers or signatories must approve transactions.
3-of-7: Common in large DAOs and protocol treasuries where decentralized control across many parties is required.

The transaction flow differs by implementation, but generally:

One keyholder initiates a transaction proposal.
The proposal is shared with other keyholders — either on-chain (for smart contract multisig) or through a coordination layer.
Each required keyholder signs the transaction with their private key.
Once the threshold of signatures is reached, the transaction is broadcast and executed.

On Bitcoin, multisig is implemented at the script level through P2SH (Pay to Script Hash) or P2WSH (Pay to Witness Script Hash) addresses. On Ethereum and EVM-compatible chains, multisig is most commonly implemented as a smart contract — the most widely deployed being Gnosis Safe (now Safe), which holds billions in assets under management across thousands of organizations.

Types of Multi-Signature Wallets

2-of-3 personal multisig. The most common individual security setup — three keys generated, one held personally (hot or cold), one stored in a separate physical location, one held by a trusted third party or recovery service. Any two sign. Losing one key doesn't lose access; stealing one key doesn't compromise funds.

Organizational multisig (3-of-5, 3-of-7). Used by companies, DAOs, and protocol teams to require multiple authorized signatories for treasury movements. Distributes trust across roles (CFO, CEO, CTO) or committee members, ensuring no single insider can unilaterally move funds.

Multi-signature hardware wallets. Hardware wallets — devices that keep private keys offline — can participate in multisig schemes. Each keyholder uses their own hardware device (Ledger, Trezor, Coldcard) to sign their portion of a multisig transaction, combining the air-gap security of hardware key storage with the threshold signing of multisig.

On-chain vs. off-chain multisig. Smart contract multisig (like Gnosis Safe) stores the signing policy on-chain and executes transactions through the contract — auditable, transparent, and programmable. Off-chain multisig (like Bitcoin's native P2SH multisig) enforces the signature threshold at the protocol level without requiring a separate contract, generally simpler but less flexible.

MPC wallets vs. multisig. Multi-Party Computation (MPC) wallets are sometimes confused with multisig — both distribute key control across parties, but through different mechanisms. MPC never constructs the full private key; instead, each party holds a key share and participates in a distributed computation to sign. MPC can appear as a single-signature transaction on-chain, offering privacy benefits, but introduces different trust assumptions at the implementation layer.

Security Benefits of Multi-Signature Wallets

Eliminates single point of failure. In a standard wallet, one compromised key means total loss. In a 2-of-3 multisig, an attacker who compromises one key gains nothing — they still need additional signatures they don't have.

Protects against insider threats. An employee with access to one key in a 3-of-5 setup cannot move funds unilaterally. Any transfer requires coordination across multiple parties, creating an audit trail and requiring collusion to circumvent.

Key loss resilience. The redundant key structure allows recovery even if one or more keys are lost, depending on the configuration. A 2-of-3 wallet survives the loss of one key; a 3-of-5 wallet survives the loss of two.

Forced review and coordination. Requiring multiple parties to approve transactions creates a natural review process — a second or third signer reviewing a transaction proposal is an additional layer of human verification against typos, errors, or social engineering attempts targeting a single keyholder.

Reduced phishing and social engineering exposure. A successful phishing attack that extracts one key from a multisig participant doesn't yield spendable funds. The attacker still needs additional keys, which forces a more complex multi-target operation.

Multi-Signature Wallet Risks and Attack Vectors

Multisig significantly raises the security bar but doesn't eliminate risk. The attack surface shifts rather than disappears.

Smart contract vulnerabilities. For smart contract multisig implementations, the security of the wallet depends on the security of the contract code. The 2017 Parity Multisig hack is the defining example: a vulnerability in the Parity wallet library contract allowed an attacker to take ownership of the library and then self-destruct it, permanently freezing approximately $150 million in funds across hundreds of wallets that depended on it. The multisig logic itself was sound; the implementation had an exploitable flaw. This is why smart contract multisig requires rigorous auditing — the contract is as much an attack surface as the keys themselves.

Coordinated social engineering. If a 2-of-3 multisig requires compromising two keyholders, an attacker shifts from targeting infrastructure to targeting people. Convincing two of three signatories that a transaction is legitimate — through impersonation, fake urgency, or phishing — is a real attack vector that multisig doesn't fully protect against.

Key custody failures. Multisig distributes keys, but each individual key still requires secure storage. A scheme where three keys all reside on the same infrastructure, or where all key backups are stored in the same location, doesn't realize the security benefits of distribution. The configuration provides the mechanism; the key management practice provides the actual security.

Signer collusion. If m of n signers are compromised or collude maliciously, the threshold is met, and funds can be drained. A 3-of-5 scheme where four of five signers are the same organization, or where multiple keyholders share key material, provides weaker guarantees than the configuration suggests.

Implementation-specific bugs. Different multisig implementations — Gnosis Safe, native Bitcoin multisig, Electrum multisig — have different security properties, upgrade paths, and potential vulnerabilities. Treating "multisig" as a monolithic security guarantee rather than examining the specific implementation in use is a common mistake in security assessments.

Conclusion

Multi-signature wallets are the standard security model for serious custody of crypto assets because they solve the most fundamental problem: single-key wallets put everything at risk the moment one secret is exposed. The m-of-n scheme forces attackers to compromise multiple parties or systems simultaneously, which dramatically increases cost and complexity. But multisig is architecture, not a guarantee. The security it provides depends entirely on how keys are distributed, stored, and managed, and on the correctness of the implementation. A multisig wallet with poor key hygiene or an unaudited smart contract can be as vulnerable as a single-key wallet in practice.