Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal for Quantum Security (NeoQS) #85

Open
igormcoelho opened this issue Feb 18, 2019 · 0 comments
Open

Proposal for Quantum Security (NeoQS) #85

igormcoelho opened this issue Feb 18, 2019 · 0 comments

Comments

@igormcoelho
Copy link

igormcoelho commented Feb 18, 2019

We intend to propose in the next weeks/months a draft of Quantum Security operations that could possibily become the NeoQS (mentioned in white paper).

NeoQS envisioned a cryptographic system based on Lattice problems. In particular, in the White Paper, a mechanism based on Shortest Vector Problem (SVP) and Closest Vector Problem (CVP) were considered.

State-of-the-art studies and reports points out that this family of problems can really generate Hard problems in worst case situation, even for average instances. On the other hand, slightly different mechanisms are being proposed, such as Learning with Errors (LWE) and its variant of Ring Learning with Errors (R-LWE).

These problems depend on the assumption of these NP-Hard problems keep hard, which is highly believed on the assumption that P != NP. Anyway, new cryptographic schemes may always be considered with care, as they can include other issues, so we will continue following the analysis of recent NIST reports, and propose a solution that could use hybrid cryptography (ECDSA + Quantum), which is safer for a transition involving classic and quantum computers.

Transaction price can be an issue, since signatures tend to be much bigger, but this is an issue that we can discuss in more details with the community for the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants