Once teams start using multisig wallets in real operations, a very practical concern shows up.

Can a single signer block or delay transactions?

The honest answer is yes, depending on how the multisig is designed. This is not a bug. It is a direct consequence of how shared control works. Whether that ability is a feature or a problem depends entirely on context.

Understanding this is critical for DAOs, foundations, and treasuries, because most multisig failures are not technical. They are governance failures.

How Blocking Happens in a Multisig

A multisig wallet executes transactions only when the required number of approvals is reached. If that threshold is not met, nothing happens.

In a 2-of-3 multisig, one signer cannot block transactions indefinitely, because the other two can approve and move forward without them.

In a 3-of-5 multisig, up to two signers can be inactive or uncooperative without blocking progress.

Blocking becomes possible when the number of unresponsive or dissenting signers is large enough that the approval threshold cannot be reached.

This is not malicious by default. It is simply how the rules work.

Blocking vs Legitimate Governance Friction

It is important to distinguish between malicious blocking and legitimate disagreement.

Multisig wallets are often used to enforce consensus. If signers disagree about a transaction, the wallet is doing exactly what it was designed to do by preventing execution.

This kind of friction is healthy when it reflects real governance concerns, such as questionable spending, unclear authority, or missing approvals.

Problems arise when blocking becomes accidental, persistent, or personal rather than principled.

When Blocking Becomes a Real Risk

Blocking turns into a serious issue in a few common scenarios.

One is signer inactivity. A signer goes on vacation, leaves the organization, or loses access to their key without telling anyone. If the multisig threshold is tight, progress can stall.

Another is poor signer distribution. If multiple signer keys are controlled by the same person or closely aligned parties, internal conflicts can paralyze the wallet.

A third is poorly chosen thresholds. A multisig that requires near-unanimous approval may look secure, but in practice it can be fragile and slow.

These problems are not hypothetical. They are common in early DAOs and fast-growing teams.

How Professional Teams Design Around Blocking

Experienced teams assume that signers will sometimes be unavailable or disagree. They design multisig wallets to tolerate that reality.

This usually means choosing thresholds that allow progress even when one signer is inactive, such as 2-of-3 or 3-of-5. It also means having clear expectations around signer responsiveness and decision timelines.

Many teams also separate concerns by using different multisig wallets for different purposes. An operational wallet might use a lower threshold for speed, while a treasury wallet uses a higher threshold for protection.

Tools like Safe support this kind of flexibility, including signer rotation and threshold changes through approved transactions.

Can a Signer Abuse Blocking Power?

Yes, but only within the rules of the multisig.

If a signer refuses to approve transactions, they can slow things down. What they cannot do is unilaterally move funds or override other signers.

In well-designed setups, persistent blocking can be resolved by governance actions, such as removing or replacing the signer, as long as the approval threshold can still be met.

Blocking power is not absolute. It exists only as long as the governance structure allows it.

Why This Is a Governance Question, Not a Technical One

Multisig wallets enforce rules. They do not decide what is fair or reasonable.

If a multisig wallet becomes unusable because of blocking, the root cause is almost always a mismatch between the governance model and the operational reality.

Good multisig design reflects how decisions are actually made, not how they are imagined on paper.

What Investors Look For

Investors and auditors increasingly look beyond whether a multisig exists. They look at how it is configured.

Reasonable thresholds
Independent signers
Clear signer roles
Documented processes for removing or replacing signers

These details determine whether blocking is a safeguard or a liability.

The Bottom Line

Yes, a signer can block or delay transactions in a multisig wallet if the approval threshold cannot be met.

This is not a flaw. It is the mechanism that enforces shared control.

The goal of multisig design is not to eliminate disagreement. It is to ensure that disagreement does not permanently paralyze the organization. When governance and thresholds are aligned, multisig provides protection without gridlock.