Google launches Multi-Party Compute: an MPC custody product in private preview for institutions

What Google announced

Google introduced a product named Google Multi-Party Compute (MPC) that combines multi-party computation (MPC) with its Confidential Space trusted execution environment to enable MPC-compatible blockchain signing and custody workflows, according to Google’s product documentation and coverage of the company’s event (cloud.google.com; coindesk.com; cryptoticker.io).

The company presented the offering at its inaugural digital assets symposium in New York City on October 28, 2026 (coindesk.com; cryptoticker.io). Google says the product is in a private or closed preview and is not generally available; it plans commercial availability in early 2027 (coindesk.com; cryptoticker.io).

Technical design and components

Google Multi-Party Compute distributes private-key fragments (shares) across separate compute environments so the full private key never exists in one place, a core MPC property intended to reduce single-point-of-compromise risk (cloud.google.com; coindesk.com; cryptoticker.io).

The design uses Google’s Confidential Space as a sealed-off compute environment (a TEE) to run the sensitive MPC signing workload. Confidential Space produces attestation claims that gate key access and validate workload integrity for MPC policy logic (cloud.google.com; cryptoticker.io).

The product’s reference architecture relies on Google Cloud components such as Artifact Registry, Cloud KMS/HSM, Cloud IAM and blockchain node hosting to orchestrate signing flows and manage associated artifacts and permissions (cloud.google.com).

Google described that co-signers can operate in multiple environments — including Google Cloud, on-premises systems, mobile devices and other clouds — and that Cloud KMS/HSM can be used to provide partial signatures or to wrap secret material used in MPC operations (cloud.google.com).

Supported signature schemes and chains

At launch Google intends to support ECDSA and Ed25519 signature methods, which cover most major current blockchains, and said post-quantum signature support is a possible future capability once networks adopt quantum-safe primitives (cryptoticker.io; coindesk.com).

Google emphasised that quantum resistance depends on blockchains themselves adopting quantum-safe signature schemes and that custodian support for quantum-resistant primitives is contingent on network-level changes (cryptoticker.io; coindesk.com).

Policy controls, threshold signing and institutional workflow

The system supports threshold signing (examples given by Google include 2-of-3 and 5-of-7) so signatures are produced only when the required number of co-signers participate (cryptoticker.io).

Google said the platform applies institutional policy checks inside Confidential Space before producing signatures — examples cited include transaction amount limits, allowed destination addresses and multi-department approvals — with those checks enforced by the attestation claims and MPC policy logic (coindesk.com; cryptoticker.io).

Custody model and liability

Google positioned the product for banks and large financial institutions; retail users are not the target of the preview or initial service (cryptoticker.io; coindesk.com).

Both Google and reporting outlets noted that Google supplies the technology but does not itself hold customer assets: custodians remain the liable party for custody and regulatory responsibilities (cryptoticker.io).

Alphabet’s internal use and preview limitations

Google’s parent company, Alphabet, is already using the same technology to secure its own digital assets on Ethereum and Solana, though Google has not disclosed which assets or their size (coindesk.com; cryptoticker.io).

Google has previously published guidance in 2023 describing how to build MPC custody on Confidential Space; the 2026 offering is a Google-operated, productised custody technology rather than guidance alone (cloud.google.com; coindesk.com).

The product is in private/closed preview; Google did not disclose pricing, the identities of development partners or testing institutions participating in the preview (coindesk.com; cryptoticker.io).

Why institutions are interested

Industry reporting cited by CryptoTicker and CoinDesk places the announcement in context: compromised private keys have been a major cause of historical crypto losses, and MPC-based custody is an institutional approach intended to lower single-point-of-failure risks and meet enterprise controls (cryptoticker.io).

CryptoTicker noted that an integrated offering from a major cloud provider could lower integration costs for institutions that already use those clouds, potentially reducing the need to contract separate specialist custody vendors (cryptoticker.io).

Regulatory, certification and contract requirements

Both CoinDesk and CryptoTicker reported Google’s timeline (private preview → commercial availability in early 2027) but emphasised that supervisory reviews, certifications and contractual arrangements will be required before banks place customer assets on the service (coindesk.com; cryptoticker.io).

The announcement therefore documents product intent and architecture but does not remove the operational and regulatory work institutions must complete before using the service to custody customer funds.

Analysis — what this means for institutional custody

Google’s productised MPC custody offering confirms the company is moving beyond published guidance to a managed, Google-operated technology product that combines MPC with TEEs and existing cloud services. The combination of Confidential Space attestation with MPC shares is a deliberate design to keep signing logic and policy enforcement inside an integrity-protected boundary (cloud.google.com).

For institutions already using Google Cloud, an integrated stack may simplify deployment compared with stitching together third-party MPC providers, HSMs and bespoke node hosting. That said, Google has not published pricing, partner identities, or details of pilot customers, so practical adoption timelines will depend on procurement and regulatory approval processes (coindesk.com; cryptoticker.io).

Importantly, Google’s role is technology supply rather than custodial ownership: custodians retain legal liability for assets placed under custody. That distinction affects regulatory oversight, contractual liability and compliance responsibilities for institutions considering the service (cryptoticker.io).

Confirmed developments and immediate significance

• Confirmed: product in private preview; commercial availability planned early 2027 (coindesk.com; cryptoticker.io).
• Confirmed: uses Confidential Space TEE and attestation to gate MPC signing (cloud.google.com; cryptoticker.io).
• Unresolved: pricing, preview participants and certification status remain undisclosed (coindesk.com; cryptoticker.io).

Useful reader questions and where to look for answers

What is Google Multi-Party Compute and how does it differ from traditional multisig? — Google’s documentation and the product announcement explain the MPC approach (private-key shares, threshold signing) and use of Confidential Space attestation; compare published reference materials for implementation differences (cloud.google.com; cryptoticker.io).

When will Google MPC be commercially available and who can use it? — Google stated a private preview now and commercial availability planned for early 2027; initial target customers are banks and large financial institutions (coindesk.com; cryptoticker.io).

Does Google hold customer assets or is it only supplying technology? — Reporting and Google’s statements indicate Google supplies the custody technology but custodians remain the liable party (cryptoticker.io).

Which cryptographic signatures and blockchains will the service support? — Google intends to support ECDSA and Ed25519 at launch and may add post-quantum methods in future pending network adoption (cryptoticker.io; coindesk.com).

What regulatory approvals do banks need to use this? — CoinDesk and CryptoTicker note supervisory reviews, certifications and contracts are required before banks will place customer assets on the service; institutions should consult their regulators and legal advisers (coindesk.com; cryptoticker.io).

Current status and next steps

Private/closed preview: Google Multi-Party Compute is available only in a private preview and is not generally available (coindesk.com; cryptoticker.io).

Planned commercial availability: Google has stated an intent to make the product commercially available in early 2027 (coindesk.com; cryptoticker.io).

Outstanding disclosures: Google has not released pricing, names of preview participants or detailed certification status; supervisory and contractual processes remain prerequisites for institutional adoption (coindesk.com; cryptoticker.io).

Sources

Google product documentation and reference architecture: cloud.google.com

Event and reporting coverage: CoinDesk (coindesk.com)

Industry reporting and context: CryptoTicker (cryptoticker.io)