Enables secure shared custody of shielded assets requiring multiple signatures to authorize transactions, protecting treasuries and shared funds without revealing signers or balances.

FURPS+

Ai generated

This section was generated by an LLM and has not yet been human-reviewed.

Functionality

  • Support flexible M-of-N threshold configurations for transaction approval
  • Enable policy updates (change signers or threshold with consensus)
  • Provide time locks with optional delays before execution
  • Support emergency recovery mechanisms if signers are lost
  • Enable transaction queuing with proposal and approval workflow

+ (Privacy, Anonymity, Censorship-Resistance)

  • Hide signer identities (authorized signers not publicly visible)
  • Conceal threshold requirements (required number of signatures not exposed)
  • Protect balances (asset amounts and types remain confidential)
  • Private proposals (transaction proposals visible only to authorized signers)
  • Anonymous execution (transaction execution doesn’t reveal which signers approved)

Demand Validation

Potential Users: DAOs, project teams, families/groups, businesses, escrow services

Use Cases:

  • DAO treasuries: Protect multisig signers from targeted attacks
  • Project funds: Secure team funds without exposing team structure
  • Shared wallets: Families or groups managing funds privately
  • Escrow services: Multi-party agreements with confidential terms
  • Corporate treasuries: Business funds without exposing financial position

Possible Implementation

  • Threshold signatures: Cryptographic threshold signature schemes (e.g., FROST, MPC) producing single signature output regardless of number of signers
  • ZK multisig: Zero-knowledge proofs that threshold was met without revealing individual signatures
  • Privacy-preserving MPC: Distributed key generation and signing where no single party holds complete key

Technical Validation

Risks & Challenges:

  • Implementing threshold cryptography in ZK circuits
  • Coordinating signers without revealing participation
  • Handling signer rotation while maintaining privacy
  • Recovering from lost signer keys
  • Proving authorization without exposing signers

Integration Points: