Google Cloud is developing a digital-asset custody service designed to address one of the biggest security challenges facing financial institutions entering crypto: how to protect assets without giving any single system control over the private keys needed to move them.
The service, called Google Multi-Party Compute (MPC), allows institutions to authorize and sign blockchain transactions collaboratively, distributing signing authority across multiple environments rather than concentrating it in one place.
The product remains in preview, but Google’s latest documentation and planned showcase signal a push to make institutional crypto security a more integrated part of its cloud infrastructure.
Google Targets the Single Point of Failure in Crypto Custody
Private keys are central to crypto security: whoever controls the credentials needed to authorize a transaction may be able to move the associated assets. For banks and other institutions managing digital assets, concentrating that authority in one system or location can create a significant vulnerability.
MPC is designed to reduce that risk by splitting signing authority among multiple participants. Rather than storing a complete private key in one place, the system uses separate key shares and a threshold-signing process that allows an authorized group to approve transactions without reconstructing the full key in a single location.
For example, a bank could maintain one key share on its own hardware, another in Google Cloud and a third with a separate provider. Under a configured threshold, a transaction would require enough participants to cooperate before it could be signed. Compromising one environment would not, by itself, necessarily give an attacker everything needed to authorize a transfer.
Google’s offering also combines transaction-signing capabilities with policy enforcement and enterprise governance controls. These can help institutions set transfer limits, restrict destination addresses and require multiple approvals before transactions proceed.
The distinction matters because securing a key is only part of the challenge. Institutions also need to control how that key can be used, who can authorize transactions and whether transfers comply with internal risk policies. MPC can reduce certain key-management risks, but it cannot eliminate every threat, including compromised credentials, flawed software or improperly configured approval rules.
Bitcoin Controls Build on Google’s Confidential Computing Work
Google Cloud has been developing the service since at least August 2026, according to its release notes. On Oct. 1, the company expanded its Bitcoin security rules to evaluate transaction amounts, identify destination address types and detect change outputs. The update also enabled Bitcoin transactions to be authorized through Google’s policy engine.
The service builds on Google’s earlier work with Confidential Space, a cloud environment designed to support secure computation and data sharing. In 2023, Google published guidance explaining how customers could use the technology to build MPC-based systems for digital-asset signing.
Confidential Space uses hardware-isolated environments to protect sensitive workloads. An attestation process can verify the environment and workload before the signing application proceeds, adding another layer of checks to the transaction process. Together, distributed signing and policy enforcement are intended to help institutions use cloud infrastructure without concentrating all signing authority in one location.
The latest documentation update came ahead of Google Cloud’s MPC Symposium in New York on Oct. 28. The event promised an unveiling of the company’s MPC products and research, with speakers from financial institutions including Morgan Stanley, OKX, Citi and Wells Fargo. Their participation indicates interest in institutional digital-asset security, but does not establish that those firms are customers of the new service.
Google’s Institutional Ambitions Face an Adoption Test
Google is entering a market where financial institutions already have specialist providers for digital-asset custody and transaction security. Its proposed service could appeal to banks seeking to combine distributed signing, transaction policies and key recovery within an established cloud infrastructure environment.
CoinDesk reported that several design partners and financial institutions are testing Google Multi-Party Compute. It also reported that Alphabet has begun using the technology to secure unspecified digital assets on Ethereum and Solana. Google has not identified the institutions testing the service or disclosed which assets its parent company is securing.
Commercial availability is planned for early 2027, according to CoinDesk, but Google has not disclosed pricing, and the service remains in private preview. Its documentation warns that preview products may have limited support.
That leaves a critical question for Google: whether its security architecture can meet the operational and governance requirements of institutions preparing to custody digital assets at scale. Banks will need to assess not only how signing authority is distributed, but also how the service handles recovery, access controls, policy changes and dependencies on cloud infrastructure.
Google’s MPC push addresses a central concern for institutional crypto adoption by reducing reliance on a single point of control. But the technology’s broader significance will depend on whether institutions move beyond testing and trust it with real assets and day-to-day operations.