Transaction Key Splitting via Hardware Security Module
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional authority management schemes in blockchain technologies face challenges with key security, convenience, and reliability due to the need for multiple users to sign transactions sequentially, which can be tedious and prone to delays or failures if keys are lost or compromised, and local key management is not secure.
Innovation Solution
A method for splitting and recovering a transaction key using a hardware security module that randomly generates a transaction key, splits it into sub-keys encrypted with public keys of users, and allows recovery only when a predetermined number of verified users collaborate, ensuring security and reliability through non-local key management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a multi-signature scheme is used where multiple users hold their own private keys for transaction authorization, then key control security is improved, but the complexity of transaction processes increases and reliability decreases when users lose or refuse to use their keys
Solution Approach 1:
The private key is segmented into multiple key shares distributed to different users. Instead of each user holding a complete private key, the system divides the key into fragments that collectively reconstruct the original key. This segmentation allows transactions to proceed when a threshold of users cooperate, eliminating the blocking problem where a single user's key loss or refusal prevents transactions.
Solution Approach 2:
The system introduces a key management entity that acts as an intermediary to manage key shares and coordinate transaction authorization. This intermediary facilitates the reconstruction of the private key when sufficient key shares are presented, simplifying the transaction process and improving reliability without requiring users to directly manage complex key operations.
2Ease of operation
If multiple users hold unchanged private keys for a period of time to maintain authority, then operational simplicity is improved, but security risk increases due to higher probability of key compromise
Solution Approach 1:
The system implements dynamic key management where key shares can be rotated, updated, or revoked without changing the underlying transaction authority structure. Users can refresh their key shares periodically or when security concerns arise, maintaining operational simplicity while reducing the window of vulnerability for key compromise attacks.
Solution Approach 2:
The system allows changing parameters such as the threshold number of key shares required for transaction authorization, the validity period of key shares, and the composition of user groups. These parameter changes enable flexible adjustment of security levels and key management policies without fundamentally altering the system architecture.
3Adaptability or versatility
If local key management is implemented where users manage their own private keys, then user autonomy is improved, but overall system security decreases
Solution Approach 1:
The system merges the advantages of local key management (user autonomy) with centralized key management (security). Users maintain control over their key shares locally, preserving autonomy, while the key management entity provides secure infrastructure for key generation, distribution, and reconstruction, enhancing overall security through coordinated management.
Data Source
AI summary
Methods for splitting and recovering a key, a storage medium, a computer program product, and a key management system (170), wherein the key management system (170) comprises a management device (110) used for managing user equipment of users in a user group and a hardware security module (160) connected to the management device (110). The method for splitting a key comprises: at the hardware security module (160): obtaining the number of the users in the user group and a first predetermined value (202); randomly generating a transaction key associated with the processing authority of the current transaction on the basis of messages of other users except the splitting user in the user group (204); splitting the transaction key into a plurality of sub-keys the same as the users in number, wherein each sub-key in the plurality of sub-keys corresponds to one user in the user group (206); and encrypting the plurality of sub-keys by using public keys of the users corresponding to the plurality of sub-keys, respectively (208).