However, this announcement is a nothing-burger. As I mentioned down-thread, you should view any QC announcement/press-release with extreme skepticism unless it includes replicable (read: open-source targeting hardware other researchers can test on) benchmarks for progress on real-world use-cases (e.g., Shor, Grover, or a newly-identified actually-interesting use-case). OP does not. Nothing to see here.
Worth saying, I am not a cryptographer—I do cryptography-adjacent research engineering. However, given the level of hype going around this industry, I think it's fair to at least expect to see the spec-sheet as it were.
All the best,
I'm not sure about the downsides of quantum-resistant DSAs.
If instead, the reference was to “cryptocurrencies,” most cryptocurrencies I am aware of depend on non-PQ constructions, and fall into the same buckets as RSA and ECC. Some systems, like Bitcoin, are in significant danger without large overhauls—if a practical CRQC is actually realized. There are efforts underway throughout the cryptocurrency communities to try to prepare for such an eventuality, but to my knowledge, none of them have major adoption yet.
As a final note on investment advice: I don't give out investment advice. :)
All the best,
All the best,
If their claim is true, then would that present an issue to RSA encryption? I find it difficult to find information on this topic that is digestible to a layman.
My understanding is that the benefit of quantum computing is parallelism, and I'm not sure how today's encryption standards would be safe from brute force attacks.
This understanding of QC is common, but isn't quite right. Quantum computation is actually really hard to parallelize (which is why Grover, though a bit frightening since it halves the security of symmetric primitives, is actually kind of damning for QC—because you can't parallelize that search really at all, so halving is the best a quantum adversary can get against things like AES-256).
I stand by my assertion that, until a QC announcement includes replicable benchmarks on actual use-cases, such things can be safely dismissed.
If you continue to be concerned (not necessarily unhealthy), engage cryptographers and security engineers to help your projects build know-how on hybrid (in this case, classical/PQ) cryptosystems, and get them deployed sooner rather than later.
All the best,