Zero-Knowledge Proof Blockchain Data Redaction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The immutability of blockchain networks poses a dilemma when sensitive data, such as bank account numbers or passport numbers, needs to be blocked, as blocking the data would break the immutability of the blockchain, while allowing it to spread could result in legal consequences.
Innovation Solution
A method using Zero-Knowledge Proofs (ZKPs) is employed to generate a modified message with sensitive data removed, allowing the validity of the modified message to be verified without revealing the sensitive information, thereby enabling the blocking of sensitive data in blockchain transactions while maintaining the integrity of the blockchain's history.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Object-affected harmful factors
If sensitive data is blocked in blockchain transactions, then legal compliance is achieved, but the immutability of the blockchain is broken
Solution Approach 1:
The patent segments data into public and sensitive portions, allowing public data to be published on the blockchain while sensitive data is excluded. This segmentation enables compliance with legal requirements without compromising blockchain immutability, as the blockchain maintains its complete transaction history while sensitive information is handled separately through zero-knowledge proofs.
Solution Approach 2:
The patent introduces zero-knowledge proofs as an intermediary mechanism that enables verification of transaction validity without exposing sensitive data. This intermediary allows the blockchain to maintain immutability while complying with legal requirements, as the proof system verifies transactions without requiring publication of sensitive information.
2Stability of the object's composition
If sensitive data is allowed to spread across the network, then blockchain immutability is maintained, but legal consequences may occur
Solution Approach 1:
The patent extracts sensitive data from the blockchain transaction record, removing it from the immutable ledger while retaining the ability to verify transaction validity through zero-knowledge proofs. This extraction resolves the contradiction by preventing legal issues while preserving blockchain immutability for non-sensitive information.
Solution Approach 2:
The patent applies different quality requirements to different parts of the data: public information is published immutably on the blockchain, while sensitive information is handled with enhanced privacy protections through zero-knowledge proofs. This local differentiation allows the system to simultaneously achieve immutability where appropriate and compliance where required.
3Object-affected harmful factors
If zero-knowledge proofs are used to block sensitive data, then legal compliance is achieved, but device complexity increases
Solution Approach 1:
The patent uses copying of transaction data with selective redaction, creating a modified version of transactions that excludes sensitive information while maintaining verifiable integrity through zero-knowledge proofs. This copying approach simplifies the system compared to fully implementing zero-knowledge proofs for all data, as it only applies the complex proof mechanism where necessary.
Data Source
AI summary
A method for blocking sensitive data in a message, the method performed on a computing device and comprising: creating a copy of said message; generating at least one zero knowledge proof, the generating of each of said at least one zero knowledge proof comprising: obtaining a mask bit string which identifies locations of at least one sensitive bit in bits of said copy; computing a public bit string by modifying said bits of said copy by assigning the at least one sensitive bit with a predetermined value; determining a secret bit string which includes said at least one sensitive bit and satisfies a requirement that said bits of said copy are equal to an output of a bitwise logical calculation using the public bit string, the mask bit string and the secret bit string; hashing the copy of said message or a portion thereof to generate an output hash value; and generating a zero knowledge proof using the public bit string, the mask bit string, the output hash value, the secret bit string; removing each of said at least one sensitive bit from said copy to generate a modified message; and outputting the modified message to a recipient together with the at least one output hash value, and the at least one zero knowledge proof to enable the recipient to prove that the modified message is valid.