Security model

Security you can check,not just trust.

Here is exactly where each key share lives, who can use it, and what an attacker gets if they break into any one of us.

Threshold

2 of 3

Full key assembled

Never

ECDSA protocol

CGGMP21

EdDSA protocol

FROST

Key lifecycle

Five moments in the life of a vault key.

At no point in this lifecycle is a whole private key written to memory, disk or paper.

1 · Create

Distributed key generation

All three parties generate their shares together in a ceremony. There is no dealer who ever sees the whole key.

2 · Sign

Threshold signing

Your share plus ours produce a standard signature after policy and approvals pass. The chain sees a normal transaction.

3 · Refresh

Proactive refresh

Shares are re-randomised on a schedule. The address stays the same; old shares stop working.

4 · Recover

Client-started recovery

If you lose your share, your admins start a time-locked reshare that the insurer co-signs.

5 · Exit

Documented exit

If you leave, you move funds to keys you control through a published procedure.

Threat model

What an attacker gets if they break in.

We designed for the case where any one party is fully compromised. These are the outcomes.

If this is compromisedThe attacker hasCan they move funds?
Merkle Vault's systemsShare B onlyNo. Every signature needs your share A.
The insurerShare C onlyNo. Share C only takes part in a recovery your admin quorum starts.
Your signing serverShare A onlyNot without passing your policies and approvers, which run on our side, in the signing service.
One approver's phoneOne approval voteNot above that approver's limit. Quorums need more than one person.
A Merkle Vault insiderAt most share BNo. HSM access needs two people, and share B alone can't sign.
Merkle Vault goes offlineNothingYour funds stay safe, and the exit procedure lets you recover them without us.

Infrastructure

  • Share B is stored in hardware security modules, used only inside isolated enclaves
  • Two production regions, each with a disaster-recovery site
  • No standing human access to production. Break-glass access needs two people and is logged.
  • Signing nodes are separate from the dashboard and API front ends
  • Memory-safe Rust core for the MPC protocols and signing service

Monitoring and audit

  • Every action lands in a hash-chained audit log you can export and verify offline
  • 24/7 security monitoring and on-call response
  • Independent cryptographic audit of our CGGMP21 and FROST implementation before general availability
  • Penetration tests every year, with summaries shared under NDA
Compliance plan

Certifications on a public timeline.

We publish what we have and what is in progress. Dates update here as audits complete.

StandardScopeStatus
SOC 2 Type ISecurity, availability, confidentialityPlanned for 2027
SOC 2 Type IISame scope, 12-month windowPlanned for 2028, then yearly
ISO/IEC 27001Information security managementPlanned for 2029
Cryptographic auditMPC library and signing serviceBefore general availability
Public bug bountyWeb app, API, signing servicePlanned for 2028
Security FAQ

Hard questions, straight answers.

Can Merkle Vault employees move our funds?

No. Our share (share B) cannot sign alone, and every signature also needs your share A. Access to the hardware security modules that protect share B requires two people and is logged.

What if Merkle Vault is hacked?

An attacker who fully compromises our systems gets share B only. Without your share A they cannot produce a signature, and your policies still run inside the signing service.

What does proactive share refresh mean?

On a schedule, all parties re-randomise their shares without changing the public key or your addresses. A share stolen before a refresh becomes useless after it, which limits the window an attacker has to collect two shares.

Is the full private key ever reconstructed?

Never. Keys are created with distributed key generation, so there is no dealer, and signing uses threshold protocols that output only the signature. Recovery reshares the key rather than reassembling it.

What happens if Merkle Vault shuts down?

A documented exit procedure lets you move your funds to keys you control. We publish the procedure so you can verify it before you deposit. [Confirm final exit design before launch.]

Responsible disclosure

Found a vulnerability? Tell us first.

Email the details to our security team. We reply within one business day, keep you updated while we fix it, and credit you if you want.

Security contact
security@merklevault.io

Machine-readable contact details are at /.well-known/security.txt. Please read our Responsible Disclosure Policy and never test against other customers' data.

Bring your security team. We'll bring the threat model.

We walk your security team through the architecture and share detailed documentation under NDA.