c6d38170-5

ConfirmedSecurity504 words3 min decode

SHRINCS Analysis Details Bitcoin's Quantum-Resistant Path at 5,777 Bytes

A Nov. 18 analysis details SHRINCS, a quantum-resistant signature proposal for Bitcoin offering 121.4-bit classical security — with signatures up to 90x larger than today's Schnorr.

SHRINCS Security Analysis Details Bitcoin’s Quantum-Resistant Design
WitnessSHRINCS Security Analysis Details Bitcoin’s Quantum-Resistant DesignMagnascan / pixabay

Outputs

  1. The 131-page SHRINCS security analysis is dated Nov. 18 and reports classical security bounds of about 121.4 to 122.7 bits.

  2. SHRINCS signatures range from 548 to 4,619 bytes stateful and 5,777 bytes stateless, versus Bitcoin's 64-byte Schnorr signatures.

  3. Wallets must permanently record each signing operation; restoring from a seed phrase forces a switch to larger stateless signatures.

  4. No independent security audit exists and SHRINCS is not ready for deployment.

  5. Some quantum-security results depend on unproven conjectures.

A 131-page security analysis dated Nov. 18 lays out SHRINCS, a proposed signature scheme designed to protect Bitcoin transactions from future quantum attacks, and the numbers it reports show the trade-off Bitcoin would face: signatures ranging from 548 bytes to 5,777 bytes, against the 64-byte Schnorr signatures the network uses today.

The document evaluates the scheme against both classical and quantum attackers. Under its framework, SHRINCS reports classical security bounds of roughly 121.4 to 122.7 bits. Some of the quantum-security results rest on conjectures that remain unproven, a caveat that will shape how cryptographers weigh the draft.

How does the scheme work?

SHRINCS combines a stateful signing method with a stateless fallback. Stateful signatures run from 548 to 4,619 bytes, while the fallback produces 5,777-byte signatures. Both figures dwarf Bitcoin's existing 64-byte Schnorr signatures.

The stateful option matters for throughput. Larger signatures mean fewer transactions fit in a block, and the stateful path could help limit the blockchain congestion and higher transaction fees that a migration to quantum-resistant signatures would otherwise bring.

The design carries a sharp operational risk, though. If wallet software reuses a one-time signing key across transactions, an attacker could forge signatures and steal funds. That is not a theoretical edge case — it is the core failure mode the proposal has to engineer around.

SHRINCS's mitigation requires wallets to permanently record each signing operation before producing a signature. If signing state becomes unreliable — including after a user restores a wallet from a seed phrase — the design calls for the software to switch to the larger stateless signatures rather than risk key reuse.

What are Blockstream's developers saying?

Blockstream researcher Mikhail Kudinov called for feedback from engineers, cryptographers and protocol developers on the draft Bitcoin Improvement Proposal.

Research director Jonas Nick made the wallet-side stakes explicit: developers need to handle the stateful component correctly. He also warned that large signatures could mean fewer transactions fit in each block, which would affect Bitcoin's value proposition.

That is the central tension in the proposal. The stateful mode keeps signatures smaller and blocks cheaper, but it pushes a heavy burden onto wallet software — the layer of the stack with the widest variance in engineering quality across the ecosystem.

Is SHRINCS ready for Bitcoin?

No. No independent security audit has been completed, and the analysis states plainly that SHRINCS is not ready for deployment. Adoption would require additional protocol changes, extensive testing and broader developer consensus — the three hurdles any Bitcoin soft fork proposal has to clear.

The unproven conjectures behind parts of the quantum-security analysis add a fourth: the cryptographic community has to be satisfied that the assumptions hold before anyone commits hashing power to them.

For now, the document is a draft seeking review, not a deployment plan. The next milestone to watch is whether cryptographers outside Blockstream validate the quantum assumptions — and whether wallet developers signal they can safely manage stateful signing at scale.

via tokenpost.com (Source)

More from Daniel Okafor

Daniel Okafor

Show full bio

Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.

1,653 articles