Google is preparing to launch a Multi-Party Computation (MPC) service for institutional digital asset custody, currently in private preview with major financial institutions testing the platform for Ethereum and Solana security, with commercial availability expected in early 2027. The development follows CERT/CC's October 26 disclosure of vulnerability VU#701544 in Fireblocks' MPC library, which affects BIP32 hardened key derivation and could weaken protections separating cryptographic key shares. MPC technology distributes private key shares across multiple parties to authorize transactions without assembling a complete key in one location, reducing single-point compromise risks in institutional crypto custody systems.
Google MPC Service Targets Institutional Custody With Ethereum and Solana Support
Google's reported MPC service is in private preview, with major financial institutions testing the technology for securing digital assets on Ethereum and Solana. Commercial availability is expected in early 2027. Google Cloud previously supported institutional MPC deployments through Confidential Space, which uses confidential computing and hardware-backed attestation to verify sensitive workloads and restrict access to protected data during blockchain transaction signing. The new service would extend Google's involvement in dedicated institutional crypto security by combining cloud infrastructure with cryptographic controls for organizations managing digital asset holdings.
CERT/CC Discloses Fireblocks MPC Library Vulnerability Affecting Key Derivation
CERT/CC published vulnerability VU#701544 on October 26, identifying a flaw in Fireblocks' mpc-lib library. The issue affects the implementation of BIP32 hardened key derivation when a required private parent key is missing. According to the advisory, the library can substitute a zero-filled buffer instead of rejecting the operation. If an attacker obtains a compromised descendant signer share and its associated chain code, the attacker may recover ancestor shares within that party's key hierarchy. The flaw does not expose a complete, spendable private key but weakens protections designed to limit how far a compromised share can expose related key material. CERT/CC stated no vendor fix was available at the time of advisory publication and recommended keeping chain codes confidential and avoiding reliance on hardened derivation to isolate signer shares until the implementation is corrected.
MPC Implementation Requires Assessment Beyond Key Distribution
MPC distributes private keys across multiple parties, with each participant holding a separate key share that collaborates to authorize transactions without assembling a complete private key in one place. This design reduces risks associated with a single compromised device or insider. Institutions assessing MPC custody systems need to evaluate implementation details, transaction approval policies, and recovery procedures, as MPC is a cryptographic technique rather than a guarantee that every component of a custody system is secure. The Fireblocks vulnerability demonstrates that derivation logic, access controls, and transaction approval mechanisms require scrutiny alongside key distribution methods.
FAQ
What is Google's MPC service for crypto custody?
Google is preparing an MPC service for institutional digital asset custody, currently in private preview with major financial institutions testing the platform for Ethereum and Solana security, with commercial availability expected in early 2027.
What vulnerability did CERT/CC disclose in Fireblocks' MPC library?
CERT/CC disclosed vulnerability VU#701544 on October 26, identifying a flaw in Fireblocks' mpc-lib library affecting BIP32 hardened key derivation that can substitute a zero-filled buffer when a required private parent key is missing, potentially allowing attackers with a compromised descendant signer share and chain code to recover ancestor shares.
How does MPC technology work in crypto custody?
MPC allows multiple parties to participate in transaction signing by holding separate key shares that collaborate to authorize transactions without assembling a complete private key in one location, reducing risks associated with a single compromised device or insider.
