Cross-chain data supervision method and system based on homomorphic encryption

Abstract

The invention discloses a cross-chain data supervision method and system based on homomorphic encryption, and the method comprises the steps: a supervisor calls an identity management contract ISC of a relay chain to carry out the registration of the identity of the supervisor, and generates a first homomorphic public and private key pair (Spk, Ssk) based on the ISC after the registration succeeds; when the user needs to participate in the cross-chain activity, a second homomorphic public and private key pair (Upk, Usk) is generated in an under-chain mode, and interaction with the supervisor is carried out based on the first homomorphic public and private key pair (Spk, Ssk) and the second homomorphic public and private key pair (Upk, Usk) so as to carry out identity registration and obtain a unique identity identifier; receiving a cross-chain transaction request of a user, and according to the type of the cross-chain transaction request, performing account registration by using the unique identity label and the data management contract DSC; and when the user completes account registration, performing cross-chain transaction by using the cross-chain historical contract HSC according to the type of the cross-chain transaction request. According to the invention, a set of cross-chain data interaction process is constructed through homomorphic encryption and intelligent contract technologies, and safe and reliable cross-chain data supervision is realized.

Description

Technical Field

[0001] The present invention relates to the field of data supervision technology, and more specifically, to a cross-chain data supervision method and system based on homomorphic encryption. Background Art

[0002] With the continuous development of blockchain technology, various industries and fields have continuously emerged with applications that combine blockchain technology, and blockchain technology plays a pivotal role in them. In this context, many companies have developed their own blockchain systems. With the continuous changes in market demand, cross-chain business has emerged in order to achieve data interaction between different blockchain systems.

[0003] However, due to the lack of a complete cross-chain standard, cross-chain operations of heterogeneous blockchain systems have become very difficult, and the identity authentication of cross-chain participants and the privacy protection of cross-chain data are particularly important. In some special cross-chain scenarios, such as cross-chain transfers and cross-chain data sharing, it is necessary to ensure the privacy of data while implementing the operation of private data and ensuring its correctness. In addition, the supervision and confirmation of cross-chain data and cross-chain transactions are also an important part of data governance.

[0004] The current supervision of cross-chain data is difficult to form a unified and effective supervision plan due to the barriers between industries. We can only trust the trusted party of the cross-chain participants, and there is a lack of traceability and tracing of cross-chain data. When a dispute arises, it can only be located in a certain cross-chain transaction.

[0005] Therefore, a cross-chain data supervision method based on homomorphic encryption is needed. Summary of the invention

[0006] The present invention proposes a cross-chain data supervision method and system based on homomorphic encryption to solve the problem of how to solve the data supervision problem of cross-chain business.

[0007] In order to solve the above problems, according to one aspect of the present invention, a cross-chain data supervision method based on homomorphic encryption is provided, and the method includes:

[0008] The regulator calls the identity management contract ISC of the relay chain to register the regulator's identity, and after successful registration, generates the first homomorphic public-private key pair (Spk, Ssk) based on the identity management contract;

[0009] When a user needs to participate in cross-chain activities, a second homomorphic public-private key pair (Upk, Usk) is generated off-chain, and based on the first homomorphic public-private key pair (Spk, Ssk) and the second homomorphic public-private key pair (Upk, Usk), the user interacts with the regulator to register his / her identity and obtain a unique identity.

[0010] Receive the user's cross-chain transaction request, and register the account using the unique identity and data management contract DSC according to the type of the cross-chain transaction request;

[0011] When the user completes the account registration, the cross-chain transaction is performed using the cross-chain historical contract HSC according to the type of cross-chain transaction request.

[0012] Preferably, the step of interacting with a regulator based on the first homomorphic public-private key pair (Spk, Ssk) and the second homomorphic public-private key pair (Upk, Usk) to register an identity and obtain a unique identity includes:

[0013] The user forms transaction parameters based on identity information and Upk in the application chain, encrypts them with Spk and sends cross-chain transactions to the relay chain;

[0014] The regulator uses Ssk to decrypt the transaction parameters and review the user's identity. When the review is successful, the regulator determines the user's unique identity based on the user name and random string, and uses Upk to encrypt the unique identity and send it back to the user's application chain;

[0015] The user uses Usk to decrypt the data packet under the application chain to obtain the unique identity.

