Google Unveils Secure Tokenized Asset & Cryptocurrency Custody Platform for Banks

Google has unveiled Google Multi-Party Compute (MPC), a digital asset security service designed to help banks and financial institutions safeguard and transfer cryptocurrencies and tokenised assets. 

The platform distributes cryptographic signing authority across separate environments rather than relying on a single system to protect an entire private key.

As of 29 October 2026, Google MPC is in private preview, with commercial availability planned for early 2027. The development highlights a growing institutional requirement: banks need stronger controls over digital asset custody as blockchain-based financial products expand.

Key Takeaways

• Google MPC distributes signing authority: Multiple independent key shares help reduce the risk of a single compromised system enabling unauthorised transactions.
• Institutional controls are central to the platform: Transaction policies, approval thresholds and governance features allow banks to manage how digital assets move.
• Commercial availability is planned for early 2027: The service remains in preview, and Google has not publicly disclosed its pricing or identified its financial institution testing partners.

What Is Google Multi-Party Compute (MPC)?

Google Multi-Party Compute is a Google Cloud custody platform designed to protect the cryptographic keys that authorise digital asset transactions. 

It combines distributed signing, transaction policy enforcement and enterprise governance controls to help institutions manage digital assets securely. Google Cloud has made the product available in preview rather than as a fully launched commercial service. 

The central idea is straightforward: no single system should hold all the information required to authorise a transaction.

In conventional key management, protecting a complete private key is critical because anyone who gains sufficient control over it may be able to move the associated assets. 

Google MPC instead distributes key shares among separate participants and requires them to collaborate to produce a valid transaction signature.

This approach is intended for institutions that need more than basic digital asset storage. 

Banks may require multiple approvals, spending limits, designated destination addresses and documented governance procedures before funds can move.

Google MPC brings these capabilities together in a dedicated service, potentially reducing the complexity of building an institutional custody system from separate components.

How Google MPC Protects Cryptocurrency and Tokenised Assets

Google MPC uses multi-party computation and threshold signing to distribute responsibility for authorising transactions. Rather than assembling a complete private key in one location, the system allows separate participants to collaborate cryptographically.

1. Private keys are divided into separate shares

A private key is a cryptographic credential that authorises transactions from a digital asset address. If an attacker obtains sufficient control over that credential, they may be able to transfer the associated assets without permission.

Google MPC generates and distributes isolated key shares across designated participants. These may include infrastructure managed by the institution itself, Google Cloud and other permitted environments.

Each participant holds only its assigned share. During transaction signing, the participants follow a cryptographic protocol to produce a valid signature without reconstructing the complete private key in one place.

Google's documentation describes the service as using threshold signature schemes, including a hardened extension of the DKLS23 protocol. The security model is designed to prevent an attacker who compromises fewer participants than the required signing threshold from reconstructing the key or forging a signature. 

2. Banks can require multiple approvals

Google MPC supports configurable signing thresholds. For example, a bank could require two of three participants to take part in signing a transaction.

A larger institution might choose a five-of-seven arrangement, depending on its operational requirements and security policies.

These arrangements help distribute responsibility across teams or infrastructure rather than concentrating transaction authority in one place.

However, the number of participants alone does not determine security. Banks must also protect each participant's credentials, control administrative access and ensure that approval procedures cannot be manipulated.

3. Transaction policies provide additional safeguards

Cryptographic signing is only one part of digital asset security. Institutions also need to decide which transactions should be permitted.

Google MPC includes policy controls that can evaluate transactions before signing. Examples include:

• Spending limits: Restricting the amount that can be transferred under defined conditions.
• Destination controls: Identifying approved blockchain addresses and restricting transfers to unauthorised destinations.
• Approval requirements: Requiring participation from designated signers or departments.
• Governance controls: Assigning different responsibilities to administrators, policy authors and transaction signers.

These controls allow institutions to establish rules that reflect their internal risk management procedures.

There is an important distinction, however. Google's documentation explains that transaction policy evaluations guide signers but do not necessarily enforce the final decision independently. A transaction denied by an automated policy may still proceed if enough authorised signers approve it. 

Banks therefore need to configure policies and signing permissions carefully rather than treating automated checks as a complete substitute for human oversight.

Why Google Is Targeting Banks and Financial Institutions

