Security

Blockstream researchers publish security analysis for SHRINCS

Blockstream researchers Jonas Nick and Mikhail Kudinov released a security analysis for SHRINCS, a post-quantum signature scheme for Bitcoin. The proposal offers stateful paths ranging from 548 to 4,619 bytes and a 5,777-byte stateless path to balance efficiency and implementation risks.

Blockstream researchers publish security analysis for SHRINCS

New security analysis for SHRINCS

SHRINCS provides a strong, conservative basis for Bitcoin’s post-quantum security by using SHA-256 to anchor its security in primitives the network already uses. Blockstream Research Director Jonas Nick and researcher Mikhail Kudinov published a security analysis on Thursday for this emerging post-quantum signature scheme. The scheme provides two spending paths to balance efficiency and security risks. The stateful path provides a compact option, while the stateless path reduces risks at the implementation level. Mikhail Kudinov, a post-quantum cryptography researcher at Blockstream, said regarding the draft Bitcoin Improvement Proposal that "there are a lot of things to check, test, complain about, or praise." The SHRINCS working group includes researchers backed by nonprofits such as Brink and OpenSats who continue to refine the proposal’s specification. Current ECDSA signatures are 71 bytes long and Taproot Schnorr signatures are 64 bytes.

Signature Type Size (Bytes)
Current ECDSA 71
Taproot Schnorr 64
SHRINCS Stateful 548 to 4,619
SHRINCS Stateless 5,777

Mitigating stateful failures and fees

The stateful signature path provides the most efficient way to handle transactions, though it creates a vulnerability where an attacker can forge a signature and steal funds if a user accidentally reuses a one-time state. Because stateful signatures rely on one-time keys, wallet developers must track each key’s state correctly. Jonas Nick told Isabel Foxen Duke on MARA Foundation TV that "it needs to be impossible for the user to behave in a way that this catastrophic event happens." To prevent this, Nick says the specification and wallet implementations must automatically enforce the stateless path fallback in any situation where a state counter could possibly be compromised. While some users might use stateless signatures out of caution, Nick warns that widespread adoption could bloat the blockchain and drive up fees. "We don’t know what the fee market will look like once we have these very big signatures," Nick said, adding that fewer transactions fitting into a block could change the value proposition of Bitcoin. Stateful signatures range from 548 to 4,619 bytes, while stateless ones are 5,777 bytes. Optimization of both signature paths is accelerating through AI-based research, though the ecosystem must still decide if it can embrace these inherent trade-offs. Nick and Kudinov are requesting review of the proposal and the security analysis.