A multi-party computation (MPC) wallet protects assets by splitting a private key into multiple shares held by different parties or devices. No single party ever holds the complete key, and transactions are signed collaboratively without ever reconstructing it.
The problem with a single key
A conventional wallet rests on one private key, usually backed up as a seed phrase. Whoever holds that secret holds everything. If it is stolen, funds are lost; if it is lost, so is access.
That is a heavy burden for an individual and an unacceptable one for an institution, where no single person should be able to move treasury funds alone.
Backups help, but each copy is another place the secret can leak. The more copies exist, the larger the attack surface becomes.
Hardware wallets improved matters by keeping the key inside a dedicated device, but the device itself can still be lost, damaged or coerced, and it is still one point on which everything depends.
How MPC works
Multi-party computation is a branch of cryptography in which several parties jointly compute a result without any of them revealing their own input. Applied to wallets, the key is never assembled in one place.
- Key generation — the parties run a protocol that produces shares. The full key is never created as a single value.
- Distribution — each share is held separately, for example on a user device, a server and a hardware-protected module.
- Signing — to approve a transaction, the shares take part in a protocol that outputs a valid signature. No share is revealed and the key is not reconstructed.
To the blockchain, the result looks like any ordinary signature from a single key.
Because the protocol never builds the key, there is no moment at which malware on a single machine could capture it whole. An attacker would have to compromise several separate environments at the same time.
There are several MPC signing schemes, each with different assumptions about how many parties may be dishonest and how many must take part. Choosing one is an engineering decision that should be documented, reviewed and tested, rather than taken on trust from a vendor description.
Why it is powerful
- No single point of failure — compromising one share is not enough.
- No seed-phrase liability — there is no single secret to lose or steal.
- Flexible policies — require multiple approvals for sensitive actions.
Refreshing shares
Shares can be periodically refreshed, producing new ones while leaving the public address unchanged. An attacker who obtains an old share gains nothing once it has been replaced, which narrows the window in which a breach can do damage.
Policy can be tied directly to the signing process. A share held by a policy engine can refuse to take part when a transfer exceeds a limit or goes to an address that has not been approved, so the rule is enforced at the moment of signing rather than reviewed afterwards.
MPC vs multisig
Both require multiple parties, but MPC produces a single standard signature off-chain (cheaper, private), while multisig enforces the rule on-chain (transparent, but chain-specific).
| MPC | Multisig | |
|---|---|---|
| Where the rule is enforced | Off-chain, in the signing protocol | On-chain, in a contract or script |
| What the chain sees | One ordinary signature | Several signatures or a contract call |
| Cost | Same as a normal transaction | Usually higher |
| Portability | Works on any chain that accepts the signature type | Tied to each chain’s own implementation |
| Transparency | Policy is not visible on-chain | Policy is publicly verifiable |
Neither is better in every case. Multisig suits situations where public, verifiable rules are a feature, such as a shared treasury whose members want to see the approvals on-chain. MPC suits cases where cost, privacy and working across many chains come first. Some systems use both.
Trade-offs to weigh
MPC is not a cure-all. The protocols are complex, and a flaw in an implementation can weaken its protections. Security depends on the shares being held in genuinely separate environments; if one party ends up controlling all of them, the benefit disappears.
- Use well-reviewed protocols and independent implementation audits.
- Keep shares on different devices, with different operators.
- Plan recovery in advance, since losing too many shares can lock the assets.
Operational discipline matters as much as the mathematics. A well-designed MPC setup documents who holds each share, how a lost share is replaced, and how the system behaves when a party is offline, so that normal operation and recovery are both understood in advance.
Where MPC is used
The technique suits situations in which several people or systems must agree before value moves, and where speed and chain compatibility matter.
- Corporate treasury — payments approved by a defined number of officers.
- Exchanges and payment providers — hot balances that must move quickly without a single exposed key.
- Consumer wallets — recovery without a seed phrase written on paper.
- Automated operations — policy engines that sign only within pre-set limits.
In each case the signing policy is part of the setup: who must approve, up to what amount, and to which destinations.
It also pairs well with other techniques. Hardware modules can protect an individual share, and smart accounts can add rules on-chain, as described in ERC-4337 smart accounts. Layering them means that no single control is relied on alone.
Syrax and MPC
The Syrax Vault is designed to use MPC as part of a hybrid security model alongside hardware protection and account abstraction. The Vault is self-custody: Syrax never holds or sees a user’s private keys or seed phrases.
The same techniques are built to protect assets on the custodial side of the ecosystem, as described in institutional crypto custody. Each regulated Syrax service will launch only upon receipt of the applicable licences.
The principle is the same on both sides: no one place should hold enough to move funds on its own.
For users, the intended result is simple recovery and everyday signing that does not depend on guarding a single phrase. For institutions, it is a signing process with approvals and limits that match their internal policies. Details of how the Vault is built to work are on the Vault page.
This article is for information only and does not constitute financial, legal or investment advice. Each regulated Syrax service will launch only upon receipt of the applicable licences.