A key that no one holds, not even us
MPC wallets are generated jointly by the Chainvara vault and your own co-signer with 2-of-2 threshold signatures: FROST for Solana, Bitcoin, the XRP Ledger, Stellar, Aptos, Sui and TON, DKLs23 threshold ECDSA for Litecoin, Dogecoin, Tron, Ethereum and every EVM chain — every mainnet Chainvara supports. The full private key is never assembled: every signature needs both sides, and your side checks the exact transaction first.
Share 1
Chainvara vault
Share 2
Your co-signer
Valid signature
bc1p… · Schnorr (BIP-340)
Full private key: never assembled
What makes it safe
Threshold signatures
FROST (RFC 9591) from the Zcash Foundation's audited implementation, and DKLs23 threshold ECDSA for EVM chains, compiled to WebAssembly and run on both sides.
93 mainnets
Ed25519 for Solana, XRP Ledger, Stellar, Aptos, Sui and TON; BIP-340 Schnorr for Bitcoin Taproot (bc1p…); ECDSA for Litecoin (ltc1q…), Dogecoin, Tron, the Cosmos Hub, Osmosis, Celestia, Noble, Akash, dYdX, Ethereum, Base, Arbitrum, Polygon, BNB Chain and the other EVM networks (77 in all, one address on all of them).
Your side verifies
Before adding its share, the co-signer decodes the transaction itself: chain, destination, amount, token, fee and every signature hash must match what was approved.
Single-use rounds
Signing nonces are used exactly once and destroyed, even when a request is refused.
Proactive share refresh
Renew both shares whenever you want, without changing the address: a share copied before the refresh no longer works with the new one. The switch happens only after both sides confirm the same key.
Same controls as any wallet
Policies, approvals, screening and the audit trail apply unchanged before the signing rounds start.
No single point of compromise
A breach of the vault alone, or of your server alone, cannot produce a signature.
2-of-3 with a backup share
Add a third share, computed by your co-signer and sealed at once to your offline recovery key — a key you set on your own machine, never one Chainvara sends. Signing stays vault + co-signer; any two of the three rebuild the key, so losing your server or losing Chainvara loses nothing.
How it works
- 1
Run the co-signer
Install the co-signer on a machine you control and connect it in Developers.
- 2
Generate the key together
Choose MPC 2-of-2 when creating a wallet: a few rounds of key generation give each side a share, and each side checks the other's proofs.
- 3
Sign together
After approvals, the vault and your co-signer each add their share; the result is a standard signature.
Create an MPC wallet
await cv.wallets.create({
network: "bitcoin",
label: "Cold treasury",
key_mode: "mpc",
});
// → address bc1p… generated with your co-signerWorks best with
Ready to see Chainvara in action?
Start free on test networks. Move to production when your controls are in place.