Privacy data processing method based on block chain, privacy system and application system

Abstract

The invention provides a privacy data processing method based on a block chain, a privacy system and an application system, and relates to the technical field of data processing.The method comprises the steps that a plurality of trusted source nodes acquire a data acquisition request of a target user sent by a client device of a decentralized application through the block chain, the data acquisition request comprises an encrypted user address; the encrypted user address is an address obtained after the client device carries out asymmetric encryption on an address of the target user on the block chain; the plurality of trusted source nodes respectively perform homomorphic encryption on the original privacy data of the target user to obtain a plurality of pieces of homomorphic encryption privacy information; the plurality of trusted source nodes perform asymmetric encryption on the plurality of pieces of homomorphic encryption privacy information to obtain a plurality of pieces of target encryption data information; and the plurality of trusted source nodes upload the plurality of target encrypted privacy information and the encrypted user address to the block chain. The privacy data of the target user is kept secret, and leakage of the privacy data of the target user is avoided.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and specifically, to a privacy data processing method, a privacy system, and an application system based on blockchain. Background Art

[0002] In the field of information technology and the Internet, the traditional centralized application model has been widely popularized, in which data storage, processing and service provision usually rely on centralized servers or platforms. Although this model meets the needs of users to a certain extent, it has problems such as single point failure, data security risks, privacy leakage and abuse by service providers.

[0003] To this end, it is necessary to realize data interaction through decentralized applications to avoid over-reliance on centralized servers or platforms and reduce data security risks. Decentralized applications are based on blockchain, distributed ledger technology or other distributed network protocols. Through distributed nodes, they jointly maintain data and execute smart contracts, thus realizing data storage and processing without the need for centralized management.

[0004] However, the transparency of blockchain in decentralized applications brings a unique problem. When private data information is uploaded to the blockchain, it becomes publicly accessible. If a data leak occurs, they may expose all private data information, which may cause significant losses to users. Summary of the invention

[0005] The purpose of this application is to address the deficiencies in the above-mentioned prior art and provide a privacy data processing method, privacy system and application system based on blockchain to keep the privacy data of the target user confidential and avoid leakage of the privacy data of the target user.

[0006] To achieve the above purpose, the technical solution adopted in the embodiment of the present application is as follows:

[0007] In a first aspect, an embodiment of the present application provides a privacy data processing method based on blockchain, which is used in a privacy system. The privacy system includes: a plurality of trusted source nodes. The method includes:

[0008] The multiple trusted source nodes obtain a data acquisition request of a target user sent by a client device of a decentralized application through a blockchain, wherein the data acquisition request includes: an encrypted user address; the encrypted user address is: the address of the target user on the blockchain asymmetrically encrypted by the client device;

[0009] The multiple trusted source nodes respectively perform homomorphic encryption on the original private data of the target user to obtain multiple homomorphic encrypted private information;

[0010] The multiple trusted source nodes asymmetrically encrypt the multiple homomorphically encrypted private information to obtain multiple target encrypted data information;

[0011] The multiple trusted source nodes upload the multiple target encrypted private information and the encrypted user addresses to the blockchain.

[0012] Optionally, the privacy system further includes: a relay node;

[0013] The multiple trusted source nodes asymmetrically encrypt the multiple homomorphically encrypted private information to obtain the multiple target encrypted private information, including:

[0014] The multiple trusted source nodes asymmetrically encrypt the multiple homomorphically encrypted private information according to the public key of the relay node to obtain the multiple target encrypted private information;

[0015] The method further comprises:

[0016] The relay node obtains the multiple target encrypted private information from the blockchain;

[0017] The relay node uses the private key of the relay node to asymmetrically decrypt the multiple target encrypted private information to obtain the multiple homomorphically encrypted private information;

[0018] The relay node performs a homomorphic computing function on the plurality of homomorphically encrypted private information to obtain a target encryption result;

[0019] The relay node uploads the target encryption result and the encrypted user address to the blockchain.

[0020] Optionally, the privacy system further includes: a zero-knowledge proof service providing node, the multiple trusted source nodes respectively perform homomorphic encryption on the original private data of the target user to obtain multiple homomorphic encrypted private information, and further includes:

[0021] The multiple trusted source nodes respectively perform homomorphic encryption on the original private data of the target user according to the public key of the zero-knowledge proof service providing node to obtain the multiple homomorphically encrypted private information.

[0022] Optionally, the decentralized application is a decentralized financial application, and the method further includes:

[0023] The zero-knowledge proof service providing node receives an asset verification request sent by the operating node of the decentralized application through the blockchain, wherein the asset verification request is triggered by a service request sent in advance by the client device of the decentralized financial application to the operating node through the blockchain; the asset verification request includes: the encrypted user address and an asset declaration statement;

[0024] The zero-knowledge proof service providing node obtains the target encryption result from the blockchain according to the encrypted user address;

[0025] The zero-knowledge proof service providing node decrypts the target encryption result according to the private key of the zero-knowledge proof service providing node to obtain the asset calculation result;

[0026] The zero-knowledge proof service providing node generates a zero-knowledge proof statement for the asset declaration statement based on the asset calculation result and using a zero-knowledge proof generation algorithm;

[0027] The zero-knowledge proof providing node uploads the zero-knowledge proof statement and the encrypted user address to the blockchain, so that the operation node performs a verification operation of the financial service corresponding to the service request.

[0028] Optionally, the zero-knowledge proof service providing node decrypts the target encryption result according to the private key of the zero-knowledge proof service providing node to obtain the asset calculation result, including:

[0029] The zero-knowledge proof service providing node starts a zero-knowledge proof procedure;

[0030] The zero-knowledge proof service providing node, as the prover, decrypts the target encryption result according to the private key of the zero-knowledge proof service providing node through the zero-knowledge proof procedure to obtain the asset calculation result.

[0031] Optionally, the method further comprises:

[0032] The operation node obtains the zero-knowledge proof statement and the encrypted user address from the blockchain;

[0033] The operation node performs a verification operation of the financial service corresponding to the service request on the target user based on the zero-knowledge proof statement and the encrypted user address.

[0034] Optionally, the operation node performs an asset verification operation of the financial service corresponding to the service request on the target user based on the zero-knowledge proof and the encrypted user address, including:

