Trustodian

Who uses Trustodian?

Configurations from individuals to institutions: same multi-signature primitive, different signer sets. Includes a deep-dive on estate and inheritance planning further down.

Individuals & Families

Self-custody that survives you, your device, and your bad day

Multi-sig removes the single-seed-phrase failure mode. Independent keys held by trusted people or hardware devices mean no one moment (a hack, a forgotten backup, coercion) puts everything at risk.

Personal Self-Custody

The wallet you'd hold your net worth in. Multi-sig backup means a lost phone doesn't lose the account.

Typical setup

2-of-3 vault: mobile · hardware wallet · sealed backup

Why Trustodian

  • Native multi-chain from one account
  • Hardware-wallet signer (roadmap)

Family Joint Custody

Shared household savings that neither partner controls alone. Everyday spending needs both parties.

Typical setup

2-of-3 vault: partner A · partner B · attorney (dormant)

Why Trustodian

  • Independent signer keys
  • On-chain M-of-N enforcement

Long-term Savings Vault

The cold vault you rarely open. Separated from your everyday spending wallet so day-to-day activity can't touch it.

Typical setup

3-of-5 vault with geographically-distributed signers

Why Trustodian

  • Spend limits
  • Address whitelisting

Estate & Inheritance Planning

Pass digital assets on without exposing the seed phrase. Heirs and a professional co-signer become the quorum after you.

Typical setup

3-of-5 vault: you · spouse · child · attorney · trust company

Why Trustodian

  • Multiple signers
  • Comprehensive audit log
Businesses & Startups

Treasury controls that survive an employee turning bad

Corporate crypto belongs behind the same governance layer as corporate cash. On-chain M-of-N replaces the “trust the finance manager not to run off with the wallet” model with a transparent, audit-ready policy.

Corporate Treasury

Company holds stablecoins, BTC, or other assets on-balance-sheet. Every movement needs board-level authorization.

Typical setup

3-of-5 vault: CEO · CFO · COO · board members

Why Trustodian

  • Policy engine
  • Business-hours restriction

Payroll & Vendor Payments

Recurring payments to employees, contractors and suppliers, authorized through workflow, not a shared seed phrase.

Typical setup

2-of-4 vault with a whitelisted contractor address book

Why Trustodian

  • Address book with Travel Rule
  • Spend limits

Cross-Border Settlements

Move value between offices, subsidiaries, or partners in different jurisdictions without correspondent-bank delays.

Typical setup

Multi-chain vaults, one per corridor · shared signer set

Why Trustodian

  • BTC + EVM + Solana from one account
  • Audit trail

Startup Runway Vault

Co-founder multi-sig for the seed round. Nobody walks off with the treasury on a bad day, and investors see governance.

Typical setup

2-of-3 vault: founder A · founder B · lead investor

Why Trustodian

  • Free tier available
  • Programmable API
Financial Institutions

The custody layer for regulated money

Exchanges, fund managers, family offices and other regulated custodians need on-chain enforcement they can prove to auditors, not a black-box MPC vendor's word.

Exchange Cold Storage

The vault that holds customer BTC / ETH / SOL between hot-wallet top-ups. Institutional-grade quorum, on-chain proof.

Typical setup

5-of-9 vault with geographically-distributed hardware signers

Why Trustodian

  • Native chain multisig where possible
  • Comprehensive audit log

Fund Management

Crypto hedge fund or venture fund holding portfolio assets. LP-visible governance without exposing LP identities.

Typical setup

3-of-5 vault: GP · CIO · compliance · custodian · limited partner rep

Why Trustodian

  • API for portfolio operations
  • Business-hours restriction

Family Office / Multi-Generation Wealth

Multi-generation family wealth custody. Family members and professional managers share governance across decades.

Typical setup

3-of-6 vault: patriarch · heirs · advisor · attorney · trust company

Why Trustodian

  • Multiple organizations (roadmap)
  • Signer rotation
DAOs & Web3

Treasury governance the community can verify

DAOs, protocols and Web3 collectives already vote on-chain. Their treasury custody should be verifiable in the same way: no off-chain MPC coordinator, no vendor able to intercept a transaction.

DAO Treasury

Community-governed treasury with core-contributor multi-sig. Executes votes with an on-chain quorum.

Typical setup

5-of-9 vault mirroring the multi-sig council structure

Why Trustodian

  • Full on-chain transparency
  • dApp integrations

Protocol Treasury

Protocol-owned liquidity, insurance funds, and grant reserves. Native to the chain the protocol lives on.

Typical setup

Native multisig on the protocol's home chain

Why Trustodian

  • Native BTC / EVM / SOL support
  • API for programmatic ops

Grant Program Treasury

Ecosystem grant treasury. Grants committee co-signs disbursements to approved recipients.

Typical setup

3-of-5 vault: grants committee · with an approved-address book

