How Many Signatures Are Needed to Approve a Multisig Transaction?
Multisig wallets get their name from requiring more than one signature to move funds, but the exact number required isn’t fixed across every wallet — it’s a setting chosen deliberately when the wallet is created.
The short answer
A multisig wallet requires a predetermined number of signatures out of a total set of authorized keys, commonly written as an “M-of-N” configuration — for example, two signatures out of three total keys. That threshold is set when the wallet is configured and applies to every transaction going forward unless the wallet is reconfigured entirely.
What M-of-N actually means
In an M-of-N multisig setup, N represents the total number of keys authorized to sign for the wallet, and M represents how many of those keys must actually sign for a given transaction to go through. A two-of-three wallet, for instance, has three keys in total, any two of which are enough to approve a transaction — meaning the wallet can tolerate one key being lost or unavailable and still function. A three-of-five wallet offers even more flexibility, tolerating up to two missing signers, though it also means coordinating among more people.
Common configurations and why they’re chosen
- Two-of-two. Requires both parties to agree on every transaction, often used for a shared arrangement between two people or two systems where independent unilateral action shouldn’t be possible.
- Two-of-three. A popular balance for individuals or small groups, since it tolerates the loss of one key without locking funds permanently, while still requiring agreement from more than one party.
- Three-of-five or higher. Common for organizations or larger groups managing shared funds, where requiring multiple approvals reduces the risk of any single person acting alone, whether through error or bad intent.
How the threshold gets chosen
The number of required signatures is a deliberate trade-off between security and convenience. A higher threshold relative to the total number of keys makes it harder for a smaller group of compromised or malicious signers to move funds without authorization, but it also makes routine transactions slower and more dependent on coordinating multiple people. This is a core part of how a multisig wallet can prevent a single point of failure — no individual key, on its own, is enough to control the funds.
What happens if not enough signers are available
If a transaction can’t gather the required number of signatures — because a key is lost, a signer is unreachable, or a device fails — the transaction simply cannot be executed, and the funds remain locked until enough valid signatures can be collected. This is different from a single-key wallet, where losing access to a private key alone can mean permanent loss; a well-designed multisig threshold is specifically meant to build in tolerance for exactly that kind of individual failure, much like how running a validator node depends on redundancy rather than any single point of control.
The takeaway
There’s no universal number of signatures required for a multisig transaction — the threshold is a configuration decision made when the wallet is set up, balancing how much redundancy is wanted against how much coordination each transaction will require. Understanding a specific wallet’s M-of-N setup is the only way to know exactly how many signers actually need to approve any given transfer.