[0035] The operation node verifies the zero-knowledge proof statement using a preset zero-knowledge proof verification algorithm;

[0036] If the verification is successful, the operation node identifies the target user according to the encrypted user address, and updates the financial service corresponding to the service request for the target user according to the identification result.

[0037] Optionally, the encrypted user address is an address obtained by asymmetrically encrypting the address of the target user in the blockchain by the client device according to the public key of the operation node;

[0038] The operation node identifies the target user according to the encrypted user address, including:

[0039] The operation node decrypts the encrypted user address according to the private key of the operation node to obtain a decrypted user address;

[0040] The operation node associates the decrypted user address with the target user to identify the target user.

[0041] In a second aspect, another embodiment of the present application provides a privacy data processing device based on blockchain, which is applied to a privacy system, wherein the privacy system includes: a plurality of trusted source nodes, and the device includes:

[0042] An acquisition module, used for the multiple trusted source nodes to acquire a data acquisition request of a target user sent by a client device of a decentralized application through a blockchain, wherein the data acquisition request includes: an encrypted user address; the encrypted user address is: the address of the target user on the blockchain asymmetrically encrypted by the client device;

[0043] A first encryption module, configured for the multiple trusted source nodes to respectively perform homomorphic encryption on the original private data of the target user to obtain multiple homomorphic encrypted private information;

[0044] A second encryption module is used for the multiple trusted source nodes to asymmetrically encrypt the multiple homomorphically encrypted privacy information to obtain multiple target encrypted data information;

[0045] An uploading module is used for the multiple trusted source nodes to upload the multiple target encrypted private information and the encrypted user addresses to the blockchain.

[0046] In the third aspect, another embodiment of the present application provides a computer device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor. When the computer device is running, the processor communicates with the memory through the bus, and the processor executes the machine-readable instructions to perform the steps of the blockchain-based privacy data processing method as described in any of the first aspects above.

[0047] In a fourth aspect, another embodiment of the present application provides a memory having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the privacy data processing method based on blockchain as described in any one of the first aspects above are executed.

[0048] In a fifth aspect, another embodiment of the present application provides a storage device, a privacy system based on blockchain, the privacy system comprising: a plurality of trusted source nodes, a relay node, and a zero-knowledge proof providing node;

[0049] The multiple trusted source nodes, the relay node, and the zero-knowledge proof providing node are all connected to the blockchain where the client device of the decentralized application is located;

[0050] The multiple trusted source nodes are used to execute the steps performed by the trusted source nodes in any of the blockchain-based privacy data processing methods described in the first aspect above; the relay nodes are used to execute the steps performed by the relay nodes in any of the blockchain-based privacy data processing methods described in the first aspect above; and the zero-knowledge proof providing node is used to execute the steps performed by the zero-knowledge proof providing node in any of the blockchain-based privacy data processing methods described in the first aspect above.

[0051] In the sixth aspect, another embodiment of the present application provides a blockchain application system, characterized in that the blockchain application system includes: a client device of the decentralized application, an operation node of the decentralized application, and the blockchain-based privacy system described in the fifth aspect above.

[0052] The beneficial effects of this application are:

[0053] The present application provides a privacy data processing method, privacy system and application system based on blockchain, wherein multiple trusted source nodes obtain the data acquisition request of the target user sent by the client device of the decentralized application through the blockchain, and the multiple trusted source nodes respectively homomorphically encrypt the original privacy data of the target user to obtain multiple homomorphically encrypted privacy information; multiple trusted source nodes asymmetrically encrypt the multiple homomorphically encrypted privacy information to obtain multiple target encrypted data information; multiple trusted source nodes upload the multiple target encrypted privacy information and encrypted user addresses to the blockchain. In the present application, after multiple trusted source nodes obtain the data acquisition request of the target user, the original privacy data of the target user is homomorphically encrypted to protect the original privacy data of the user from being directly accessed, and even if the homomorphically encrypted privacy information is attacked, the original privacy data cannot be obtained. After the original privacy data is homomorphically encrypted, it is asymmetrically encrypted again to ensure the security of uploading the homomorphically encrypted privacy information to the blockchain. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0055] Figure 1 A flowchart of a privacy data processing method based on blockchain provided in an embodiment of the present application;

[0056] Figure 2 A schematic diagram of a process for uploading a target encryption result in a privacy data processing method based on blockchain provided in an embodiment of the present application;

[0057] Figure 3 A schematic diagram of data interaction between a relay node and a blockchain in a privacy data processing method based on blockchain provided in an embodiment of the application;

[0058] Figure 4 A schematic diagram of a verification process of a service request in a privacy data processing method based on blockchain provided in an embodiment of the present application;

[0059] Figure 5 A schematic diagram of the interaction between a zero-knowledge proof service providing node and a decentralized application operating node and a blockchain provided in an embodiment of the present application;

[0060] Figure 6 A schematic diagram of a process for obtaining asset calculation results in a privacy data processing method based on blockchain provided in an embodiment of the present application;

[0061] Figure 7 A flowchart of asset verification corresponding to financial services in a privacy data processing method based on blockchain provided in an embodiment of the present application;

[0062] Figure 8 A flowchart of asset verification corresponding to financial services in another blockchain-based privacy data processing method provided in an embodiment of the present application;

[0063] Fig. 9 A schematic diagram of a process for identifying a target user in a privacy data processing method based on blockchain provided in an embodiment of the present application;

[0064] Fig.10 A schematic diagram of the structure of a privacy data processing device based on blockchain provided in an embodiment of the present application;

[0065] Fig.11 A schematic diagram of the structure of a privacy system based on blockchain provided in an embodiment of the present application;

[0066] Fig.12 A schematic diagram of the structure of a blockchain application system provided in an embodiment of the present application;

[0067] Fig.13 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0068] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of explanation and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn in real proportion. The flowchart used in this application shows the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowchart can be implemented out of sequence, and the steps without logical context can be reversed in order or implemented simultaneously. In addition, those skilled in the art can add one or more other operations to the flowchart under the guidance of the content of the present application, or remove one or more operations from the flowchart.

