Developer Quantum Impact

Understand how the quantum threat impacts your code, libraries, and protocols — and what to do about it.

For the Developer / Engineer

“The code you write today may be vulnerable before its end of life. Understanding PQC is now a core engineering skill.”

Why This Matters for You

Every line of cryptographic code you ship today uses algorithms that quantum computers will break. Library migrations are already underway (OpenSSL 3.5, BoringSSL, Go 1.24), and larger PQC keys/signatures break assumptions baked into protocols, databases, and network stacks. Developers who understand PQC now will lead their teams through the most significant cryptographic transition in internet history.

2 critical impacts2 high impacts6 total threats

Key Threat Impacts

critical

Crypto Library Transitions

OpenSSL, BoringSSL, Go crypto, and AWS-LC are adding PQC support. Your code may need API changes.

2024-2027

critical

Larger Keys & Signatures Break Assumptions

ML-KEM public keys are 800-1568 bytes (vs 32-133 for ECC). ML-DSA signatures are 2420-4627 bytes (vs 64-72 for ECDSA).

Immediate design impact

high

TLS Handshake Size Increase

PQC key exchange adds ~1KB to the TLS handshake. Some networks and middleboxes may not handle this.

2025-2028

high

Code Signing & Verification

Software supply chain signatures (npm, Docker, Git) will transition to PQC algorithms.

2026-2030

Knowledge Domains

PQC Fundamentals

Understand the quantum threat and how new algorithms work.

PQC 101 Quantum Threats

Protocol Migration

Learn how TLS, SSH, JWT, and web protocols integrate PQC.

TLS Basics API & JWT VPN/SSH Web Gateways

Architecture Patterns

Design crypto-agile systems with hybrid and composite approaches.

Hybrid Crypto Crypto Agility PKI

Supply Chain Security

Secure your build pipeline and distribution with PQC signing.

Code Signing

Workshop: 3-Step Action Plan

Step 1: Why It Matters

Assess your personal exposure with an interactive self-assessment. See how each quantum threat impacts your specific responsibilities.

Step 2: What to Learn

Identify skill gaps with a guided self-rating tool. Get a personalized learning path with direct links to relevant modules.

Step 3: How to Act

Build a phased action plan with immediate quick wins, 30-day milestones, and long-term KPIs tailored to your role.

Quick Wins to Start Today

Run a crypto grep on your codebase

Search for RSA, ECDSA, ECDH, AES-128 to map your crypto footprint in minutes.

Check your OpenSSL version

Run `openssl version` — 3.5+ has ML-KEM/ML-DSA support built in.

Test ML-KEM TLS in your browser

Chrome 131+ uses ML-KEM by default for TLS 1.3. Check your site’s support.

Learning module content can be inaccurate. Please double-check its information. Report inaccuracies in PQC Today GitHub Discussions.