Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: pko996 on October 04, 2023, 11:24:47 AM



Title: Emerging Solutions for Quantum Computing Threats
Post by: pko996 on October 04, 2023, 11:24:47 AM
Hello everyone,

I'm studying how to safeguard blockchain from quantum threats for my research assignment. Could you kindly share your thoughts on these techniques?
•   Post-Quantum Cryptography (PQC)
       o   Coded-based cryptosystems
       o   Lattice-based
       o   Multivariate-based
       o   Hybrid schemes
       o   Super-singular elliptic-curve isogenie cryptosystems
       o   Hash-based digital signature cryptosystems
•   Quantum Key Distribution (QKD)
I'd greatly appreciate insights on their effectiveness, challenges, user-friendliness, and any other observations.

Thank you for your time and expertise!




Title: Re: Express Your Opinions on Emerging Solutions for Quantum Computing Threats
Post by: j2002ba2 on October 04, 2023, 05:54:19 PM
"Super-singular elliptic-curve isogeny cryptosystems" has been broken classically (https://eprint.iacr.org/2022/975.pdf), isn't it?


There are no "Quantum Computing Threats". QC simply couldn't scale exponentially, and no workarounds would "enable" it.

It all comes down to the noise, the random events altering the energy and space. There's no way to hide from it. Random gravitation pulse, a single neutrino passing, and it's all gone. Somebody making a step far away - all gone. If 256 bit private key is to be found - somebody laughs on the other side of the Earth - all gone. Most of the time such system have to represent at least 2256 states simultaneously... well, even if it was 2128 the noise eats it all.

Some people put hope into "quantum error correction". Unfortunately the error correction system, while canceling some noise, produces more of it, since the process takes time and space.

The more time passes - the more noise is accumulated. The bigger space a qubit "occupies", the more noise as well.

It would be wonderful if I'm wrong, but for now the above looks correct.