{"id":1107,"date":"2026-11-04T02:00:51","date_gmt":"2026-11-03T18:00:51","guid":{"rendered":"https:\/\/onemoremoney.com\/onemorebitcoin\/google-mpc-crypto-custody-banks\/"},"modified":"2026-11-04T02:00:51","modified_gmt":"2026-11-03T18:00:51","slug":"google-mpc-crypto-custody-banks","status":"publish","type":"post","link":"https:\/\/onemoremoney.com\/onemorebitcoin\/google-mpc-crypto-custody-banks\/","title":{"rendered":"Google Multi-Party Compute: What MPC Custody Means for Banks"},"content":{"rendered":"\n
Google Multi-Party Compute: What MPC Custody Means for Banks<\/h1>\n\n\n\n
Google is not launching a crypto wallet for you and me. It is building something more consequential for the plumbing of finance: a service that lets banks hold and move cryptocurrency and tokenised assets without any single machine ever holding a complete private key. The product is called Google Multi-Party Compute, and it puts one of the world’s largest cloud providers directly into the institutional custody market.<\/p>\n\n\n\n
This article explains what Google Multi-Party Compute actually is, how multi-party computation differs from the older ways of guarding keys, and what it could mean for banks moving on-chain. It also covers the part that usually gets skipped: what MPC does not protect against.<\/p>\n\n\n\n
1. Why Google Multi-Party Compute Matters Now<\/h2>\n\n\n\n
On 28 October 2026, CoinDesk reported that Google was presenting Google Multi-Party Compute at a digital assets event in New York. The service is in private preview, with commercial availability planned for early 2027. Google told CoinDesk it had not previously offered a dedicated MPC custody product for cryptocurrencies, although it already sells general-purpose key services such as Cloud KMS and Cloud HSM.<\/p>\n\n\n\n
The timing is not accidental. Stolen keys remain the single biggest route to crypto theft. CoinDesk, citing Chainalysis, noted that compromised private keys accounted for 43.8% of crypto stolen in 2024. For a bank, one leaked key is not a bad day, it is a potential capital and reputational event.<\/p>\n\n\n\n
> “Digital asset adoption and tokenization are at an inflection point.” > Rich Widmann, Google Cloud, quoted by CoinDesk<\/p>\n\n\n\n
Key Facts at a Glance<\/h3>\n\n\n\n
Item<\/th>
Detail<\/th><\/tr><\/thead>
Product<\/td>
Google Multi-Party Compute (MPC)<\/td><\/tr>
Provider<\/td>
Google Cloud<\/td><\/tr>
Status<\/td>
Preview, under Google’s Pre-GA Offerings Terms<\/td><\/tr>
Commercial launch<\/td>
Planned for early 2027<\/td><\/tr>
Assets targeted<\/td>
Cryptocurrencies and tokenised assets<\/td><\/tr>
Signing schemes<\/td>
ECDSA on secp256k1 (Bitcoin, Ethereum, EVM chains); Ed25519 for Solana listed as coming soon<\/td><\/tr>
Approval thresholds<\/td>
Configurable, e.g. 2-of-3 or 5-of-7<\/td><\/tr>
Named bank customers<\/td>
None disclosed<\/td><\/tr>
Pricing<\/td>
Not disclosed<\/td><\/tr>
Known internal user<\/td>
Alphabet, for its own assets on Ethereum and Solana<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Data as of 4 November 2026. Verify before publishing.<\/em><\/p>\n\n\n\n
2. What Google Multi-Party Compute Actually Is<\/h2>\n\n\n\n
Google’s own documentation describes Multi-party Compute as a custody platform for digital asset signing keys. It combines three things: threshold signing, a transaction policy engine, and governance controls such as user roles and approval keys. Each customer gets a dedicated, isolated instance.<\/p>\n\n\n\n
In plain terms, it is the machinery a bank needs to approve and sign blockchain transactions at scale, packaged as a cloud service. It is infrastructure, not a consumer product, and there is no Google token involved.<\/p>\n\n\n\n
What Google has and has not disclosed<\/h3>\n\n\n\n
Several financial institutions and design partners are testing it, but Google has not named them<\/li>
Pricing has not been announced<\/li>
Alphabet is using the system to secure its own digital assets on Ethereum and Solana<\/li>
Google did not say which assets Alphabet holds or how much<\/li>
Google says it cannot access customers’ key material in unencrypted form, even when shares sit on its infrastructure<\/li><\/ul>\n\n\n\n
We found no public statement from any bank confirming it plans to use the service. Until names appear, “banks are testing it” is the full extent of what is known.<\/p>\n\n\n\n
3. How MPC Differs From Single-Key, HSM and Multisig Custody<\/h2>\n\n\n\n
Every blockchain transaction is authorised by a digital signature made with a private key. Custody is really the question of where that key lives and who can use it. There are four broad models.<\/p>\n\n\n\n
Single key<\/h3>\n\n\n\n
One key, stored in one place. Simple, and catastrophic if it leaks, because whoever holds the key holds the assets. This is the model behind most of the thefts in the statistic above.<\/p>\n\n\n\n
HSM-based custody<\/h3>\n\n\n\n
A hardware security module is a tamper-resistant device that holds a complete key and signs inside the hardware. Google’s documentation notes its own Cloud HSM signs quickly, at 20 to 50 milliseconds at the 95th percentile. The weakness is structural: the full key still exists in one boundary, so a credential breach at the wrong level can mean full key exposure.<\/p>\n\n\n\n
Multisig<\/h3>\n\n\n\n
Multisig uses several independent keys, and the blockchain itself requires a set number of them, say 2-of-3, to approve a transaction. It is transparent and battle-tested on Bitcoin. The trade-off is that the rules live on-chain, the setup differs from chain to chain, and changing signers usually means moving funds to a new address.<\/p>\n\n\n\n
MPC threshold signing<\/h3>\n\n\n\n
MPC also uses a threshold, but it works off-chain. A single private key is generated and used as separate shares held by independent parties. When enough of them cooperate, they jointly produce one ordinary signature, and the complete key is never assembled anywhere. Google’s documentation puts it directly: “The complete private key doesn’t exist in plaintext in any single location.”<\/p>\n\n\n\nEach party holds one key share, and a threshold of them must cooperate to produce a signature.<\/figcaption><\/figure>\n\n\n\n
To the blockchain, an MPC signature looks like any normal single-key signature. That makes the approach chain-agnostic, which matters to a bank that wants one control system across Bitcoin, Ethereum and tokenised assets rather than a different setup for each.<\/p>\n\n\n\n
The technical details Google has published<\/h3>\n\n\n\n
Uses a hardened extension of the DKLS23 threshold ECDSA protocol<\/li>
Signing nodes run inside Google’s Confidential Space on AMD SEV-SNP hardware-encrypted enclaves<\/li>
Key shares are encrypted at rest, with key encryption keys protected by Cloud HSM or external HSMs<\/li>
Shares are released into enclave memory only after a hardware attestation check<\/li>
Customers keep control of their encryption keys through Cloud KMS in their own organisation<\/li>
Keys cannot be deleted, only disabled<\/li>
Signing is slower than an HSM, under one second at the 95th percentile, which is the price of distributing the work<\/li><\/ul>\n\n\n\n
CoinDesk described a typical arrangement: a bank might hold one share in Google Cloud, one on its own hardware, and one with another cloud provider. An attacker who compromises fewer parties than the threshold can neither forge a signature nor rebuild the key.<\/p>\n\n\n\n
4. The Policy Layer: Where Banks Will Live Day to Day<\/h2>\n\n\n\n
Cryptography protects the key. A policy engine decides what the key is allowed to sign. According to CoinDesk, a transaction first enters Confidential Space, where it is checked against the institution’s rules before signing.<\/p>\n\n\n\n
The kinds of rules a bank can set<\/h3>\n\n\n\n
Transfer amount limits<\/li>
Destination wallet allowlists and restrictions<\/li>
Approvals required from several departments<\/li>
Signing thresholds such as 2-of-3 or 5-of-7 participants<\/li><\/ul>\n\n\n\n
Google’s documentation adds a detail worth reading twice. Policies are written in the Cedar language and produce a permit or deny verdict, but that verdict guides signers rather than enforcing the decision. A denied transaction can still execute if enough signers approve it. In other words, the final control is human, and the quality of a bank’s signer discipline matters as much as the maths.<\/p>\n\n\n\nApproval rules decide which transactions get signed, so their configuration matters as much as the cryptography.<\/figcaption><\/figure>\n\n\n\n
5. What MPC Solves, and What It Does Not<\/h2>\n\n\n\n
MPC removes the single point of compromise. That is a genuine improvement, and it directly targets the stolen-key problem that dominates crypto theft. It also allows recovery and signing to continue when a party fails, provided the threshold is still met.<\/p>\n\n\n\n
What it does not do is make custody risk disappear. CoinDesk’s own reporting was clear on the limits.<\/p>\n\n\n\n
Risks MPC does not remove<\/h3>\n\n\n\n
Provider dependency.<\/strong> Banks would still rely on Google for the software, the policy engine and the operating infrastructure<\/li>
Configuration risk.<\/strong> Security depends on how an institution sets thresholds, protects its signers and controls who can change approval rules<\/li>
Social engineering.<\/strong> Rules can block transfers that break preset limits, but legitimate signers can still be tricked into approving a malicious transaction<\/li>
Collusion above the threshold.<\/strong> If enough insiders or compromised signers act together, the system will sign, because that is what it is designed to do<\/li>
Unproven performance.<\/strong> Google provided no independently verified comparison with existing custody products<\/li>
Pre-GA status.<\/strong> The service is in preview, offered under pre-release terms with limited support<\/li><\/ul>\n\n\n\n
On the longer-term threat, Google told CoinDesk its architecture can support post-quantum upgrades, with no timetable, and that any upgrade depends on blockchains adopting the new cryptography. MPC is designed against stolen credentials and unauthorised transactions, not against a break of the underlying signature schemes. We covered that separate debate in Crypto Bunker Mode: Can AI Math Break Your Wallet Keys?<\/a>.<\/p>\n\n\n\n
![\"Three](\"https:\/\/onemoremoney.com\/onemorebitcoin\/wp-content\/uploads\/2026\/11\/google-mpc-crypto-custody-banks-01-key-shares.jpg\")
![\"A](\"https:\/\/onemoremoney.com\/onemorebitcoin\/wp-content\/uploads\/2026\/11\/google-mpc-crypto-custody-banks-02-policy-engine.jpg\")
![\"Several](\"https:\/\/onemoremoney.com\/onemorebitcoin\/wp-content\/uploads\/2026\/11\/google-mpc-crypto-custody-banks-03-custody-landscape.jpg\")