DAO & Partnership Signers

DAOs and multi-party partnerships share an awkward requirement: a common treasury that no single member controls, signed by representatives who each answer to a different organization. Putting everyone into one shared account defeats the purpose — it collapses separate members into a single group and tangles their audit trails together. What these treasuries actually need is a quorum assembled from independent orgs.

SigVault's cross-organization key sharing is built exactly for this. Keys can come from members of different organizations, and each org keeps its own workspace, roles, and records.

The shape of a partnership treasury

A threshold policy — for example 3-of-5 — with one key contributed by each member organization:

• Five member orgs, each nominating one representative
• Each representative signs with their own hardware wallet
• Any three of the five can authorize a disbursement

Raise or lower the threshold to match how much consensus a payment should require. A larger treasury might use 4-of-7; a tight partnership might use 2-of-3.

How it works in SigVault

1. Each member organization stays separate. Every org has its own SigVault workspace; representatives sign in to their own accounts.
2. Connect hardware wallets. Each representative uses their own device — Ledger, Jade, BitBox02, Trezor, or Coldcard — and only the public key is read.
3. Share one device per org into the treasury vault builder. Sharing exposes a public key to the shared vault; it grants visibility, not authority, and is revocable at any time.
4. Build the threshold vault. SigVault assembles a descriptor-based multisig (BIP-388), portable and auditable across the ecosystem.
5. Each representative approves the specific vault, per-vault and never blanket.

wsh(sortedmulti(
  3,
  [org-a/48'/0'/0'/2']xpub6...,
  [org-b/48'/0'/0'/2']xpub6...,
  [org-c/48'/0'/0'/2']xpub6...,
  [org-d/48'/0'/0'/2']xpub6...,
  [org-e/48'/0'/0'/2']xpub6...
))

Governance in practice

When the DAO votes to fund a proposal, a representative drafts the transaction in SigVault and it routes to the other signers. Each one reviews the amount and destination on their hardware wallet and signs. Once the threshold is reached — three of five — the payment broadcasts. No representative can move treasury funds alone, and no member organization can be out-voted into losing custody, because the keys are physically distributed across independent parties.

Audit trails stay inside each organization. Sharing a device into the shared treasury never exposes an org's internal workflow, members, or records to the others.

Why partnerships trust it

• Distributed custody. No single org or person controls the treasury.
• Independent members. Each organization keeps its own workspace and audit trail.
• Tunable consensus. Set the threshold to match your governance rules.
• Revocable participation. Any org can withdraw a shared device; approval is always per-vault.