Blockchain Transaction Root Privacy via Zero-Knowledge Proof Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing blockchain technologies are prone to data leakage, compromising the security and privacy of transaction data across the network.
Innovation Solution
A data processing method and apparatus that utilizes one-way functions to generate transaction roots and constructs proof data using zero-knowledge proofs, ensuring the authenticity and privacy of transaction data by only allowing verified nodes to access and validate transaction information on the blockchain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If transaction data is stored publicly on the blockchain, then transparency and traceability are improved, but data security and privacy are compromised
Solution Approach 1:
The patent segments transaction data into two distinct parts: transaction roots (hash values) that are stored publicly on the blockchain for transparency and verification, and sensitive transaction details (amounts, addresses, etc.) that are encrypted and stored separately. This segmentation allows the system to maintain public transparency while protecting sensitive information from exposure.
Solution Approach 2:
The patent introduces encrypted data as an intermediary layer between public transaction roots and sensitive transaction details. The encrypted data acts as a mediator that allows verification of transaction validity without exposing the actual sensitive information, thus maintaining both transparency and security.
2Adaptability or versatility
If all transaction data is made accessible to all nodes, then network transparency is improved, but the risk of data leakage and unauthorized access increases
Solution Approach 1:
The patent applies local quality by making different parts of the transaction data accessible to different entities. Transaction roots and metadata are made publicly accessible to all nodes for verification, while sensitive transaction details are restricted to authorized parties only through encryption, thus providing appropriate access control to different data elements.
Solution Approach 2:
The patent segments transaction data into publicly accessible components (transaction roots, timestamps, verification data) and privately protected components (encrypted amounts, addresses, sender/receiver information). This segmentation enables the network to maintain transparency where needed while protecting sensitivity where required.
3Quantity of substance
If sensitive information is stored on the blockchain, then transaction completeness is improved, but the vulnerability to data leakage increases
Solution Approach 1:
The patent extracts sensitive information from the public blockchain storage and stores it separately in encrypted form. Only non-sensitive transaction roots and verification data remain on the public blockchain, while the extracted sensitive details are protected through encryption and stored in a manner accessible only to authorized parties.
Solution Approach 2:
The patent uses encrypted data as an intermediary that preserves transaction information completeness without exposing sensitive details. The encrypted data serves as a mediator that allows the system to maintain complete transaction records while protecting sensitive information from unauthorized access.
Data Source
AI summary
A data processing method may include: determining, by a transaction initiation node in a blockchain, transaction data of a transaction and information to be hidden in the transaction data; obtaining, by using the transaction data as an input of a predetermined one-way function, a transaction root of the transaction, and constructing, based on the transaction root, proof data corresponding to the information to be hidden; and, after signing the transaction root, initiating a transaction request to write the transaction root and the proof data on the blockchain, for a node in the blockchain to perform consensus verification on the transaction root and the proof data, and approve or reject the transaction request based on a verification result.