[0016] Preferably, the types of cross-chain transaction requests include: cross-chain transfer transactions and cross-chain data transactions.

[0017] Preferably, according to the type of cross-chain transaction request, the cross-chain historical contract HSC is used to perform the cross-chain transaction, including:

[0018] When the cross-chain transaction request is a cross-chain transfer transaction, the data management contract DSC is used to verify the identity of U1 through the unique identity identifier U1id of the transaction initiator U1 and the public key U1pk in the corresponding second homomorphic public-private key pair; after successful verification, the value with U1 as the key is searched in the first set Tmap of the cross-chain history contract HSC, and a new transfer record is added to the back, and the status is changed to Pending. After the entire cross-chain transaction is completed, the status is changed to Finish. At the same time, in the cross-chain history contract DSC, U1pk is used to homomorphically reduce the balance, and the public key U2pk in the second homomorphic public-private key pair corresponding to the transaction recipient is used to homomorphically increase the transfer amount; wherein, the first set Tmap stores the transfer records of all accounts.

[0019] Preferably, according to the type of cross-chain transaction request, the cross-chain historical contract HSC is used to perform the cross-chain transaction, including:

[0020] When the cross-chain transaction request is a cross-chain data transaction, the data management contract DSC contract is used to determine whether U1 is the owner of D1 through the unique identity U1id of the transaction initiator U1 and the data name; after successful verification, the value with the data name D1 is found in the second set Dmap of the cross-chain history contract HSC, and a new shared record is added to the back, and the status is modified to Pending. After the entire cross-chain transaction is completed, the status is modified to Finish, and the unique identity U2id of the transaction recipient is added to the cross-chain history contract DSC as the authorized person; wherein, the operation records of all data are stored in the second set Dmap.

[0021] Preferably, the method further comprises:

[0022] The regulator queries the complete transaction records of users on a specific node through the cross-chain historical contract HSC; among them, the records in the cross-chain historical contract HSC are all stored in a chain structure.

[0023] According to another aspect of the present invention, a cross-chain data supervision system based on homomorphic encryption is provided, the system comprising:

[0024] The supervisor identity registration module is used to enable the supervisor to call the identity management contract ISC of the relay chain to register the supervisor identity, and generate the first homomorphic public-private key pair (Spk, Ssk) based on the identity management contract after successful registration;

[0025] A user registration module is used to generate a second homomorphic public-private key pair (Upk, Usk) off-chain when a user needs to participate in a cross-chain activity, and interact with the regulator based on the first homomorphic public-private key pair (Spk, Ssk) and the second homomorphic public-private key pair (Upk, Usk) to register the identity and obtain a unique identity;

[0026] An account registration module is used to receive a user's cross-chain transaction request and, according to the type of the cross-chain transaction request, register an account using the unique identity and the data management contract DSC;

[0027] The cross-chain transaction module is used to perform cross-chain transactions using the cross-chain historical contract HSC according to the type of cross-chain transaction request when the user completes account registration.

[0028] Preferably, the user registration module interacts with the regulator based on the first homomorphic public-private key pair (Spk, Ssk) and the second homomorphic public-private key pair (Upk, Usk) to perform identity registration and obtain a unique identity, including:

[0029] The user forms transaction parameters based on identity information and Upk in the application chain, encrypts them with Spk and sends cross-chain transactions to the relay chain;

[0030] The regulator uses Ssk to decrypt the transaction parameters and review the user's identity. When the review is successful, the regulator determines the user's unique identity based on the user name and random string, and uses Upk to encrypt the unique identity and send it back to the user's application chain;

[0031] The user uses Usk to decrypt the data packet under the application chain to obtain the unique identity.

[0032] Preferably, the types of cross-chain transaction requests include: cross-chain transfer transactions and cross-chain data transactions.

[0033] Preferably, the cross-chain transaction module uses the cross-chain historical contract HSC to perform cross-chain transactions according to the type of cross-chain transaction request, including:

