Quantum-Safe Digital Signatures via Lattice-Based Secret Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cryptographic systems are vulnerable to quantum attacks, as quantum computers can efficiently factor large integers, compromising the integrity and reliability of digital security technologies.
Innovation Solution
A quantum-safe digital signature system based on Shamir's secret sharing and multi-key homomorphic encryption (MKHE) using the BFV scheme, which relies on the cryptographic hardness of ring-learning with errors (R-LWE) to ensure security against both classical and quantum computers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Power
If quantum computers are developed to perform complex computations, then computational power and processing speed are improved, but existing cryptographic systems become vulnerable to attacks
Solution Approach 1:
The patent transitions from classical cryptographic parameters (integer factorization, discrete logarithms) to post-quantum cryptographic parameters (lattice-based problems, ring-learning with errors). This parameter change enables security that remains computationally hard even for quantum computers, resolving the vulnerability created by quantum computational power.
2Ease of operation
If classical cryptographic algorithms are used for digital signatures, then ease of operation is maintained, but security against quantum attacks deteriorates
Solution Approach 1:
The patent replaces classical cryptographic mechanisms (RSA, ECDSA based on number theory) with lattice-based cryptographic mechanisms (ring-LWE, homomorphic encryption). This substitution maintains the operational interface of digital signatures while fundamentally changing the mathematical foundation to resist quantum attacks.
3Reliability
If Shamir's secret sharing is implemented with multiple users, then security distribution is improved, but system complexity increases
Solution Approach 1:
The patent combines Shamir's secret sharing scheme with multi-key homomorphic encryption to create a unified system. This merging allows multiple users to share secrets and perform computations on encrypted data without requiring separate complex protocols for each function, reducing overall system complexity while maintaining security.
Solution Approach 2:
The patent creates a universal cryptographic framework that simultaneously provides secret sharing, secure multi-party computation, and homomorphic encryption capabilities through a single lattice-based foundation. This multi-functionality eliminates the need for multiple separate cryptographic systems, simplifying the overall architecture.
Data Source
AI summary
A quantum safe method provides for creation and verification of a digital signature. The method includes steps of: encrypting, a plurality of shares associated with a User A, by using an encryption scheme to obtain encrypted plurality of shares; passing, the plurality of encrypted shares associated with the User A, to the platform; re-encrypting, the plurality of the shares to obtain the encrypted plurality of shares by the platform; decrypting, the plurality of shares shared by the User B; receiving, the plurality of shares associated with the User B from the User B by the User A; sharing, by the platform, half of the plurality of shares encrypted for the User A, with the User A and the other half of the plurality of shares encrypted for the User B, with User B; independently combining, by the User A, the plurality of shares associated with the User A with the plurality of shares associated with the User B, received from the User B; independently combining, by the User B, the plurality of shares associated with the User B with the plurality of shares associated with the User A, received from the User A; re-creating, the same secret key which is the “collective identity” for the User A and the User B in context; and creating, the collective ID between the User A and the User B to enable establishing secure communication between the user A, the User B, and the platform.