Cowrie Research

mpcvault-primary-sources-2026-04-26

3 min read

MPCVault primary-source snapshot

Fetched: 2026-04-26 UTC

1) Official docs overview

Source: https://docs.mpcvault.com/

Selected excerpts from the official docs:

MPCVault is a non-custodial wallet for teams built on multi-party computation (MPC) technology.

MPCVault splits your key into three shares distributed across your device and two separate cloud environments. All three shares are required to sign transactions—no single party ever has complete control.

Additional signals from the docs:

  • The overview frames MPCVault as team-oriented operational infrastructure rather than as a retail wallet
  • The docs emphasize self-custody, multi-chain coverage, batch payments, DeFi access, API automation, cards, and off-ramp flows in one surface
  • The product scope looks more like a wallet control plane than a narrow custody feature

2) Architecture docs

Source: https://docs.mpcvault.com/architecture.md

Selected excerpts from the architecture docs:

MPCVault uses a 3-of-3 multi-party computation (MPC) setup.

Share 1 | You | Your device Share 2 | MPCVault | Google Cloud | AMD SEV Share 3 | MPCVault | Microsoft Azure | Intel SGX

All three shares are required for signing. No single party ever has access to the complete private key.

Additional signals from the docs:

  • The multi-cloud / mixed-TEE design is a core differentiator and part of the trust model, not an implementation footnote
  • The docs explicitly position the product against counterparty risk and describe recovery/export paths, which is unusually helpful for cataloging the operational model
  • This supports classifying MPCVault as institutional wallet infrastructure rather than as a simple “multisig wallet” brand

3) API overview

Source: https://docs.mpcvault.com/api-reference/overview.md

Selected excerpts from the API docs:

Integrate MPCVault into your applications with our REST and gRPC APIs.

What You Can Build

  • Automated Transactions
  • Deposit Addresses
  • Batch Payments
  • Message Signing

Additional signals from the docs:

  • The official API surface spans wallet creation, balances, signing requests, batch payments, and network support, indicating a programmable backend platform rather than only a web dashboard
  • REST plus gRPC support and a builder-oriented signing flow reinforce that MPCVault expects direct developer integration into treasury and operational systems

4) Client signer docs

Source: https://docs.mpcvault.com/guides/18-how-to-enable-api/client-signer.md

Selected excerpts from the client-signer docs:

The client signer is a Docker container that:

  1. Maintains a secure connection to MPCVault
  2. Receives signing callbacks when you call ExecuteSigningRequests
  3. Approves transactions based on your callback server’s response

Docker image: ghcr.io/mpcvault/client-signer:latest

Additional signals from the docs:

  • MPCVault publishes concrete automation runbooks rather than just saying an API exists
  • The callback-based approval flow, Docker deployment guidance, health checks, and Node.js example handler make the operational integration surface explicit
  • This is strong evidence that MPCVault is meant for production treasury/workflow automation, not only manual multisig approvals

5) Docs index and public API repo

Source: https://docs.mpcvault.com/llms.txt Source: https://github.com/mpcvault/mpcvaultapis Source: https://raw.githubusercontent.com/mpcvault/mpcvaultapis/main/README.md

Selected excerpts from the materials:

This repo contains public interface definitions of MPCVault APIs.

MPCVault APIs use Protocol Buffers version 3 (proto3) as the Interface Definition Language (IDL) to define the API interface and the structure of the payload messages.

Additional signals from the docs and repo:

  • The docs index exposes a surprisingly broad first-party surface including architecture, encryption, key export, key refresh, cards, off-ramp, transaction policies, and API references
  • The public proto repo reinforces that the product has a real machine-facing integration layer, not just private enterprise docs
  • The docs-plus-proto combination makes MPCVault especially legible as wallet / signing / treasury operations infrastructure

Notes

  • This pass did not locate a classic standalone MPCVault whitepaper or litepaper.
  • MPCVault appears best categorized as institutional MPC wallet infrastructure / wallet control plane / programmable signing platform.
  • The strongest primary materials were the official docs overview, architecture page, API overview, client-signer runbook, docs index, and public API definitions repo.

Graph View