✓
✓
·
threshold · 2 of 3
feature01
Multi-signature security
Customizable quorum policies like 2-of-3 or 3-of-5 protect funds with multiple signers.
§ Capabilities
Built like an instrument,
not a dashboard.
Purpose-built for securing significant Bitcoin holdings — primitives that compose into real operational security.
LDGR
JADE
BBX2
TREZR
COLD
feature02
Hardware signing
Native support for Ledger, Jade, BitBox02, Trezor, and Coldcard.
you
∅
sigvaultfeature03
Non-custodial
Your keys, your coins. SigVault never sees your private material.
wsh(sortedmulti(
2,
[6fb270de/48'/0'/0'/2']xpub6...
[35858ac5/48'/0'/0'/2']xpub6...
))
bip-388
feature04
Descriptor-based wallets
Built on BIP-388, Miniscript, and output descriptors for maximum interoperability across tools.
primaryrecovery
day 0t+180d
feature05
Time-locked recovery
Configurable recovery paths with timelocks so you never lose access, even if a device is lost.
txs · last 12m
feature06
Institutional audit trail
Every transaction logged and traceable. Compliance-ready reporting for desks and custodians.
§ Ceremony
Four steps to a
signed transaction.
No custodial step. No trust assumption beyond your own hardware.
- step · 0101
Create account
Sign up with email and set up multi-factor authentication. Identity hardened before a single satoshi ever touches the vault.
- step · 0202
Connect devices
Plug in your hardware wallets. SigVault auto-detects Ledger, Jade, BitBox02, Trezor and Coldcard — no manual configuration needed.
- step · 0303
Build your vault
Pick a template or design a custom multi-sig policy. Set quorum thresholds, time-locks, and recovery paths — all descriptor-native.
- step · 0404
Fund & transact
Deposit BTC to your vault. When sending, collect the required signatures on each device — fully air-gapped if you prefer.
§ Collaboration
Multisig with people,
not just keys.
Organizations let teams, families, and institutions hold a vault together — and keys can come from members of different organizations, without merging anyone's workspace or audit trail.
use case01
Business treasuries
Co-sign the company vault across founders, finance, and an external accountant — each from their own organization, none with custody.
use case02
Family vaults
Joint custody across households. Every member keeps their own SigVault account and shares one device into the family org.
use case03
Cross-party escrow
One key from the buyer's org, one from the seller's, one from a neutral third party. No team merge required.
use case04
DAO & partnership signers
Treasury co-signed by representatives drawn from several member orgs. Audit trails stay inside each org.
§ Trust Model
Three layers of opt-in
before a key joins a vault.
Sharing a device gives an org visibility into a public key — not authority to spend. Every layer is revocable in one click.
- layer · 0101
Join the org
Accept an invite to become a member with a defined role and a per-permission grant set.
- layer · 0202
Share a device
Opt in to expose a hardware device's public key to the org's vault builder. Revocable anytime.
- layer · 0303
Approve each vault
Explicitly consent to your key joining each specific multisig. Per-vault, never blanket.
SigVault never holds keys, signs on a member's behalf, or auto-includes a device in a vault. The org is a coordination layer, not a custodian.
§ Signing Devices
Works with the hardware
you already trust.
Five native integrations. Firmware-validated, descriptor-aware, and tested against every recent release.
6fb270de
Ledgernative
35858ac5
Jadenative
14d0c2f8
BitBox02native
455537ce
Trezornative
a1b9f4e2
Coldcardnative
§ Latest from the blog
Field notes on Bitcoin custody
§ Begin
Your keys.
Your formation.
Start with a template, or build a custom multi-sig policy from scratch. No credit card. No custodial middleman.
non-custodialopen-sourceaudit-ready