Blockstream Publishes SHRINCS: A Post-Quantum Signature Scheme Tailored for Bitcoin
Blockstream has taken a significant step toward post-quantum security in Bitcoin by publishing a Bitcoin Improvement Proposal (BIP) for SHRINCS, an experimental post-quantum signature scheme. SHRINCS notably operates in production on the Liquid sidechain, marking it as the first concrete proposal explicitly designed for Bitcoin’s unique signature and transaction model.
SHRINCS is distinct from other post-quantum schemes largely due to its smaller size and Bitcoin-native approach. Expert voices describe it as “the most Bitcoin-native post-quantum signature design anyone has produced,” reflecting Blockstream’s focus on integrating quantum resistance without radically disrupting Bitcoin’s existing architecture.
Post-Quantum Signature Size: SHRINCS Balances Compactness with Complexity
Most NIST-endorsed post-quantum signature schemes are dramatically larger than Bitcoin’s current ECDSA and Schnorr signatures. Industry data report these schemes can be between 38 and 123 times larger, imposing significant costs on constrained blockchain environments.
SHRINCS reduces this burden considerably: its minimum signature size starts at 548 bytes plus a 48-byte public key, with upper limits approaching around 4,619 bytes. Although this is still roughly nine times larger than Bitcoin’s Schnorr signatures, which are 64 bytes, it is comparatively lean in the post-quantum landscape.
| Signature Scheme | Minimum Signature Size | Relative Size to Schnorr (64 bytes) | Notes |
|---|---|---|---|
| Bitcoin Schnorr | 64 bytes | 1x | Current state-of-the-art signature scheme for Bitcoin |
| NIST Post-Quantum Schemes | ~2,432 to ~7,872 bytes* | 38x to 123x | Hash and lattice-based signatures |
| Blockstream SHRINCS | 548 to 4,619 bytes | ~9x | Blockchain-native, stateful, smaller than most PQS schemes |
*Approximate midpoint calculated from 38–123 times Schnorr size.
Segregated Witness (SegWit) within Bitcoin softens the block size cost of larger signatures like SHRINCS, since SegWit discounts signature data for block weight calculations. This means the bigger signatures don’t translate linearly into bigger blocks, preserving Bitcoin’s throughput more efficiently than initially assumed.
Stateful Design: Complexity Trade-offs in SHRINCS for Space Efficiency
SHRINCS achieves its size advantage by adopting a stateful signature design. Rather than relying on complex stateless mechanisms, it stores used keys locally on the signing device to ensure no key reuse, significantly saving on signature space.
This introduces operational complexities absent from Bitcoin’s traditional stateless signatures. For example:
- Each signature increases in size by approximately 16 bytes every time it is used.
- If the signing device is lost, a large “stateless fallback” transaction of around 5,777 bytes is required for recovery.
This trade-off can create user and developer challenges, especially for hardware wallets or multi-device environments.
// Conceptual Solidity illustration of the reentrancy risk analogy:
contract StatefulSignature {
mapping(address => uint256) public usageCount;
// Simplified state update on signature use
function useSignature(address signer) external {
require(usageCount[signer] < 1000, "Max usage reached");
usageCount[signer] += 1;
// Additional logic to handle signature and prevent reuse...
}
}
The above is a conceptual demonstration: managing state carefully is critical to avoid vulnerabilities like reentrancy or improper state increments, which could analogically resemble the need for state tracking in SHRINCS to prevent key reuse.
Blockstream addresses the intrinsic statefulness challenge by introducing SHRIMPS, a companion scheme released earlier in 2026, allowing multiple backup devices initialized from the same seed to sign transactions collaboratively, mitigating single point of failure risks.
Real-World Testing on Liquid Mainnet Proves Viability but Security Proof Pending
SHRINCS is not purely theoretical — it has been tested in production on the Liquid sidechain since March 2026 and demonstrated effective operation on common hardware wallets, affirming practical feasibility.
However, the BIP explicitly states “a security proof is TODO,” highlighting that SHRINCS is still in the experimental phase cryptographically. Its formal security validation has yet to be finalized, which is crucial for confidently deploying it in Bitcoin’s mainnet environment.
Beyond cryptographic rigor, SHRINCS’s use requires strict compatibility management: the BIP cautions that keys generated with one optimization (hypertree pruning) are incompatible with implementations lacking support, risking loss of funds when importing across versions.
// Example of safe external call to illustrate guarding against reentrancy,
// an archetypal vulnerability for stateful systems:
contract ReentrancyGuard {
bool internal locked;
modifier noReentrant() {
require(!locked, "ReentrancyGuard: reentrant call");
locked = true;
_;
locked = false;
}
function sensitiveOperation() external noReentrant {
// critical logic here
}
}
Although SHRINCS’s statefulness is not a smart contract vulnerability per se, managing state safely and ensuring atomicity in updates is conceptually parallel to guarding Solidity contracts against reentrancy or state corruption, emphasizing the importance of disciplined design in new cryptographic integrations.
Governance, Not Cryptography, Is the Primary Barrier to Bitcoin’s Quantum Upgrade
While the advent of post-quantum signature schemes like SHRINCS addresses the cryptographic frontiers of quantum security, the defining obstacle within Bitcoin’s ecosystem is governance.
Expert analysis emphasizes that “the binding constraint in Bitcoin’s quantum migration isn’t cryptography, it’s governance.” Decisions around protocol upgrades involve consensus among diverse stakeholders, cautious risk management, and incremental coordination.
Integrating SHRINCS or any post-quantum signature must harmonize with Bitcoin’s decentralization principles and long-term stability imperatives, not just the technological readiness of the scheme.
Summary and Security Implications
SHRINCS represents a milestone in blockchain cryptography by proposing a reasonably compact, Bitcoin-native post-quantum signature scheme that has seen real-world deployment in Liquid since early 2026. Its stateful design reduces signature size relative to competing schemes but introduces operational complexity that must be carefully managed.
The trade-offs here invite ongoing collaboration between cryptographers, wallet developers, and Bitcoin governance stakeholders. Post-quantum resistance is essential, but transitioning must not sacrifice security principles or introduce new failure modes.
| Feature | Traditional Bitcoin Signatures | SHRINCS Post-Quantum Scheme |
|---|---|---|
| Signature Type | Stateless, ECDSA / Schnorr | Stateful, hash-based |
| Signature Size | 64 bytes | 548 to 4619 bytes |
| Operation Complexity | Minimal | Grows with each use; recovery costs high |
| Cryptographic Maturity | Fully mature and validated | Security proof pending |
| Production Deployment | Bitcoin Mainnet | Tested on Liquid sidechain |
| Compatibility Risks | Low | High due to hypertree pruning |
Soken Security Insight:
From our experience auditing complex cryptographic systems, statefulness in signature schemes inevitably imposes extra operational burdens and attack surfaces. The trade-offs SHRINCS makes for size economy must be accompanied by rigorous device and software handling protocols. Moreover, preserving interoperability and avoiding subtle incompatibilities is paramount to prevent catastrophic fund losses as the ecosystem moves toward quantum-safe signatures.
Embedding SHRINCS into Bitcoin’s architecture offers promising quantum-resistant gains but also reveals nuanced complexity in signature management and recovery workflows. The scheme’s reduced signature sizes versus comparable post-quantum approaches could ease blockchain space concerns, particularly with SegWit’s efficiencies factored in. However, the stateful design requires developers and hardware wallet manufacturers to implement robust key usage tracking and fallback mechanisms.
Governance hurdles loom large, reminding us that cryptographic innovation alone cannot drive adoption. Transitioning Bitcoin’s signature algorithms demands thorough community engagement and multilayered coordination to align security goals with consensus-driven deployment.
For smart contract developers and blockchain teams exploring related signature upgrades or cryptographic tool integrations, understanding the trade-offs and statefulness implications is invaluable. Soken’s expertise in thorough audits and security strategy development can help design resilient cryptographic onboarding pathways aligned with Bitcoin’s ethos.
Informed by these developments, teams seeking to prepare for the quantum transition should prioritize integrating post-quantum innovations like SHRINCS cautiously, advocating for comprehensive security proofs and compatibility protocols. Implementations can draw lessons from classical smart contract security patterns—particularly around state management and reentrancy protections—to avoid analogous pitfalls in cryptographic statefulness. Leveraging detailed audit frameworks, such as those Soken offers under our Services - IT, can help validate these novel schemes meet the rigorous standards Bitcoin’s ecosystem demands.
This announcement situates Blockstream’s SHRINCS proposal as a foundational milestone in Bitcoin’s long-term quantum resilience journey while underscoring that the path ahead combines cryptographic innovation with governance, interoperability, and security engineering challenges. Forward-looking protocol research and holistic engagement across developers, hardware providers, and governance bodies will be essential to successful post-quantum migration.