[0034] When the cross-chain transaction request is a cross-chain transfer transaction, the data management contract DSC is used to verify the identity of U1 through the unique identity identifier U1id of the transaction initiator U1 and the public key U1pk in the corresponding second homomorphic public-private key pair; after successful verification, the value with U1 as the key is searched in the first set Tmap of the cross-chain history contract HSC, and a new transfer record is added to the back, and the status is changed to Pending. After the entire cross-chain transaction is completed, the status is changed to Finish. At the same time, in the cross-chain history contract DSC, U1pk is used to homomorphically reduce the balance, and the public key U2pk in the second homomorphic public-private key pair corresponding to the transaction recipient is used to homomorphically increase the transfer amount; wherein, the first set Tmap stores the transfer records of all accounts.

[0035] Preferably, the cross-chain transaction module uses the cross-chain historical contract HSC to perform cross-chain transactions according to the type of cross-chain transaction request, including:

[0036] When the cross-chain transaction request is a cross-chain data transaction, the data management contract DSC contract is used to determine whether U1 is the owner of D1 through the unique identity U1id of the transaction initiator U1 and the data name; after successful verification, the value with the data name D1 is found in the second set Dmap of the cross-chain history contract HSC, and a new shared record is added to the back, and the status is modified to Pending. After the entire cross-chain transaction is completed, the status is modified to Finish, and the unique identity U2id of the transaction recipient is added to the cross-chain history contract DSC as the authorized person; wherein, the operation records of all data are stored in the second set Dmap.

[0037] Preferably, the system further comprises:

[0038] The query module is used to enable the regulator to query the complete transaction records of users on a specific node through the cross-chain historical contract HSC; among them, the records in the cross-chain historical contract HSC are all stored in a chain structure.

[0039] The present invention provides a cross-chain data supervision method and system based on homomorphic encryption, including: a supervisor calls an identity management contract ISC of a relay chain to register the supervisor's identity, and generates a first homomorphic public-private key pair (Spk, Ssk) based on the identity management contract after successful registration; when a user needs to participate in a cross-chain activity, a second homomorphic public-private key pair (Upk, Usk) is generated in an off-chain manner, and based on the first homomorphic public-private key pair (Spk, Ssk) and the second homomorphic public-private key pair (Upk, Usk), the supervisor interacts with the supervisor to register the identity and obtain a unique identity; a cross-chain transaction request from the user is received, and according to the type of the cross-chain transaction request, the unique identity and the data management contract DSC are used to register the account; when the user completes the account registration, according to the type of the cross-chain transaction request, a cross-chain history contract HSC is used to perform a cross-chain transaction. The present invention uses homomorphic keys to manage the identities of regulators and users, and verifies user identities through a combination of user public keys and user IDs; uses homomorphic encryption technology to encrypt transaction plaintext, transmits ciphertext on the chain, and can perform ciphertext calculations; builds a cross-chain data interaction process through homomorphic encryption and smart contract technology, realizes safe and reliable cross-chain data supervision, and can provide full-cycle data traceability function under the premise of ensuring data privacy and operability. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] A more complete understanding of exemplary embodiments of the present invention may be obtained by referring to the following drawings:

[0041] Figure 1 It is a flowchart of a cross-chain data supervision method 100 based on homomorphic encryption according to an embodiment of the present invention;

[0042] Figure 2 is a structural diagram of an ISC according to an embodiment of the present invention;

[0043] Figure 3 is a structural diagram of a DSC according to an embodiment of the present invention;

[0044] Figure 4 is a structural diagram of an HSC according to an embodiment of the present invention;

[0045] Figure 5 A flow chart for registering a supervisor for a supervisor according to an embodiment of the present invention;

[0046] Figure 6 A flowchart of a registered user according to an embodiment of the present invention;

[0047] Figure 7 A flowchart of data or account registration according to an embodiment of the present invention;

[0048] Figure 8 A flow chart of a transfer process according to an embodiment of the present invention;

[0049] Fig. 9 A flowchart of data sharing processing according to an embodiment of the present invention;

[0050] Fig.10 It is a structural diagram of a cross-chain data supervision system 1000 based on homomorphic encryption according to an embodiment of the present invention. DETAILED DESCRIPTION

[0051] Now, exemplary embodiments of the present invention are described with reference to the accompanying drawings. However, the present invention can be implemented in many different forms and is not limited to the embodiments described herein. These embodiments are provided to disclose the present invention in detail and completely and to fully convey the scope of the present invention to those skilled in the art. The terms used in the exemplary embodiments shown in the accompanying drawings are not intended to limit the present invention. In the accompanying drawings, the same units / elements are marked with the same reference numerals.

