Key facts
- Blockstream's Jonas Nick and Mikhail Kudinov published a security analysis of SHRINCS, a post-quantum Bitcoin signature scheme.
- SHRINCS uses SHA-256 and combines a compact stateful path with a larger stateless fallback.
- Nick said wallets must automatically enforce the stateless fallback where a state counter could be compromised.
- Stateful SHRINCS signatures run 548 to 4,619 bytes; stateless ones are 5,777 bytes, per the report.
- Nick said heavy stateless use could take block space and raise fees across the network.
Blockstream Research Director Jonas Nick, with researcher Mikhail Kudinov and collaborators, published a security analysis on Thursday of SHRINCS, a candidate post-quantum signature scheme for Bitcoin. Kudinov, a post-quantum cryptography researcher at Blockstream, asked engineers, cryptographers and protocol developers for feedback on a draft of the scheme's Bitcoin Improvement Proposal.
SHRINCS is a hash-based signature scheme that uses SHA-256, the hash function Bitcoin already relies on, which the researchers describe as a conservative effort to limit the proposal's trust assumptions. The scheme combines two spending paths: a compact stateful signature option and a larger, costlier stateless path with fewer implementation risks.
The stateful path relies on one-time keys that can safely sign only a single transaction. If a one-time state is reused by accident, an attacker could forge a signature for that address and take the funds, so wallet developers must track each key's state. Nick told Isabel Foxen Duke, head of the MARA Foundation, during an appearance on MARA Foundation TV that it must be impossible for a user to trigger that failure and that wallet developers need to handle the stateful component correctly. He said the specification and wallet implementations must automatically fall back to the stateless path wherever a state counter could be compromised.
Signature sizes differ widely. Bitcoin's current ECDSA signatures are typically 71 bytes and Taproot Schnorr signatures 64 bytes, according to the report. Under SHRINCS, stateful signatures run from 548 to 4,619 bytes and stateless ones are 5,777 bytes. Nick said heavy use of stateless signatures could take up block space and raise fees, and that fewer transactions would fit in a block. He said optimizations of both paths have been accelerating with AI-based research.
