Google's Multi-Party Compute buys stronger key security at one new dependence.谷歌的 Multi-Party Compute 用更强的密钥安全，换来一项新的依赖。

Your coins now move only when Google's cloud agrees to sign. That is the trade worth seeing.

Unveiled October 28 at Google's first MPC symposium in New York, the service splits a private key into fragments held on separate systems, so no single breach hands over the whole key. That part is real security. Alphabet already runs its own Ethereum and Solana holdings on it, general availability is slated for early 2027, and the target is clearly Fireblocks and BitGo.

But splitting the key does not remove the dependence; it relocates it. The fragments, the signing coordination, and the machines all sit inside one cloud. The failure you engineer out is a hacker stealing the key. The failure you engineer in is the vendor declining to sign: an outage, a compliance hold, a jurisdiction. The single point of failure moved from your attacker to your supplier.

The custody layer of money that was supposed to need no trusted third party is consolidating into the same hyperscalers that already run traditional finance. Alphabet securing its own coins on its own product is the tell.

So before adopting it, price the trade: can you keep a decisive fragment, or the signing quorum, off Google and migrate without its cooperation? If not, you swapped theft risk for vendor risk. We would revise this if Google's general-availability terms let institutions hold a decisive fragment outside its cloud and migrate at low cost.

Research, not investment advice.