[0069] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0070] It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the existence of the features declared thereafter, but does not exclude the addition of other features.

[0071] In order to clearly describe a blockchain-based privacy data processing method provided in an embodiment of the present application, the blockchain-based privacy data processing method is explained below in combination with multiple accompanying drawings. The blockchain-based privacy data processing method in the present application is applied to a privacy system, and the privacy system includes: multiple trusted source nodes. Figure 1 A flowchart of a privacy data processing method based on blockchain provided in an embodiment of the present application is shown in FIG. Figure 1 As shown, the method includes:

[0072] Step 101: Multiple trusted source nodes obtain a data acquisition request of a target user sent by a client device of a decentralized application through a blockchain.

[0073] Among them, the data acquisition request includes: encrypted user address; the encrypted user address is: the address after the client device asymmetrically encrypts the address of the target user on the blockchain. Asymmetric encryption is based on a pair of keys, namely a public key and a private key. The encryption function Encrypt() takes the plaintext message and the public key as input and returns the ciphertext. The decryption function Decrypt() takes the ciphertext and the private key as input and returns the original plaintext message. The public key can be shared with anyone in the system, while the private key is kept confidential by the owner of the encryption scheme. The public key in the asymmetric encryption of this application is the public key of the decentralized protocol corresponding to the client of the decentralized application, and the corresponding private key in the asymmetric encryption is the private key of the decentralized protocol corresponding to the client of the centralized application. The trusted source node is used to store reliable, secure and verifiable information data. Multiple trusted source nodes can be different types of nodes, each of which exists independently and does not rely on the participation or cooperation of other trusted sources. The trusted source node can be a trusted third-party entity that provides users with accurate asset quantities. These trusted sources can include off-chain centralized banks, on-chain exchanges, audit companies, or other recognized institutions in the system, etc., and the embodiments of this application are not limited to this. The client device of a centralized application can be a device that runs client software to access and use centralized services or applications. The blockchain is a public blockchain. The address of the target user on the blockchain is the unique identifier of the target user on the blockchain, which is used to distinguish different users. The target user has multiple addresses on the blockchain, each of which is associated with a different blockchain asset. The data acquisition request of the target user sent on the blockchain uses a specific on-chain address as the address of the target user.

[0074] Optionally, after receiving the blockchain address of the target user, the authenticity of the target user information is verified. After the verification is passed, the client device encrypts the address of the target user on the blockchain to obtain the encrypted user address, and sends the encrypted user address to multiple trusted source nodes, so that multiple trusted source nodes obtain the data acquisition request of the target user sent by the client device of the decentralized application through the blockchain. Among them, the process of verifying the target user information by the trusted source node can be to verify the address of the target user and the address of the relevant sensitive information owned by the trusted source. For example, the trusted source node uses the public key of the address to be verified to encrypt the message on the blockchain, and requires the target user to use the corresponding private key to decrypt it.

[0075] Step 102: Multiple trusted source nodes respectively perform homomorphic encryption on the original private data of the target user to obtain multiple homomorphically encrypted private information.

[0076] The original privacy data includes the privacy data of the target user in multiple trusted source nodes. Homomorphic encryption consists of a public key, a private key, an encryption function, a decryption function, and two calculation functions, including the original function and the homomorphic encryption function.

[0077] For example, when multiple trusted source nodes are T1, T2, ..., Tn, the target user's assets distributed in different institutions are represented by A1, A2, ..., An, where each Ai represents the number of assets held. The sum of assets A1, A2, ..., An is represented by resultU. When the original private data of the target user is A1, A2, ..., An, the homomorphically encrypted private information obtained by homomorphic encryption is C1, C2, ..., Cn.

[0078] Step 103: Multiple trusted source nodes asymmetrically encrypt multiple homomorphically encrypted private information to obtain multiple target encrypted data information.

[0079] Step 104: Multiple trusted source nodes upload multiple target encrypted privacy information and encrypted user addresses to the blockchain.

[0080] Optionally, multiple trusted source nodes asymmetrically encrypt multiple homomorphically encrypted private information, and upload the target encrypted private information and the user encrypted address to the blockchain, so that the original private data is encrypted at each stage, avoiding the leakage of the target user's original private data after uploading the target encrypted private information to the blockchain.

[0081] The present application provides a privacy data processing method based on blockchain, wherein multiple trusted source nodes obtain the data acquisition request of the target user sent by the client device of the decentralized application through the blockchain, and the multiple trusted source nodes respectively homomorphically encrypt the original privacy data of the target user to obtain multiple homomorphically encrypted privacy information; multiple trusted source nodes asymmetrically encrypt the multiple homomorphically encrypted privacy information to obtain multiple target encrypted data information; multiple trusted source nodes upload the multiple target encrypted privacy information and encrypted user addresses to the blockchain. In the present application, after multiple trusted source nodes obtain the data acquisition request of the target user, the original privacy data of the target user is homomorphically encrypted to protect the original privacy data of the user from being directly accessed, and even if the homomorphically encrypted privacy information is attacked, the original privacy data cannot be obtained. After the original privacy data is homomorphically encrypted, it is asymmetrically encrypted again to ensure the security of uploading the homomorphically encrypted privacy information to the blockchain.

[0082] Based on the above embodiment, the privacy system further includes: a relay node. To this end, the present application provides a process for uploading the target encryption result in a privacy data processing method based on blockchain. Figure 2 A flowchart of uploading a target encryption result in a privacy data processing method based on blockchain provided in an embodiment of the present application is shown in FIG. Figure 2As shown, in the above step 102, multiple trusted source nodes asymmetrically encrypt multiple homomorphically encrypted private information to obtain multiple target encrypted private information, including:

[0083] Step 201: Multiple trusted source nodes asymmetrically encrypt multiple homomorphically encrypted private information according to the public key of the relay node to obtain multiple target encrypted private information.

[0084] Among them, the relay node is unable to decrypt homomorphically encrypted private information. The relay node is independent of other nodes. The relay node uploads the received information and generated results to the blockchain for information tracing. It has a pair of asymmetric encrypted public and private keys, which can be recorded as pkR and skR.

