Google Pitches Banks on Splitting Crypto Keys Across Clouds With New Custody Service

Introduction

Google Cloud is positioning itself as a custodian‑agnostic security layer for financial institutions venturing into digital assets. Its new Multi‑Party Compute (MPC) service lets a bank distribute a cryptographic private key across three independent environments—its own hardware, Google Cloud, and a competing cloud provider. By never assembling the full key in one place, the service promises to reduce the risk of key theft, insider abuse, and single‑point failures while still supporting popular blockchain signatures such as ECDSA and Ed25519.

How the key‑splitting model works

• Threshold signing – The private key is broken into multiple shares. A predefined threshold (e.g., 2‑of‑3 or 5‑of‑7) must collaborate to produce a valid signature. An attacker who compromises fewer parties than the threshold cannot reconstruct the key or forge transactions.
• Distributed storage – Each share lives on dedicated hardware: the bank’s on‑prem HSM, Google’s Confidential Space, and a third‑party cloud’s secure enclave. Google states it never sees the shares in plaintext, even on its own servers.
• Policy engine – Before a signature is generated, a policy layer checks transaction attributes (spending caps, approved destinations, etc.). While the engine provides advisory guidance, a sufficient number of signers can override a denial, giving banks flexibility in governance.

Why banks might care

1. Reduced concentration risk – No single vendor holds the entire key, mitigating the impact of a breach or outage at any one provider.
2. Regulatory alignment – The model aligns with emerging guidance that encourages multi‑party controls and auditability for crypto custodians.
3. Future‑proofing – Google’s roadmap includes post‑quantum signing upgrades, addressing long‑term concerns about quantum‑grade attacks on current curves.
4. Operational continuity – Distributed shares can survive a cloud‑provider outage; the remaining parties can still meet the signing threshold if configured appropriately.

Competitive landscape

Google’s entry joins established custodial players such as BitGo, Fireblocks, and Forge that already offer threshold‑signing and policy‑driven transaction controls. Google differentiates itself by leveraging its massive cloud infrastructure, Confidential Space for secure computation, and the promise of seamless integration with other Google services. However, the advisory nature of its policy engine and the ability to override denials may raise governance questions for highly regulated banks.

Practical considerations for early adopters

• Integration effort – Banks will need to provision HSMs on‑prem, establish secure connectivity to Google’s Confidential Space, and negotiate a partnership with a third‑party cloud. API compatibility with existing blockchain nodes and wallet software must be verified.
• Cost transparency – Google has not disclosed pricing. Institutions should request detailed usage‑based estimates, especially for high‑throughput environments.
• Governance design – Defining the signing threshold, share distribution, and policy rules requires close collaboration between the bank’s risk, compliance, and engineering teams.
• Testing and audit – Private‑preview partners are already piloting the service. Prospective users should demand audit logs, cryptographic proofs of share isolation, and third‑party security assessments before moving to production.

Looking ahead

Google aims for a general availability launch in early 2027, giving banks ample time to evaluate the service, run pilots, and align internal policies. As tokenization and blockchain adoption accelerate in the regulated finance sector, solutions that blend cloud scalability with distributed key security could become a baseline expectation rather than a differentiator.

--- For banks weighing crypto custody options, Google’s Multi‑Party Compute offers a compelling mix of distributed security and cloud‑native flexibility, but success will hinge on careful integration, clear governance, and transparent cost structures.