[0052] Unless otherwise specified, the terms (including technical terms) used herein have the commonly understood meanings to those skilled in the art. In addition, it is understood that the terms defined in commonly used dictionaries should be understood to have the same meanings as those in the context of the relevant fields, and should not be understood as idealized or overly formal meanings.

[0053] Figure 1 1 is a flow chart of a cross-chain data supervision method 100 based on homomorphic encryption according to an embodiment of the present invention. Figure 1 As shown, the cross-chain data supervision method based on homomorphic encryption provided by the embodiment of the present invention uses homomorphic keys to manage the identities of the supervisor and the user, and verifies the user identity by means of a combination of the user public key and the user ID; uses homomorphic encryption technology to encrypt the transaction plaintext, and the ciphertext is transmitted on the chain and the ciphertext calculation can be performed; a set of cross-chain data interaction processes are constructed through homomorphic encryption and smart contract technology, which realizes safe and reliable cross-chain data supervision, and can provide data full-cycle traceability function under the premise of ensuring data privacy and operability. The cross-chain data supervision method 100 based on homomorphic encryption provided by the embodiment of the present invention starts from step 101. In step 101, the supervisor calls the identity management contract ISC of the relay chain to register the identity of the supervisor, and generates a first homomorphic public-private key pair (Spk, Ssk) based on the identity management contract after successful registration.

[0054] The present invention is based on the currently popular cross-chain architecture of "application chain-relay chain-application chain", and the blockchain system as the application chain and relay chain needs to support smart contracts and can integrate the homomorphic encryption paillier library.

[0055] In the present invention, three contracts are deployed on the relay chain, namely, the identity management contract (ISC), the data management contract (DSC) and the cross-chain history contract (HSC). The contract structure diagrams are as follows: Figure 2 , Figure 3 and Figure 4 As shown in the figure, ISC is responsible for managing the identities of users participating in the cross-chain, DSC is responsible for managing cross-chain data, and HSC is responsible for recording cross-chain data information; cross-chain data information includes: content, ownership, and cross-chain transactions involved.

[0056] In the present invention, the regulator needs to directly call the identity management contract (ISC) of the relay chain to register the regulator's identity. After successful registration, the contract generates a pair of homomorphic public and private keys (Spk, Ssk). The public key is stored in the contract and made public, and the private key is stored by the regulator off-chain. The registration process of the regulator is as follows: Figure 5 shown.

[0057] In step 102, when the user needs to participate in cross-chain activities, a second homomorphic public-private key pair (Upk, Usk) is generated off-chain, and based on the first homomorphic public-private key pair (Spk, Ssk) and the second homomorphic public-private key pair (Upk, Usk), the user interacts with the regulator to register the identity and obtain a unique identity.

[0058] Preferably, the step of interacting with a regulator based on the first homomorphic public-private key pair (Spk, Ssk) and the second homomorphic public-private key pair (Upk, Usk) to register an identity and obtain a unique identity includes:

[0059] The user forms transaction parameters based on identity information and Upk in the application chain, encrypts them with Spk and sends cross-chain transactions to the relay chain;

[0060] The regulator uses Ssk to decrypt the transaction parameters and review the user's identity. When the review is successful, the regulator determines the user's unique identity based on the user name and random string, and uses Upk to encrypt the unique identity and send it back to the user's application chain;

[0061] The user uses Usk to decrypt the data packet under the application chain to obtain the unique identity.

[0062] Combination Figure 6As shown, in the present invention, ordinary user U needs to register his identity first if he wants to participate in cross-chain activities. Specifically, the registration process includes: user U generates homomorphic public and private keys (Upk, Usk) in an off-chain manner, composes his own identity information and Upk into transaction parameters, encrypts with Spk and sends the cross-chain transaction to the relay chain, the regulator decrypts the transaction parameters through Ssk and verifies the user's identity, and after the review is successful, the U name and a string of random numbers are combined into a string as the unique identity (Uid) of U in the cross-chain system, recorded in ISC together with Upk, and the Uid is encrypted with Upk and sent back to the application chain where U is located. U uses Usk to decrypt the data packet off-chain to obtain Uid, and any subsequent operations need to send the decrypted Uid as part of the transaction content.