[0085] For example, multiple trusted source nodes asymmetrically encrypt multiple homomorphically encrypted private information C1, C2, ..., Cn according to the public key pkR of the relay node to obtain multiple target encrypted private information EC1, EC2, ..., ECn.

[0086] On the basis of the above steps 101 to 104, the method includes:

[0087] Step 202: The relay node obtains multiple target encrypted private information from the blockchain.

[0088] For example, the relay node obtains multiple target encrypted private information EC1, EC2, ..., ECn from the blockchain.

[0089] Step 203: The relay node uses the private key of the relay node to asymmetric decrypt multiple target encrypted privacy information to obtain multiple homomorphically encrypted privacy information.

[0090] For example, the relay node uses the private key skR of the relay node to asymmetric decrypt multiple target encrypted privacy information EC1, EC2, ..., ECn, and obtains multiple homomorphically encrypted privacy information C1, C2, ..., Cn.

[0091] Step 204: The relay node executes a homomorphic computing function on multiple homomorphically encrypted private information to obtain a target encryption result.

[0092] Among them, the homomorphic computing function is the Hom f() function, which is used to homomorphically encrypt multiple private information to obtain a target encryption result.

[0093] For example, the relay node executes the homomorphic computing function Hom f() on the homomorphically encrypted private information C1, C2, ..., Cn to obtain the target encryption result Cresult U.

[0094] Step 205: The relay node uploads the target encryption result and the encrypted user address to the blockchain.

[0095] For example, the relay node uploads the target encryption result Cresult U and the encrypted user address CaddrU to the blockchain.

[0096] For example, Figure 3 A schematic diagram of data interaction between a relay node and a blockchain in a privacy data processing method based on blockchain provided in an embodiment of the application, such as Figure 3 As shown, multiple trusted source nodes asymmetrically encrypt multiple homomorphically encrypted privacy information C1, C2, ..., Cn according to the public key of the relay node, obtain multiple target encrypted privacy information EC1, EC2, ..., ECn, and upload them to the blockchain, the relay node obtains the multiple target encrypted privacy information EC1, EC2, ..., ECn from the blockchain; the relay node uses the private key of the relay node to asymmetrically decrypt the multiple target encrypted privacy information to obtain multiple homomorphically encrypted privacy information C1, C2, ..., Cn; the relay node executes the homomorphic calculation function on the multiple homomorphically encrypted privacy information C1, C2, ..., Cn to obtain the target encryption result Cresult U; the relay node uploads the target encryption result and the encrypted user address to the blockchain.

[0097] In an embodiment of the present application, the relay node obtains multiple target encrypted privacy information from the blockchain, and executes a homomorphic computing function on the homomorphic encrypted privacy to obtain a target encryption result, and uploads the target encryption result and the encrypted user address to the blockchain. The present application can ensure that the target user's privacy information always exists in an encrypted form. Homomorphic encryption ensures that the data is calculated without decryption, thereby protecting the privacy of user data.

[0098] On the basis of the above embodiment, the privacy system further includes: a zero-knowledge proof service providing node. To this end, the present application provides a process for determining homomorphically encrypted privacy information in a privacy data processing method based on blockchain, wherein in the above step 103, multiple trusted source nodes asymmetrically encrypt multiple homomorphically encrypted privacy information to obtain multiple target encrypted data information, and further includes:

[0099] Multiple trusted source nodes respectively provide the public keys of the nodes based on the zero-knowledge proof service, and homomorphically encrypt the original private data of the target user to obtain multiple homomorphically encrypted private information.

[0100] Among them, the zero-knowledge proof service provides nodes to prove the scope of the target's private data, while retaining the confidentiality of the actual results representing the user's overall private data. The zero-knowledge proof service has a pair of asymmetric encrypted public and private keys, which can be represented as public key pkZ and private key skZ.

[0101] For example, multiple trusted source nodes encrypt the target user's original private data A1, A2, ..., An through the encryption function Encrypt() in homomorphic encryption based on the public key pkZ of the zero-knowledge proof service provider node, and obtain multiple homomorphic encrypted private information C1, C2, ..., Cn.

[0102] In the embodiment of the present application, multiple trusted source nodes perform homomorphic encryption on the original private data of the target user according to the public key of the zero-knowledge proof service provider node, and obtain multiple homomorphically encrypted private information. It is ensured that the multiple homomorphically encrypted private information can be decrypted by the decryption function in the homomorphic encryption only through the private key of the zero-knowledge proof service provider node, ensuring that the user's private data is not leaked during the uplink and downlink process.

[0103] On the basis of the above embodiment, the decentralized application is a decentralized financial application. The present application also provides a verification process of a service request in a privacy data processing method based on blockchain. Figure 4 A schematic diagram of the verification process of a service request in a privacy data processing method based on blockchain provided in an embodiment of the present application is as follows: Figure 4 As shown, based on the above steps 101 to 104, the method further includes:

[0104] Step 401: The zero-knowledge proof service providing node receives an asset verification request sent by the operating node of the decentralized application through the blockchain.

[0105] Among them, the asset verification request is an asset verification request triggered by a service request sent in advance by the client device of the decentralized financial application to the operating node through the blockchain; the asset verification request includes: an encrypted user address, and an asset declaration statement. The operating node of the centralized application is a decentralized finance (DeFi) protocol operating node. The encrypted user address is the user address encrypted by the public key provided by the zero-knowledge proof service. The asset declaration statement can be information such as the specific scope of the asset or the definition of the asset, which is not limited in the embodiments of the present application. The operating node provides services to users through the information of the target user, and the user's information can be the user's address on the blockchain.

[0106] Optionally, the client device of the decentralized financial application sends a service request to the decentralized financial protocol operation node through the blockchain in advance, triggering an asset verification request, and the zero-knowledge proof service provider node receives the asset verification request sent by the centralized financial (DeFi) protocol operation node through the regional block.

[0107] Step 402: The zero-knowledge proof service providing node obtains the target encryption result from the blockchain according to the encrypted user address.

[0108] Optionally, the zero-knowledge proof service provider node obtains the target encryption result from the blockchain according to the encrypted user address, that is, the homomorphically encrypted privacy information of the target user's original private data.

[0109] Step 403: The zero-knowledge proof service providing node decrypts the target encryption result according to the private key of the zero-knowledge proof service providing node to obtain the asset calculation result.

