About trustless MPC (tMPC)

How trustless MPC lets your signers control a vault's key without relying on io.finnet as a trusted party

Trustless Multi-Party Computation (tMPC) is how io.finnet builds on Multi-Party Computation (MPC) and Threshold Signature Schemes (TSS). It lets your signers control a vault's key without relying on io.finnet as a trusted party.

Each signer in an io.vault vault holds a key share and its own amount of signing power. To sign a transaction, the signers who approve it must together hold enough signing power to meet the vault's threshold. Until they do, the key can't be used.

This enforces your approval policy with cryptography. Try it with the interactive example below.


Set the vault threshold

The signing power needed to approve a transaction or reshare request.

2Threshold

Add signers

Each signer can approve and sign transactions and changes for this vault.

SignerSigning power
Alex Morgan
iPhone 16 ProA1b2
1
Jamie Chen
Pixel 9Jc7Q
1
Total: 2 signers2/2 Threshold met

With tMPC, each signer generates and stores its key share on its own device, not on io.vault's servers, so you don't rely on io.finnet as a trusted party. Key shares are never revealed to other signers or to io.finnet, and no full private key exists during normal operation.

tMPC is cross-platform and multi-device. People sign with the Mobile Signer on their own devices, which have full-resolution screens and secure enclave hardware, so they see what they approve instead of signing blind. For automated workflows, a Virtual Signer applies your approval policy and signs on a server.

The tMPC stack supports weighted signing (signing power), server-based signing (Virtual Signer), an offline disaster recovery process, web3 decentralised application (dApp) integration, and centralised exchange (CEX) connectivity.

If io.vault is unavailable, you recover a vault's assets with the offline, open-source disaster recovery tool. It reconstructs the private key from enough signers' backups to meet the vault's threshold, together with the key that opens each backup: a Mobile Signer's secret phrase or a Virtual Signer's recovery private key.

MPC, TSS, and tMPC work together to provide distributed trust and defence in depth for digital asset management.

Secure Multi-Party Computation (MPC)

MPC is a subfield of cryptography that enables multiple parties to jointly compute a function over their inputs while keeping those inputs private. In digital asset custody, MPC lets a private key exist only as key shares, each held by a different party.

Key properties of MPC:

  • Each party has access only to its own key share, not the full private key.
  • Signing a transaction requires a threshold number of parties to contribute their shares.
  • Even if some shares are compromised, the private key stays secure as long as the threshold isn't met.

Each of a vault's signers holds its own key share on its own device.

Threshold Signature Schemes (TSS)

TSS is a cryptographic protocol that allows a group to collectively sign a message or transaction, provided a threshold number of participants agree. Rather than using a single private key, TSS combines key shares to produce a valid signature for the corresponding public address. You set the threshold that determines how much signing power a signature needs.

You can hold key shares in different locations, with different people. If one share is stolen, the attacker can't sign unless that share alone meets the threshold.

Combined with MPC, TSS eliminates the single point of failure normally associated with self-custody of digital assets. It also lets you determine the security level for each vault (number of shares and required threshold) and distribute signing power across multiple people rather than relying on one trusted individual.

In a TSS setup:

  • A private key is split into N shares, held by N parties.
  • Any M out of N parties can collaborate to produce a valid signature (M <= N).
  • The private key is never reconstructed in full during signing.

When you start a transaction in io.vault, signing works like this:

  1. io.vault sends the transaction to every signer in the vault.
  2. Each signer that approves uses its key share to produce a partial signature.
  3. When the approving signers meet the threshold, their partial signatures are combined into a valid final signature.
  4. io.vault broadcasts the signed transaction to the blockchain network.

When no single signer meets the threshold alone, no one signer can sign a transaction, and compromising fewer signers than the threshold needs doesn't let an attacker sign. You set the threshold for each vault to balance security and availability. See Vaults, signers, and thresholds.


Did this page help you?