[0063] In step 103, a cross-chain transaction request from the user is received, and according to the type of the cross-chain transaction request, the unique identity identifier and the data management contract DSC are used to register an account.

[0064] Preferably, the types of cross-chain transaction requests include: cross-chain transfer transactions and cross-chain data transactions.

[0065] In step 104, when the user completes the account registration, the cross-chain transaction is performed using the cross-chain historical contract HSC according to the type of cross-chain transaction request.

[0066] Preferably, according to the type of cross-chain transaction request, the cross-chain historical contract HSC is used to perform the cross-chain transaction, including:

[0067] When the cross-chain transaction request is a cross-chain transfer transaction, the data management contract DSC is used to verify the identity of U1 through the unique identity identifier U1id of the transaction initiator U1 and the public key U1pk in the corresponding second homomorphic public-private key pair; after successful verification, the value with U1 as the key is searched in the first set Tmap of the cross-chain history contract HSC, and a new transfer record is added to the back, and the status is changed to Pending. After the entire cross-chain transaction is completed, the status is changed to Finish. At the same time, in the cross-chain history contract DSC, U1pk is used to homomorphically reduce the balance, and the public key U2pk in the second homomorphic public-private key pair corresponding to the transaction recipient is used to homomorphically increase the transfer amount; wherein, the first set Tmap stores the transfer records of all accounts.

[0068] Preferably, according to the type of cross-chain transaction request, the cross-chain historical contract HSC is used to perform the cross-chain transaction, including:

[0069] When the cross-chain transaction request is a cross-chain data transaction, the data management contract DSC contract is used to determine whether U1 is the owner of D1 through the unique identity U1id of the transaction initiator U1 and the data name; after successful verification, the value with the data name D1 is found in the second set Dmap of the cross-chain history contract HSC, and a new shared record is added to the back, and the status is modified to Pending. After the entire cross-chain transaction is completed, the status is modified to Finish, and the unique identity U2id of the transaction recipient is added to the cross-chain history contract DSC as the authorized person; wherein, the operation records of all data are stored in the second set Dmap.

[0070] In the present invention, the DSC contract divides cross-chain transactions into two types, namely cross-chain transfer and cross-chain data sharing. Before initiating a transfer transaction, the user needs to register an account, including the account name, and the initial balance (encrypted using Upk); before initiating a cross-chain data sharing transaction, the user needs to register data information (including data name, data information and data owner Uid). The account and data registration process is as follows: Figure 7 shown.

[0071] The HSC contract maintains two collections, one collection stores the transfer records of all accounts (Tmap), and the other collection stores the operation records of all data (Dmap).

[0072] Specifically, combined Figure 8 As shown, the process of conducting a cross-chain transfer transaction includes: when U1 on chain A initiates a cross-chain transfer transaction to U2 on chain B, the DSC contract verifies the identity of U1 through U1id and U1pk. After successful verification, it searches for the value with U1 as the key in the Tmap of HSC, adds a new transfer record (transfer recipient, transfer amount and transaction id of the transfer transaction in chain A), and changes the status to Pending. After the entire cross-chain transaction is completed, the status is changed to Finish. At the same time, in DSC, U1pk is used to homomorphically reduce the balance, and U2pk is used to homomorphically increase the transfer amount.

[0073] Specifically, combined Fig. 9 As shown, the process of cross-chain data transaction includes: when A chain U1 initiates a cross-chain data D1 sharing transaction to B chain U2, the DSC contract determines whether U1 is the owner of D1 through U1id and data name. After successful verification, it searches for the value with data name D1 in HSC's Dmap, adds a new sharing record (sharing recipient, the transaction id of the transfer transaction in A chain) at the end, and changes the status to Pending. After waiting for the entire cross-chain transaction to be completed, it changes the status to Finish. At the same time, in DSC, U2id is added as the authorized person.

[0074] Preferably, the method further comprises:

[0075] The regulator queries the complete transaction records of users on a specific node through the cross-chain historical contract HSC; among them, the records in the cross-chain historical contract HSC are all stored in a chain structure.

[0076] In the present invention, the records in HSC are stored in a chain structure. The regulator can query a specific node through HSC to query the user's complete historical transfer records and the shared records of certain data. When an abnormal situation occurs, the transaction status can be queried on the application chain based on the transaction ID corresponding to the record.