[0110] Optionally, the target encryption result is the original private data encrypted by the public key of the zero-knowledge proof service provider node. The zero-knowledge proof service provider node obtains the target encryption result from the blockchain, decrypts the target encryption result by using the private key of the zero-knowledge proof service provider node, and obtains the asset calculation result.

[0111] Step 404: The zero-knowledge proof service providing node generates a zero-knowledge proof statement for the asset declaration statement based on the asset calculation result and using a zero-knowledge proof generation algorithm.

[0112] Among them, there are two basic entities in zero-knowledge proof, namely the prover and the verifier. Zero-knowledge proof is an encryption method in which the prover can convince the verifier that a statement is true without revealing any other information except the authenticity of the statement itself. Zero-knowledge proof includes a proof generation function Generation() and a proof verification function Verification(). The input of the proof generation function is a statement or question, denoted as Q. The prover executes the Generation(Q) function, which generates a zero-knowledge proof P. After executing the Verification(P) function, the verifier V will be able to determine that the output is True (correct) or False (wrong). The zero-knowledge proof statement can be one or more, and the embodiments of the present application do not limit this.

[0113] Optionally, the zero-knowledge proof service providing node adopts a zero-knowledge proof generation algorithm based on the asset calculation result, uses the asset calculation result as the zero-knowledge proof P, and generates a zero-knowledge proof statement of the asset based on the asset declaration statement.

[0114] Step 405: The zero-knowledge proof providing node uploads the zero-knowledge proof statement and the encrypted user address to the blockchain, so that the operation node performs the verification operation of the financial service corresponding to the service request.

[0115] For example, Figure 5 A schematic diagram of the interaction between a zero-knowledge proof service providing node and a decentralized application operation node and a blockchain provided in an embodiment of the present application is shown in FIG. Figure 5As shown, the zero-knowledge proof service provider node receives the asset verification request sent by the operating node of the decentralized application through the blockchain. The zero-knowledge proof service provider node obtains the target encryption result Cresult U from the blockchain according to the encrypted user address CaddrU; the zero-knowledge proof service provider node decrypts the target encryption result according to the private key of the zero-knowledge proof service provider node to obtain the asset calculation result result U; the zero-knowledge proof service provider node uses the zero-knowledge proof generation algorithm based on the asset calculation result result U to generate a zero-knowledge proof statement P for the asset declaration statement; the zero-knowledge proof provider node uploads the zero-knowledge proof statement and the encrypted user address CaddrU to the blockchain, so that the operating node executes the verification operation of the financial service corresponding to the service request.

[0116] In an embodiment of the present application, the asset declaration statement is verified through a zero-knowledge proof service node to obtain a verification result, and the zero-knowledge proof statement and the encrypted user address are uploaded to the blockchain. The specific range of the user's asset calculation result can be determined without leaking the user's original privacy data, thereby protecting the user's privacy when obtaining financial services and increasing the security of on-chain transactions.

[0117] Based on the above embodiments, this application also provides a process for obtaining asset calculation results in a privacy data processing method based on blockchain. Figure 6 A flowchart of obtaining asset calculation results in a privacy data processing method based on blockchain provided in an embodiment of the present application is shown in FIG. Figure 6 As shown, in the above step 403, the zero-knowledge proof service providing node decrypts the target encryption result according to the private key of the zero-knowledge proof service providing node to obtain the asset calculation result, including:

[0118] Step 601: The zero-knowledge proof service provider node starts the zero-knowledge proof program.

[0119] Among them, the zero-knowledge proof program is used to perform zero-knowledge proof.

[0120] Optionally, after the zero-knowledge proof service receives an asset verification request sent by the operation node of the centralized application through the blockchain, the zero-knowledge proof service is triggered.

[0121] Step 602: The zero-knowledge proof service providing node, as the prover, uses the zero-knowledge proof procedure to decrypt the target encryption result according to the private key of the zero-knowledge proof service providing node to obtain the asset calculation result.

[0122] Optionally, the zero-knowledge proof service providing node acts as a prover, decrypts the target encryption result according to the private key of the zero-knowledge proof service providing node, and performs zero-knowledge proof according to the asset calculation result and the asset verification request.

[0123] In the embodiment of the present application, the zero-knowledge proof service provider node starts the zero-knowledge proof program. The zero-knowledge proof service provider node, as the prover, uses the zero-knowledge proof program to decrypt the target encryption result according to the private key of the zero-knowledge proof service provider node to obtain the asset calculation result. The asset calculation result can be decrypted by the private key of the zero-knowledge proof service provider node. Only the calculation result of the asset can be known through the private key of the zero-knowledge proof service provider node, and the specific source of the asset cannot be determined, which ensures that the original asset information of the user is not leaked.

[0124] Based on the above embodiments, the present application also provides a process for asset verification corresponding to financial services in a privacy data processing method based on blockchain. Figure 7 A flowchart of asset verification corresponding to financial services in a privacy data processing method based on blockchain provided in an embodiment of the present application is shown in FIG. Figure 7 As shown, based on the above steps 401 to 405, the method further includes:

[0125] Step 701: The operation node obtains the zero-knowledge proof statement and encrypted user address from the blockchain.

[0126] Step 702: The operation node performs a verification operation of the financial service corresponding to the service request on the target user based on the zero-knowledge proof statement and the encrypted user address.

[0127] Optionally, the operation node performs a verification operation on the financial service corresponding to the service request executed by the target user according to the zero-knowledge proof statement based on the zero-knowledge proof statement and the encrypted user address, and determines whether the verification of the financial service corresponding to the service request executed by the target user is successful.

[0128] In the embodiment of the present application, the operation node obtains the zero-knowledge proof statement and the encrypted user address from the blockchain, and performs the verification operation of the service request corresponding to the financial service on the target user based on the zero-knowledge proof statement and the encrypted user address. It can ensure that the operation node can perform the verification operation of the financial service corresponding to the service request on the target user based on the zero-knowledge proof statement without knowing the original privacy data of the target user, thus avoiding the privacy leakage of the user in the process of obtaining financial services and improving the security of the user's original privacy data.

