Blockstream has developed an enterprise custody product that runs the multi-party computation signing protocol entirely inside Thales hardware security modules, the company said on Nov 13. The design targets a part of institutional key management that server-based MPC leaves exposed: the machine that performs the signing calculations.
The product is offered through Blockstream Enterprise and combines what the company calls Secure-MPC with FROST threshold signatures. It builds on a Thales relationship that Blockstream says began two years ago. The company’s announcement names no customers, HSM model or price.
That absence matters more than it might in other markets. In crypto infrastructure, custody is the area where buyers follow bank-style procurement processes: security questionnaires, certification files, audit reports and reference calls. A vendor that leads with architecture rather than customer names is making a technical bet: that the difference between signing on a hardened appliance and signing on a general-purpose server is now large enough to justify the cost.
What changed in the signing process
MPC custody divides a private key into shares held by separate parties. Each signing session combines the shares without ever reconstructing the key. A common criticism of the model concerns not the cryptography but the host: the shares are combined by software on ordinary servers, making the security of the arrangement depend on how well commodity computing systems are hardened. An attacker who gains access to such a server gets the inputs to a signing ceremony rather than a single keyfile. That is an improvement, but it is not the same as never accessing the material at all.
Blockstream says its implementation runs the signing protocol inside the HSM’s secure environment instead of sending cryptographic operations to the host. In its release, the company says the approach keeps sensitive key material protected “throughout the transaction lifecycle, including during signing.”. If that claim holds up under audit, the practical result is that the institution’s signing authority sits behind a boundary validated against a public standard, rather than one secured only by a vendor’s internal hardening checklist.
According to Thales product documentation, its Luna general-purpose modules, which it sells for digital asset deployments, are designed to meet FIPS 140-3 Level 3 and Common Criteria requirements. The wording is precise: designed to meet is not the same as certified, and Blockstream’s release does not identify the module it uses or cite a certificate. Buyers who require the certificate will ask for it during due diligence, not in a press release.
The other component is FROST, the Flexible Round-Optimized Schnorr Threshold signature scheme specified in IETF RFC 9591. FROST allows a threshold of authorized parties to produce a single Schnorr signature without reconstructing the key. This matters for Bitcoin because the result is one ordinary signature that looks like any other signature on-chain. Jeff Boortz, Blockstream’s chief product officer, described the combination as a way to maintain familiar signing workflows while tightening the underlying process.
“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 said in the release. He also said the company had “invested heavily in advanced cryptographic technologies, including FROST, to address the security requirements of institutional bitcoin custody.”
The commercial case centers on who bears the risk
Michael Minkevich, Blockstream’s president and chief operating officer, linked the launch to how banks buy infrastructure, rather than to how traders use it. “Financial institutions require secure, reliable infrastructure as they integrate bitcoin into their existing operations,” he said, adding that the work with Thales “builds on a two-year relationship to combine advanced hardware security with Blockstream’s bitcoin engineering expertise.”
Look past the messaging and the product is a pitch about transferring risk. A bank that runs MPC on its own servers is responsible for patching, network segmentation, insider controls and the forensic account if something goes wrong. A bank running the same protocol inside a certified appliance shifts part of that responsibility to the appliance boundary, narrowing the questions and providing documentation to support the answers. Blockstream is not selling a new cryptographic primitive. It is selling a shorter list of things customers must prove to their own auditors.
The tradeoff is dependence. An HSM-based signing process ties the institution to one hardware vendor’s supply chain and certification schedule. It also raises disaster-recovery questions about exporting, escrow and restoring key shares when the appliance is unavailable. Blockstream’s announcement does not address recovery, escrow or what happens during an HSM firmware upgrade. Those are the questions a custody committee asks after seeing the architecture slide.
Thales is now part of two of the largest institutional platforms
The launch is also the second time this year that a major crypto custody platform has built its security case around Thales hardware. In February, BlockchainReporter covered Fireblocks’ integration of Thales Luna HSMs into its platform. The two companies presented certified hardware as a bridge that lets banks retain existing security models while holding digital assets.
The announcements are 276 days apart, and the overlap is worth noting. Two of the market’s largest institutional signing platforms now describe their security boundaries in terms of modules from the same vendor. For buyers, that is convenient: they can reuse a familiar name in procurement, audit and regulatory discussions. From a systemic perspective, it creates concentration. A flaw or certification lapse in one product line would affect customers across more than one platform.
The release does not call the relationship exclusive. Thales also offers the same modules for PKI, code signing, TLS, mobile networks and digital identity, as well as digital assets, which helps explain the certifications they carry. Concentration is common in this layer of financial infrastructure, where a small group of vendors supplies hardware for card networks and certificate authorities. Still, a custody risk committee should be able to describe this dependency in one sentence.
The November custody race this lands in
Custody has become a competitive front in institutional crypto this quarter. On Nov 9, Coinbase received final approval for a national trust bank charter from the OCC, a structure that places its custody business under federal supervision without making it a deposit-taking bank. On Nov 13, DTCC said it would extend tokenized DTC securities to Solana in 2027, adding a third network to a tokenization service already operating in production. Bank-adjacent custody, exchange custody and market-infrastructure custody are converging on the same buyers.
In this market, Blockstream is not pursuing the same mandate as a trust bank. It sells the signing layer and the platform beneath an institution’s own custody operation. Its natural customer is therefore a firm that has decided to hold keys itself and needs to show a regulator it did so properly. That is a smaller market than “custody for everyone”, and a more defensible one, because the buyer has already decided that self-operated custody is a strategic requirement.
The timing is deliberate. Bank custody procurement can take quarters, and a product launched without a certification file is competing for the next cycle rather than the current one. Hardware-backed signing is an easy argument to make in a due diligence meeting. Proving the case takes longer, and vendors that win mandates are usually those that arrive with the paperwork already complete.
What the announcement does not establish
Four items are missing. Each could help turn a strong architecture case into a signed contract, or leave it on the shelf.
First, certification evidence. The release says signing takes place inside Thales HSMs but does not identify the module, firmware version or certificate number. It also does not say whether the specific configuration has been validated as a system or only as a component. Second, independent review. The announcement names no auditor, penetration test or code review, and uses the phrase “establishing a new standard” without identifying a standard-setting body. Third, references. It names no institution as a user, pilot participant or design partner, which is unusual for a launch aimed at bank procurement. Fourth, commercial terms and recovery procedures, neither of which is mentioned.
None of this proves the claim is false. It means the product is at an early stage. A vendor announcement describes an intended architecture; a FIPS validation listing, a SOC 2 report and a named customer describe a product in use. The gap between those states is usually measured in quarters, and it will determine whether this becomes a product line or remains a press release.
The release also leaves open a technical question: what threshold is used. FROST supports different signing thresholds across different numbers of participants. A two-of-three arrangement behind an HSM boundary has different failure and collusion properties from a three-of-five arrangement distributed across jurisdictions. Blockstream’s description of “distributed protection” is consistent with either. Custody buyers will want the specific configuration, because it determines what happens if one share holder is unavailable, compromised or subpoenaed.
What to watch next
The first signal will be a certificate. If Blockstream publishes a FIPS 140-3 validation or a Common Criteria certificate for the specific configuration, the architecture claim will move from description to evidence. The second will be a named customer, ideally one whose regulator has already examined the setup. The third will be recovery documentation explaining how shares are backed up, how a signing quorum is restored after a hardware failure and who holds the escrow.
Until then, the launch is best understood as a positioning move in a market that is reassessing operational risk. Blockstream has sold Bitcoin infrastructure to institutions that wanted to hold their own keys since 2014. The pitch is that the last vulnerable point in that stack, the machine that assembles a signature, can be placed behind certified hardware. Whether banks accept that case depends less on the cryptography than on the documentation that follows.
