Blockchain Transaction Supervision Using ZK Proofs and Encrypted Review
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge in blockchain-based transaction supervision is maintaining data privacy while ensuring compliance and legality, as transaction information is recorded in a ciphertext form, requiring supervision by multiple parties without disclosing it to unrelated users.
Innovation Solution
A transaction supervision method using encryption and zero-knowledge proofs, where transaction plaintext is encrypted with supervision public keys, and signed ciphertext is stored on the blockchain after verification by associated supervision nodes, ensuring privacy and compliance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If transaction information is recorded in ciphertext form on the blockchain, then data privacy is protected, but supervision and verification of transaction legitimacy becomes more difficult
Solution Approach 1:
The transaction information is segmented into two forms: ciphertext for public recording on blockchain to protect privacy, and plaintext provided separately to authorized supervision nodes for verification. This segmentation allows different parts of the system to access different forms of the same information according to their needs.
Solution Approach 2:
Authorized supervision nodes act as intermediaries between the public blockchain and the need for verification. They receive plaintext information from payers, verify transaction legitimacy, and can access decrypted information when needed, while ordinary users cannot. This intermediary role resolves the contradiction by enabling supervision without compromising overall privacy.
2Reliability
If multiple supervision nodes are involved to verify compliance and legality, then transaction security is improved, but system complexity increases
Solution Approach 1:
Authorized supervision nodes are designed with multi-functionality: they can verify transaction legitimacy, decrypt information when needed, and update transaction states. This universal design reduces overall system complexity by consolidating multiple functions into single authorized nodes rather than requiring separate specialized components for each function.
Solution Approach 2:
Payers pre-register authorized supervision nodes and their public keys before transactions occur. This preliminary action establishes the supervision framework in advance, so that during actual transactions, the verification process can proceed efficiently without setting up complex authorization arrangements at the moment of transaction.
3Reliability
If plaintext is disclosed to supervision nodes for verification, then compliance checking is enabled, but information leakage risk increases
Solution Approach 1:
Different quality of information access is assigned to different entities: ordinary users and the public receive only ciphertext form, while authorized supervision nodes receive plaintext form. This local differentiation of information quality allows compliance verification where needed while maintaining privacy protection where sufficient, resolving the contradiction between verification needs and leakage risks.
Solution Approach 2:
The information form parameter is changed based on the recipient: ciphertext for public recording, plaintext for authorized supervision. This parameter change allows the same information to serve different purposes (privacy protection vs. compliance verification) by adjusting its form according to the context and recipient authorization level.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
A blockchain-based transaction supervision method, relating to the technical field of blockchains. The method comprises: a payer client node acquires transaction plaintext information and transaction ciphertext information, and obtains and sends transaction supervision ciphertext information; an associated supervisor node decrypts the transaction supervision ciphertext information to obtain information to be supervised, obtains and sends signature ciphertext information when transaction plaintext information in the information to be supervised is correct and complete, and records the transaction as a first state; the payer client node sends the signature ciphertext information and zero-knowledge proof to a blockchain; when the zero-knowledge proof is established, a blockchain verification node stores the signature ciphertext information to the blockchain; and when detecting that the signature ciphertext information has been stored on the blockchain, the associated supervisor node modifies the transaction to a second state.