Google Targets 2027 Crypto Custody Launch With MPC Preview

Google MPC targets an early-2027 commercial launch

Google told CoinDesk in its October 28 report that major financial institutions and design partners are testing the service. The company did not identify those institutions or disclose pricing.

Alphabet is also using the technology for its own digital assets on Ethereum and Solana, the report said. The assets and amounts were not disclosed. That use does not establish a public rollout for customers across both networks.

Google’s overview still labels Solana support as coming soon, while listing Bitcoin and Ethereum signing. Its release notes describe earlier Curve25519 and Ed25519-related additions. Those statements should not be collapsed into a claim that every documented chain feature is generally available.

The distinction is practical for institutions comparing suppliers. A working internal deployment, a private customer trial and an unrestricted commercial service represent different levels of access, support and operational commitment.

The preview documentation also warns that pre-release offerings are supplied as is and may have limited support. Banks considering production use therefore still need clarity on contractual service commitments, recovery arrangements and the supported transaction types at launch.

No public customer asset total or transaction-volume figure was disclosed in the sources reviewed. Google’s brand recognition gives the preview attention, but those missing adoption measures prevent a reliable comparison of its custody footprint with established providers.

Google MPC signers can override policy denials

The platform’s most consequential qualification concerns the difference between automated screening and final signing authority.

Google’s transaction-policy documentation says transactions are denied by default unless a permission rule matches. A matching prohibition takes precedence over permission. However, a denied transaction can still be signed when enough authorized signers approve it.

The policy result therefore stops automatic signing, while leaving a route for human or organizational authorization. The original evaluation record remains attached to the transaction for auditing. An override is documented behavior, rather than evidence that someone has bypassed the platform’s cryptography.

That architecture makes the signer threshold a central institutional decision. In practical terms, distributing key shares reduces reliance on a single machine, but the institution still decides which people or systems can collectively authorize an exception.

The policy guide also describes a rule-writing hazard: a prohibition that fails to evaluate because information is missing is skipped. Another matching permission can then allow the transaction. Google provides examples showing how rules can require the relevant information instead.

The implication is narrower than a promise to prevent unauthorized transfers. Institutions need both resilient signing infrastructure and approval rules that reflect their intended controls. A cryptographically valid signature does not independently establish that a transfer was commercially sensible or consistent with an institution’s obligations.

These governance questions also arise when banks expand crypto services inside consumer accounts. Access, revenue and asset protection are separate measures of a product’s progress.

Bitcoin controls expanded before Google’s public preview

Google’s release history dates back to August, so the October unveiling should not be described as the first existence of its MPC technology.

An October 1 update added Bitcoin policy features including spending-amount evaluation, change-output detection and destination-address classification. Change detection helps distinguish coins returned to the sender from coins paid to another address, an important distinction when evaluating a transfer’s economic size.

An October 15 update added external identity-provider authentication. Google’s identity-federation guide explains how institutions can use existing corporate identities for staff and automated signing workloads rather than create separate Google Accounts.

The guide separates permission to call the service from roles inside the custody instance. It also requires cryptographic approvals associated with registered authorization keys. That separation is relevant to banks trying to preserve distinct administrative, policy-writing and transaction-approval responsibilities.

The broader crypto mood remained neutral: Alternative.me’s Fear & Greed Index showed 51 when checked October 29. The reading is a sentiment measure, not a test of custody demand or Google’s security claims.

The next milestones are a firm commercial release date, pricing, named institutional deployments and a consistent public statement of chain support. Until then, the announcement establishes a preview and a product direction, while leaving the scale of customer adoption unresolved.