Institutional demand for digital asset infrastructure extends beyond cryptocurrency ownership. Banks and other financial organisations are exploring blockchain-based payments, tokenised financial products and services that require secure control over assets held on-chain.

These activities introduce operational requirements that differ from ordinary digital wallet management.

A bank may need to demonstrate who authorised a transfer, which rules applied, where signing credentials were held and how access is controlled. It must also consider recovery procedures if a device becomes unavailable or a credential is compromised.

Google MPC addresses several of these requirements through distributed key management, signing thresholds and institutional governance features.

Digital asset custody is a security requirement

Digital asset custody refers to the safeguarding and administration of the credentials and systems used to control digital assets.

Unlike a conventional payment instruction that may be stopped or reversed through established banking processes, a confirmed blockchain transaction is generally difficult or impossible to reverse.

An unauthorised transfer can therefore create immediate financial losses. Recovering stolen assets may be difficult, particularly when the recipient cannot be identified or the funds move through multiple addresses.

Distributed signing can reduce dependence on a single credential or machine. Combined with transaction controls, it may help institutions limit the damage caused by particular types of compromise.

It does not remove every risk. Fraudulent instructions, compromised signers, poor configuration and failures in surrounding systems can still undermine custody security.

Tokenisation increases the need for secure infrastructure

Tokenisation represents an asset or a claim associated with an asset through a digital token on a blockchain.

Depending on the structure, tokenised assets may represent financial instruments, ownership interests, fund units or other rights. The token's legal meaning and the arrangements supporting it depend on the issuer and applicable rules.

For institutions, tokenisation can create new ways to record ownership and coordinate transactions. It also means that private-key security, transaction authorisation and operational continuity become central to managing those assets.

Readers seeking more context on this process can explore Bitrue's guide to tokenised transactions.

Google MPC is relevant because it focuses on the security layer that allows institutions to authorise blockchain transactions. It is not itself a tokenisation platform that issues every type of financial asset.

Digital payments and custody solve different problems

Digital asset custody and payment processing are related, but they serve different purposes.

Custody focuses on protecting the credentials and controls used to hold and transfer assets. Payment processing concerns the handling of payment instructions and the movement of value between participants.

An institution may need both capabilities when developing blockchain-based payment services. Strong custody controls help protect the assets involved, while payment infrastructure manages the broader transaction workflow.

Bitrue's cryptocurrency payment processor guide explains the payment-processing side of the ecosystem.

Google MPC is primarily a custody and transaction-signing service, not a general-purpose payment processor.

Which Blockchains and Digital Assets Can Google MPC Support?

Google's published documentation identifies supported cryptographic signing algorithms and the blockchain networks associated with them.

The distinction matters because a custody service's compatibility depends on the cryptographic requirements of the networks it supports, not simply on whether an asset is described as a cryptocurrency.

The documentation lists ECDSA support for Bitcoin, Ethereum and compatible networks. Solana support through Ed25519 is marked as coming soon in the published supported-blockchains table.

This distinction should not be overlooked when evaluating the service's readiness for a particular institutional use case. Support for a cryptographic algorithm does not automatically mean every asset, transaction type or blockchain feature is available.

What about Ethereum and Solana?

Reports published on 28 October 2026 stated that Alphabet had begun using Google MPC to secure its own digital assets on Ethereum and Solana. However, the company had not publicly identified the specific assets or disclosed their value. 

The reported use of the system on these networks is separate from the status shown in the public technical documentation. In particular, Solana remained marked as coming soon in the supported-blockchains table at the time of research.

The available information does not establish a complete list of supported tokens or confirm that every network-specific custody feature is ready for general commercial use.

Institutions evaluating Google MPC should therefore verify the current technical documentation and confirm that their intended assets and transaction workflows are supported.

Google MPC Launch Date, Availability and Pricing

Google Multi-Party Compute remains in preview as of 29 October 2026. Google has indicated that commercial availability is planned for early 2027, but a specific general availability date and pricing have not been disclosed. 

The following table summarises the publicly reported status.

The preview stage means institutions should not assume the service is already available for unrestricted commercial deployment. Product features, support arrangements and availability may change before general release.

Financial institutions considering adoption will also need to assess implementation requirements, operational dependencies, recovery arrangements and the responsibilities assigned to each signing participant.

