Best MPC Wallet Providers in 2026: A Security Comparison

By the Guardian team Updated November 2026 5 min read

Quick answer. Fireblocks, Fordefi, BitGo, Dfns, Utila and Cobo are institutional MPC providers worth comparing, and none wins outright. They differ in who holds key shares, where policy runs and what audits they publish. Choose on those, then test recovery.

Watch: Best MPC Wallet Providers in 2026: A Security Comparison 1:45

Video transcript

An MPC wallet splits a signing key into shares, so no single share can sign. That moves the risk rather than removing it.

We compared providers on three things a security reviewer checks: who holds key shares, where the policy engine runs, and what assurance they publish.

Fireblocks, Fordefi, BitGo, Dfns, Utila and Cobo are all worth comparing, and none wins outright. Choose on their design, then test recovery yourself.

The policy engine decides what a stolen API key or rogue admin can sign. Dfns evaluates policy inside the signing path. At BitGo, recovery with user and backup keys bypasses it.

So ask each provider where policy runs, who can change it, whether changes need a quorum, and which recovery paths skip it.

In August 2023, BitForge exposed threshold signing flaws at over 15 providers and projects, some allowing full key extraction. Ask who audited your provider's implementation.

Fireblocks, Ripple and Paxos each announced a wallet acquisition in late 2025. That is not a flaw, but ask for a key export path that works without the vendor.

Guardian advises on approval thresholds and key custody before they are built. Its offchain automation pentest tests threshold signers, including recovery after one node is compromised.

Pressure-test your MPC provider before you sign. Read the full comparison, or book a system review with a Guardian engineer at guardian.security.

An MPC wallet splits a signing key into shares held by separate parties. No single share can sign.

That moves the risk rather than removing it. It now sits with the share holders, the policy engine and the code that runs the cryptography.

Ownership is moving too. Three wallet providers changed hands between October and November 2025.

How We Compared Providers

We looked at three things a security reviewer checks:

Key shares: how many, who holds them, and where they run.
Policy engine: what it enforces, where it runs, and who can change it.
Published assurance: certifications, named audits and bug bounties.

Every provider claim comes from its own docs and security pages, read in November 2026. Where a page is silent, we say so.

We do not rank them. The right design depends on who you want holding shares. Embedded wallets for consumer apps are a separate choice: see Privy vs Turnkey vs Dynamic.

Providers Compared

Provider	Key shares	Policy engine	Published assurance
Fireblocks	Your Co-signer or app, plus Fireblocks cloud co-signers	Ordered rules on who, from where, to where	SOC 2 Type 2, ISO 27001, CCSS QSP Level 3
Fordefi (Paxos)	Independent shares; server share in AWS Nitro Enclaves	First matching rule; changes need admin quorum	SOC 2 Type II (EY); Skylight Cyber pentest
BitGo	2-of-3: user, backup and BitGo	Applies where BitGo signs	"SOC attestations"; bug bounties
Dfns	MPC, HSM, TEE or your own key	Runs inside the MPC signing path	SOC 2 Type II; five named testers
Utila	Two shares: Utila and the customer	Set only by an admin quorum	SOC 2 Type II; Halborn audit
Cobo	Threshold signing nodes inside TEEs	"Customizable risk controls"	SOC 2 Type II; ISO 27001 compliant

Fireblocks

Fireblocks says key shares sign through rounds of computation "without ever being brought into the same environment."

Your API Co-signer runs in Intel SGX, AWS Nitro or Google Cloud enclaves. Fireblocks cites NCC-audited cryptographic libraries and a HackerOne bug bounty.

Fordefi

Admins must back up organization keys within seven days, using recovery phrases, an air-gapped key, CoinCover, Station70 or a YubiKey.

Fordefi is rolling out MPC share refresh, which periodically re-randomizes key shares.

BitGo

BitGo's docs point to a DKLs23 threshold ECDSA library to explain its MPC. For self-custody MPC wallets, you must manage the backup key yourself; a key recovery service cannot.

Dfns

Dfns runs its own protocols: CGGMP24, FROST and KU25. It names quarterly audits and pentests by Halborn, IBM, Kudelski, Quarkslab and Borg Security.