[0077] The cross-chain data supervision method provided by the present invention has the following advantages:

[0078] 1. In cross-chain transaction interaction activities, except for applying for user registration and reviewing user registration, which require manual operations, the rest of the processes are automatically triggered and executed by the contract. The core cross-chain business is recorded on the chain to ensure that it cannot be tampered with and can be reviewed and traced.

[0079] 2. Manage user identity through homomorphic encryption technology, and jointly authenticate user identity through homomorphic public key and user ID generated by the regulator based on the public key.

[0080] 3. Encrypt sensitive data through homomorphic encryption, perform ciphertext data processing in the relay chain (such as ciphertext addition and subtraction of transfer amounts), and ensure the privacy of sensitive data during cross-chain circulation.

[0081] Fig.10 Schematic diagram of the structure of a cross-chain data supervision system 1000 based on homomorphic encryption according to an embodiment of the present invention. Fig.10 As shown, the cross-chain data supervision system 1000 based on homomorphic encryption provided by an embodiment of the present invention includes: a supervisor identity registration module 1001, a user registration module 1002, an account registration module 1003 and a cross-chain transaction module 1004.

[0082] Preferably, the regulator identity registration module 1001 is used to enable the regulator to call the identity management contract ISC of the relay chain to register the regulator's identity, and generate a first homomorphic public-private key pair (Spk, Ssk) based on the identity management contract after successful registration.

[0083] Preferably, the user registration module 1002 is used to generate a second homomorphic public-private key pair (Upk, Usk) through an off-chain method when the user needs to participate in cross-chain activities, and interact with the regulator based on the first homomorphic public-private key pair (Spk, Ssk) and the second homomorphic public-private key pair (Upk, Usk) to perform identity registration and obtain a unique identity.

[0084] Preferably, the user registration module 1002 interacts with the regulator based on the first homomorphic public-private key pair (Spk, Ssk) and the second homomorphic public-private key pair (Upk, Usk) to perform identity registration and obtain a unique identity, including:

[0085] The user forms transaction parameters based on identity information and Upk in the application chain, encrypts them with Spk and sends cross-chain transactions to the relay chain;

[0086] The regulator uses Ssk to decrypt the transaction parameters and review the user's identity. When the review is successful, the regulator determines the user's unique identity based on the user name and random string, and uses Upk to encrypt the unique identity and send it back to the user's application chain;

[0087] The user uses Usk to decrypt the data packet under the application chain to obtain the unique identity.

[0088] Preferably, the account registration module 1003 is used to receive a cross-chain transaction request from a user, and perform account registration using the unique identity identifier and data management contract DSC according to the type of the cross-chain transaction request.

[0089] Preferably, the types of cross-chain transaction requests include: cross-chain transfer transactions and cross-chain data transactions.

[0090] Preferably, the cross-chain transaction module 1004 is used to perform cross-chain transactions using the cross-chain historical contract HSC according to the type of cross-chain transaction request when the user completes account registration.

[0091] Preferably, the cross-chain transaction module 1004 performs cross-chain transactions using the cross-chain historical contract HSC according to the type of the cross-chain transaction request, including:

[0092] When the cross-chain transaction request is a cross-chain transfer transaction, the data management contract DSC is used to verify the identity of U1 through the unique identity identifier U1id of the transaction initiator U1 and the public key U1pk in the corresponding second homomorphic public-private key pair; after successful verification, the value with U1 as the key is searched in the first set Tmap of the cross-chain history contract HSC, and a new transfer record is added to the back, and the status is changed to Pending. After the entire cross-chain transaction is completed, the status is changed to Finish. At the same time, in the cross-chain history contract DSC, U1pk is used to homomorphically reduce the balance, and the public key U2pk in the second homomorphic public-private key pair corresponding to the transaction recipient is used to homomorphically increase the transfer amount; wherein, the first set Tmap stores the transfer records of all accounts.

[0093] Preferably, the cross-chain transaction module 1004 performs cross-chain transactions using the cross-chain historical contract HSC according to the type of the cross-chain transaction request, including:

