Multisig Decision Framework

Helps users understand multisig wallets, decide when multisig is appropriate, and design signer configurations for personal, family, or small-organization use.

Overview

Multisig Decision Framework helps users understand multi-signature wallets — what they are, when they make sense, and how to design a signer configuration that matches their security goals. It covers M-of-N logic, threshold selection, signer distribution, common pitfalls, and recovery planning.

This skill does not recommend specific multisig wallet providers, inspect smart contracts, or verify on-chain data. It works from user-provided context and general multisig design principles.

When to Use This Skill

Use this skill when:

• You are managing a shared treasury or organizational funds.
• You want additional security for significant personal holdings.
• You are setting up a family crypto account.
• You ask "should I use a multisig wallet?"
• You want to understand M-of-N thresholds and signer configuration tradeoffs.

Core Workflow

1. Ask about the use case: personal security, shared control, organizational treasury, or inheritance setup.
2. Ask about the people involved: number, locations, technical comfort, and availability.
3. Explain multisig fundamentals: M-of-N logic, threshold reasoning, signing flow, and how multisig differs from single-key wallets.
4. Help the user choose an appropriate threshold based on security needs, signer availability, and failure scenarios.
5. Identify common multisig pitfalls: all keys in one location, inaccessible signers, threshold too high or too low.
6. Design a signer distribution plan and a recovery procedure for lost signers.

Output Format

For each evaluation, the skill provides:

• Use case classification — personal, shared, organizational, or inheritance
• Recommended threshold and rationale — why this M-of-N fits the scenario
• Signer distribution plan — who holds which keys and where
• Common pitfalls to avoid — configuration mistakes specific to this use case
• Signer loss recovery procedure — what to do if a signer becomes unavailable
• Decision summary — key tradeoffs and next steps

Safety Boundaries

This skill cannot and will not:

• Recommend specific multisig wallet providers or smart contract implementations.
• Verify the security of any particular multisig setup or its underlying contracts.
• Guarantee that multisig prevents all forms of theft or loss.
• Access any on-chain data, verify signer addresses, or inspect multisig contracts.

Important disclaimer: Multisig introduces smart contract risk. All signers being compromised simultaneously, or a contract bug, can still result in total loss. Multisig reduces certain risks (single key compromise) but does not eliminate risk. Verify the specific contract's audit history and deployment parameters independently.

Refusal example: "I cannot confirm that a 3-of-5 Safe on Ethereum mainnet is secure. Multisig contracts can have bugs. You should verify the specific contract's audit history and deployment parameters independently."

Examples

Example: Family Shared Treasury

User provides: "My partner and I want to set up a shared crypto wallet for long-term savings. We also want our adult child to be able to access it if something happens to both of us."

Skill response:

• Use case classification: Shared control with inheritance consideration.
• Recommended threshold: 2-of-3.
  • Rationale: Any two of the three can move funds. This allows normal operation (you + partner) while preventing any single person from unilaterally accessing funds. If one person is incapacitated, the other two can still operate. If both you and your partner are incapacitated, your child plus either of you (if recovered) can access.
• Signer distribution plan:
  • Signer 1: Your hardware wallet, stored securely at home.
  • Signer 2: Your partner's hardware wallet, stored securely at home (different location within the home).
  • Signer 3: Your child's hardware wallet, stored at their residence.
• Common pitfalls to avoid:
  • Do not store all three signer devices in the same physical location — a single fire or theft event would compromise quorum.
  • Choose a threshold that works when one signer is unavailable (2-of-3 passes this test; 3-of-3 would not).
  • Ensure all signers understand how to use the multisig and have practiced signing at least once on testnet.
• Signer loss recovery: If one signer is permanently lost, you can replace them by having the remaining two signers execute a signer-replacement transaction. The key is that you always maintain quorum (2 signers) while replacing the lost third.
• Decision summary: 2-of-3 provides a good balance. The child has access only with one parent's cooperation during normal times, but full access if both parents are unavailable. Next step: choose a multisig platform and practice the setup on testnet first.

Acceptance Criteria

• Explains M-of-N logic clearly without jargon.
• Helps user choose appropriate threshold with rationale.
• Identifies common multisig mistakes (all keys in one place, threshold too high/low).
• Includes signer-loss recovery planning.
• Does not recommend specific multisig products.
• All responses in English.
• No code execution, API calls, wallet connections, or live chain queries.