The platform

Twelve tools. One keythat never exists.

Every module runs on the same 2-of-3 MPC signing layer and the same policy engine, so a rule you write once protects the console, the API and every chain.

MPC wallets

A vault for every entity, desk and use case.

Create unlimited vaults and deposit addresses across Bitcoin, EVM chains and Solana. Choose hot, warm or cold signing per vault, and keep cold vaults behind an extra offline approval. Each vault is backed by its own 2-of-3 key set, so a problem in one never touches another.

  • EVM chains, Bitcoin, Solana and more from one key set per signature type
  • Deposit addresses per customer, with automatic sweeps
  • A gas station keeps fee balances topped up across chains
  • Address book with labels, so approvers see names, not hex
VaultsIllustrative
Treasury · MainWARM · 6 ASSETSActive
Reserves · ColdCOLD · OFFLINE APPROVALCold
Payouts · OpsHOT · AUTO-SIGN UNDER $10KHot
Customer depositsPER-CUSTOMER ADDRESSES · SWEEP HOURLYSweeping
Policy engine

Rules in plain language, enforced before signing.

Write who can send what, where and when. Rules run inside the signing service, so even a compromised dashboard session or leaked API key can't get around them. The first matching rule decides: allow, require approval or block.

  • Conditions on amount, asset, vault, destination, initiator and time
  • Velocity limits per hour, day or rolling window
  • Dry-run any rule change against last month's transfers
Policy · outbound transfers4 rules
IFamount > $100,000ANDvault = TreasuryTHENrequire 2 of Finance
IFdestination not allow-listedTHENblock
IFinitiator = API key "payouts"ANDamount < $10,000THENauto-approve
IFscreening risk = highTHENblock and alert Compliance
Governance

Nobody changes the rules alone. Including admins.

Roles separate who proposes, approves, signs and audits. Changing a policy, adding a user or editing the allow-list needs its own admin quorum, recorded in a hash-chained audit log you can verify offline.

InitiatorApproverAdminAuditor (read-only)API signer
Admin change · add user● Awaiting quorum
CFCFOApproved
CTCTOApproved
COCompliancePending

Quorum: 3 of 3 admins for user changes. Each approval is signed on the approver's phone and written to the audit log.

Treasury automation

Balances that manage themselves, within limits you set.

See every vault, exchange account and chain in one ledger. Automate sweeps, rebalancing and batch payouts, all still checked by policy, so automation never means a bot with unlimited access.

  • Batch payouts from CSV or API, one approval per batch
  • Fiat value at transfer time for accounting exports
  • Daily statements per entity and vault
Balances · last 12 weeksIllustrative
Auto-sweep
Deposits → Treasury, hourly
Rebalance
Keep Ops at $250k
Gas station
Top up below 0.2 ETH
Tokenization

Issue and govern your own tokens.

Deploy token contracts from audited templates, then mint, burn, freeze and upgrade with the same approval quorums as any transfer. Built for stablecoins, deposit tokens and tokenized funds.

ERC-20ERC-721 / 1155SPLRole-based mint
Settlement network

Pay counterparties by name, not by address.

Connect with other Merkle Vault customers once, then send to them without copying addresses. Fresh deposit addresses are exchanged automatically, which removes address-poisoning and clipboard-swap risk.

Your vaultCounterparty
Insured recovery

Lose your share, not your assets.

If your share is lost or a device is destroyed, you start a recovery. The insurer's share and ours run a one-time reshare, and you receive a fresh share. The insurer can't start this process, and the key is never reassembled.

Step 1

You request recovery

Signed by your admin quorum, with identity checks.

Step 2

Time-lock window

A waiting period during which any of your admins can cancel a fake request.

Step 3

Insurer co-signs a reshare

Shares B and C refresh the key set. Funds never move.

Step 4

You hold a new share

The old share stops working everywhere.

And the rest of the stack.

Exchange connectivity

Link exchange and prime broker accounts by API key, see balances next to your vaults, and move funds under policy.

DeFi and staking

Connect to dApps through WalletConnect, stake on supported networks, and see a decoded, readable preview before anyone approves.

Compliance

Transaction screening through a leading KYT provider, Travel Rule messaging, and audit exports built for SOC 2 and regulators.

Developer API

REST API, signed webhooks, SDKs for Node, Python and Go, and a testnet sandbox with the same policy engine.

Read the docs →

Embedded wallets

Offer MPC wallets to your own users inside your app, where each user's device holds their share.

Mobile approvals

iOS and Android apps for approvers, with biometric sign-off and full transaction detail on screen.

Platform FAQ

How the pieces fit.

Which blockchains does Merkle Vault support?

ECDSA chains such as Bitcoin, Ethereum and EVM networks (Arbitrum, Base, Optimism, Polygon, BNB Chain and others) through CGGMP21, and EdDSA chains such as Solana through FROST. One key set covers every chain of the same signature type. The full list will be published at launch.

Where do policies run?

Inside the signing service, next to Merkle Vault's key share, not in the dashboard. A compromised browser session or API key cannot skip a rule, because share B refuses to sign anything that fails policy.

Can we test policy changes before they go live?

Yes. Dry-run any rule change against your past transfers to see exactly what would have been allowed, held for approval or blocked. Applying the change still needs your admin quorum.

Do approvers need special hardware?

No. Approvers use the Merkle Vault iOS or Android app, with biometric sign-off and the full, decoded transaction on screen. Enterprise customers can also approve with hardware keys.

See your own policies running on test funds.

We set up a sandbox workspace with your vault structure and approval rules in the first call.