[0094] When the cross-chain transaction request is a cross-chain data transaction, the data management contract DSC contract is used to determine whether U1 is the owner of D1 through the unique identity U1id of the transaction initiator U1 and the data name; after successful verification, the value with the data name D1 is found in the second set Dmap of the cross-chain history contract HSC, and a new shared record is added to the back, and the status is modified to Pending. After the entire cross-chain transaction is completed, the status is modified to Finish, and the unique identity U2id of the transaction recipient is added to the cross-chain history contract DSC as the authorized person; wherein, the operation records of all data are stored in the second set Dmap.

[0095] Preferably, the system further comprises:

[0096] The query module is used to enable the regulator to query the complete transaction records of users on a specific node through the cross-chain historical contract HSC; among them, the records in the cross-chain historical contract HSC are all stored in a chain structure.

[0097] The cross-chain data supervision system 1000 based on homomorphic encryption of an embodiment of the present invention corresponds to the cross-chain data supervision method 100 based on homomorphic encryption of another embodiment of the present invention, which will not be repeated here.

[0098] The invention has been described above with reference to a few embodiments. However, it is readily apparent to a person skilled in the art that other embodiments than the ones disclosed above are equally within the scope of the invention, as defined by the appended patent claims.

[0099] Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise therein. All references to "a / said / the [means, components, etc.]" are to be openly interpreted as at least one instance of said means, components, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not necessarily have to be performed in the exact order disclosed, unless explicitly stated otherwise.

[0100] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0101] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0102] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0103] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0104] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the relevant field should understand that the specific implementation methods of the present invention can still be modified or replaced by equivalents. Any modification or equivalent replacement that does not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A cross-chain data supervision method based on homomorphic encryption, characterized in that: The method comprises: The regulator calls the identity management contract ISC of the relay chain to register the regulator's identity, and after successful registration, generates the first homomorphic public-private key pair (Spk, Ssk) based on the identity management contract; When a user needs to participate in cross-chain activities, a second homomorphic public-private key pair (Upk, Usk) is generated off-chain, and based on the first homomorphic public-private key pair (Spk, Ssk) and the second homomorphic public-private key pair (Upk, Usk), the user interacts with the regulator to register his / her identity and obtain a unique identity. Receive the user's cross-chain transaction request, and register the account using the unique identity and data management contract DSC according to the type of the cross-chain transaction request; When the user completes the account registration, the cross-chain transaction is performed using the cross-chain historical contract HSC according to the type of cross-chain transaction request.

2. The method according to claim 1, characterized in that The interacting with the regulator based on the first homomorphic public-private key pair (Spk, Ssk) and the second homomorphic public-private key pair (Upk, Usk) to register an identity and obtain a unique identity includes: The user forms transaction parameters based on identity information and Upk in the application chain, encrypts them with Spk and sends cross-chain transactions to the relay chain; The regulator uses Ssk to decrypt the transaction parameters and review the user's identity. When the review is successful, the regulator determines the user's unique identity based on the user name and random string, and uses Upk to encrypt the unique identity and send it back to the user's application chain; The user uses Usk to decrypt the data packet under the application chain to obtain the unique identity.

3. The method according to claim 1, characterized in that The types of cross-chain transaction requests include: cross-chain transfer transactions and cross-chain data transactions.

4. The method according to claim 1, characterized in that: According to the type of cross-chain transaction request, the cross-chain historical contract HSC is used to perform cross-chain transactions, including: When the cross-chain transaction request is a cross-chain transfer transaction, the data management contract DSC is used to verify the identity of U1 through the unique identity identifier U1 id of the transaction initiator U1 and the public key U1 pk in the corresponding second homomorphic public-private key pair; after successful verification, the value with U1 as the key is searched in the first set Tmap of the cross-chain history contract HSC, and a new transfer record is added to the back, and the status is changed to Pending. After the entire cross-chain transaction is completed, the status is changed to Finish. At the same time, in the cross-chain history contract DSC, U1 pk is used to homomorphically reduce the balance, and the public key U2pk in the second homomorphic public-private key pair corresponding to the transaction recipient is used to homomorphically increase the transfer amount; wherein, the first set Tmap stores the transfer records of all accounts.

