Distributed key generation
You, Merkle Vault and the insurer generate shares together. No dealer ever sees a whole key, because there isn't one.
Merkle Vault splits every signing key into three shares: one for you, one for us, one for an independent insurer. Two shares sign together, the full key never exists anywhere, and nothing moves without your approval.
Waiting for 2 of 3 shares
Built for: Corporate treasuries, Exchanges, Hedge funds, Fintech apps, Payment companies, Token issuers, Banks, DAO treasuries.
You, Merkle Vault, insurer. Each one useless alone.
And your share or approval is always one of them.
Not in memory, on disk, on paper or in a backup.
Breach any one party and funds stay where they are.
Most wallets protect a key. Merkle Vault removes it. Every signing key is born as three shares, lives in three places and is never assembled, not for a signature, not for a backup, not for a recovery.
Every transfer passes your rules and your approvers before two key shares compute a signature together. No share ever leaves its home, and the private key is never rebuilt.
A teammate or your backend asks to move funds through the console or the API.
Amount limits, allow-listed destinations, time windows and screening run first.
The quorum you set signs off from their phones, with full transaction detail.
Your share and ours run the MPC protocol. The insurer's share stays at rest.
The signed transaction goes on-chain and lands in your hash-chained audit log.
Store, move, govern and issue assets from one console and one API, with the same MPC security and policy engine under every feature.
Vaults and deposit addresses across Bitcoin, EVM chains and Solana, hot to cold, with address books and sweeps.
Explore wallets →Rules on amount, asset, destination, initiator and time, checked inside the signing service before any share is used.
Explore policies →Roles, approval quorums and an admin quorum for changing the rules themselves.
Explore governance →Live balances, auto-sweeps, rebalancing, gas top-ups and batch payouts.
Explore treasury →Deploy, mint, burn and freeze tokens and stablecoins under the same approvals.
Explore tokenization →Pay counterparties by name, skip address copy-paste and settle between vaults.
Explore the network →Link exchange and prime broker accounts and move funds under the same policies.
Explore connectivity →Connect to dApps and stake, with a decoded, readable preview before anyone approves.
Explore DeFi access →Transaction screening, Travel Rule messaging and exportable, verifiable audit trails.
Explore compliance →REST API, signed webhooks and SDKs, with a sandbox that behaves like production.
Read the docs →Lose your share and the insurer's share restores access, only when you start it.
How recovery works →Give your own customers MPC wallets inside your app, under your brand.
Explore embedded →Each vault key is created as three shares and never assembled. Your share is required on every transfer, so Merkle Vault and the insurer can't sign around you, even together.
On your servers, your HSM or your approvers' phones. Required for every signature.
In HSMs inside enclaves, used only after your policy and approvals pass.
Held cold by an independent insurance partner. Used only for a recovery you start.
Any one share is useless alone. Losing one never means losing funds.
Whether you run a corporate treasury, an exchange or a stablecoin, the same 2-of-3 signing layer and policy engine adapt to your workflow.
Hold stablecoins and reserves with the controls your CFO expects from a bank portal: separate vaults per entity, approval chains by amount, and exports your auditors can read.
Merkle Vault for corporate treasury →Generate a deposit address per customer, sweep automatically, and auto-sign small withdrawals from an API key while large ones wait for people.
Merkle Vault for exchanges →Keep each fund and strategy in its own vault, move collateral to exchanges under policy, and give your administrator read-only access to everything.
Merkle Vault for funds and asset managers →Use the API to create wallets for your customers, pay out in stablecoins, and receive webhooks for every state change, with policies guarding each transfer.
Merkle Vault for fintech and payments →Deploy token contracts from audited templates and keep mint, burn and freeze rights behind MPC keys and quorums, so no single admin can print supply.
Merkle Vault for token issuers →Three common ways businesses secure digital assets, and where each one puts the risk.
A third party holds your keys and moves assets on your instructions.
Several whole keys each sign, and a smart contract checks the count.
Three shares compute one standard signature. No whole key, ever.
Want the detail? Read MPC vs multisig and custodial vs non-custodial.
Automate deposits, payouts and sweeps from your own systems. Policies and approvals run on API transfers exactly as they do in the console, and every state change fires a signed webhook.
POST /v1/transactions
{
"vault_id": "vlt_treasury_main",
"asset": "USDC_ETH",
"amount": "250000.00",
"destination": { "type": "allowlist", "id": "dst_payroll" },
"note": "November payroll"
}
→ 202 Accepted
{ "id": "tx_8f2c…", "status": "PENDING_APPROVAL" }import { MerkleVault } from "@merklevault/sdk";
const mv = new MerkleVault({ apiKey: process.env.MV_API_KEY });
const tx = await mv.transactions.create({
vaultId: "vlt_treasury_main",
asset: "USDC_ETH",
amount: "250000.00",
destination: { type: "allowlist", id: "dst_payroll" },
});
// tx.status === "PENDING_APPROVAL"from merklevault import MerkleVault
mv = MerkleVault(api_key=os.environ["MV_API_KEY"])
tx = mv.transactions.create(
vault_id="vlt_treasury_main",
asset="USDC_ETH",
amount="250000.00",
destination={"type": "allowlist", "id": "dst_payroll"},
)
# tx.status == "PENDING_APPROVAL"A flat platform fee, a small annual fee on assets under control, and overage that stays low as you grow. Insured recovery is in every plan.
Compare plans and estimate your bill →Still curious? Our learning hub explains MPC wallets, threshold signatures and treasury controls in plain language.
Merkle Vault is a non-custodial MPC wallet and treasury platform for businesses. It lets companies hold, move and govern digital assets with bank-grade controls (policies, approval quorums, audit trails) without handing their assets to a custodian or protecting a single seed phrase.
No. Every vault key is split into three shares: one held by you, one by Merkle Vault and one by an independent insurance partner. Any transfer needs two shares, and the platform is configured so that your share, or your approval, is always one of them. Merkle Vault and the insurer cannot move your assets together without you.
An MPC (multi-party computation) wallet never creates a whole private key. Instead, several parties each hold a key share and run a cryptographic protocol that produces a normal blockchain signature together. The full key never exists in any memory, disk or backup, so there is no single secret to steal.
CGGMP21 for ECDSA chains such as Bitcoin, Ethereum and other EVM networks, and FROST for EdDSA chains such as Solana. Both are peer-reviewed threshold signature schemes, and our implementation is written in Rust.
Your admins start a recovery. After a time-locked waiting period that any admin can cancel, the insurer's share and Merkle Vault's share run a one-time reshare that issues you a fresh share. Funds never move during recovery, and the old share stops working. The insurer cannot start this process on its own.
Plans start at $1,000 a month (Starter), with Growth at $4,000 and Enterprise at $12,500. Each plan adds a small annual fee on assets under control (10, 7 or 4 basis points) and low overage on outbound volume above the included amount. Insured recovery is included in every plan.
See a live 2-of-3 signing ceremony and walk through your own policy setup with our team.