Google Cloud Advances Multi-Party Computation Service for Institutional Bitcoin Custody

Google Cloud has publicly outlined a new Multi-party Compute (MPC) platform designed to support institutional custody of digital assets, with a particular focus on Bitcoin.

The service, currently available in preview, reportedly enables multiple parties to collaboratively authorize and sign blockchain transactions without any single participant ever holding or reconstructing a complete private key.

This approach addresses longstanding risks in institutional digital asset management, where concentrated control of signing credentials has historically created single points of failure for theft, operational downtime, or irreversible loss.

The platform combines threshold signature schemes with enterprise governance tools.

Independent, hardware-backed parties—potentially spanning Google Cloud infrastructure, a customer’s own on-premises systems, alternative cloud providers, or even mobile devices—each generate and retain isolated key shares.

During a signing operation, these parties execute a multi-party protocol that produces a valid blockchain signature without assembling the full private key in any one location.

An attacker who compromises fewer shares than the configured threshold cannot forge a signature or recover the underlying key.

At the same time, the system remains operational if individual parties become unavailable, provided the remaining shares meet the threshold. Google’s documentation describes a hardened extension of the DKLS23 protocol as the foundation for this process.

Supported cryptographic algorithms currently include ECDSA over the secp256k1 curve, which covers Bitcoin, Ethereum, and other EVM-compatible networks.

Support for EdDSA on the Ed25519 curve, used by Solana, is listed as forthcoming.

Once a distributed key is generated, the service returns the corresponding public key and derived blockchain addresses.

Organizational controls are modeled within a dedicated, isolated instance.

Administrators define KeyRings and associated KeyPolicies that specify which teams or users hold shares, the required approval threshold (for example, 2-of-3 or 5-of-7), and the physical or cloud location of each share.

Users are assigned roles such as Admin, Policy Author, or Signer, and teams allow policies to reference groups rather than individuals.

Transaction policies, expressed in the Cedar policy language, evaluate proposed transfers against rules such as spending limits or destination allowlists before signing begins.

These automated checks guide signers but do not ultimately block a transaction if a sufficient number of authorized signers approve it.

On October 1, 2026, Google expanded Bitcoin-specific policy capabilities to assess transaction amounts, identify destination address types, and detect change outputs—features that address practical custody workflows beyond basic signing.

Release notes indicate development activity dating back to at least August 2026.

The documentation update preceded Google Cloud’s MPC Symposium in New York, an event described as an exclusive presentation of the company’s frontier MPC product and related research.

Speakers included representatives from major financial institutions such as Morgan Stanley, Citi, and Wells Fargo, alongside the crypto exchange OKX.

A Google Cloud spokesperson has indicated that the company aims for general availability of the MPC Key Management Service in early 2027.

The offering builds on earlier work with Confidential Space, a confidential computing environment previously used to support secure multi-party computation and controlled data sharing.

For institutions exploring Bitcoin custody, tokenization, or on-chain settlement, the service offers a packaged alternative to assembling MPC signing, policy engines, and key recovery from separate tools.

It remains in preview status, with support levels that may differ from a fully generally available product.

As regulated entities continue to evaluate blockchain-based operations, Google Cloud’s entry positions a major cloud provider to compete with specialized digital-asset security vendors on key management architecture that distributes trust across independent environments.



Sponsored Links by DQ Promote

 

 

Disclosure Quest

Reg A - Form 1-A Filings Beta

Beta. Initial Form 1-A only. Target raise is the stated Amount to be Raised, totaled. Compared with the same dates one year earlier.

YTD: Jan 1, 2026 - Nov 20, 2026 vs Jan 1, 2025 - Nov 20, 2025

Share this graph
Number of Filings140Prior 132 +6.1%
Target Raise, Total$3.56BPrior $3.63B -1.9%
This YTDYear priorChange
Filings 140 132 +6.1%
Target raise $3.56B $3.63B -1.9%

Sponsored by the Crowded Media Group the leading digital news service covering the global Fintech Industry, including digital assets, crowdfunding, tokenization, and other innovations in capital markets. email us @CrowdfundInside

Source: DisclosureQuest. Initial Form 1-A only.

Created by Crowded Media Group

This display counts initial Form 1-A filings only. It does not represent subsequent filings, including Form 1-A/A amendments or Form 1-A POS post-qualification updates filed by the issuer. Amounts are the stated Amount to be Raised on the initial filing, not capital raised and not amounts revised in later filings.

0 0 votes
Article Rating
Subscribe
Notify of
guest

This site uses Akismet to reduce spam. Learn how your comment data is processed.

0 Comments
Newest
Oldest Most Voted
 
0
Would love your thoughts, please comment.x
()
x
Send this to a friend