Crypto news account @WatcherGuru said on October 28 that Google had unveiled a new system for banks. The report points to an institutional product rather than a consumer wallet or trading service, with the focus on controlling the private keys and transaction approvals needed to move digital assets securely.
The available reporting indicates that the product is called Google Multi-Party Compute, or Google MPC. However, the details remain limited. CoinDesk reported that the system is in private preview, is being tested by financial institutions and is expected to become commercially available in early 2027.
CoinDesk said the product uses multi-party computation, a cryptographic approach that divides control of a private key among multiple parties or systems. Rather than keeping a complete signing key in one location, the design can require several coordinated components to approve a transaction. That can reduce the consequences of a single compromised server, credential or administrator account.
The report did not identify the financial institutions testing the system. It also did not specify which cryptocurrencies, tokenized assets or blockchains are supported. Google has not publicly described whether Google Multi-Party Compute is intended to operate as a custody platform, a hardware-backed key management service, a cloud security product or a broader suite for tokenized securities.
CoinDesk also said it did not identify a public Google announcement or product page for the 2026 product. That distinction matters. The system appears to be an emerging offering in private preview, rather than a broadly available service with published specifications, pricing and customer documentation.
Google Cloud has previously described technology that could provide part of the foundation for this type of infrastructure. In its technical material on Confidential Space and multi-party computation for digital assets, Google Cloud explained how confidential computing and MPC can be combined to protect digital-asset operations.
Confidential computing is designed to protect data while it is being processed, including within a protected execution environment. For digital assets, that could help institutions perform signing or transaction-related operations without exposing sensitive information to ordinary applications, administrators or underlying infrastructure. MPC adds another layer by distributing the authority required to authorize a transaction.
These technologies address a central challenge for banks entering crypto markets. In traditional finance, institutions can often reverse or investigate certain transactions through established intermediaries. Blockchain transactions typically depend on cryptographic authorization, and a lost, stolen or misused key can create a direct operational and financial risk.
A bank-focused security system could therefore support more than simple asset storage. It could be used for transaction approvals, treasury operations, settlement workflows and controls around transfers between institutions. Those functions would need to work alongside compliance checks, internal permissions, audit records and procedures for responding to suspected attacks.
Google’s wider digital-asset strategy also includes infrastructure for tokenized financial products. In a separate Google Cloud explanation of its Universal Ledger, the company described the platform as infrastructure for issuing, managing and settling tokenized assets, including bonds, funds and collateral.
Universal Ledger is not documentation for the new custody system, and Google Cloud did not present it as evidence that Google Multi-Party Compute is commercially available. It does, however, show how Google is positioning its institutional blockchain activity. The company is addressing several layers of the market, from the infrastructure used to represent and settle tokenized assets to the security systems needed to protect the authority to move them.
That combination could become important as banks explore tokenized deposits, funds, securities and collateral. Issuing a token is only one part of the process. Financial institutions also need reliable controls for who can transfer it, how approvals are recorded, how assets are segregated and what happens when a key, system or service provider is compromised.
The competitive implications could extend beyond traditional crypto custodians. Cloud providers, specialist custody companies and blockchain infrastructure firms all offer tools for key management, policy enforcement and transaction execution. Google’s participation could give banks access to those capabilities through infrastructure they already use, although adoption will depend on security certifications, regulatory acceptance, service reliability and integration with existing banking systems.
The product also faces limitations. Crypto Briefing’s Kaye Quema argued that MPC does not remove risks caused by weak approval policies, insider collusion or vulnerabilities in the software used to sign transactions. In other words, distributing key material can reduce a single point of failure, but it cannot replace strong governance.
That is the only critical reaction identified in the sources reviewed for this report. No opposing institutional or regulatory response was provided. The absence of a broader response means the system’s significance is still difficult to assess.
Google’s announcement, as described by the available reporting, is best viewed as an early institutional-security development. The important evidence will come when the company publishes technical documentation, names customers or partners, identifies supported networks and explains how the service handles audits, customer-asset segregation, incident response and regulatory obligations.
If Google delivers those capabilities, it could help banks treat digital assets less as an isolated technology experiment and more as a manageable part of financial infrastructure. For now, the private preview signals ambition, but the product’s commercial scope and security model remain unconfirmed.
- coindesk.com · Link preview (og:image)
Jessica Jones is not a person. No notebook, no deadlines, no face behind the name — just a byline this newsroom publishes under. Here is the production line underneath it, because a name beside a portrait reads like a journalist, and this one is not one.
The models. Writing: gpt-5.6-luna. Out on the live web: gpt-5.6-luna and gpt-5.6-terra. Pictures: gpt-image-1. Swap one in the newsroom and this line swaps with it — it is read off the machines, not typed here.
How a story is made
- Research. The searching model reads around the story, pointed at primary sources — the filing, the post, the repository — rather than at somebody else's write-up of them.
- Writing. The writing model drafts it against what was found, at Jessica Jones's usual length and in Jessica Jones's usual register.
- The loop. A reviewer reads the draft and sends it back with notes. Then reads it again. A piece can go round several times before it leaves the building.
- Enrichment. A quotation has to appear word for word on the page it is taken from. A chart may only use figures that appear in the source it cites. Whatever fails is dropped, and the reason is kept.
- Fact check. A last pass hunts for claims the article makes and its sources do not.
- A human stop. Sensitive subjects are held for a person to read before publication, and a person can kill any of it at any point.
If that sounds less like a newsroom and more like a factory: quite. It is called Press Factory.
This article was generated using AI and published automatically without human pre-publication review.
Read and checked by admin on 10/28/2026
How this article was made
The article was produced by the Grandmonts Media News Engine using automated research, drafting and verification workflows. No human editor reviewed the article before publication. Grandmonts Media remains responsible for the published content. Errors can be reported at office@grandmonts.cz.