Illustration of a case file representing an internal investigation into a disputed multisig treasury wallet

A multisignature wallet is adopted specifically to prevent any single person, including a founder or a trusted employee, from moving company funds alone. It is one of the better structural defenses against internal theft that exists in cryptocurrency custody. The same design that makes it resistant to a single bad actor also makes it dependent on every required signer remaining reachable, cooperative, and in possession of their key. When one of them is not, the wallet can become just as unusable as if it had been compromised, even though nothing has technically been stolen yet.

How this actually happens

We see a handful of recurring patterns behind a stalled multisig treasury. A co-signer leaves the company on bad terms and refuses to participate in transactions, sometimes explicitly using their required signature as leverage in an unrelated dispute. A co-founder becomes genuinely unreachable, through estrangement, incapacity, or in rarer cases, death, without the wallet's threshold having been designed to survive that. A signer loses their hardware device or key without a documented recovery process, which is functionally identical to that signer refusing to cooperate, regardless of intent. And occasionally, a signer acts in outright bad faith, attempting to use their position to extract a payment before agreeing to sign a legitimate transaction.

The common thread across all of these is that the wallet's security assumption, that the required threshold of signers would always be available and acting in good faith, turns out not to have accounted for ordinary business and personal disruption. A 2-of-3 or 3-of-5 scheme designed only around preventing theft, without also planning for a signer becoming unavailable, creates exactly this exposure.

What can and cannot be done technically

Once a wallet is deployed with a fixed signer set and threshold, there is generally no way to remove or replace an uncooperative signer without that signer's own cooperation, unless the multisig setup was specifically built with a recovery or key-rotation mechanism in advance. This is the uncomfortable core of the problem: the same rigidity that makes multisig secure against a single rogue actor makes it inflexible against an ordinary, foreseeable disruption to that actor's availability.

Key Point

The best time to solve a rogue-cosigner problem is before it happens, by choosing a multisig scheme with a built-in recovery path, a higher signer count than the strict minimum, or a time-locked backup mechanism. Once the wallet is deployed and a signer is already uncooperative, options narrow considerably and often shift from technical to legal.

What investigative and legal options generally exist

  • A documented record of the wallet's governance, who was designated as a signer, under what agreement, and what that agreement says about resignation, removal, or incapacity, is the starting point for any legal remedy.
  • Where a signer is refusing to cooperate for improper reasons, that refusal can sometimes be addressed through the underlying commercial agreement between the parties, particularly if the wallet's governance was documented in a shareholder or operating agreement.
  • Where funds are demonstrably at risk of being permanently locked, civil remedies such as an application to compel performance of an agreement, or in some jurisdictions a court order addressing the specific asset, may be available, though this depends heavily on the governing agreement and jurisdiction, and is a matter for qualified counsel rather than something to assume in advance.
  • A forensic review of the wallet's transaction history and signer activity can establish, independent of any dispute narrative, exactly what each signer did or did not do and when, which is often decisive in resolving a dispute about intent.

Building the next wallet to survive this

For a business setting up treasury custody today, the lesson from these cases is less about avoiding multisig and more about not treating the initial threshold configuration as a permanent, static decision. A signer set that includes a documented succession plan, a threshold with some margin above the strict operational minimum, and a written governance agreement covering what happens if a signer becomes unavailable, addresses most of what turns an isolated personnel problem into a frozen treasury.

multisig walletsbusiness treasuryinsider threatwallet governance

Related reading

How Civil Freezing Orders Are Used to Recover Stolen CryptoEvidence to Preserve in the First Hours After a Business Wallet Is CompromisedWhat Happens to a Crypto Wallet When Its Owner Dies Without a Plan