What happens when one secret number protects a billion dollars of crypto? For a bank, that's a nightmare scenario.
MPC custody explained in one sentence: it's a way to guard crypto so the full private key never sits in one place. On 28 October 2026, Google previewed a service built on that idea. It came at the company's first digital assets symposium in New York.
The product is called Google Multi-Party Compute. Several financial institutions are testing it privately, though Google hasn't named them. Google plans a commercial launch in early 2027 and hasn't shared pricing.
This mpc custody explained guide covers how the tech works and how it compares with older options. It ends with what to ask any provider.
Every crypto wallet runs on a private key. That's a long secret number that proves ownership and lets you move coins. Whoever holds it controls the money.
This creates a single point of failure. If the key leaks, a thief can drain the account in minutes. If it's lost, the funds are gone for good. Blockchain transfers can't be reversed.
Older fixes helped, but they had limits. A hardware wallet keeps the key on one offline device. That's safer than a laptop. Still, one device means one thing to lose, steal, or force someone to unlock.
Banks want more. They need several people to approve big transfers, just like wire payments. They need spending limits and a clear record of who signed off. One key can't enforce any of that.
Multi-party computation, or MPC, was built for this gap. It's a branch of cryptography where several parties work on one result together. Nobody has to reveal their private piece to the others.
That's the idea behind every MPC wallet, and it's where MPC custody explained properly begins. It's also why banks care first.
The easiest way to get MPC custody explained is a kitchen. Picture three chefs guarding one secret recipe. Each knows only one ingredient. They cook behind a curtain. The dish comes out perfect, yet no chef ever learns the whole recipe.
MPC custody works in much the same way. The recipe is the private key. The ingredients are key shares, small pieces of secret data stored in separate places. The finished dish is a valid signature, the proof that approves a transaction.
Here's the basic flow of MPC custody explained, step by step:
Setup: the parties run a joint ceremony that creates the shares. The complete key is never built.
Request: someone proposes a transfer.
Signing: enough shares work together to produce one signature.
Broadcast: the blockchain sees a normal signature and can't tell a group made it.
Threshold signing is the rule for how many shares must agree. It's written as "k-of-n." In a 2-of-3 setup, any two of three shares can sign. Losing one share won't lock you out. One stolen share can't move funds alone.
A 5-of-7 setup asks for five approvals from seven shares. That suits large teams with tight controls. Google says its preview supports both patterns.
That's MPC custody explained at its simplest: many hands, no single master key.
Next comes the guard at the gate, the part of MPC custody explained that feels most like normal banking controls. Before signing starts, a policy engine checks the transfer against written rules. Google says this runs inside Confidential Space, a hardware-isolated computing environment that shields data while it's in use.
Example rules include spending limits, approved destination lists, and sign-off from several departments. Google's documentation also describes Bitcoin checks on amounts, address types, and change outputs. Change outputs are the leftover coins sent back to the sender.
The same documentation says the design builds on DKLS23, a threshold-signing protocol. It also says breaching fewer parties than the threshold can't forge a signature. Treat that as a vendor claim for now. We couldn't find a public independent audit of the service yet.
MPC custody explained next to its rivals starts with three models. They dominate institutional custody tech, and they solve the same problem in different ways.
Model | Where the key lives | Who approves | Main weakness |
Cold storage | One full key on an offline device | Usually one holder | Loss, theft, or a tricked operator |
Multisig | Several full keys, rule set on-chain | A set number of signers | Rigid setup, changes happen on-chain |
MPC custody | Shares of one key, no full key | A threshold of share holders | Depends on code quality and share security |
Multisig puts the approval rule on the blockchain itself. Each signer holds a complete key, and anyone can verify the rule. That public audit trail is its biggest strength.
The cost is rigidity. Changing signers usually means an on-chain change. Each chain also has its own multisig format.
MPC keeps the rules off-chain. The network sees one ordinary signature. Providers say they can add signers or refresh shares without changing the wallet address. The cost is trust, since you rely on cryptography you can't inspect on-chain.
Cold storage and MPC aren't strict rivals. Cold storage means keeping keys offline. Some providers say an air-gapped device can hold one MPC share. So you can mix both ideas.
What about an MPC wallet vs hardware wallet? A hardware wallet protects one full key. An MPC wallet avoids having a full key at all. So MPC custody explained against a hardware wallet comes down to one full key versus none. The right pick depends on team size, transfer volume, and risk appetite.
Google already sells Cloud KMS and Cloud HSM. These services store and protect keys. An HSM is a tamper-resistant hardware box built for key storage. The new service adds MPC signing, transaction policies, and key recovery in one package.
It isn't Google's first step here. In 2023, Google published a guide for building MPC signing on Confidential Space. Banks had to assemble the pieces themselves. The preview turns that blueprint into a managed product. In short, it's MPC custody explained as a service rather than a build-it-yourself kit.
The pitch is about control. A bank could keep one share on its own hardware. A second could sit in Google Cloud, and a third with another cloud provider. Google says it can't read any share in plaintext. No single cloud or employee would hold enough to sign.
So why do institutions use MPC? Three reasons stand out:
Approvals: several teams must agree, just like in traditional finance.
Speed: signing is coordinated off-chain, so there's no extra on-chain approval step.
Flexibility: signers can change without moving funds to a new address, according to providers.
Specialist custody firms have sold MPC for years. Seen from the market, MPC custody explained means Google is arriving late, not first. Its edge is cloud scale, and whether banks prefer it over specialists is unproven.
Google also says its parent company already uses the service for its own digital assets. It hasn't said which assets.
Is MPC custody safe? It's a strong upgrade over a single key, yet it isn't magic. Every honest guide to MPC custody explained must cover the risks:
Proof is thin. Google claims fast signing and key recovery. No independent benchmarks came with the claim.
Implementation matters. Security depends on the protocol code and on where each share sits. A poorly built system can be weaker than a well-run single key.
Threshold attacks. If attackers or insiders reach enough shares, they can sign. A 2-of-3 setup has a lower bar than 5-of-7.
Recovery cuts both ways. Lose too many shares and funds get stuck. Backups, meanwhile, create new targets.
Cloud trust. Spreading shares across clouds helps, but cloud accounts and admin rights still need strict control.
Quantum risk. The signature types Google plans to support, ECDSA and Ed25519, are expected to weaken against future quantum computers. Google mentions upgrade paths but has set no public release date.
Preview status. The service is invitation-only until early 2027, and pricing is unknown.
None of these kills the idea. That's the honest side of MPC custody explained. They just show that a polished announcement isn't proof. A custody setup is only as strong as its weakest share.
Google's preview shows MPC custody moving from a niche tool to bank-level infrastructure. The design is clear: split the key, set a threshold, and check every transfer against rules. Audit results, real-world speed, and pricing remain unknown.
That's MPC custody explained well enough to judge any pitch. Before you trust a provider, ask these five questions:
Where does each key share live, and who controls that environment?
What's the signing threshold, and what happens if shares are lost?
Has an independent firm audited the protocol, and can you read the report?
Who can change the policy rules, and are changes logged?
What's the plan for post-quantum upgrades?
Disclaimer: This article is for information only and isn't financial, legal, or investment advice. Crypto is high-risk, and custody tech can fail or change. Details reflect public reports and Google's statements as of 29 October 2026. Do your own research before making decisions.