Shrincs bitcoin post-quantum signature analysis

Blockstream researchers detail SHRINCS, a hash‑based post‑quantum signature for Bitcoin, noting stateful signatures of 548‑4,619 bytes and stateless ones of 5,777 bytes.
Key takeaways
- Blockstream researchers published a security analysis of SHRINCS on 11/19/2026.
- Stateful SHRINCS signatures range from 548 to 4,619 bytes, while stateless signatures are 5,777 bytes.
- Wallets must enforce a stateless fallback to avoid catastrophic reuse of one‑time keys.
- Widespread stateless use could bloat the blockchain and increase transaction fees.
On 19 November 2026 Blockstream Research Director Jonas Nick and researcher Mikhail Kudinov released a security analysis of SHRINCS, an emerging hash‑based post‑quantum signature scheme for Bitcoin. The proposal aims to protect the network against future quantum attacks while keeping the core cryptographic primitive—SHA‑256—unchanged.
How SHRINCS changes Bitcoin’s signature size
Current Bitcoin signatures are compact: ECDSA signatures average 71 bytes and Taproot Schnorr signatures are 64 bytes. SHRINCS introduces two signing paths. The stateful path produces signatures between 548 and 4,619 bytes, whereas the stateless path creates a fixed 5,777‑byte signature. The larger size could reduce the number of transactions that fit in a block and pressure the fee market.
The stateful option is attractive for efficiency because it is smaller, but it relies on a one‑time key that must never be reused. If a wallet accidentally signs two transactions with the same key, an attacker could forge a signature and steal funds. Hence, Nick stresses that wallet software must automatically switch to the stateless path whenever a state counter is at risk.
Implementation risks and the need for automatic safeguards
Nick warned that a single user error in handling the stateful component could lead to a catastrophic loss. To prevent this, the specification must require wallets to enforce a stateless fallback without user intervention. Kudinov echoed the call for extensive peer review, inviting engineers, cryptographers and protocol developers to test the draft BIP.
If developers fail to embed these safeguards, the network could see isolated attacks that undermine confidence in Bitcoin’s security model. The working group, supported by nonprofits such as Brink and OpenSats, is therefore focusing on rigorous code audits and formal verification before any main‑net deployment.
Read also: Aud and gbp fall as fed rate bets shift, bitcoin tests $62k
Potential impact on Bitcoin’s fee market and scalability
Larger signatures directly affect block space. With stateless signatures at 5,777 bytes, fewer transactions can be packed into the 4‑million‑byte block limit, pushing fees higher. Nick noted that the fee market’s future shape is uncertain until real‑world data on signature adoption becomes available.
AI‑driven research is already accelerating optimizations for both signature paths, but the trade‑off remains: higher security against quantum threats versus increased on‑chain data. Traders and investors will watch how quickly the Bitcoin community adopts the stateless fallback and whether miners adjust fee expectations.
What to watch next
The SHRINCS working group plans to refine the BIP over the coming months, seeking feedback from the broader ecosystem. Key milestones include a public review period, test‑net implementations, and a potential activation vote. Monitoring block‑size usage and fee trends during test‑net runs will provide early signals of market impact.
- 19 Nov 2026 – Security analysis of SHRINCS released
- Stateful signature size: 548‑4,619 bytes
- Stateless signature size: 5,777 bytes
- Block limit: ~4 million bytes per block
Frequently asked questions
Why does SHRINCS use SHA‑256 instead of new cryptographic primitives?
SHRINCS builds on Bitcoin’s battle‑tested SHA‑256 hash function, which reduces trust assumptions because the hash is already widely deployed in the protocol and has withstood decades of scrutiny.
What is the main security concern with the stateful signing path?
The stateful path relies on one‑time keys; if a wallet reuses a key, an attacker could forge a signature for that address and steal the funds, so wallets must enforce a stateless fallback whenever a state counter could be compromised.
Related news
- Aud and gbp fall as fed rate bets shift, bitcoin tests $62k
- Market overview: dollar strength pressures EUR/USD and gold slides toward 14‑month low
- Bitcoin stays below $65K as hawkish Fed minutes fuel crypto sell‑off
- Bitcoin bearish signals deepen as demand contracts by 400k BTC
More from ITF
This article is compiled from international market news for information only. It is not investment advice.