Google to preview crypto custody security system as AI threats grow

Institutional crypto custody has relied on vendors like Fireblocks, Coinbase Custody and BitGo, which split private keys using multi-party computation to avoid a single point of failure after years of exchange hacks going back to Mt. Gox. Google now wants a seat at that table, previewing its own MPC service at a New York digital asset security symposium while a newly disclosed flaw in Fireblocks' MPC library reminds the market that even distributed-key systems carry implementation risk.

Banks testing Google's system get an alternative to handing custody entirely to specialist vendors, distributing transaction-signing authority across multiple parties so no single compromised server can move funds. Alphabet's own use of the tool to secure Ethereum and Solana holdings doubles as a public stress test. Institutions weighing adoption must still wait: commercial availability isn't planned until early 2027, so any near-term shift in who custodies bank crypto holdings stays theoretical.

MPC is sold as removing single points of failure, but routing institutional custody through Google Cloud's infrastructure concentrates a different kind of dependency in one company's hands. A cloud provider holding the rails for bank-grade crypto key management sits awkwardly next to the industry's self-custody ethos, and the Fireblocks bug shows that 'distributed' key systems can still fail in ordinary software ways, not just through theoretical quantum attacks Google cites as justification.

The real test arrives with commercial availability in early 2027, when it becomes clear whether the banks now in private preview actually move production assets onto Google's system or treat it as a backup to incumbents like Fireblocks. Watch also whether Google discloses which institutions are testing the service and whether the Fireblocks vulnerability gets patched before rivals use it to question MPC's security claims broadly.