5. The method according to claim 1, characterized in that: According to the type of cross-chain transaction request, the cross-chain historical contract HSC is used to perform cross-chain transactions, including: When the cross-chain transaction request is a cross-chain data transaction, the data management contract DSC contract is used to determine whether U1 is the owner of D1 through the unique identity identifier U1 id and data name of the transaction initiator U1; after successful verification, the value with the data name D1 is found in the second set Dmap of the cross-chain history contract HSC, and a new shared record is added behind it, and the status is modified to Pending. After the entire cross-chain transaction is completed, the status is modified to Finish, and the unique identity identifier U2 id of the transaction recipient is added to the cross-chain history contract DSC as the authorized person; wherein, the operation records of all data are stored in the second set Dmap.

6. The method according to claim 1, characterized in that The method further comprises: The regulator queries the complete transaction records of users on a specific node through the cross-chain historical contract HSC; among them, the records in the cross-chain historical contract HSC are all stored in a chain structure.

7. A cross-chain data supervision system based on homomorphic encryption, characterized in that: The system comprises: The supervisor identity registration module is used to enable the supervisor to call the identity management contract ISC of the relay chain to register the supervisor identity, and generate the first homomorphic public-private key pair (Spk, Ssk) based on the identity management contract after successful registration; A user registration module is used to generate a second homomorphic public-private key pair (Upk, Usk) off-chain when a user needs to participate in a cross-chain activity, and interact with the regulator based on the first homomorphic public-private key pair (Spk, Ssk) and the second homomorphic public-private key pair (Upk, Usk) to register the identity and obtain a unique identity; An account registration module is used to receive a user's cross-chain transaction request and, according to the type of the cross-chain transaction request, register an account using the unique identity and the data management contract DSC; The cross-chain transaction module is used to perform cross-chain transactions using the cross-chain historical contract HSC according to the type of cross-chain transaction request when the user completes account registration.

8. The system according to claim 7, characterized in that The user registration module interacts with the regulator based on the first homomorphic public-private key pair (Spk, Ssk) and the second homomorphic public-private key pair (Upk, Usk) to perform identity registration and obtain a unique identity, including: The user forms transaction parameters based on identity information and Upk in the application chain, encrypts them with Spk and sends cross-chain transactions to the relay chain; The regulator uses Ssk to decrypt the transaction parameters and review the user's identity. When the review is successful, the regulator determines the user's unique identity based on the user name and random string, and uses Upk to encrypt the unique identity and send it back to the user's application chain; The user uses Usk to decrypt the data packet under the application chain to obtain the unique identity.

9. The system according to claim 7, characterized in that The types of cross-chain transaction requests include: cross-chain transfer transactions and cross-chain data transactions.

10. The system according to claim 7, characterized in that The cross-chain transaction module uses the cross-chain historical contract HSC to perform cross-chain transactions according to the type of cross-chain transaction request, including: When the cross-chain transaction request is a cross-chain transfer transaction, the data management contract DSC is used to verify the identity of U1 through the unique identity identifier U1 id of the transaction initiator U1 and the public key U1 pk in the corresponding second homomorphic public-private key pair; after successful verification, the value with U1 as the key is searched in the first set Tmap of the cross-chain history contract HSC, and a new transfer record is added to the back, and the status is changed to Pending. After the entire cross-chain transaction is completed, the status is changed to Finish. At the same time, in the cross-chain history contract DSC, U1 pk is used to homomorphically reduce the balance, and the public key U2pk in the second homomorphic public-private key pair corresponding to the transaction recipient is used to homomorphically increase the transfer amount; wherein, the first set Tmap stores the transfer records of all accounts.

11. The system according to claim 7, characterized in that The cross-chain transaction module uses the cross-chain historical contract HSC to perform cross-chain transactions according to the type of cross-chain transaction request, including: When the cross-chain transaction request is a cross-chain data transaction, the data management contract DSC contract is used to determine whether U1 is the owner of D1 through the unique identity identifier U1 id and data name of the transaction initiator U1; after successful verification, the value with the data name D1 is found in the second set Dmap of the cross-chain history contract HSC, and a new shared record is added behind it, and the status is modified to Pending. After the entire cross-chain transaction is completed, the status is modified to Finish, and the unique identity identifier U2 id of the transaction recipient is added to the cross-chain history contract DSC as the authorized person; wherein, the operation records of all data are stored in the second set Dmap.

12. The system according to claim 7, characterized in that The system further comprises: The query module is used to enable the regulator to query the complete transaction records of users on a specific node through the cross-chain historical contract HSC; among them, the records in the cross-chain historical contract HSC are all stored in a chain structure.

Images