Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

Monero needs to step up for quantum safety, not by replacing the existing encryption, but by adding a quantum safety encryption layer on top. Google's recent paper on quantum risks to cryptocurrencies had identified Monero as being at risk. This is not tomorrow's problem; it requires initiating action today, so these efforts can bear fruit by the time the quantum hardware is ready, perhaps by 2029.


All coins are aware of quantum safety requirements, yet quantum computers are still far enough in the future that it makes sense to wait, and first see what those post-quantum mitigations should look like.


Burying the head in the sand doesn't work. Quantum-safe algorithm candidates exist. Post-quantum cryptography is a bonafide field with families of algorithms that exist, e.g. lattice/hash/code/multivariate based. If a user has to choose between two cryptocurrencies, one of which is quantum safe and the other isn't, the user will choose the one that is. The ultimate choice of algorithm doesn't have to be finalized right now; that will remain a work in progress for decades, but getting there is not a one-hop journey.

For comparison, XRP already has a roadmap: https://cryptonews.com/news/ripple-post-quantum-readiness-xr...


Because XRP is not decentralized, it will be easy to upgrade. With bitcoin, you have to convinve the node runners to upgrade - which means the taken patchset must be sound and verified in depth beforehand.


We are on a Monero thread. It has scheduled forks.


None if the crypto currencies will survive the quantum apocalypse because all the people who can pull off the migration have long left.


I wouldn't worry since AI can do research, identify approaches, and implement them. The human of course needs to review every line with a critical eye, and compare the implementations against their academic specifications.


Yeah but then who does the audit if the humans are not capable? Should they all get mythos to review stuff?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: