Multisig Wallet Recovery and Descriptors

A multisig wallet does not fail like a single-key one — losing one cosigner’s seed does not necessarily mean losing the funds, and having enough keys does not necessarily mean the wallet is easy to rebuild.

Threshold first: how many of how many

A multisig wallet is defined by a threshold — a “2-of-3” or “3-of-5” setup, for example — and recoverability starts with that number, not with counting surviving seeds in isolation. Two working cosigners out of three is normally sufficient to spend; two out of a required three is not, no matter how confident the two remaining backups look.

Signing material vs. wallet policy

Enough private keys to meet the threshold can make funds spendable. Rediscovering the exact set of historical outputs those keys control efficiently is a separate question, and depends on the wallet’s construction — cosigner public keys or extended public keys, derivation paths, script type, and ordering rules such as sorted multisig. In practice, a coordinating wallet’s saved configuration can be as valuable for recovery as an individual cosigner’s seed.

Descriptors make construction explicit

Modern output descriptors describe this construction directly rather than leaving it implicit — something like wsh(sortedmulti(2, xpub_A/…, xpub_B/…, xpub_C/…)) for a 2-of-3 wrapped multisig. Where a descriptor or an equivalent wallet-policy export survives, reconstruction is far more direct than reverse-engineering the setup from keys alone.

Derivation conventions for multisig

BIP48 defines a multi-script HD hierarchy for certain multisig setups, though wallet-specific derivation conventions also exist outside it — another reason to preserve the exact coordinating software and version alongside the keys themselves.

One lost cosigner seed is not automatically a lost wallet

Because spending only requires meeting the threshold, a single missing or destroyed cosigner backup in an N-of-M setup with more than N surviving signers does not put the funds at risk by itself. It does make the margin for a second loss thinner, and it is worth restoring the missing signer’s capacity rather than continuing to operate below the original design threshold.

Preserve the coordinator’s configuration, not just keys

Wallet-coordinator software — the application that tracks the multisig setup and assembles signatures — often stores exactly the policy information described above. Back up its configuration file or descriptor export alongside the individual signer backups: losing it can turn an otherwise-recoverable wallet into an expensive reconstruction problem even with sufficient keys in hand.

Verify reconstructed outputs against known addresses

Before relying on a rebuilt multisig configuration, confirm it derives addresses and unspent outputs that match what was actually observed on-chain — the same principle as single-key verification, but with more configuration variables that could each be subtly wrong.

Related: Wallet Seeds, Derivation Paths and Account Reconstruction · Cryptocurrency Wallet Recovery Workflow · Recovering Encrypted Wallet Files and Keystores · Recovery Copies