Multisig

Multisig (short for multi-signature) is a wallet or account setup that requires a chosen threshold of authorized signers before an action can be executed. The rule is often written as M-of-N: for example, 2-of-3 means any two of three authorized signers must approve. Multisig can reduce reliance on one key, but it cannot by itself guarantee that funds are safe.

In-Depth Explanation

The word describes an authorization rule, not one universal wallet design. Bitcoin can encode a threshold in a spending script, while Ethereum smart accounts can check approvals in contract code. In either case, the security depends on the exact rules, how signers protect their private keys, and how the arrangement is operated.

How M-of-N works

In a 2-of-3 arrangement, three public keys or signer accounts are authorized and two valid approvals are needed. Any two can meet the threshold unless the wallet adds further conditions. This can help a user tolerate the loss of one key, but only if the remaining keys are available and independent. If two of the three keys are lost, a 2-of-3 wallet may be impossible to access; if one person controls all three, the nominal threshold offers little separation of control.

On Bitcoin, a multisig script sets the number of required signatures and the set of public keys that can provide them. Bitcoin’s developer guide explains the M-of-N rule and demonstrates a 2-of-3 spend. Wallet software coordinates the signing process, but the network enforces the script condition when the transaction is spent.

Smart-account multisig

On Ethereum and other EVM networks, multisig is commonly implemented by a smart-contract account. The account stores its owners and a threshold, collects confirmations, and executes a transaction after enough valid approvals. A contract account can apply more elaborate rules too, such as a delay, a spending cap, or a recovery process. Those features are specific to the account’s code and configuration, so the word “multisig” alone does not tell you which protections are present.

Multisig, MPC, and account abstraction

Traditional multisig generally uses several distinct on-chain keys or signer accounts. Multi-party computation (MPC) instead lets participants jointly produce a signature through an off-chain protocol, often presenting a single public key on-chain. Account abstraction is a broader way to make account authorization programmable; a smart account may use a threshold rule, but account abstraction is not another name for multisig. Each design has different trust, recovery, privacy, cost, and implementation trade-offs.

What a threshold does not solve

A threshold can limit the damage from losing or compromising one signer, but the remaining signers can still be phished, collude, or approve a malicious transaction. Keys stored together can fail together. A contract bug, unsafe upgrade path, compromised interface, or weak recovery procedure can also defeat the intended policy. Ronin’s 2022 bridge incident is a reminder that a multi-party validator threshold is only as resilient as its key custody, independence, and surrounding controls.

Before relying on a setup, owners should understand who controls each key, whether those keys are kept separately, what happens if a signer becomes unavailable, how a transaction is reviewed, and whether the contract can be upgraded. Recovery plans should be tested before funds depend on them.

History

2012 — Bitcoin’s Pay-to-Script-Hash format made it more practical to receive funds locked to a script, including common multisig scripts.
2018 — Ethereum’s ERC-1271 proposed a standard interface for contracts to validate signatures, including policies used by smart-contract wallets.
2022 — After the Ronin bridge exploit, Ronin described new withdrawal thresholds, review delays, and circuit-breaker controls as part of its bridge changes.

Common Misconceptions

“Multisig makes a wallet immune to theft.” It changes the authorization rule; it does not prevent signers from being deceived, keys from being compromised together, or vulnerable contract code from authorizing the wrong action.

“A higher threshold is always safer.” A higher threshold can make unauthorized spending harder, but it also makes legitimate spending and recovery harder. The right balance depends on signer independence, availability, and the consequences of losing access.

“Every multisig works the same way.” Bitcoin script multisig, smart-contract wallets, and MPC systems have different on-chain behavior and trust assumptions. The implementation and configuration matter.

Criticisms

Coordination overhead. Signers need a reliable process to review and approve transactions, which can slow time-sensitive actions.
Recovery can be unforgiving. If too many keys are lost or the required signers cannot be reached, a valid threshold may never be met.
Visible complexity can hide concentrated control. A multi-key policy is not meaningfully distributed when one operator controls the keys or when all signers share the same devices and access systems.

Social Media Sentiment

r/ethereum: A 2023 discussion about choosing guardians for multisig and social-recovery wallets focused on balancing trusted people, signer availability, and recovery risk. It is one practical thread, not a representative survey of wallet users.

Last updated: 2026-10

Related Terms

Sources

Bitcoin Developer Guide: Transactions — Defines Bitcoin transaction scripts and explains M-of-N multisig conditions and signature ordering.
Safe Docs: Smart Account Concepts — Describes smart-account owners, approval thresholds, signature checks, and transaction execution.
EIP-1271: Standard Signature Validation for Contracts — Specifies how a contract account can determine whether a supplied signature is valid under its own authorization rules.
Ronin Network: The Ronin Bridge Is Open — Records the 2022 bridge losses and the later addition of withdrawal thresholds, review delays, and circuit-breaker controls.