Cloudflare Sets 2029 Deadline for Post‑Quantum Authentication, Raising Bitcoin Signature Risk
Cloudflare will harden its platform against quantum attacks by 2029, prioritizing authentication. Here’s why signatures—not encryption—are the squeeze point for Bitcoin and the web.

Because Bitcoin
April 8, 2026
The internet’s quantum migration just got a timeline. Cloudflare plans to finish a platform-wide shift to post‑quantum protection by 2029, with an explicit tilt toward authentication over simple encryption upgrades—a choice that quietly speaks to Bitcoin’s biggest vulnerability: signatures.
The pivot to authentication is where the real engineering gravity sits. Upgrading TLS encryption is largely a client‑server change. Swapping out authentication touches identities, keys, software update pipelines, and every trust boundary where a forged signature can pass as real. Cloudflare warns that if authentication keys fall, attackers can pose as servers, burrow into systems, or push poisoned updates. That’s the supply‑chain nightmare scenario quantum computing threatens to scale.
Why the hurry now? The industry’s “Q‑Day” clock—when a practical quantum machine can crack today’s cryptography—keeps inching closer. Work from major labs, including IBM and Google, suggests a plausible window around 2032, and Google has publicly aimed for post‑quantum authentication by 2029. Cloudflare is now matching that cadence. The message: plan on compressed timelines, not leisurely roadmaps.
Cloudflare’s posture isn’t new, but it is getting sharper. Since 2022, the company has enabled post‑quantum encryption across most products; it says over 65% of human traffic it handles already uses post‑quantum ciphers. The missing piece is authentication. The rollout plan:
- Mid‑2026: post‑quantum authentication for origin connections - Mid‑2027: expansion to visitor connections - Early 2028: coverage across its enterprise networking stack - 2029: completion across services
Sharon Goldberg, who leads product management for this effort, has emphasized that authentication migration entails more moving parts than encryption and needs to start early to avoid a messy, last‑minute scramble.
This is not just a web problem. Bitcoin’s security model leans on elliptic‑curve digital signatures (ECDSA) to prove coin ownership and authorize spends. Leading builders across ecosystems—including Ethereum’s Vitalik Buterin, Solana’s Anatoly Yakovenko, and Cardano’s Charles Hoskinson—have signaled the same core risk: Shor’s algorithm on a sufficiently powerful quantum computer could derive a private key from a public key, breaking signatures unless the network moves to post‑quantum schemes.
How close is “sufficiently powerful”? A recent study from Caltech and Oratomic argued that, on a neutral‑atom quantum computer, breaking Bitcoin’s cryptography could be feasible with roughly 10,000 qubits. Even so, Oratomic’s Dolev Bluvstein has cautioned that raw qubit counts are a distraction; fabricating 10,000 physical qubits might be achievable relatively soon, but turning that into a fault‑tolerant, attack‑capable machine is a far harder systems problem.
Here’s the strategic takeaway: authentication is the choke point where quantum turns from abstract math to operational risk. Businesses can wrap data in post‑quantum encryption and feel safer today, but if signature schemes lag, adversaries could still impersonate infrastructure or rewrite software provenance. In crypto, that translates to signature agility—how quickly networks, wallets, and hardware can rotate to quantum‑safe algorithms without fracturing compatibility or user experience.
What I’m watching:
- Vendor and standards alignment: TLS, code‑signing, package registries, and HSMs need consistent post‑quantum primitives, or upgrades will stall at the edges. - Migration ergonomics: key sizes, signature verification costs, and latency matter. If authentication slows critical paths, operators will hesitate. - Crypto governance: Bitcoin and other chains will need credible paths to post‑quantum signatures before Q‑Day feels imminent, or capital will price tail‑risk into custody and transaction policies. - “Harvest‑now, forge‑later” risk: adversaries may archive data and binaries today to exploit with quantum‑forged signatures tomorrow, pressuring earlier authentication cutovers.
Cloudflare’s staged plan acknowledges a hard truth: the cryptographic future arrives asymmetrically. Encryption gets you partway. Authentication decides who you trust. On both the internet and Bitcoin, that’s where the quantum race will be won—or lost.
