SHRINCS Security Analysis Details Bitcoin’s Quantum-Resistant Design
The 131-page analysis gives classical security bounds of about 121.4 to 122.7 bits, while some quantum results rely on unproven conjectures.

A new security analysis of SHRINCS outlines a proposed way to protect Bitcoin (BTC) transactions from future quantum attacks, while highlighting wallet risks and the larger signatures the design would introduce.
The 131-page document, dated Nov. 18, evaluates the proposed signature scheme against classical and quantum attackers. It reports security bounds of about 121.4 to 122.7 bits against classical attacks under its framework. Some quantum-security results depend on conjectures that remain unproven.
SHRINCS combines a stateful signing method with a stateless fallback. Stateful signatures range from 548 to 4,619 bytes, while the fallback produces 5,777-byte signatures. Both are larger than Bitcoin’s existing 64-byte Schnorr signatures. The stateful option could help limit blockchain congestion and higher transaction fees associated with a shift to quantum-resistant signatures.
The stateful design carries a risk if wallet software reuses a one-time signing key across transactions: an attacker could then forge signatures and steal funds. SHRINCS’s proposed mitigation requires wallets to permanently record each signing operation before producing a signature. If signing state becomes unreliable, including after restoring a wallet from a seed phrase, the design calls for the software to switch to the larger stateless signatures.
Blockstream researcher Mikhail Kudinov called for feedback from engineers, cryptographers and protocol developers on the draft Bitcoin Improvement Proposal. Research director Jonas Nick said wallet developers need to handle the stateful component correctly. He also warned that large signatures could mean fewer transactions fit in a block and affect Bitcoin’s value proposition.
No independent security audit has been completed, and SHRINCS is not ready for deployment. Adoption would require additional protocol changes, extensive testing and broader developer consensus.