Keys can be Dfns-managed, shared or held on your premises. It lists CCSS Level 3 as in progress.

Utila and Cobo

Utila says only an approved administrator on the customer's side can recover keys.

Cobo's homepage does not say who holds shares, and names no audit firm.

Ownership Changes

October 23, 2025: Fireblocks announced it had acquired Dynamic, an embedded wallet provider.
November 3, 2025: Ripple announced it had acquired Palisade, a custody and wallet-as-a-service provider.
November 25, 2025: Paxos announced it had acquired Fordefi, which "will continue operating its product independently."

New ownership is not a flaw. But ask for change-of-control notice, which entity's SOC 2 covers you, and a key export path that works without the vendor.

Our vendor due diligence questionnaire has the full question set.

Policy Engines and Approvals

The policy engine decides what a stolen API key or a rogue admin can sign. Where it runs matters as much as what it says.

Dfns: evaluates policy inside the signing path. "Either the policy passes, or the signature doesn't happen."
Fordefi: applies the first rule that matches, so order decides the outcome. Policy changes need the Admin Quorum, shown as a diff.
Fireblocks: also evaluates rules in order, and advises placing the most restrictive first.
BitGo: will "only countersign if the transaction meets the policies you've set." Recovery with the user and backup keys bypasses them.

Ask each provider:

Does policy run in the signing path, or in a server before it?
Who can change it, and does a change need a quorum?
Which recovery or admin paths skip it?
Is the default to deny?
Can we export the full policy and its change history?

MPC Vulnerabilities to Ask About

Flaws in threshold ECDSA code have hit many providers before.

BitForge (August 2023). Fireblocks found flaws in GG18, GG20 and Lindell17 implementations at over 15 providers and projects, some allowing full key extraction.
TSSHOCK (August 2023). Verichains showed three key-extraction attacks on GG18, GG20 and CGGMP21 implementations.
THORChain (May 2026). About $10M was lost to "a cryptographic attack targeting the threshold signing process."

THORChain says the attack combined three individually low-severity issues, present since its early use of GG20. Fireblocks says its own protocols were not affected by BitForge.

So ask:

Which protocol and library do you run, and who audited this implementation?
Were you affected by BitForge or TSSHOCK, and what changed?
How often are shares refreshed?
What can parties below the threshold force, such as aborts or leaks from failed signatures?
Can we recover and sign without you, and when did we last test it?

For how MPC fits beside HSMs, KMS and multisig, see private key management. For onchain thresholds, see multisig best practices.

How Guardian Helps

For institutions, Guardian advises on custody and signing "while they are still decisions": approval thresholds and key custody, specified before they are built.

Its offchain automation pentest tests threshold signers: share storage, participant authentication, what a subset below threshold can force, and recovery after one node is compromised.

Start with a system review call: an hour with a Guardian engineer on who holds the keys, and a written summary afterwards.

Frequently Asked Questions

Who are the best MPC wallet providers?

Fireblocks, Fordefi, BitGo, Dfns, Utila and Cobo are institutional MPC providers worth comparing. None is best for everyone: they differ in who holds key shares, where policy runs and what they publish. Choose on those, then test recovery yourself.

Is MPC safer than multisig?

Neither wins outright. MPC signs offchain and puts one ordinary signature onchain, so its policy runs offchain, in vendor software. Multisig enforces the threshold onchain, where anyone can check it.

What MPC vulnerabilities should I ask a provider about?

Ask whether its threshold ECDSA implementation was affected by BitForge or TSSHOCK, both disclosed in August 2023. Then ask who audited the implementation, how often shares are refreshed, and what a party below the threshold can force.

Which MPC wallet providers have changed owners?

Fireblocks announced it had acquired Dynamic on October 23, 2025. Ripple announced it had acquired Palisade on November 3, 2025, and Paxos announced it had acquired Fordefi on November 25, 2025.

Sources

Pressure-test your MPC provider before you sign

Spend an hour with a Guardian engineer on who holds your keys, and leave with a written summary.

Talk to Guardian Book a system review