MPC (Multi‑Party Computation)
Cryptography for shared key operations.
MPC, or multi-party computation, is cryptography that lets several participants jointly compute a result without revealing their private inputs to one another. In crypto custody, MPC commonly distributes key material into shares and produces a valid blockchain signature without reconstructing the full private key in one place.
Threshold signature schemes can require a chosen number of parties to cooperate. A two-of-three arrangement may distribute shares among a user device, recovery service, and secure server. If one share is stolen, the attacker still lacks signing authority. If enough authorized shares remain, the wallet can continue after one device is lost.
MPC matters because it reduces single-key concentration and can produce a normal signature accepted by blockchains without native multisig support. Institutions use it for transaction policies, geographic separation, and controlled recovery. Embedded wallets may use MPC to provide familiar login and recovery while avoiding one server with a complete user key.
MPC differs from an on-chain multisig. A smart contract multisig publicly enforces separate signer approvals and can expose the threshold. MPC usually presents one address and signature, while policy enforcement occurs in the signing system. This improves compatibility but makes off-chain implementation and governance especially important.
The design does not eliminate trust or endpoint risk. Malware can trick participants into signing a malicious transaction. Vendors may coordinate sessions, store shares, update clients, or control recovery. Poor randomness, protocol mistakes, collusion, inaccessible shares, and undocumented succession can compromise confidentiality or availability.
Organizations should review the specific cryptographic protocol, audits, participant independence, authentication, transaction display, logs, rate limits, recovery, rotation, and vendor exit path. Test disaster recovery and staff changes. A marketing claim of “no private key” can mislead because signing authority still exists in distributed form. MPC improves resilience when its shares, software, operations, and governance are genuinely separated and securely managed.
Procurement should establish who owns key shares and whether assets remain recoverable after the provider closes or changes terms. Teams need a documented ceremony for adding, replacing, and revoking participants. Cryptographic threshold alone does not enforce business intent, so transaction policies should require independent human review, value limits, verified destinations, and alerts. Recovery must be tested without silently giving one party a path to reconstruct control.
Frequently asked questions
- MPC wallets distribute cryptographic shares and jointly produce one standard signature, so the blockchain may see an ordinary single-key account. Multisig uses separate keys and enforces a signature threshold through protocol or smart contract rules visible on-chain. MPC can support broad chain compatibility, while multisig offers clearer public policy. Recovery, upgrades, and vendor dependence differ.
- MPC is used in institutional custody, exchanges, embedded wallets, treasury systems, and consumer recovery designs where no single device or person should hold a complete signing key. Shares may be distributed across devices, people, or service providers. The complete workflow still needs authentication, transaction policy, backups, monitoring, role separation, and a plan for unavailable or compromised participants.
- MPC protocols and implementations are complex, and users may depend on proprietary coordinators, recovery services, or upgradeable software. Share compromise across the threshold, bad randomness, protocol flaws, endpoint malware, insider collusion, or failed recovery can cause loss. Evaluate independent audits, cryptographic design, access policies, portability, disaster recovery, and whether the provider can censor or reconstruct control.