Private Key Generation for Password Changes Without Seed Phrase Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain wallet systems require users to manually record and store complex seed phrases, which is insecure and burdensome, and changing passwords is not user-friendly, leading to potential data loss and increased vulnerability to hacking.
Innovation Solution
A system for generating and managing private keys using a password-protected method, allowing users to change passwords conveniently and securely, with biometric options, and utilizing secure storage to reduce the need for manual seed phrase recording.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If users manually record and store seed phrases, then key retrieval is possible, but security is compromised and user burden increases
Solution Approach 1:
The patent extracts the seed phrase from the user's direct control and stores it securely on the server side. The system separates the private key generation into two parts: the user provides a password, and the server provides the seed phrase, combining them to generate the private key. This removes the security burden from the user while maintaining retrieval capability.
Solution Approach 2:
The patent introduces a server as an intermediary between the user and the private key management. The server acts as a trusted third party that securely stores the seed phrase and participates in private key generation, eliminating the need for users to directly handle and store sensitive seed phrases.
2Reliability
If users manually record and store seed phrases, then key retrieval is possible, but user burden and complexity increase
Solution Approach 1:
The system automates the seed phrase management process. Instead of requiring users to manually write down, store, and retrieve seed phrases, the server automatically generates, stores, and manages seed phrases. Users simply need to remember their password, significantly reducing operational burden.
Solution Approach 2:
The patent removes the seed phrase management task from the user's responsibilities and transfers it to the server. Users no longer need to perform the complex tasks of writing down and securely storing seed phrases, as the system handles this automatically.
3Reliability
If password changes require seed phrase retrieval and re-entry, then security is maintained, but user-friendliness decreases
Solution Approach 1:
The server acts as an intermediary that manages password changes without requiring users to handle seed phrases. When a user wants to change their password, they provide the new password to the server, which then regenerates the private key using the stored seed phrase and new password, maintaining security while simplifying the process.
Solution Approach 2:
The system performs preliminary actions by pre-storing the seed phrase on the server. This allows password changes to be handled efficiently, as the server already has the seed phrase ready and can immediately regenerate the private key with the new password without requiring users to retrieve or re-enter seed phrases.
4Ease of operation
If simple password protection is used, then user-friendliness increases, but security against hacking may be reduced
Solution Approach 1:
The patent combines multiple security elements: a user-chosen password (simple for users) with a server-stored seed phrase (secure for the system). This composite approach creates a private key that is both user-friendly to manage and secure against hacking, as neither component alone can compromise the system. An attacker would need both the password and the seed phrase to compromise the private key.
Solution Approach 2:
The private key generation is segmented into two independent components: the user's password and the server's seed phrase. This segmentation ensures that neither component alone can generate the private key, providing both user-friendliness (simple password) and security (secure seed phrase storage on server).
Data Source
AI summary
A method for generating a private key for an asymmetric key cryptography algorithm using a password, wherein the password can be changed without the private key changing is presented. The method has applications to blockchain wallets, digital signing, passkeys, and other identity and access management systems in which password changing is currently difficult or impossible. The method generates a first matching code for a first password to derive a private key, and when the first password is changed to be a second password, the first matching code is altered to a second matching code to maintain derivation of the same private key, and the first password may be discarded or forgotten.