[0129] Based on the above embodiments, this application also provides another process of asset verification corresponding to financial services in a privacy data processing method based on blockchain. Figure 8A flowchart of asset verification corresponding to financial services in another blockchain-based privacy data processing method provided in an embodiment of the present application is as follows: Figure 8 As shown, in the above step 701, the operation node performs an asset verification operation of the financial service corresponding to the service request on the target user based on the zero-knowledge proof and the encrypted user address, including:

[0130] Step 801: The operation node uses a preset zero-knowledge proof verification algorithm to verify the zero-knowledge proof statement.

[0131] Optionally, the operating node acts as a verifier and uses a preset zero-knowledge proof verification algorithm, that is, a proof verification function, to verify the zero-knowledge proof statement. By executing the proof verification function, it can be determined whether the zero-knowledge proof statement is correct or incorrect.

[0132] For example, when the zero-knowledge proof statements are "Alice's asset calculation result belongs to the interval (W, X]" and "Alice's asset calculation result belongs to the interval (X, Y]", the zero-knowledge proof service provider node generates the following zero-knowledge proof statement based on the asset calculation result: "Alice's asset calculation result belongs to the interval (X, Y] is True, and Alice's asset calculation result belongs to the interval (W, X] is False".

[0133] If the verification is successful, execute step 802.

[0134] Step 802: The operation node identifies the target user according to the encrypted user address, and updates the financial service corresponding to the service request of the target user according to the identification result.

[0135] Optionally, if the verification passes, that is, the zero-knowledge proof statement is correct, the operation node then identifies the target user based on the encrypted user address, determines the specific information of the target user based on the identification result, and updates the financial service corresponding to the service request for the target user.

[0136] On the basis of the above embodiment, the encrypted user address is the address after the client device asymmetrically encrypts the target user's address on the blockchain according to the public key of the operating node; for this purpose, the present application also provides a process for identifying the target user in a privacy data processing method based on blockchain, Fig. 9 A flowchart of identifying the identity of a target user in a privacy data processing method based on blockchain provided in an embodiment of the present application is shown in FIG. Fig. 9 As shown, in the above step 802, the operation node identifies the target user according to the encrypted user address, including:

[0137] Step 901: The operation node decrypts the encrypted user address according to the private key of the operation node to obtain the decrypted user address.

[0138] Optionally, the encrypted user address is encrypted by a public key pair of an operating node. After the application node obtains the encrypted user address, the encrypted user address is decrypted by a private key of the operating node to obtain a decrypted user address.

[0139] Step 902: The operation node associates the decrypted user address with the target user to identify the target user.

[0140] Optionally, the operation node associates the decrypted user address with the target user, thereby identifying the identity of the target user, and provides financial services to the target user based on the identity of the target user.

[0141] In an embodiment of the present application, the operating node decrypts the encrypted user address according to the private key of the operating node to obtain the decrypted user address, and associates the decrypted user address with the target user, thereby identifying the target user. The user's privacy information can be used without leaking the privacy of the target user on the blockchain.

[0142] Based on the above method, when any of the trusted source nodes, relay nodes, zero-knowledge proof service provider nodes and operation nodes in this application is attacked, the original privacy data of the target user will not be leaked.

[0143] For example, when a trusted source node is attacked, it is impossible to obtain the original private data of the target user's precise asset information and associate it with the target user's address by destroying the trusted source node. Multiple trusted source nodes hold the original private data about the target user. However, since multiple trusted source nodes do not have the public key of the operating node, they cannot encrypt the user address stored on the blockchain. Similarly, due to the lack of the private key of the zero-knowledge proof service providing node, they cannot encrypt the target encryption result. Therefore, if an attacker attacks a trusted source node, all the attacker can know is the open source of the original private data.

[0144] For example, when a relay node is attacked, for the relay node, it receives multiple target encrypted private information from a trusted source and decrypts them into multiple homomorphically encrypted private information and target encryption results as homomorphically encrypted ciphertext. Since the relay node does not have the public key of the operating node, it cannot encrypt the address of the target user stored on the blockchain. Similarly, multiple homomorphically encrypted private information and target encryption results are encrypted with the public key of the zero-knowledge proof service provider node, and can only be decrypted with the private key of the zero-knowledge proof service provider node, so the relayer cannot know the plaintext of multiple homomorphically encrypted private information and target encryption results. If an attacker attacks the relay node, then all the attacker can know is multiple homomorphically encrypted private information and target encryption results.

[0145] For example, when the zero-knowledge proof service providing node is attacked, since the encrypted user address is encrypted using the public key of the operating node, the zero-knowledge proof service providing node cannot decrypt it. All it can decrypt is the target encryption result, because the target encryption result is encrypted using the public key of the zero-knowledge proof service providing node. Therefore, the zero-knowledge proof service providing node cannot determine the exact asset value associated with the target user on the blockchain. Therefore, if an attacker attacks the zero-knowledge proof service providing node, all the attacker can know is the asset value result associated with the unknown user.

[0146] For example, when an operation node is attacked, the operation node cooperates with the zero-knowledge proof service provider node to obtain a zero-knowledge proof statement based on the encrypted user address. The validity of the proof is verified using an algorithm. In addition, the operation node has a private key to decrypt the encrypted user address. Therefore, if the operation node is attacked, it is limited to the knowledge of the target user's address and the user's assets within a certain range, and the accurate asset value cannot be obtained.

[0147] At the same time, when there are malicious users attacking the privacy system, it cannot affect the operations of other users. During the asset information upload phase, users interact only by providing the trusted source node with the address of the address user on the blockchain. Malicious users may try to cheat by submitting a wrong address instead of their address. However, the trusted source node verifies the legitimacy of the initiating user before performing the upload task. Data upload by the trusted source node depends on the successful verification of the initiating address and the related data addresses held by the trusted source node. Therefore, if a malicious user submits a wrong address, the initial identity verification will fail, stopping further protocol procedures.

[0148] During the asset verification phase, users can only send their addresses to the operating node, and malicious users may send the wrong address from their actual address. The operating node can decrypt and identify the inconsistency between the decrypted address and the requested address. When there is a discrepancy between and, the operating node will refuse to provide services to the malicious user.

