Key Highlights:
- Blockstream has integrated its Bitcoin signing protocol directly into Thales Hardware Security Modules (HSMs) using the FROST threshold signature scheme, removing the need to execute Multi-Party Computation (MPC) on general-purpose host servers.
- The collaboration enables institutions to transfer operational risk to certified hardware boundaries, reflecting a growing architectural concentration as Thales now underpins signing operations for both Blockstream and Fireblocks.
- The initial announcement omits critical procurement details, including specific FIPS certification listings, independent audit documentation, named institutional reference customers, and disaster recovery mechanics.
Re-Engineering the Bitcoin Signing Path
In standard Multi-Party Computation (MPC) custody architectures, private keys are divided into discrete shares distributed among several participants. A signing ceremony combines these shares without ever exposing or reconstituting the complete private key. However, institutional custody risk has traditionally centered on the compute layer: these cryptographic shares are often processed and combined via software operating on standard, commodity servers. This setup leaves the signing inputs vulnerable to attacks aimed at host-level vulnerabilities, forcing enterprise operators to bear the full burden of internal server hardening, patching, and forensic isolation.
Blockstream is altering this operational model by executing its signature protocol directly within the tamper-resistant hardware boundary of Thales Hardware Security Modules (HSMs). According to the company’s announcement, this mechanism ensures sensitive key shares remain protected throughout the transaction lifecycle, including during signing.
By embedding the cryptographic operations within a dedicated physical appliance, the platform shifts institutional security boundaries from an internal vendor-maintained server checklist to an externally verifiable standard.
The system leverages Flexible Round-Optimized Schnorr Threshold (FROST) signatures, an open standard defined under IETF RFC 9591. FROST allows a predefined threshold of authorized entities to collaborate and generate an ordinary, standard Schnorr signature without revealing underlying key shares, yielding a single transaction output that appears identical to standard Bitcoin network activity. Explaining the architectural pivot, Jeff Boortz, Blockstream’s chief product officer, stated that By moving MPC execution inside the HSM, this architecture addresses critical security risks while preserving practical and popular signing capabilities valued by organizations who manage digital assets.
Boortz added that Blockstream had invested heavily in advanced cryptographic technologies, including FROST, to address the security requirements of institutional bitcoin custody.
Commercial Risk Transfer and Hardware Vendor Concentration
Beyond theoretical security gains, the integration is aimed directly at how institutional risk committees and regulated entities evaluate digital asset custody. Michael Minkevich, Blockstream’s president and chief operating officer, framed the product around institutional procurement priorities, noting, Financial institutions require secure, reliable infrastructure as they integrate bitcoin into their existing operations.
Minkevich noted that the initiative with Thales builds on a two-year relationship to combine advanced hardware security with Blockstream’s bitcoin engineering expertise.
By containing the MPC process within an appliance boundary, custody institutions can simplify their technical compliance audits. Rather than justifying every operating system update, segmentation protocol, and insider control across a farm of custom MPC servers, institutions can rely on formal hardware appliance validation. However, this model introduces dependencies: relying on HSM-resident execution binds the entity strictly to a single hardware vendor’s proprietary supply chain and firmware delivery cycle, while elevating questions around share escrow and catastrophic recovery should hardware units fail.
The partnership also underscores a growing vendor concentration across enterprise digital asset infrastructure. This deployment marks the second time in 2024 that an institutional custody heavyweight has standardized its security claims around Thales technology; in February, Fireblocks announced its own platform integration with Thales Luna HSMs. With 276 days separating the two announcements, Thales now serves as the foundational root of trust for two of the crypto ecosystem’s primary signing platforms. While shared infrastructure streamlines due diligence for procurement teams familiar with Thales Luna appliances, it introduces systemic supply-chain concentration risks across the broader institutional digital asset market.
Missing Institutional Artifacts and Procurement Hurdles
While the architectural premise is clear, Blockstream’s initial release lacks several operational details required to convert marketing momentum into signed enterprise contracts. Thales Luna documentation positions its modules as designed to meet
FIPS 140-3 Level 3 and Common Criteria standards; however, Blockstream’s release does not supply an active certification record, a specific cryptographic module number, or designated firmware revisions.
Key unanswered components essential for enterprise sign-off include:
- Formal Certification Documentation: The announcement lacks a public FIPS 140-3 validation certificate for this specific integrated configuration.
- Third-Party Validation: No independent code reviews, penetration test outcomes, or accredited standards organizations were cited to substantiate claims of
establishing a new standard.
- Designated Reference Clients: No banks, qualified custodians, or production pilot institutions were revealed as launch partners.
- Operational Recovery Frameworks: The release omits mechanics governing quorum configuration thresholds (such as 2-of-3 versus 3-of-5 layouts), disaster recovery schemes, and share extraction procedures during hardware failures or firmware revisions.
Why This Matters
The institutional custody sector is undergoing rapid evolution across multiple fronts. Key market milestones in November emphasize this shift: Coinbase obtained final regulatory approval for a national trust bank charter from the Office of the Comptroller of the Currency (OCC), and the Depository Trust and Clearing Corporation (DTCC) announced plans to introduce tokenized DTC securities onto the Solana blockchain in 2027. Amid this expanding playing field, custody models from trust banks, centralized exchanges, and infrastructure providers are competing for overlapping institutional capital.
Blockstream’s model does not compete with full-service institutional trust banks for broad deposit custody. Instead, it targets tier-one institutions committed to running self-operated custody stacks that must satisfy regulatory examinations. In these high-compliance environments, sales cycles take multiple quarters. For Blockstream, achieving institutional adoption will ultimately rely on presenting signed third-party audit reports, public FIPS validation listings, and robust escrow workflows to enterprise custody committees.
Frequently Asked Questions
How does running FROST inside an HSM differ from traditional MPC custody?
Standard MPC solutions execute transaction-signing protocols using proprietary software running on general-purpose host servers, meaning the operational host represents a potential target. Blockstream’s implementation confines the FROST signature execution directly within the physical, tamper-evident boundaries of a Thales Luna HSM, eliminating server-level exposure during the signing process.
Why does reliance on Thales by both Blockstream and Fireblocks matter?
Thales now supplies the hardware foundation for two major institutional digital asset custody architectures. While this provides procurement familiarity for compliance officers, it creates systemic concentration risk. Any hardware flaw, architectural vulnerability, or certification disruption within the underlying Thales Luna product line could simultaneously impact multiple market infrastructure providers.
What must Blockstream present next to win regulated institutional mandates?
To pass comprehensive institutional due diligence, Blockstream must publish public FIPS 140-3 certification records for this exact software-hardware combination, provide third-party audit reports, reveal named pilot clients, and publish documentation detailing key share recovery and firmware upgrade procedures.