Why Trustodian

  • Address whitelisting
  • Spend limits per grantee
Non-profits, Foundations & Developers

Purpose-built vaults and programmatic access

Registered charities, foundations, and software teams get the same custody primitives with governance shaped to their operating model.

Charitable Foundations

Registered charity holds donated crypto. Board approves disbursements; regulators see the audit trail.

Typical setup

3-of-5 vault mirroring the foundation's board

Why Trustodian

  • KYB verification
  • Public transaction record

AI Agents & Autonomous Payments

An AI agent, service, or automation needs to make small payments, with strict limits, screening, and human override for anything unusual.

Typical setup

Personal wallet with x402 delegated key + Safe Allowance Module

Why Trustodian

  • x402 add-on
  • Per-tx / daily / monthly caps

SaaS Merchant & API Billing

Accept and settle payments in crypto via API. Programmatic access with the same governance the human dashboard uses.

Typical setup

Vault with an IP-whitelisted API key for automated flows

Why Trustodian

  • Granular API scopes
  • KYT screening on every recipient

Real setups

How some of them actually run

The same M-of-N primitive, with the signers, chains and quorums each one uses.

1/5

Web3 · Base · Ethereum

A DAO's operating treasury

Four core contributors, three community-elected members. The signer set rotates every quarter — the rotation itself is a multisig transaction.

“The community doesn't have to trust us; they can watch the quorum on-chain.”

2/5

Fiduciary · BTC · Cardano

A family trust

Two trust attorneys, the grantor, their partner, and their sister. The estate keeps moving even if two signers disappear.

“The court doesn't care about our governance. It cares about the audit trail.”

3/5

Business · USDC on Base

A Series-A startup treasury

Two co-founders, CFO, external general counsel, ops lead. Business-hours-only. Weekly payroll runs against the same vault.

4/5

Family Office · BTC · Ethereum

A family office

Second-generation principal, three family members, two external advisors, three hardware-only signers.

“We do private banking-grade custody. We just don't need a private bank to do it.”

5/5

Non-profit · USDC · XRP

A refugee-relief non-profit

Five-person board, treasurer, external auditor. Address book locked to two field-office wallets — no ad-hoc payments.

Deep dive

Estate & Inheritance Planning

The multi-signature primitive is the foundation of every serious crypto-inheritance plan. Below are two sample vault configurations, one for a family and one for institutional wealth, and an honest look at what Trustodian handles today and where the gaps still are.

Family

2-of-3 family vault

During life: you + your partner sign day-to-day movements. After your death: your partner + the attorney unlock the estate. The attorney's key stays sealed with written instructions until it's needed.

A

You

Mobile signer

You
B

Spouse / partner

Mobile signer

Family
C

Estate attorney

Hardware wallet, sealed with instructions

Professional
// during life
A + B → 2-of-3 quorum

// after estate trigger
B + C → 2-of-3 quorum

Family office / high-value estate

3-of-5 vault with professional fiduciaries

Multiple family members plus an estate attorney and a licensed trust company. Any three of the five can execute. Heirs alone can't collude below quorum, and the estate isn't hostage to any single professional retiring or firm closing.

A

You

Mobile signer

You
B

Spouse / partner

Mobile signer

Family
C

Adult child / heir

Mobile signer

Family
D

Estate attorney

Hardware wallet

Professional
E

Licensed trust company

Institutional signer

Professional
// any 3 heirs / fiduciaries
Any 3 of B, C, D, E → executes

What Trustodian handles today

  • Independent signer keys: no single seed phrase to hand off
  • M-of-N up to 10 signers (Enterprise) for realistic family + fiduciary configurations
  • On-chain quorum enforcement: the estate isn't dependent on Trustodian's continued existence
  • Multi-chain from a single account (BTC, EVM, SOL, TRX, XRP, ADA)
  • Comprehensive audit log: evidence for probate and executor review
  • KYB-verified professional signers (attorney, trust company)
  • Hardware-wallet signers on the roadmap for cold, sealed heir keys

Honest gaps to plan around

  • No native “dead-man’s switch” (inactivity trigger) yet; heirs currently need to know when to act rather than the vault triggering on its own
  • No legal-document generation; will language, executor instructions and jurisdiction handling stay with your attorney
  • Bitcoin native multisig can't rotate signers without moving funds to a new address (Safe on EVM and Squads on Solana can)
  • On-chain multisig signers see vault balances; inheritance privacy from heirs during life needs procedural sealing
  • Jurisdiction-specific rules (forced heirship, digital-asset statutes) are not encoded in-product

One primitive, many configurations

Your use case doesn't have to match a template. It just has to fit an M-of-N.

Everything on this page is a variation on the same technical primitive: independent signer keys, on-chain quorum, comprehensive audit log. If your use case isn't listed but sounds like it belongs on the page, it probably works. Talk to us.