How Google MPC Addresses AI and Future Quantum Security Risks

Google's custody initiative arrives amid concerns about compromised credentials, increasingly sophisticated cyberattacks and the longer-term implications of quantum computing.

These risks require different responses, and it is important to distinguish the protections currently described from capabilities that may be introduced in the future.

Protection against compromised credentials

A compromised private key can give an attacker the ability to authorise unauthorised transactions. Google MPC aims to reduce the risk that compromising one system or participant will be enough to obtain control over the entire signing process.

Its distributed architecture and transaction policies can provide additional safeguards when configured correctly.

However, multi-party signing does not automatically prevent phishing, social engineering or malicious instructions approved by legitimate signers. If authorised participants are deceived into approving a fraudulent transfer, the transaction may still proceed.

Institutions must combine cryptographic controls with staff training, identity management, monitoring and clear approval procedures.

AI-related threats remain a broader concern

Artificial intelligence can help attackers scale social engineering, automate reconnaissance and produce convincing fraudulent communications. These activities can increase the difficulty of identifying malicious requests.

Google MPC's signing controls may help prevent some unauthorised transfers, particularly when transaction rules detect suspicious destinations or amounts.

The service should not, however, be described as an AI-powered defence system that can independently identify every scam. Its documented core functions concern key management, signing and transaction policies.

Post-quantum cryptography is a future consideration

Quantum computing presents a longer-term challenge because sufficiently capable quantum computers could threaten some cryptographic systems used today.

Google has said its MPC architecture is designed to accommodate future upgrades to post-quantum cryptography. That does not mean the current service already protects every transaction against quantum attacks.

No specific timetable for introducing post-quantum signing capabilities has been announced. Institutions should treat this as a future upgrade path rather than a currently confirmed protection.

What Google MPC Means for Institutional Crypto Security

Google's entry into institutional digital asset custody reflects a broader shift towards infrastructure designed to support financial organisations operating on blockchains.

Its main proposition is the combination of distributed signing keys, configurable transaction policies and governance controls within a dedicated cloud service.

For banks, the potential benefit is a more structured way to manage digital asset authorisation without relying on a complete private key stored in one location. The approach could also help institutions align blockchain transactions with existing approval and risk management procedures.

The actual security outcome will depend on implementation. Key shares must remain protected, signing thresholds must be appropriate, and policy changes must be subject to effective oversight. Institutions must also evaluate their dependence on cloud infrastructure and establish procedures for service disruption and recovery.

Google MPC is therefore a development worth monitoring, but its preview status and the absence of public pricing mean that commercial readiness remains an open question.

Conclusion

Google Multi-Party Compute introduces a dedicated approach to institutional cryptocurrency custody by combining distributed signing authority, transaction policies and governance controls. Its design aims to reduce single points of compromise while giving banks greater control over how digital assets are authorised and transferred.

The planned early 2027 commercial rollout will be an important milestone, but institutions still need to assess supported networks, operational requirements and the limitations of the preview service. For now, Google MPC represents a developing option for banks seeking stronger security infrastructure as cryptocurrency custody and tokenised assets gain institutional attention.

FAQ

What is Google Multi-Party Compute?

Google Multi-Party Compute is a Google Cloud service designed to secure digital asset signing keys through distributed cryptographic signing, transaction policies and institutional governance controls.

Is Google MPC available to the public?

No. As of 29 October 2026, the service is in preview. Commercial availability is planned for early 2027.

How does Google MPC protect cryptocurrency?

It distributes cryptographic key shares among separate participants and requires sufficient participation to generate transaction signatures. This reduces the risk of a single compromised system exposing the entire private key.

Does Google MPC support Ethereum and Solana?

Google's documentation lists ECDSA support for Ethereum and compatible networks, while Solana support through Ed25519 is marked as coming soon. Reports also state that Alphabet has used the service for digital assets on both networks.

Has Google announced Google MPC pricing?

No. Google has not publicly disclosed pricing or provided a specific commercial launch date.

Disclaimer: The views expressed belong exclusively to the author and do not reflect the views of this platform. This platform and its affiliates disclaim any responsibility for the accuracy or suitability of the information provided. It is for informational purposes only and not intended as financial or investment advice.