Blockstream has built an enterprise custody product that runs the multi-party computation signing protocol entirely inside Thales hardware security modules, the company said on Nov 13, a design that targets the part of institutional key management that server-based MPC leaves exposed: the machine doing the signing arithmetic.
The product ships through Blockstream Enterprise and pairs what the company calls Secure-MPC with FROST threshold signatures. It extends a Thales relationship Blockstream describes as two years old. Details are in the company’s announcement, which names no customer, no HSM model, and no price.
That gap matters more than it usually would. Custody is the one corner of crypto infrastructure where buyers run procurement the way banks run it: security questionnaires, certification files, audit reports, reference calls. A vendor that leads with architecture rather than logos is making a technical bet, and the bet is that the difference between signing on a hardened appliance and signing on a general-purpose server is now large enough to pay for.
What actually changed inside the signing path
MPC custody splits a private key into shares held by separate parties, and each signing session combines those shares without ever rebuilding the key. The usual criticism of the model is not the cryptography but the host: the shares are combined by software running on ordinary servers, so the security of the whole arrangement depends on the hardening of commodity compute. An attacker who reaches that server gets the inputs to a signing ceremony rather than a single keyfile, which is better, but not the same as never touching the material at all.
Blockstream’s claim is that its implementation executes the signing protocol inside the HSM’s own secure environment instead of passing cryptographic operations out to the host. In the release, the company says the approach keeps sensitive key material protected “throughout the transaction lifecycle, including during signing.” If that holds under audit, the practical effect is that the institution’s signing authority sits behind a boundary that has been validated against a public standard rather than a vendor’s internal hardening checklist.
Thales describes its Luna general-purpose modules, the product line it sells into digital asset deployments, as designed to meet FIPS 140-3 Level 3 and Common Criteria requirements, according to the vendor’s product documentation. That phrase is doing careful work: designed to meet is not the same as certified, and the Blockstream release does not name the module it uses or point to a certificate. Buyers who need the certificate will ask for it in diligence, not in a press release.
The second ingredient is FROST, the Flexible Round-Optimized Schnorr Threshold signature scheme specified in IETF RFC 9591. FROST lets a threshold of authorized parties produce one Schnorr signature without reconstructing the key, which matters for Bitcoin because the result is a single ordinary signature that looks like any other on-chain. Jeff Boortz, Blockstream’s chief product officer, framed the combination as a way to keep 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 argument is about who carries the risk
Michael Minkevich, Blockstream’s president and chief operating officer, tied 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 Thales work “builds on a two-year relationship to combine advanced hardware security with Blockstream’s bitcoin engineering expertise.”
Read past the language and the product is a risk-transfer pitch. A bank that runs MPC on its own servers owns the patching, the network segmentation, the insider controls, and the forensic story if something goes wrong. A bank that runs the same protocol inside a certified appliance pushes part of that story onto the appliance boundary, where the questions become narrower and the answers come with paperwork. Blockstream is not selling a new cryptographic primitive; it is selling a shorter list of things the customer has to prove to its own auditors.
The cost is dependence. An HSM-resident signing path ties the institution to one hardware vendor’s supply chain and to that vendor’s certification schedule, and it makes disaster recovery a question about how key shares are exported, escrowed, and restored 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 the architecture slide.
Thales now sits under two of the largest institutional platforms
The launch also marks the second time this year that a major crypto custody platform has built its security story around Thales hardware. In February, BlockchainReporter covered Fireblocks integrating Thales Luna HSMs into its platform, with the two firms positioning certified hardware as the bridge that lets banks keep existing security models while holding digital assets.
That is 276 days between the two announcements, and the overlap is worth naming. Two of the market’s largest institutional signing platforms now describe their security boundary in terms of the same vendor’s modules. From a buyer’s perspective that is convenient: procurement, audit, and regulator conversations can reuse a familiar name. From a systemic perspective it is concentration. A flaw or a certification lapse in one product line would not stay inside one platform’s customer base.
The release does not describe the relationship as exclusive, and Thales positions the same modules across PKI, code signing, TLS, mobile networks and digital identity as well as digital assets, which is exactly why the hardware carries the certifications it does. Concentration is ordinary in this layer of financial infrastructure, where a short list of vendors supplies the hardware behind card networks and certificate authorities. It is still a dependency that a custody risk committee should be able to describe in one sentence.
The November custody race this lands in
Custody has become the competitive front of institutional crypto this quarter. On Nov 9, Coinbase received final approval for a national trust bank charter from the OCC, a structure that puts federal supervision around its custody business without turning it into a deposit-taking bank. On Nov 13, DTCC said it would extend tokenized DTC securities onto Solana in 2027, adding a third network to a tokenization service that already runs in production. Bank-adjacent custody, exchange custody, and market-infrastructure custody are converging on the same buyers.
Against that field, Blockstream is not competing for the same mandate as a trust bank. It sells the signing layer and the platform underneath an institution’s own custody operation, which means its natural customer is the firm that has decided to hold keys itself and needs to convince a regulator that it did so properly. That is a smaller market than “custody for everyone” and a more defensible one, because the buyer has already concluded that self-operated custody is a strategic requirement.
The timing is not accidental. Custody procurement cycles at banks run for quarters, and a product that arrives without a certification file is competing for the next cycle rather than this one. Hardware-backed signing is an easy argument to make in a diligence meeting. Proving it is a longer project, and the vendors that win mandates are usually the ones that arrive with the paperwork already finished.
What the announcement does not establish
Four things are missing, and each one is the kind of item that turns a good architecture story into a signed contract or leaves it on the shelf.
First, certification evidence. The release says the signing happens inside Thales HSMs but does not identify the module, the firmware version, or the certificate number, and it does not say whether the specific configuration has been validated as a system rather than as a component. Second, independent review. No auditor, penetration test, or code review is named, and the phrase “establishing a new standard” appears without a standard-setting body behind it. Third, references. No institution is named as a user, pilot, or design partner, which is unusual for a launch aimed at bank procurement. Fourth, commercial terms and recovery mechanics, neither of which appears in the text.
None of that makes the claim false. It makes it early. A vendor announcement describes an intended architecture; a FIPS validation listing, a SOC 2 report, and a named customer describe a shipped one. The distance between those two states is usually measured in quarters, and it is the distance that determines whether this becomes a product line or a press release.
There is also a technical question the release leaves open: how the threshold is set. FROST supports different signing thresholds among different numbers of participants, and a two-of-three arrangement behind an HSM boundary has very different failure and collusion properties from a three-of-five arrangement spread across jurisdictions. Blockstream’s description of “distributed protection” is compatible with either. Custody buyers will want the specific configuration, because that is the number that decides what happens when 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 moves from description to evidence. The second will be a reference customer with a name attached, ideally one whose regulator has already examined the setup. The third will be recovery documentation: 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 read as a positioning move in a market that is repricing operational risk. Blockstream has sold Bitcoin infrastructure since 2014 to institutions that wanted to hold their own keys, and the pitch here is that the last soft spot in that stack, the machine that assembles a signature, can be pushed behind certified hardware. Whether banks accept that framing depends less on the cryptography than on the paperwork that follows it.
About the author
Blockchain analyst specializing in the regulatory impact of government policies on the crypto industry. Known for his thorough research and clear, engaging writing, Emmanuel provides insightful analysis on the latest trends, market shifts, and emerging crypto innovations. His work aims to educate and inform both novice and experienced readers, offering expert perspectives on the fast-evolving world of digital assets. With a passion for staying ahead of the curve, Ogwu is a trusted voice in the cryptocurrency and blockchain space.
