Other threads already answer very clearly that quantum comps could easily "break" /attack bitcoins chain.

Now: Are there any ideas among the bitcoin devs circulating out there, how to save bitcoin from future quantum attacks? its only a couple years away right?

What could be viable options to change and make btc quantum proof, changing hashing algorithm to which new algorithm?



  • 1
  • it is not a real duplicate. your referenced link talks about the effect. So it only partly answers my question (yes, bitcoin would break easily by quantum comps). But 2nd question is still valid: Are there currently any code changes discussed for the future by btc core devs? And how could solutions to this quantum problems look like, changing hashing algorithm to which new algorithm? or is this really too far away in the future? I think not – johnsmiththelird Mar 4 at 22:54
  • 2
    The hashing algorithm is probably the most quantum-resistant piece of cryptography right now in Bitcoin. Barring any specific breaks, SHA256 and RIPEMD160 are as quantum-resistant as hash functions can be (there is an inevitable square-root speedup that applies to any hash function). Much more can be said about the quantum resistance of digital signatures. – Pieter Wuille Mar 5 at 0:03
  • @PieterWuille hi thx. i did not know that sha256 is secure. makes sense, its symmetric -Then pls tell me, which precise parameters of bitcoins chain would be susceptible to quantum attacks (u said signatures, what else)? - And what could be ways to prevent future attacks on those parameters? Any ideas circulating among btc dev community on how to "adjust" those parameters? - Or is the current consensus rather to wait for the crypto community till they provide new crypto schemes which are quantum proof (waiting for the NIST Post-Quantum Crypto Competition ) ... thank u very much! – johnsmiththelird Mar 5 at 16:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.