Multisig Wallets
A multisig (multi-signature) wallet requires M-of-N signatures to authorize a transaction. For example, a 2-of-3 wallet needs any 2 out of 3 registered devices to sign before a transaction can be broadcast. This eliminates single points of failure and enables shared custody.
When to Use a Multisig Wallet
Section titled “When to Use a Multisig Wallet”Multisig wallets are suited for:
- Shared custody — Multiple parties must approve transactions (e.g., business partners)
- Enhanced security — Losing one device doesn’t compromise funds
- Organizational treasuries — Board approval requirements for spending
- Redundant backups — Multiple devices mean multiple recovery options
Custody Models
Section titled “Custody Models”Sigvault supports three multisig custody configurations:
Custodial Multisig
Section titled “Custodial Multisig”All keys are system-managed. The service controls multiple signing keys and can authorize transactions without user devices. Useful for automated or institutional workflows.
Non-Custodial Multisig
Section titled “Non-Custodial Multisig”All keys are held on user-controlled hardware devices. Sigvault only stores public keys and coordinates the signing ceremony. Users retain full control.
Collaborative Multisig
Section titled “Collaborative Multisig”A mix of system-managed and user-managed keys. For example, in a 2-of-3 setup, the user holds 2 hardware devices while the system holds 1 backup key. This provides both user control and a recovery path.
How It Works
Section titled “How It Works”- Device Registration — Each key holder registers their hardware device
- Wallet Creation — Define the threshold (M-of-N) and assign devices to each key slot
- Receiving — Addresses are derived from all public keys combined in a multisig descriptor
- Sending — A PSBT is built and routed to each required signer. Once M signatures are collected, the transaction is finalized and broadcast
Wallet Templates
Section titled “Wallet Templates”Sigvault provides pre-configured multisig templates:
| Template | Configuration | Use Case |
|---|---|---|
| Family Joint Wallet | 2-of-3 | Family members share custody |
| Small Business Treasury | 2-of-2 | Owner + accountant dual approval |
| Enterprise Treasury | 3-of-4 | Executive committee approval |
| DAO Treasury | 3-of-5 | Governance structure |
Creating a Multisig Wallet
Section titled “Creating a Multisig Wallet”- Register devices for each key holder
- Navigate to Wallets and select Create Wallet
- Choose a multisig template or configure a custom setup
- Set the threshold — how many signatures are required (M)
- Assign devices to each key slot (N total)
- Review and confirm
Signing Ceremony
Section titled “Signing Ceremony”When a transaction requires multiple signatures:
- The transaction initiator builds and submits the PSBT
- Sigvault tracks which signatures are still needed
- Each required signer connects their hardware device through the desktop app
- Each device displays the transaction for verification and signs independently
- Once the threshold is met (M signatures collected), the transaction is finalized
- The fully signed transaction is broadcast to the network
The signing process doesn’t need to happen simultaneously — signers can sign at different times.
Considerations
Section titled “Considerations”- Coordination overhead — Multiple signers must be available (though not at the same time)
- Threshold selection — Too low reduces security; too high increases the risk of lockout
- Backup planning — Consider what happens if one key holder becomes unavailable
- Device diversity — Using different hardware wallet brands reduces risk from firmware vulnerabilities