Google is stepping in to build crypto custody security itself 🔐
According to CoinDesk, Google Cloud previewed Google Multi-Party Compute (MPC) at its first digital assets symposium in New York on 10-28. It’s aimed at banks and financial institutions.
1️⃣ Private keys are split into fragments and stored separately: for example, one with Google Cloud, one on the bank’s own hardware, and one with another cloud provider. Signing thresholds can be set, such as 2-of-3 or 5-of-7.
2️⃣ Before anything is signed, it goes through a policy engine: transfer limits, whitelisted destination addresses, and approvals from multiple departments are all checked in an isolated Confidential Space environment.
3️⃣ It’s currently in private preview, with several institutions testing it, but Google hasn’t named any of them.
4️⃣ Alphabet is already using it to protect assets on the $ETH and $SOL blockchains. The specific assets haven’t been disclosed.
5️⃣ Commercial launch is planned for early 2027, and pricing hasn’t been announced. At GA, it will support ECDSA and Ed25519, with a post-quantum upgrade planned for later.
My take: MPC isn’t new—Fireblocks, BitGo, and others have been doing it for years. What’s new is that Google has packaged it as a ready-made product, so banks don’t have to build their own solution from scratch. For TradFi, saying “we use Google” may carry more weight in a compliance meeting than the technology itself.
The real thing to watch is who signs up when it launches in 2027. It’s still only a preview for now, so don’t read too much into it.
Source: CoinDesk report dated 10-28 (Google provided information to CoinDesk). Not investment advice.
According to CoinDesk, Google Cloud previewed Google Multi-Party Compute (MPC) at its first digital assets symposium in New York on 10-28. It’s aimed at banks and financial institutions.
1️⃣ Private keys are split into fragments and stored separately: for example, one with Google Cloud, one on the bank’s own hardware, and one with another cloud provider. Signing thresholds can be set, such as 2-of-3 or 5-of-7.
2️⃣ Before anything is signed, it goes through a policy engine: transfer limits, whitelisted destination addresses, and approvals from multiple departments are all checked in an isolated Confidential Space environment.
3️⃣ It’s currently in private preview, with several institutions testing it, but Google hasn’t named any of them.
4️⃣ Alphabet is already using it to protect assets on the $ETH and $SOL blockchains. The specific assets haven’t been disclosed.
5️⃣ Commercial launch is planned for early 2027, and pricing hasn’t been announced. At GA, it will support ECDSA and Ed25519, with a post-quantum upgrade planned for later.
My take: MPC isn’t new—Fireblocks, BitGo, and others have been doing it for years. What’s new is that Google has packaged it as a ready-made product, so banks don’t have to build their own solution from scratch. For TradFi, saying “we use Google” may carry more weight in a compliance meeting than the technology itself.
The real thing to watch is who signs up when it launches in 2027. It’s still only a preview for now, so don’t read too much into it.
Source: CoinDesk report dated 10-28 (Google provided information to CoinDesk). Not investment advice.