Google is preparing to introduce a new digital-asset security system designed to help banks and financial institutions protect cryptocurrencies and tokenized assets as blockchain adoption expands and cybersecurity risks continue to challenge the industry.
The product, called Google Multi-Party Compute (MPC), is currently available in a private preview and is being tested by selected design partners and major financial institutions. Google has also begun using the technology to protect its own digital assets on the Ethereum and Solana blockchains. The company plans to make the service commercially available in early 2027, although pricing and the identities of participating institutions have not been disclosed.
Multi-party computation is an established security approach that divides a private cryptographic key into separate shares distributed across multiple systems. Rather than relying on one complete key stored in a single location, the method allows authorized participants to jointly approve transactions without any individual system holding the entire signing credential. This approach can reduce the risk associated with a single point of failure.
Google has previously supported MPC-based digital-asset infrastructure through its cloud security tools, but the new service is designed specifically for institutional crypto custody. It combines transaction signing, customizable approval policies, and key recovery in a dedicated product, building on existing services such as Google Cloud Key Management Service and Cloud HSM.
The launch comes as financial institutions explore blockchain-based payments, tokenized securities, and digital-asset custody. These activities require strong controls because blockchain transactions are generally difficult or impossible to reverse once confirmed. If an attacker obtains control of a wallet's private key, the assets may be transferred without the owner's authorization.
Security remains a major concern for the digital-asset sector. Historical incidents involving compromised private keys have resulted in substantial losses, highlighting the importance of protecting the credentials used to authorize blockchain transactions. As financial institutions expand their exposure to digital assets, security systems must address not only external attacks but also operational errors, unauthorized approvals, and weaknesses in internal access controls.
Google's system is designed to distribute signing credentials across different environments. For example, a financial institution could store one key share in Google Cloud, another on its own hardware, and a third with a separate cloud provider. When a transaction is requested, it enters Google's Confidential Space environment, where a policy engine checks whether it complies with the institution's rules before signing can proceed.
These policies can include transfer limits, approved destination wallets, and mandatory authorization from multiple departments. The system supports different approval thresholds, including arrangements that require two of three participants or five of seven participants to cooperate in producing a valid signature. This flexibility could help banks retain greater control over their assets while using cloud infrastructure for transaction processing.
Google says the service also supports rapid transaction signing and key recovery. However, independent performance comparisons with competing products have not been provided. Its effectiveness will depend on how institutions configure their security policies, protect participating systems, and restrict changes to transaction-approval rules.
The planned launch also places Google in closer competition with established digital-asset security providers such as Fireblocks, Fordefi, and BitGo. These companies already offer technology designed to help institutions secure wallets and authorize blockchain transactions. Google is positioning its cloud infrastructure and established relationships with financial institutions as potential advantages, while presenting itself as a technology provider that allows banks to operate their own custody services.
Nevertheless, distributing cryptographic keys does not eliminate every security risk. Institutions may still rely on Google for critical software, policy enforcement, and operational infrastructure. Vulnerabilities in these components, misconfigured permissions, compromised approval participants, or unauthorized changes to security rules could still create exposure.
As artificial intelligence tools become more capable, financial institutions must also consider how AI-assisted attacks could increase the speed and sophistication of phishing, social engineering, and attempts to compromise access credentials. Strong cryptographic controls, carefully designed approval procedures, and continuous monitoring will remain important regardless of which technology provider an institution selects.
Google's upcoming service reflects the growing demand for institutional-grade infrastructure as traditional finance moves deeper into blockchain-based markets. Its long-term success will depend on whether banks view the system as a reliable way to strengthen custody operations, maintain control over transaction authorization, and reduce their dependence on any single security component.