[0149] Based on the same inventive concept, the embodiments of the present application also provide a privacy data processing device based on blockchain corresponding to the privacy data processing method based on blockchain. Since the principle of solving the problem by the device in the embodiments of the present application is similar to the above-mentioned privacy data processing method based on blockchain in the embodiments of the present application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0150] Fig.10 A schematic diagram of the structure of a privacy data processing device based on blockchain provided in an embodiment of the present application, the device includes:

[0151] The acquisition module 1001 is used for multiple trusted source nodes to acquire a data acquisition request of a target user sent by a client device of a decentralized application through a blockchain, wherein the data acquisition request includes: an encrypted user address; the encrypted user address is: the address of the target user on the blockchain asymmetrically encrypted by the client device;

[0152] The first encryption module 1002 is used for multiple trusted source nodes to respectively perform homomorphic encryption on the original private data of the target user to obtain multiple homomorphic encrypted private information;

[0153] The second encryption module 1003 is used for multiple trusted source nodes to asymmetrically encrypt multiple homomorphically encrypted private information to obtain multiple target encrypted data information;

[0154] The upload module 1004 is used for multiple trusted source nodes to upload multiple target encrypted privacy information and encrypted user addresses to the blockchain.

[0155] Optionally, the privacy system also includes: a relay node; a first encryption module 1002, which is specifically used for: multiple trusted source nodes asymmetrically encrypting multiple homomorphically encrypted privacy information according to the public key of the relay node to obtain multiple target encrypted privacy information.

[0156] The first encryption module 1002 is further used for: the relay node obtains multiple target encrypted private information from the blockchain;

[0157] The relay node uses the private key of the relay node to asymmetric decrypt multiple target encrypted private information to obtain multiple homomorphically encrypted private information;

[0158] The relay node performs homomorphic computing functions on multiple homomorphically encrypted private information to obtain the target encryption result;

[0159] The relay node uploads the target encryption result and encrypted user address to the blockchain.

[0160] Optionally, the privacy system also includes: a zero-knowledge proof service providing node, a first encryption module 1002, and is also used for: multiple trusted source nodes to homomorphically encrypt the original privacy data of the target user according to the public key of the zero-knowledge proof service providing node, to obtain multiple homomorphically encrypted privacy information.

[0161] Optionally, the first encryption module 1002 is further used for: the zero-knowledge proof service providing node receives an asset verification request sent by the operating node of the decentralized application through the blockchain, where the asset verification request is triggered by a service request sent in advance by a client device of the decentralized financial application to the operating node through the blockchain; the asset verification request includes: an encrypted user address, and an asset declaration statement;

[0162] The zero-knowledge proof service provider node obtains the target encryption result from the blockchain based on the encrypted user address;

[0163] The zero-knowledge proof service provider node decrypts the target encryption result according to the private key of the zero-knowledge proof service provider node to obtain the asset calculation result;

[0164] The zero-knowledge proof service provider node generates a zero-knowledge proof statement for the asset declaration statement based on the asset calculation results and using the zero-knowledge proof generation algorithm;

[0165] The zero-knowledge proof providing node uploads the zero-knowledge proof statement and encrypted user address to the blockchain, allowing the operating node to perform verification operations for the financial services corresponding to the service request.

[0166] Optionally, the first encryption module 1002 is specifically used to: a zero-knowledge proof service providing node to start a zero-knowledge proof program;

[0167] The zero-knowledge proof service provider node, as the prover, uses the zero-knowledge proof procedure to decrypt the target encryption result based on the private key of the zero-knowledge proof service provider node to obtain the asset calculation result.

[0168] Optionally, the first encryption module 1002 is further used for: the operation node to obtain a zero-knowledge proof statement and an encrypted user address from the blockchain;

[0169] The operation node performs verification operations on the target user's service request for the corresponding financial service based on the zero-knowledge proof statement and encrypted user address.

[0170] Optionally, the first encryption module 1002 is specifically used to: the operation node uses a preset zero-knowledge proof verification algorithm to verify the zero-knowledge proof statement;

[0171] If the verification is successful, the operation node will identify the target user based on the encrypted user address, and based on the identification result, update the financial service corresponding to the service request for the target user.

[0172] Optionally, the encrypted user address is an address obtained by asymmetrically encrypting the address of the target user in the blockchain by the client device according to the public key of the operation node; the first encryption module 1002 is specifically used for: the operation node decrypts the encrypted user address according to the private key of the operation node to obtain the decrypted user address;

[0173] The operation node associates the decrypted user address with the target user to identify the target user.

[0174] For descriptions of the processing flow of each module in the device and the interaction flow between each module, reference may be made to the relevant descriptions in the above method embodiment, which will not be described in detail here.

[0175] The present application also provides a privacy system based on blockchain. Fig.11 A schematic diagram of the structure of a privacy system based on blockchain provided in an embodiment of the present application is shown in FIG. Fig.11 As shown, the privacy system 1100 includes: a plurality of trusted source nodes 1101, a relay node 1102, and a zero-knowledge proof providing node 1103;

[0176] Multiple trusted source nodes 1101, relay nodes 1102, and zero-knowledge proof providing nodes 1103 are all connected to the blockchain 1104 where the client device of the decentralized application is located;

[0177] Multiple trusted source nodes 1101 are used to execute the steps performed by the trusted source nodes in the above-mentioned blockchain-based privacy data processing method, the relay node 1102 is used to execute the steps performed by the relay node in the above-mentioned blockchain-based privacy data processing method, and the zero-knowledge proof providing node 1103 is used to execute the steps performed by the zero-knowledge proof providing node in the above-mentioned blockchain-based privacy data processing method.

[0178] The present application also provides a blockchain application system. Fig.12 A schematic diagram of the structure of a blockchain application system provided in an embodiment of the present application is shown in FIG. Fig.12 As shown, the blockchain application system includes: a client device 1201 of a decentralized application, an operating node 1202 of a decentralized application, and a privacy system 1100 based on blockchain.

