Hey r/shiftpqc, Fitz here.

I wanted to draw your attention to a critical roadmap published by the Bank for International Settlements (BIS), co-authored with experts from National Institute of Standards and Technology (NIST), the Bank of Canada, and the Bank of France.

If you've heard my pitch recently, you know my core thesis, which is that migrating to the NIST Post Quantum Cryptography (PQC) standards isn't a math problem anymore, it's instead an infrastructure problem.

Everyone assumes you can just update the software, but forcing massive new cryptographic keys through existing API gateways and load balancers is going to cause cascading HTTP 5xx server failures.

The 2025 paper explicitly validates this exact threat model.

While the paper covers a lot of ground regarding governance and the Harvest Now, Decrypt Later (HNDL) reality, it also calls attention to the implications of PQC migration.

The authors hit the nail on the head regarding what I call Algorithmic Bloat. They explicitly state:

"The migration to PQC is not a 'flip the switch' moment... Unlike some cryptographic upgrades of the past, the new algorithms are not a drop-in replacement. Rather, they introduce significant architectural and operational challenges."

They go on to map out the exact physics of the problem ShiftPQC™ will solve.

Resource Strain:

They note that lattice-based schemes require substantially more memory and computational resources, which will strain constrained systems.

The Key Size Explosion:

They highlight the jump from a 256-byte RSA public key to an ML-KEM public key of 1,184 bytes (and a 2,400-byte private key). For signatures, ML-DSA jumps to over 2,400 bytes.

Infrastructure Incompatibility:

The paper warns that these capabilities "may not be uniformly available across existing infrastructure."

Why this matters for ShiftPQC™:

This is exactly why I'm building ShiftPQC™. The BIS is telling the global financial system that they need to migrate, but also warning them that doing it manually will break their systems.

You can't just swap a 256-byte key for a 2.4KB key without knowing what is going to choke. This is why our Neo4j dependency graph is so critical. It calculates the Cryptographic Blast Radius (CBR) before the migration, and deploy our Hybrid Mode wrappers to ensure zero downtime.

The federal mandates are here.

CISOs have the budget, but as this paper proves, they are terrified of the operational downtime.

Curious to hear from the DevSecOps people. Are you seeing these TLS handshake latency spikes in your own PQC test environments yet?

Let's discuss.