OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Security & Custody

Mpcium

Mpcium is an open-source Go infrastructure project for running resilient multi-party computation nodes that generate and manage distributed cryptocurrency wallets. It uses threshold cryptography so participating nodes hold separate key shares and produce signatures through a quorum rather than reconstructing the complete private key.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Mpcium — OpenViST project profile in Security & Custody.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Mpcium when a crypto service needs self-hosted, distributed key management with configurable t-of-n participation instead of a single process holding a complete private key.

Who it is for

  • Developers building self-hosted crypto wallet infrastructure.
  • Teams designing MPC-based custody backends.
  • Engineers experimenting with distributed key-generation and signing workflows.

Documented uses

  • Coordinate MPC nodes for distributed wallet generation.
  • Generate threshold key material across multiple nodes.
  • Produce signatures when the configured node quorum participates.
  • Store encrypted local key shares and session data.
  • Connect wallet infrastructure to Go or TypeScript client integrations.
Before you choose

Requirements & limits

The repository is public, open source and licensed under Apache-2.0. It is designed for Linux and server-based self-hosting.

  • The deployment must operate supporting NATS messaging and Consul service discovery.
  • Local key-share storage uses Badger KV with encryption settings and configurable backup locations.
  • The threshold design requires selecting the total node count and signing quorum.
  • Cryptographic support is documented for ECDSA secp256k1 and EdDSA Ed25519 workflows.
  • Integration resources are available for Go and TypeScript clients.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Configure the Mpcium infrastructure settings

Prepare the documented YAML settings for local storage, backups, messaging and service discovery.

Before you start

  • A Linux or server environment for the self-hosted nodes.
  • NATS and Consul services, with their URLs or addresses available.
  • A YAML configuration file for Mpcium.
  • A password and filesystem locations for the encrypted Badger database and backups.

Steps

  1. Set the Badger database password with badger_password and choose the local storage path with db_path.

  2. Configure nats.url with the NATS server URL and consul.address with the Consul server address.

  3. Set backup_enabled, backup_period_seconds and backup_dir for the encrypted backup policy.

  4. Review the resulting configuration before connecting the MPC nodes to the supporting services.

Expected outcome

The documented configuration values are prepared for an Mpcium node environment, including storage, backup, messaging and discovery settings.

Guide limitations

  • These settings describe configuration preparation; they do not establish that a cluster has been launched or that signing has completed.
Documentation 1 ↗Documentation 2 ↗
Evidence and transparency

Sources & review

Official repository ↗Guide documentation ↗
Source record details
Source availability
Active
Sources checked
3 October 2026
Original website title
fystack/mpcium · Official homepage title · retained in its source language
How we review sourcesSuggest a correction