[0179] The present application also provides a computer device, Fig.13 A schematic diagram of the structure of a computer device provided in an embodiment of the present application is shown in FIG. Fig.13As shown, the computer device includes: a processor 1301, a memory 1302, and optionally, a bus 1303. The memory 1302 stores machine-readable instructions executable by the processor 1301. When the computer device is running, the processor 1301 communicates with the memory 1302 through the bus 1303. When the machine-readable instructions are executed by the processor 1301, the steps of the above-mentioned blockchain-based privacy data processing method are executed.

[0180] An embodiment of the present application also provides a computer-readable memory having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the privacy data processing method of the above-mentioned blockchain are executed.

[0181] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the system and device described above can refer to the corresponding process in the method embodiment, and will not be repeated in this application. In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0182] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a memory, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned memory includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code.

[0183] The above are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be covered by the protection scope of the present application.

Claims

1. A privacy data processing method based on blockchain, characterized in that: Applied to a privacy system, the privacy system comprises: a plurality of trusted source nodes, the method comprises: The multiple trusted source nodes obtain a data acquisition request of a target user sent by a client device of a decentralized application through a blockchain, wherein the data acquisition request includes: an encrypted user address; the encrypted user address is: the address of the target user on the blockchain asymmetrically encrypted by the client device; The multiple trusted source nodes respectively perform homomorphic encryption on the original private data of the target user to obtain multiple homomorphically encrypted private information; The multiple trusted source nodes asymmetrically encrypt the multiple homomorphically encrypted private information to obtain multiple target encrypted data information; The multiple trusted source nodes upload the multiple target encrypted private information and the encrypted user addresses to the blockchain.

2. The method for processing privacy data based on blockchain according to claim 1, characterized in that: The privacy system also includes: a relay node; The multiple trusted source nodes asymmetrically encrypt the multiple homomorphically encrypted private information to obtain multiple target encrypted private information, including: The multiple trusted source nodes asymmetrically encrypt the multiple homomorphically encrypted private information according to the public key of the relay node to obtain the multiple target encrypted private information; The method further comprises: The relay node obtains the multiple target encrypted private information from the blockchain; The relay node uses the private key of the relay node to asymmetrically decrypt the multiple target encrypted private information to obtain the multiple homomorphically encrypted private information; The relay node performs a homomorphic computing function on the multiple homomorphically encrypted private information to obtain a target encryption result; The relay node uploads the target encryption result and the encrypted user address to the blockchain.

3. The method for processing privacy data based on blockchain according to claim 2, characterized in that: The privacy system further includes: a zero-knowledge proof service providing node, the multiple trusted source nodes respectively perform homomorphic encryption on the original private data of the target user to obtain multiple homomorphic encrypted private information, and further includes: The multiple trusted source nodes respectively perform homomorphic encryption on the original private data of the target user according to the public key of the zero-knowledge proof service providing node to obtain the multiple homomorphically encrypted private information.

4. The method for processing privacy data based on blockchain according to claim 3 is characterized in that: The decentralized application is a decentralized financial application, and the method further includes: The zero-knowledge proof service providing node receives an asset verification request sent by the operating node of the decentralized application through the blockchain, wherein the asset verification request is triggered by a service request sent in advance by the client device of the decentralized financial application to the operating node through the blockchain; the asset verification request includes: the encrypted user address and an asset declaration statement; The zero-knowledge proof service providing node obtains the target encryption result from the blockchain according to the encrypted user address; The zero-knowledge proof service providing node decrypts the target encryption result according to the private key of the zero-knowledge proof service providing node to obtain the asset calculation result; The zero-knowledge proof service providing node generates a zero-knowledge proof statement for the asset declaration statement based on the asset calculation result and using a zero-knowledge proof generation algorithm; The zero-knowledge proof providing node uploads the zero-knowledge proof statement and the encrypted user address to the blockchain, so that the operation node performs a verification operation of the financial service corresponding to the service request.

5. The method for processing privacy data based on blockchain according to claim 4 is characterized in that: The zero-knowledge proof service providing node decrypts the target encryption result according to the private key of the zero-knowledge proof service providing node to obtain the asset calculation result, including: The zero-knowledge proof service providing node starts a zero-knowledge proof procedure; The zero-knowledge proof service providing node, as the prover, decrypts the target encryption result according to the private key of the zero-knowledge proof service providing node through the zero-knowledge proof procedure to obtain the asset calculation result.

6. The method for processing privacy data based on blockchain according to claim 4 is characterized in that: The method further comprises: The operation node obtains the zero-knowledge proof statement and the encrypted user address from the blockchain; The operation node performs a verification operation of the financial service corresponding to the service request on the target user based on the zero-knowledge proof statement and the encrypted user address.

7. The method for processing privacy data based on blockchain according to claim 6, characterized in that: The operation node performs an asset verification operation of the financial service corresponding to the service request on the target user based on the zero-knowledge proof and the encrypted user address, including: The operation node verifies the zero-knowledge proof statement using a preset zero-knowledge proof verification algorithm; If the verification is successful, the operation node identifies the target user according to the encrypted user address, and updates the financial service corresponding to the service request for the target user according to the identification result.

8. The method for processing privacy data based on blockchain according to claim 7, characterized in that: The encrypted user address is the address of the target user in the blockchain asymmetrically encrypted by the client device according to the public key of the operating node; The operation node identifies the target user according to the encrypted user address, including: The operation node decrypts the encrypted user address according to the private key of the operation node to obtain a decrypted user address; The operation node associates the decrypted user address with the target user to identify the target user.

9. A privacy system based on blockchain, characterized in that: The privacy system includes: a plurality of trusted source nodes, relay nodes and zero-knowledge proof providing nodes; The multiple trusted source nodes, the relay node, and the zero-knowledge proof providing node are all connected to the blockchain where the client device of the decentralized application is located; The multiple trusted source nodes are used to execute the steps performed by the trusted source nodes in the blockchain-based privacy data processing method described in any one of claims 1-8, the relay node is used to execute the steps performed by the relay node in the blockchain-based privacy data processing method described in any one of claims 2-8, and the zero-knowledge proof providing node is used to execute the steps performed by the zero-knowledge proof providing node in the blockchain-based privacy data processing method described in any one of claims 3-8.

10. A blockchain application system, characterized in that: The blockchain application system includes: a client device of the decentralized application, an operation node of the decentralized application, and the blockchain-based privacy system as described in claim 9.

Images