On-chain wallet with multisig built in
Trustodian is a non-custodial wallet on Bitcoin, EVM, Solana, Tron, XRP, and Cardano. Multi-signature isn't an add-on. It's a first-class account type, enforced by each chain's own multisig, verifiable on the blockchain, and yours to configure signer-by-signer.
Personal wallets or shared vaults: same platform, same chains
Every account holds any mix of personal wallets and multisig vaults. Both are real on-chain addresses, both hold real balances, both can send and receive. The difference is whose signature is required to move funds.
Personal Wallets
Standard single-signer accounts on every supported chain. Generate a fresh wallet or import an existing one by private key. One EVM wallet address serves Ethereum, Base, Arbitrum, Optimism, Polygon, BNB, and Avalanche.
Multisig Vaults
Shared M-of-N accounts where every movement requires a quorum. Each signer holds an independent key. The quorum rule is enforced by the chain itself, not by a Trustodian server that could be compromised or coerced.
Four steps from wallet to on-chain quorum vault
Create or import your wallet
Pick a network, generate a fresh keypair, or import an existing wallet with a private key or your BIP-39 recovery phrase. Personal wallets are immediately usable: send, receive, and connect to dApps.
Create a vault (optional)
Add signer addresses, choose the quorum (any M-of-N up to 10 signers), and activate. On EVM this deploys a Safe; on Solana it opens a Squads vault; on BTC, TRX, XRP, and ADA it uses each chain's native multisig.
Every action is a signed transaction
Send funds, change signers, adjust the quorum. Nothing moves without the required signatures. Pending transactions sit in a shared inbox visible to every signer, with full context: recipient, amount, fee, initiator.
The chain executes on quorum
Once the last required signature is added, the transaction broadcasts automatically and settles on-chain like any other transaction. There is no Trustodian intermediary between quorum and execution.
Each chain's own multisig, none of the bridges
Trustodian doesn't wrap your BTC into an ERC-20, doesn't run funds through a router, and doesn't hold a master smart contract that owns everything. A Bitcoin vault is a Bitcoin multisig script. A Solana vault is a Squads account. An EVM vault is a Safe. The multisig lives on the chain the funds live on.
Bitcoin
Native P2SH / P2WSH multisig
Standard Bitcoin multisig scripts. No smart contracts, no bridge, no wrapped tokens. Just Bitcoin.
EVM (7 chains)
Safe smart contract wallet
Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, and Avalanche. One Safe address per vault per chain.
Solana
Squads Protocol
On-chain multisig program used by the largest SOL treasuries. Native to Solana's account model.
Tron
Native multisig accounts
Tron's built-in permission system with a signature threshold. No off-chain coordinator required.
XRP
Native SignerList
The XRP Ledger's built-in multi-signature, one of the earliest native multisig implementations in production.
Cardano
Native scripts
Cardano's script-based multisig. On-chain quorum enforcement with no smart-contract runtime needed.
book, dApps, API, notifications, audit: one platform
Address Book
Save trusted recipients with a name, chain, and category (wallet, exchange, contract, partner). Auto-suggests during Send flows. Validated per-chain: an EVM address in an EVM send, a BTC address in a BTC send.
WalletConnect & dApps
Connect any personal wallet to external Web3 apps. Uniswap, OpenSea, Aave, a custom Solana dApp. Trustodian shows up as a signer, you review the request, and sign inside the platform.
Real-time notifications
Every step of a vault transaction (submitted, signed, ready for execution, executed, failed) pushes an in-app notification. Deposits, owner changes, and threshold updates are all surfaced immediately.
API & SDK
Programmatic access with granular per-key permissions (view balances, view history, create wallet, create vault, initiate transfer, initiate withdrawal, update vault settings). Optional IP whitelist per key.
Audit log
Every account action recorded with a timestamp, IP address, device, and event type. Filter by date range and event class. Export to CSV; filtered exports contain exactly the filtered rows, not the whole database.
Organizations
Group personal wallets under an organization with a Master account and Employee accounts. Assets are segregated by workspace, so personal funds never mix with corporate funds. Grant employees access to specific wallets, revoke it instantly.
Three things we deliberately don't do
Custody products get muddled fast: half-custodian, off-chain quorum coordinators, in-house trading engines. Trustodian's boundaries are intentional and they matter for how you think about the risk model.
Not a custodian
Trustodian never holds your funds. Your keys, your wallets, your on-chain balances. If Trustodian went away tomorrow, your BIP-39 recovery phrase reproduces every wallet in any external wallet that supports the same chain.
Not MPC or TSS
Signers hold real, independent private keys, not shares of a distributed secret. Every quorum is enforced by the blockchain, verifiable by anyone. No off-chain MPC coordinator that could be compromised, coerced, or subpoenaed.
Not an exchange
No order book, no trading engine, no commingled customer funds. Trustodian is a wallet and a vault manager. Deposits go into your address, withdrawals come from your address, and the addresses are yours alone.
One wallet, every chain, real multisig
Pick the pieces you need. Trustodian doesn't require you to use all of it
Start with a personal wallet on one chain. Add a vault when a second signer joins. Wire up the API when a service needs programmatic access. The mental model is always the same: your keys, your chain, your quorum.