What Is Multi-Party Computation (MPC)?

Picture a signature that requires two people to each hold half a stamp, neither of which works alone, and neither half ever needs to be combined into a whole stamp to use it. That's roughly what multi-party computation, or MPC, does with a private key: it distributes signing authority across separate devices so the complete key never has to exist in one place, not even for a moment.

How signing works without ever assembling the full key

In an MPC setup, each device holds its own independently generated share of a key. When a transaction needs a signature, the devices run a joint mathematical process where each contributes its share of the computation and the result is a valid signature — without any device transmitting its share to the others or reconstructing the underlying key at any point. The math is built so the final signature is correct only if enough shares participate, and useless if attempted with too few.

How that differs from just keeping a backup copy

A backup copy is still a complete key sitting somewhere, waiting to be used the moment someone accesses it — the risk is concentrated wherever that copy lives. MPC shares aren't copies of each other and none of them is a smaller version of the key; each is only useful in combination with the others through the joint signing process. Compromising one device doesn't hand an attacker a usable key or even a fragment they can brute-force on their own — it just gives them one share out of a threshold that was never met.

This is one of a few approaches wallets use to distribute signing authority — see Wallet Types for how it compares to hardware and multisignature setups, and Key Security for how key exposure is generally assessed and prevented.