Business news and discussion on TalkFuse.
Meet SHRINCS: Bitcoin’s Emerging Frontrunner for a Post-Quantum Signature
Blockstream researchers have published a security analysis of SHRINCS, a proposed hash-based signature scheme that could help Bitcoin prepare for future quantum-computing threats. The proposal uses SHA-256, already central to Bitcoin, and is being reviewed as a possible signature option; its safety and practical costs will depend on feedback from developers, cryptographers and other network participants.
SHRINCS offers a compact stateful signing path and a larger stateless fallback. Reusing a one-time key in the stateful path could let an attacker forge a signature and steal funds, so wallets would need to track key state and switch automatically to the stateless path if it might be compromised. Current Bitcoin signatures are typically 64 to 71 bytes; SHRINCS signatures range from 548 to 4,619 bytes when stateful and are 5,777 bytes when stateless, potentially reducing block capacity and increasing fees.
In short
- Researchers are seeking review of SHRINCS for Bitcoin.
- Reused stateful keys could expose funds to theft.
- Much larger signatures may reduce capacity and raise fees.
Steelman: both sides, in good faith
The strongest fair case each way — we don't pick a winner.
The case for
SHRINCS could give Bitcoin a way to prepare for future quantum threats using SHA-256, a hash function already central to the network. Its compact stateful option may limit the costs for wallets that can reliably track one-time key use, while a stateless fallback offers another route if key state is uncertain; reviewing the proposal now could help developers assess these trade-offs before quantum risks become pressing.
The case against
Adopting SHRINCS could impose substantial costs: even its stateful signatures are much larger than current Bitcoin signatures, and the stateless form is larger still, potentially reducing block capacity and raising fees. The stateful option also creates a serious wallet-management risk, since reusing a one-time key could enable theft; relying on automatic fallback and careful state tracking may add complexity and leave room for costly failures.