Quantum Computing’s Nearest Target: Encrypted Chats Before Bitcoin
IBM is working with Signal and Threema on quantum‑safe messaging as experts warn of “harvest now, decrypt later.” Why chats may face nearer risk than Bitcoin—and what’s being upgraded.

Because Bitcoin
March 11, 2026
The conversation around quantum risk usually fixates on Bitcoin’s elliptic‑curve cryptography. That’s valid—but the softer target sits in your inbox. Encrypted messengers face a unique asymmetry: adversaries can capture traffic today and decrypt it years from now once quantum machines mature. That time‑shifted threat reshapes priorities far sooner for communications than for coins.
IBM’s latest report says its researchers are collaborating with Signal and Threema to remodel messaging protocols for a post‑quantum world. The effort acknowledges a hard trade-off: swapping in quantum‑safe primitives one‑for‑one can bloat bandwidth. In tests porting Signal’s metadata‑protection scheme, a naive upgrade pushed estimated bandwidth needs up to roughly 100x—forcing a ground‑up redesign to keep speed and efficiency.
Why messaging is exposed sooner - Store‑and‑forward risk: Communications can be intercepted and archived now, then cracked later with quantum resources. That “harvest‑now, decrypt‑later” play is tailor‑made for signals intelligence. - Longevity of secrets: Many conversations (governments, journalists, corporations) must remain confidential for years, sometimes decades. History shows intercepted traffic is often broken retroactively once new cryptanalytic tools appear. - Real‑world stakes: Encrypted apps are widely used at the highest levels. In 2025’s “Signalgate,” senior U.S. national security officials—including Defense Secretary Pete Hegseth—used disappearing Signal messages on personal devices and even added a journalist to a group chat. That episode underscored how sensitive policy discussions increasingly ride over consumer‑grade apps.
The Bitcoin contrast Bitcoin’s exposure profile looks different. The network relies on elliptic‑curve cryptography; in theory, a sufficiently powerful quantum computer running Shor’s algorithm could derive private keys from public keys. However, many researchers argue machines capable of such attacks remain well beyond current capability. The security window also behaves differently: with prudent key hygiene and upgrade paths, the community can often migrate protections before a break is practical. You can’t retroactively re‑encrypt yesterday’s chat.
Quantum progress—and its pressure on roadmaps Work from IBM, Google, and Caltech has improved qubit stability, scaling, and error correction. While no one can timestamp “practical quantum,” momentum tends to compress timelines in technology planning. As progress becomes more concrete, decision cycles shrink and implementation work accelerates.
What the messaging stack is changing now - Signal: Launched in 2014, Signal provides end‑to‑end encrypted messages, calls, and groups with keys held on user devices. It added a PQXDH upgrade in 2023 to protect new sessions against future decryption. In 2025, Signal extended safeguards across ongoing conversations, calls, and media with a Sparse Post‑Quantum Ratchet (SPQR). - Threema: Live since 2012 with end‑to‑end encryption and client‑side keys, Threema is exploring integration of the NIST‑standardized ML‑KEM for key establishment in partnership with IBM cryptographers. - Metadata protection: Hiding who is talking to whom in large groups is often the bandwidth and latency bottleneck. IBM’s team found that simply substituting quantum‑safe components into existing designs could inflate bandwidth by up to two orders of magnitude, motivating entirely new, communication‑efficient constructions.
The deeper issue to solve The hardest part isn’t just swapping Diffie‑Hellman for a lattice KEM; it’s rebuilding group and metadata protocols so they scale without crushing user experience. Users tolerate a touch more CPU, but they rarely accept 100x more data or slower delivery. That puts product teams in a bind: deliver quantum resilience without degrading reliability on low‑end phones and spotty networks. The right answer likely blends: - Algorithm agility to rotate primitives over time, - Lightweight post‑quantum KEMs (e.g., ML‑KEM) combined with compact authentication, - Redesigned group keying that amortizes costs across members, - And selective, privacy‑preserving metadata schemes that don’t balloon traffic.
Where this leaves crypto and comms For messengers, the obligation is immediate: ship post‑quantum key agreement for new sessions, extend protection to ongoing threads, and re‑architect metadata defenses. For Bitcoin, vigilance matters, but the practical risk remains further out; the ecosystem can plan migrations and minimize on‑chain public key exposure while monitoring quantum milestones.
As one researcher put it, once the threat feels tangible, teams move faster. Sensible leaders won’t wait for that moment. They will build quantum‑ready pathways now, treat protocol agility as a feature, and assume adversaries are already recording what they can.
