Temporary Blockchain Address Generation for Transaction Privacy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The openness and transparency of blockchain systems pose privacy concerns, as transaction content is sensitive and managing multiple public-private key pairs increases management difficulty for recipients.
Innovation Solution
A shared key is generated using a public key of a first blockchain node and a private key of a second blockchain node, allowing temporary public key addresses for transactions, reducing the need for recipients to store multiple key pairs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a new public key address is used in each transaction process, then privacy protection is achieved, but management difficulty increases due to storing and managing multiple public-private key pairs
Solution Approach 1:
The patent segments the key management approach by introducing temporary public key addresses for each transaction while maintaining a single fixed private key. This divides the key usage into permanent (fixed private key) and transient (temporary public key address) components, allowing privacy protection through address segmentation without requiring management of multiple key pairs.
Solution Approach 2:
The patent applies dynamics by making public key addresses transient and transaction-specific rather than static. Each transaction generates a new temporary public key address that is discarded after use, creating a dynamic key management system where addresses are continuously regenerated rather than reused, thereby protecting privacy while simplifying management.
2Reliability
If multiple public-private key pairs are stored for privacy protection, then transaction privacy is maintained, but system complexity increases
Solution Approach 1:
The system segments key functionality by separating the fixed private key (stored once) from multiple temporary public key addresses (generated per transaction). This segmentation allows the system to maintain transaction privacy through address diversity while avoiding the complexity of storing and managing multiple complete key pairs, as only one private key needs to be securely stored.
Solution Approach 2:
The patent introduces a temporary public key address as an intermediary between the fixed private key and the blockchain network. This intermediary allows transactions to be initiated and verified without exposing the fixed private key, maintaining privacy while simplifying the system architecture by eliminating the need to manage multiple private keys.
3Ease of operation
If a fixed private key is used for all transactions, then key management is simplified, but privacy protection is weakened due to address reuse
Solution Approach 1:
The patent resolves this contradiction by introducing dynamics into the public key address generation process. While the private key remains fixed and simple to manage, the public key address becomes dynamic and transaction-specific. Each transaction generates a new temporary public key address from the fixed private key, maintaining both management simplicity and privacy protection simultaneously.
Solution Approach 2:
The system segments the identity representation by using a single fixed private key for authentication while generating multiple segmented temporary public key addresses for transaction identification. This segmentation allows the fixed private key to provide consistent authentication (simplicity) while the segmented temporary addresses provide privacy protection (untraceability).
Data Source
AI summary
Embodiments of this disclosure disclose an address generation method which includes: a first blockchain node generates a shared key based on a private key of a first blockchain node and a first public key of a second blockchain node, generates a temporary first public key address of the second blockchain node based on the shared key and first transaction content, and writes first transaction information into a blockchain, where the first transaction information includes a public key address of the first blockchain node, the first public key address, and first transaction content between the first blockchain node and the second blockchain node; and the first public key address needs to be verified by using the shared key, and a recipient may also generate the shared key by using a public key of the first blockchain node and a first private key of the second blockchain node, to verify the transaction information.