🛼 I Got a Brand New Pair of Roller Skates; You Got a Brand New Key 🔑
By design, the lone private key that once sat at the heart of the security setup—that long-standing single point of failure—is gone; instead, key shares are distributed across hardware-backed environments, and no party, custodian or counterparty alike, ever holds or reconstructs a complete key.
Several details follow.
Distributed key shares move across Google Cloud, on-premises hardware, other clouds, or compact devices, and signing takes place via a multi-party protocol in which the master key is never assembled—a parliament of shards, so to speak, producing a signature without any member seeing the whole.
The system is built on the DKLS23 protocol, supported by threshold signatures in configurations such as 2-of-3 or 5-of-7: attacks below the threshold fail, and the system holds as long as enough shares stay online.
ECDSA over secp256k1 is supported for Bitcoin, Ethereum, and EVM networks; EdDSA support is promised rather than delivered.
Governance is built in rather than added on—KeyRings and KeyPolicies, roles such as Admin and Signer, and automated pre-signing checks written in the Cedar policy language, including Bitcoin-specific rules, added in October 2026.
Notably, those policy checks advise signers rather than hard-blocking transactions a quorum has already approved—a whisper in the ear, not a padlock on the door.
Morgan Stanley, Citi, Wells Fargo, and OKX were among the banks present at Google's MPC symposium, a turnout that indicates institutional appetite far from lukewarm.
The packaged service consolidates what was once a fragmented security stack into a single offering, and in doing so puts big tech squarely in competition with digital currency native vendors.
The overall verdict: cloud-native threshold cryptography is making single-party key control obsolete for institutional digital asset custody.
