B.BlockAxis⌕ Search
Menu

Multisig: policy, backups and recovery

A multisignature arrangement requires several signatures under a defined policy, such as two of three keys.

IntermediateContent revised · 13.09.20263 min reading · allow 5–10 more minutes for the workshopBlockAxis

Your learning plan

Design for both unauthorized spending and lost access

By the end, explain the diagram in your own words, solve the case and justify the correction.

Prerequisites : Hot, warm and cold wallets · Hashes, keys and signatures

Level 2 · Intermediate →

Reading path · 21 / 35 · Intermediate

Key takeaway

A multisignature arrangement requires several signatures under a defined policy, such as two of three keys.

The essentials

A multisignature arrangement requires several signatures under a defined policy, such as two of three keys. Unlike many MPC schemes, the condition may be visible or enforced at the blockchain script or contract level. Implementation details vary by network.

How it works

Separating signers can reduce dependence on one compromised or unavailable key. It also increases coordination and backup requirements. For Bitcoin, recovering a wallet may require its descriptor or equivalent script information in addition to sufficient private keys. Losing policy data can make recovery harder even when key material survives.

What to watch

Test a complete recovery with an appropriately controlled setup before relying on the arrangement. Record key ownership, replacement procedures and the response to one compromised signer. A two-of-three wallet is weakened if two keys are stored together or if the same person can instruct every signer without independent verification.

Understand the details

A multisignature policy requires several signatures under a defined rule. On Bitcoin this can be expressed through spending conditions; on smart-contract networks it may be implemented by wallet code. The threshold is only part of the design. Signer identities, transaction review and the ability to modify the policy also matter.

Boundaries and common mistakes

Increasing the threshold can reduce unilateral action while making recovery harder. Multiple devices held by one person do not create organizational separation. Backups must preserve whatever public configuration is needed to reconstruct the wallet, and signers should review the same transaction rather than relying only on a coordinator’s summary.

The mechanism at a glance

  1. Proposed transaction
  2. Independent signer review
  3. Required signatures
  4. Policy verified on spend
Design for both unauthorized spending and lost access. Conceptual map: read these four landmarks together with the explanation above.
Applied workshop · work at your own pace

Apply the lesson to a case

Compare 2-of-3 and 3-of-3 policies when one signer is unavailable. Then compare them when one signer is malicious. Make two columns: ability to spend legitimately and ability for the attacker to spend alone.

Which policy tolerates one unavailable signer, and what assumption remains?

Choose one answer.

Terms in this lesson
MPC
Multi-party computation; threshold-signing schemes can use it to produce signatures from distributed secret shares.
Multisig
A spending policy requiring several signatures, such as two of three authorised keys.
Private key
A cryptographic secret used to authorise signatures under a signing scheme.
Prepare a correction note

Describe the passage and the proposed correction. This creates a local note for you to share; it sends nothing. Do not include personal or confidential information.