Digital asset issuing monitoring method and device, storage medium and program product

Abstract

The embodiment of the invention provides a digital asset issuing monitoring method and device, a storage medium and a program product, and relates to the technical field of block chains. The method comprises the following steps: in response to a compliance information verification request sent by a block chain, generating and sending a compliance information acquisition request to at least one issuer terminal; wherein the compliance information verification request is generated and sent by the block chain based on a pre-deployed monitoring smart contract in response to a monitoring request sent by a monitoring terminal; receiving a zero-knowledge proof fed back by the issuer terminal, and determining a compliance information verification result corresponding to the issuer terminal according to the zero-knowledge proof and a pre-generated oracle private key; and sending the compliance information verification result to the block chain, so that the block chain sends the compliance information verification result to the monitoring terminal based on the pre-deployed monitoring smart contract. According to the method provided by the invention, the compliance of digital asset issuing is improved.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and in particular to a method, device, storage medium and program product for monitoring the issuance of digital assets. Background Art

[0002] Digital assets refer to non-monetary assets in the form of electronic data owned or controlled by an enterprise or individual and held for sale or in the production process in daily activities.

[0003] In the prior art, in the process of issuing digital assets, in order to unload the pressure on the blockchain and improve transaction performance, the issuance method of off-chain issuance and on-chain trusted verification is often adopted. However, the above issuance method will cause the problem of private over-issuance of digital assets.

[0004] Therefore, there is an urgent need for a digital asset issuance monitoring system to solve the problem of private over-issuance of digital assets, thereby improving the compliance of digital asset issuance. Summary of the invention

[0005] The present application provides a method, device, storage medium and program product for monitoring the issuance of digital assets, so as to solve the technical problem of poor compliance of the issuance of digital assets.

[0006] In a first aspect, the present application provides a method for monitoring the issuance of digital assets, comprising:

[0007] In response to a compliance information verification request sent by the blockchain, generate and send a compliance information acquisition request to at least one issuer terminal; wherein the compliance information verification request is generated and sent by the blockchain in response to a monitoring request sent by a monitoring terminal based on a pre-deployed monitoring smart contract; the compliance information acquisition request includes a pre-generated oracle public key;

[0008] Receive the zero-knowledge proof fed back by the issuer terminal, and determine the compliance information verification result corresponding to the issuer terminal according to the zero-knowledge proof and the pre-generated oracle private key; wherein the zero-knowledge proof is the proof information generated by the issuer terminal according to the oracle public key and compliance information in response to the compliance information acquisition request;

[0009] The compliance information verification result is sent to the blockchain, so that the blockchain sends the compliance information verification result to the monitoring terminal based on the pre-deployed monitoring smart contract.

[0010] In a second aspect, the present application provides a digital asset issuance monitoring device, comprising:

[0011] A generation module, configured to generate and send a compliance information acquisition request to at least one issuer terminal in response to a compliance information verification request sent by a blockchain; wherein the compliance information verification request is generated and sent by the blockchain in response to a monitoring request sent by a monitoring terminal based on a pre-deployed monitoring smart contract; and the compliance information acquisition request includes a pre-generated oracle public key;

[0012] A determination module, configured to receive the zero-knowledge proof fed back by the issuer terminal, and determine the compliance information verification result corresponding to the issuer terminal according to the zero-knowledge proof and the pre-generated oracle private key; wherein the zero-knowledge proof is the proof information generated by the issuer terminal according to the oracle public key and the compliance information in response to the compliance information acquisition request;

[0013] A processing module is used to send the compliance information verification result to the blockchain, so that the blockchain sends the compliance information verification result to the monitoring terminal based on the pre-deployed monitoring smart contract.

[0014] An embodiment of the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0015] The memory stores computer-executable instructions;

[0016] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementations of the first aspect.

[0017] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect above and / or various possible implementations of the first aspect.

[0018] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementation methods of the first aspect.

[0019] The issuance monitoring method of digital assets provided in the present application generates and sends a compliance information acquisition request to at least one issuer terminal in response to a compliance information verification request sent by a blockchain, receives a zero-knowledge proof fed back by the issuer terminal, and determines the compliance information verification result corresponding to the issuer terminal according to the zero-knowledge proof and the pre-generated oracle private key, and sends the compliance information verification result to the blockchain, so that the blockchain sends the compliance information verification result to the monitoring terminal based on the pre-deployed monitoring smart contract, wherein the issuance monitoring method of digital assets provided in the present application verifies the compliance information of the issuer terminal based on the zero-knowledge proof, and can efficiently and securely monitor the issuance of digital assets of the issuer terminal, thereby improving the compliance of the issuance of digital assets, wherein, in the process of obtaining the zero-knowledge proof and the feedback process of the contract information verification result, the reliability of the process implementation is improved based on the pre-deployed smart contract in the blockchain, thereby improving the compliance of the issuance of digital assets. In summary, the issuance monitoring method of digital assets provided in the embodiment of the present application improves the compliance of the issuance of digital assets. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0021] Figure 1 A schematic diagram of the scenario for monitoring the issuance of digital assets provided for this application;

[0022] Figure 2 Schematic diagram of the process of monitoring the issuance of digital assets provided for this application Figure 1 ;

[0023] Figure 3 Schematic diagram of the process of monitoring the issuance of digital assets provided for this application Figure 2 ;

[0024] Figure 4 The signaling flow chart provided for this application;

[0025] Figure 5 A schematic diagram of the structure of the digital asset issuance monitoring device provided in this application;

[0026] Figure 6 A schematic diagram of the structure of the electronic device provided in this application.

[0027] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0028] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0029] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant countries and regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0030] It should be noted that the digital asset issuance monitoring method, device, storage medium and program product provided in this application can be used in the field of blockchain technology, and can also be used in any field outside the field of blockchain technology. The application field of the digital asset issuance monitoring method, device, storage medium and program product in this application is not limited.

[0031] Figure 1 A schematic diagram of the scenario for monitoring the issuance of digital assets provided in this application. Figure 1 As shown, the specific application scenario of the present application includes a monitoring terminal 101, a blockchain 102, an oracle 103, and at least one issuer terminal 104. The blockchain 102 is connected to the monitoring terminal 101 and the oracle 103 respectively, and the oracle 103 is also connected to each of the at least one issuer terminal 104 respectively.

[0032] Among them, the oracle 103 is used to implement the digital asset issuance monitoring method provided in this application, which will not be repeated here.

[0033] The monitoring terminal 101 is a terminal for monitoring the issuance of digital assets for each of the at least one issuer terminal 104 based on the blockchain 102 and the oracle 103. The blockchain 102 is used to enable the monitoring terminal 101 and the oracle 103 to implement the issuance monitoring process of digital assets based on the smart contract deployed thereon. The issuer terminal 104 is a terminal for issuing digital assets.

[0034] The digital asset issuance monitoring method, device, storage medium and program product provided in this application are intended to solve the above technical problems of the prior art.

[0035] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0036] Figure 2 Schematic diagram of the process of monitoring the issuance of digital assets provided in this application Figure 1 , the execution subject is the oracle, such as Figure 2 As shown, the method includes:

[0037] Step S201: In response to a compliance information verification request sent by the blockchain, generate and send a compliance information acquisition request to at least one issuer terminal.

[0038] Specifically, in response to a compliance information verification request sent by the blockchain, a compliance information acquisition request can be generated and sent to each of the at least one issuer terminal.

[0039] Among them, the compliance information verification request is generated and sent by the blockchain in response to the monitoring request sent by the monitoring terminal, based on the pre-deployed monitoring smart contract.

[0040] Among them, the monitoring request is a request generated by the monitoring terminal and sent to the blockchain to monitor the compliance of the issuance of digital assets by at least one target issuer terminal. Among them, the target issuer terminal is the issuer terminal to be monitored, and the present application does not limit the number of target issuer terminals corresponding to the monitoring request. Optionally, the number of target issuer terminals corresponding to the monitoring request is less than or equal to the number of issuer terminals that undergo feasibility verification in the above-mentioned blockchain. For example, if the number of target issuer terminals corresponding to the monitoring request is equal to the number of issuer terminals that undergo feasibility verification in the above-mentioned blockchain, the monitoring terminal monitors the compliance of the issuance of digital assets by all issuer terminals corresponding to the blockchain. For example, if the number of target issuer terminals corresponding to the monitoring request is less than the number of issuer terminals that undergo feasibility verification in the above-mentioned blockchain, the monitoring terminal monitors the compliance of the issuance of digital assets by some of the issuer terminals corresponding to the blockchain.

[0041] Optionally, a monitoring request can be generated and sent to the blockchain for the monitoring terminal at a preset time period or a preset sending policy, so as to monitor the compliance of digital asset issuance by the issuer terminal corresponding to the blockchain at a preset time period or a preset monitoring policy.

[0042] Among them, the monitoring request includes information of each target issuer terminal in at least one target issuer terminal. Among them, this application does not limit the information of the target issuer terminal, and optionally, it may include but is not limited to: at least one of the information such as the name of the issuer's organization, the ID information of the issuer terminal, etc.

[0043] The compliance information verification request is generated and sent to the oracle by the blockchain in response to the monitoring request sent by the monitoring terminal, based on the pre-deployed monitoring smart contract and the information of each target issuer terminal included in the monitoring request, and is used to request the oracle to verify the compliance information of each target issuer terminal. Optionally, the compliance information verification request includes the information of each target issuer terminal in at least one target issuer terminal.

[0044] Among them, this application does not limit the process of generating a compliance information acquisition request in response to a compliance information verification request sent by the blockchain. Optionally, in response to the compliance information verification request sent by the blockchain, a compliance information acquisition request can be generated based on the information of each target issuer terminal in at least one target issuer terminal included in the compliance information verification request. Among them, the number of generated compliance information acquisition requests corresponds to the number of target issuer terminals, so that each target issuer terminal can receive the compliance information acquisition request.

[0045] Among them, at least one issuing terminal to which the compliance information acquisition request is sent is the target issuer terminal described above.

[0046] The compliance information acquisition request includes a pre-generated oracle public key. Specifically, the pre-generated oracle public key is a key pre-generated by the oracle for obtaining information fed back by the issuer terminal.

[0047] Step S202: Receive the zero-knowledge proof fed back by the issuer terminal, and determine the compliance information verification result corresponding to the issuer terminal based on the zero-knowledge proof and the pre-generated oracle private key.

[0048] Specifically, after generating and sending a compliance information acquisition request to at least one issuer terminal in response to a compliance information verification request sent by the blockchain, a zero-knowledge proof fed back by the issuer terminal can be received.

[0049] Among them, zero-knowledge proof is the proof information generated by the issuer terminal in response to the compliance information acquisition request based on the oracle public key and compliance information. Specifically, zero-knowledge proof is a cryptographic tool that allows two untrusted communicating parties to prove the validity of a proposition without leaking any additional information. Among them, compliance information is information stored in the issuer terminal for proving the compliance of the issuance of digital assets. Optionally, it can be information stored in the issuer terminal for proving the compliance of the issuance quantity of the issued digital assets. Among them, this application does not limit the process of generating proof information based on the oracle public key and compliance information in response to the compliance information acquisition request by the issuer terminal. Any process that can generate the zero-knowledge proof described above based on the oracle public key and compliance information in response to the compliance information acquisition request can be used as the process of generating proof information based on the oracle public key and compliance information in response to the compliance information acquisition request provided by this application.

[0050] Specifically, after receiving the zero-knowledge proof fed back by the issuer terminal, the compliance information verification result corresponding to the issuer terminal can be determined based on the zero-knowledge proof and the pre-generated oracle private key.

[0051] The pre-generated oracle private key corresponds to the pre-generated oracle private key described in step S101, and is used to decrypt the zero-knowledge proof generated according to the oracle public key. The compliance information verification result is the result obtained after verifying the compliance information corresponding to the issuer terminal.

[0052] Among them, this application does not limit the process of determining the compliance information verification result corresponding to the issuer terminal based on the zero-knowledge proof and the pre-generated oracle private key. Optionally, the zero-knowledge proof can be first decrypted according to the pre-generated oracle private key to obtain the decrypted zero-knowledge proof, and then the compliance information verification result corresponding to the issuer terminal can be determined based on the decrypted zero-knowledge proof.

[0053] Step S203: Send the compliance information verification result to the blockchain, so that the blockchain sends the compliance information verification result to the monitoring terminal based on the pre-deployed monitoring smart contract.

[0054] Specifically, after determining the compliance information verification result corresponding to the issuer terminal based on the zero-knowledge proof and the pre-generated oracle private key, the compliance information verification result can be sent to the blockchain, so that the blockchain sends the compliance information verification result to the monitoring terminal based on the pre-deployed monitoring smart contract, thereby enabling the monitoring terminal to monitor the compliance of the digital asset issuance of each issuer terminal based on the received compliance information verification result.

[0055] Among them, this application does not limit the process of sending the compliance information verification result to the blockchain so that the blockchain sends the compliance information verification result to the monitoring terminal based on the pre-deployed monitoring smart contract. Optionally, the compliance information verification result can be signed according to the pre-generated oracle private key, and then the signed compliance information verification result is sent to the blockchain, so that the blockchain, based on the pre-deployed oracle contract, performs signature verification processing on the signed compliance information verification result, and sends the compliance information verification result passed through the signature verification processing to the monitoring terminal based on the pre-deployed monitoring smart contract.

[0056] The digital asset issuance monitoring method provided in this embodiment generates and sends a compliance information acquisition request to at least one issuer terminal in response to a compliance information verification request sent by the blockchain, receives the zero-knowledge proof fed back by the issuer terminal, and determines the compliance information verification result corresponding to the issuer terminal according to the zero-knowledge proof and the pre-generated oracle private key, and sends the compliance information verification result to the blockchain so that the blockchain sends the compliance information verification result to the monitoring terminal based on the pre-deployed monitoring smart contract. Among them, the digital asset issuance monitoring method provided in this application verifies the compliance information of the issuer terminal based on the zero-knowledge proof, and can efficiently and securely monitor the issuance of digital assets by the issuer terminal, thereby improving the compliance of the digital asset issuance. Among them, in the process of obtaining the zero-knowledge proof and the process of feeding back the contract information verification result, it is realized based on the pre-deployed smart contract in the blockchain, which improves the reliability of the process implementation, thereby improving the compliance of the digital asset issuance. Based on the above description, the digital asset issuance monitoring method provided in the embodiment of this application improves the compliance of the digital asset issuance.

[0057] In a possible embodiment, if the compliance information includes: the issued quantity x and the issuance quantity threshold X, then the process in which the issuer terminal described in step S202 generates a zero-knowledge proof according to the oracle public key and the compliance information in response to the compliance information acquisition request may include:

[0058] First, obtain an integer a1, an integer a2, an integer b1, and an integer b2, where the obtained integers satisfy the following relational expressions with the issued quantity x and the issuance quantity threshold X: x = a1 / b1, X = a2 / b2.

[0059] Second, obtain a random number r1 and a random number r2, where the obtained random numbers meet the following requirements: 0 < r1 < n and r1 and n are relatively prime, 0 < r2 < n and r2 and n are relatively prime, where n is one of the constants in the pre-generated oracle public key PK(n, g).

[0060] Then, according to the obtained random number, process parameter 1 E(a1) and process parameter 2 E(n-b1) are calculated, where E(a1)=g a1 r1 n mod n 2 、E(n-b1)=g （n-b1） r2 n mod n 2 , where g is another constant in the pre-generated oracle public key PK(n,g).

[0061] Finally, based on the homomorphic scalar multiplication algorithm and the homomorphic addition algorithm, the calculated process parameters are calculated to obtain the zero-knowledge proof E, where E=E(a1)*b2*E(n-b1)*a2=(g a1b2 r1 n mod n 2 )*(g (n-b1)a2 r2 n modn 2 )=g （a1b2-b1a2+na2） (r1r2) n mod n 2 .

[0062] The issued quantity x is the number of digital assets issued by the issuing institution corresponding to the issuing terminal. The issued quantity threshold X is the maximum value of the number of digital assets allowed to be issued by the issuing institution corresponding to the issuing terminal.

[0063] Figure 3 Schematic diagram of the process of monitoring the issuance of digital assets provided for this application Figure 2 ,like Figure 3 As shown, in this embodiment Figure 2 Based on the embodiment, a process of determining the compliance information verification result corresponding to the issuer terminal according to the zero-knowledge proof and the pre-generated oracle private key is described in detail. The method includes:

[0064] Step S301: Decrypt the zero-knowledge proof according to the pre-generated oracle private key to obtain the decrypted zero-knowledge proof.

[0065] Specifically, according to the pre-generated oracle private key, the zero-knowledge proof can be decrypted to obtain the decrypted zero-knowledge proof. For the description of the pre-generated oracle private key and the zero-knowledge proof, please refer to the description in step S202, which will not be repeated here.

[0066] Optionally, if the generation process of the zero-knowledge proof is as described in the above embodiment, for example, the zero-knowledge proof E=E(a1)*b2*E(n-b1)*a2=(ga1b2 r1 n mod n 2 )*(g (n-b1)a2 r2 n mod n 2 )=g （a1b2-b1a2+na2） (r1r2) n modn 2 , then the zero-knowledge proof is decrypted according to the pre-generated oracle private key, and the decrypted zero-knowledge proof D can be the decrypted zero-knowledge proof D=D(E)=(a1b2-b1a2+na2)mod n=(a1b2-b1a2)mod n.

[0067] Step S302: Determine the compliance information verification result corresponding to the issuer terminal based on the zero-knowledge proof after decryption.

[0068] Specifically, according to the zero-knowledge proof obtained after decryption in step S301, the compliance information verification result corresponding to the issuer terminal can be determined, wherein the compliance information verification result is verification passed or verification failed.

[0069] Among them, this application does not limit the process of determining the compliance information verification result corresponding to the issuer terminal based on the zero-knowledge proof after decryption processing. Optionally, the process of determining the compliance information verification result corresponding to the issuer terminal based on the zero-knowledge proof after decryption processing may include: first determining the size relationship between the issued quantity and the issuance quantity threshold based on the zero-knowledge proof after decryption processing. Among them, if it is determined that the issued quantity is less than the issuance quantity threshold, then the compliance information verification result is determined to be verification passed. Otherwise, the compliance information verification result is determined to be verification failed.

[0070] The compliance information includes: the issued quantity and the issued quantity threshold. The description of the issued quantity and the issued quantity threshold can refer to the description in the above embodiment, which will not be repeated here.

[0071] Specifically, if the zero-knowledge proof after decryption processing is as described in step S301, that is, the zero-knowledge proof after decryption processing D = D(E) = (a1b2 - b1a2 + na2) mod n = (a1b2 - b1a2) mod n. Since the issued quantity x - the issuance quantity threshold X = (a1b2 - a2b1) / b1b2, (b1b2 > 0), therefore, if the zero-knowledge proof after decryption processing D > 0, then a1b2 - a2b1 > 0, so the size relationship between the issued quantity and the issuance quantity threshold can be obtained as x > X; if the zero-knowledge proof after decryption processing D = 0, then a1b2 - a2b1 = 0, so the size relationship between the issued quantity and the issuance quantity threshold can be obtained as x = X; if the zero-knowledge proof after decryption processing D < 0, then a1b2 - a2b1 < 0, so the size relationship between the issued quantity and the issuance quantity threshold can be obtained as x < X.

[0072] Specifically, after obtaining the size relationship between the issued quantity and the issuance quantity threshold, if it is determined that the issued quantity is less than the issuance quantity threshold x < X, that is, the zero-knowledge proof after decryption processing D < 0, then the compliance information verification result is determined to be verified passed. If it is determined that the issued quantity is greater than or equal to the issuance quantity threshold x > X, or x = X, that is, the zero-knowledge proof after decryption processing D <= 0, then the compliance information verification result is determined to be verified failed.

[0073] Among them, in the process of determining the compliance information verification result corresponding to the issuer terminal according to the zero-knowledge proof after decryption processing, the size relationship between the issued quantity and the issuance quantity threshold is determined according to the zero-knowledge proof after decryption processing, and the actual issued quantity and the issuance quantity threshold of the issuer terminal are not actually obtained, so the security in the issuance monitoring of digital assets is ensured, thereby improving the compliance of the issuance of digital assets.

[0074] In the process of determining the compliance information verification result corresponding to the issuer terminal provided by the embodiment of the present application according to the zero-knowledge proof and the pre-generated oracle private key, the zero-knowledge proof is decrypted according to the pre-generated oracle private key to obtain the zero-knowledge proof after decryption processing, and the compliance information verification result corresponding to the issuer terminal is determined according to the zero-knowledge proof after decryption processing. Among them, in the process of determining the compliance information verification result corresponding to the issuer terminal, the obtained zero-knowledge proof is encrypted for transmission, so the accuracy of the issuance monitoring of digital assets is ensured, and in the process of determining the compliance information verification result corresponding to the issuer terminal, it is determined according to the zero-knowledge proof after decryption processing, and the compliance information of the issuer terminal is not actually obtained, so the security in the issuance monitoring of digital assets is ensured, thereby improving the compliance of the issuance of digital assets.

[0075] In a possible embodiment, the process of sending the compliance information verification result to the blockchain so that the blockchain sends the compliance information verification result to the monitoring terminal based on the pre-deployed monitoring smart contract may include: first, signing the compliance information verification result according to the pre-generated oracle private key. Then, the signed compliance information verification result is sent to the blockchain so that the blockchain performs signature verification on the signed compliance information verification result based on the pre-deployed oracle contract, and sends the compliance information verification result that passes the signature verification to the monitoring terminal based on the pre-deployed monitoring smart contract.

[0076] Specifically, for the description of the pre-generated oracle private key, please refer to the description in the above embodiment, which will not be repeated here.

[0077] Among them, the oracle contract is pre-deployed in the blockchain, and is used to enable the blockchain to perform signature verification after receiving the compliance information verification result after the signature processing.

[0078] Among them, in the process of sending the compliance information verification results to the blockchain, so that the blockchain sends the compliance information verification results to the monitoring terminal based on the pre-deployed monitoring smart contract, the two processes of signature processing and signature verification ensure that the compliance information verification results transmitted to the blockchain are complete, thereby ensuring the accuracy of digital asset issuance monitoring, thereby improving the compliance of digital asset issuance.

[0079] In one possible embodiment, a pre-deployed monitoring smart contract is generated for the monitoring terminal and sent to the blockchain to be deployed as a contract in the blockchain.

[0080] Specifically, the pre-deployed monitoring smart contract is a contract that is generated by the monitoring terminal and sent to the blockchain during the initialization process of the issuance monitoring of the digital asset to be deployed in the blockchain.

[0081] Among them, the pre-deployed monitoring smart contract enables the blockchain to generate and send a compliance information verification request to the oracle based on the received monitoring request after receiving the monitoring request sent by the monitoring terminal. The specific description of this process can refer to the description of the compliance information verification request in step S201, which will not be repeated here.

[0082] Optionally, the pre-deployed monitoring smart contract is also used to process or standardize monitoring requests so that the oracle can correctly handle the request when it receives a compliance information verification request.

[0083] Among them, the pre-deployed monitoring smart contract enables the blockchain to send the verification result of the compliance information processed through signature verification to the monitoring terminal. For the specific description of this process, reference can be made to the description in the above embodiments of the process of sending the verification result of the compliance information to the blockchain, so that the blockchain sends the verification result of the compliance information to the monitoring terminal based on the pre-deployed monitoring smart contract, which will not be elaborated here.

[0084] Among them, this application does not limit the process of generating the monitoring smart contract by the monitoring terminal and the process of deploying the monitoring smart contract by the blockchain.

[0085] Among them, by means of pre-deploying the monitoring smart contract, the immutability of the monitoring process is improved, thereby enhancing the security in the issuance monitoring of digital assets and further improving the compliance of the issuance of digital assets.

[0086] In a possible embodiment, during the initialization process of the issuance monitoring of digital assets, the method for issuing and monitoring digital assets further includes: generating an oracle public key and an oracle private key based on the homomorphic encryption algorithm.

[0087] Among them, homomorphic encryption (HE) refers to an encryption algorithm that satisfies the property of homomorphic operations on ciphertexts. That is, after the data is homomorphically encrypted, specific calculations are performed on the ciphertext, and the plaintext obtained after corresponding homomorphic decryption of the ciphertext calculation result is equivalent to directly performing the same calculation on the plaintext data, realizing the "computable but invisible" of the data. Optionally, the Paillier algorithm can be selected. For example, based on the homomorphic encryption algorithm, the oracle public key is generated as described in the above embodiments, PK(n, g), and the oracle private key can be SK(λ, μ). Optionally, based on the generation of the public-private key pair here, the corresponding encryption process can be: for the plaintext m (0 <= m <= n), a random number r is selected such that 0 < r < n and r is relatively prime to n, and the ciphertext c = g m r n mod n 2 ; based on the generation of the public-private key pair here, the corresponding decryption process is: using the private key (λ, μ), the plaintext m = L(cλ mod n 2 )μ mod n.

[0088] Among them, in the process of generating the oracle public key and the oracle private key, the homomorphic encryption algorithm has the advantages of high security and high efficiency, thereby enhancing the security and efficiency in the issuance monitoring of digital assets and further improving the compliance of the issuance of digital assets.

[0089] In a possible embodiment, during the initialization process of monitoring the issuance of digital assets, the method for monitoring the issuance of digital assets further includes: first generating an oracle contract according to the oracle public key, and then sending the oracle contract to the blockchain so that the oracle contract is deployed in the blockchain.

[0090] Among them, the description of the oracle contract can refer to the description of the process of sending the compliance information verification results to the blockchain in the above embodiment, so that the blockchain sends the compliance information verification results to the monitoring terminal based on the pre-deployed monitoring smart contract, which will not be repeated here.

[0091] Among them, the pre-deployed oracle contract is generated according to the oracle public key, so that based on the pre-deployed oracle contract, when the compliance information verification result after the signature processing is signed and verified, the oracle public key can be determined first, and then the compliance information verification result after the signature processing is signed and verified according to the determined oracle public key. Among them, the oracle public key corresponds to the oracle that performs the signature processing, which ensures the validity of the signature verification, thereby improving the security of the issuance monitoring of digital assets and further improving the compliance of the issuance of digital assets.

[0092] Figure 4 A signaling flow chart provided for this application. Among them, the monitoring terminal generates and sends a monitoring request to the blockchain; the blockchain, in response to the monitoring request, generates and sends a compliance information verification request based on a pre-deployed monitoring smart contract; the oracle, in response to the compliance information verification request, generates and sends a compliance information acquisition request to the issuer terminal; the issuer terminal, in response to the compliance information acquisition request, generates and sends a zero-knowledge proof to the oracle based on the oracle public key and compliance information; the oracle, based on the zero-knowledge proof and the pre-generated oracle private key, determines and sends the compliance information verification result corresponding to the issuer terminal to the blockchain; the blockchain sends the compliance information verification result to the monitoring terminal based on the pre-deployed monitoring smart contract. Among them, the specific description of the signaling transmission process described above can refer to the specific description in the embodiment shown above, which will not be repeated here.

[0093] Figure 5 A schematic diagram of the structure of the digital asset issuance monitoring device provided in this application, such as Figure 5 As shown, the digital asset issuance monitoring device 50 provided in this embodiment includes:

[0094] A generation module 501 is used to generate and send a compliance information acquisition request to at least one issuer terminal in response to a compliance information verification request sent by the blockchain; wherein the compliance information verification request is generated and sent by the blockchain in response to a monitoring request sent by the monitoring terminal based on a pre-deployed monitoring smart contract; and the compliance information acquisition request includes a pre-generated oracle public key;

[0095] The determination module 502 is used to receive the zero-knowledge proof fed back by the issuer terminal, and determine the compliance information verification result corresponding to the issuer terminal according to the zero-knowledge proof and the pre-generated oracle private key; wherein the zero-knowledge proof is the proof information generated by the issuer terminal according to the oracle public key and the compliance information in response to the compliance information acquisition request;

[0096] The processing module 503 is used to send the compliance information verification result to the blockchain, so that the blockchain sends the compliance information verification result to the monitoring terminal based on the pre-deployed monitoring smart contract.

[0097] In one possible implementation, the determination module 502 is specifically used to decrypt the zero-knowledge proof according to the pre-generated oracle private key to obtain the decrypted zero-knowledge proof; based on the decrypted zero-knowledge proof, determine the compliance information verification result corresponding to the issuer terminal; wherein the compliance information verification result is verification passed or verification failed.

[0098] In one possible implementation, the compliance information includes: the issued quantity and the issuance quantity threshold; the determination module 502 is further specifically used to determine the size relationship between the issued quantity and the issuance quantity threshold based on the zero-knowledge proof after decryption processing; if it is determined that the issued quantity is less than the issuance quantity threshold, then the compliance information verification result is determined to be verification passed; otherwise, the compliance information verification result is determined to be verification failed.

[0099] In one possible implementation, the processing module 503 is specifically used to sign the compliance information verification result according to the pre-generated oracle private key; send the signed compliance information verification result to the blockchain, so that the blockchain performs signature verification on the signed compliance information verification result based on the pre-deployed oracle contract, and sends the compliance information verification result that has passed the signature verification to the monitoring terminal based on the pre-deployed monitoring smart contract.

[0100] In one possible implementation, the processing module 503 is also used to generate an oracle public key and an oracle private key based on a homomorphic encryption algorithm.

[0101] In one possible implementation, the processing module 503 is also used to generate an oracle contract based on the oracle public key; and send the oracle contract to the blockchain so that the oracle contract is deployed in the blockchain.

[0102] In one possible implementation, a pre-deployed monitoring smart contract is generated for the monitoring terminal and sent to the blockchain to be deployed as a contract in the blockchain.

[0103] The digital asset issuance monitoring device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be described in detail here.

[0104] Figure 6 This is a schematic diagram of the structure of the electronic device provided in this application. Figure 6 As shown, the electronic device 60 provided in this embodiment includes: at least one processor 601 and a memory 602. Optionally, the device 60 also includes a communication component 603. The processor 601, the memory 602 and the communication component 603 are connected via a bus 604.

[0105] In a specific implementation process, at least one processor 601 executes the computer execution instructions stored in the memory 602, so that at least one processor 601 executes the above method.

[0106] The specific implementation process of the processor 601 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

[0107] In the above embodiments, it should be understood that the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the invention can be directly implemented as a hardware processor, or can be implemented by a combination of hardware and software modules in the processor.

[0108] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (NVM), such as at least one disk storage.

[0109] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of this application is not limited to only one bus or one type of bus.

[0110] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0111] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.

[0112] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present application.

[0113] It should be further noted that, although the various steps in the flowchart are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0114] It should be understood that the above-mentioned device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0115] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present application may be integrated into one unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The above-mentioned integrated unit / module may be implemented in the form of hardware or in the form of a software program module.

[0116] If the integrated unit / module is implemented in the form of hardware, the hardware may be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. Unless otherwise specified, the processor may be any appropriate hardware processor, such as a CPU, a GPU, an FPGA, a DSP, an ASIC, etc. Unless otherwise specified, the storage unit may be any appropriate magnetic storage medium or magneto-optical storage medium, such as a resistive random access memory (RRAM), a dynamic random access memory (DRAM), a static random access memory (SRAM), an enhanced dynamic random access memory (EDRAM), a high-bandwidth memory (HBM), a hybrid memory cube (HMC), etc.

[0117] If the integrated unit / module is implemented in the form of a software program module 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 application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. 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, server or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0118] In the above embodiments, the description of each embodiment has its own emphasis. For the part not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0119] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0120] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for monitoring the issuance of digital assets, characterized in that: Applied to oracles, including: In response to a compliance information verification request sent by the blockchain, generate and send a compliance information acquisition request to at least one issuer terminal; wherein the compliance information verification request is generated and sent by the blockchain in response to a monitoring request sent by a monitoring terminal based on a pre-deployed monitoring smart contract; the compliance information acquisition request includes a pre-generated oracle public key; Receive the zero-knowledge proof fed back by the issuer terminal, and determine the compliance information verification result corresponding to the issuer terminal according to the zero-knowledge proof and the pre-generated oracle private key; wherein the zero-knowledge proof is the proof information generated by the issuer terminal according to the oracle public key and compliance information in response to the compliance information acquisition request; The compliance information verification result is sent to the blockchain, so that the blockchain sends the compliance information verification result to the monitoring terminal based on the pre-deployed monitoring smart contract.

2. The method according to claim 1, characterized in that According to the zero-knowledge proof and the pre-generated oracle private key, the compliance information verification result corresponding to the issuer terminal is determined, including: Decrypting the zero-knowledge proof according to the pre-generated oracle private key to obtain a decrypted zero-knowledge proof; According to the zero-knowledge proof after the decryption process, a compliance information verification result corresponding to the issuer terminal is determined; wherein the compliance information verification result is verification passed or verification failed.

3. The method according to claim 2, characterized in that The compliance information includes: the issued quantity and the issued quantity threshold; according to the decrypted zero-knowledge proof, determining the compliance information verification result corresponding to the issuer terminal, including: Determine the magnitude relationship between the issued quantity and the issued quantity threshold according to the zero-knowledge proof after the decryption process; If it is determined that the issued quantity is less than the issued quantity threshold, then the compliance information verification result is determined to be the verification passed; otherwise, the compliance information verification result is determined to be the verification failed.

4. The method according to claim 1, characterized in that: Sending the compliance information verification result to the blockchain, so that the blockchain sends the compliance information verification result to the monitoring terminal based on the pre-deployed monitoring smart contract, including: The compliance information verification result is signed according to the pre-generated oracle private key; The compliance information verification result after signature processing is sent to the blockchain, so that the blockchain performs signature verification processing on the compliance information verification result after signature processing based on the pre-deployed oracle contract, and sends the compliance information verification result after signature verification processing to the monitoring terminal based on the pre-deployed monitoring smart contract.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Based on the homomorphic encryption algorithm, the oracle public key and the oracle private key are generated.

6. The method according to claim 5, characterized in that The method further comprises: Generate an oracle contract based on the oracle public key; Sending the oracle contract to the blockchain so that the oracle contract is deployed in the blockchain.

7. The method according to claim 5, characterized in that The pre-deployed monitoring smart contract is generated for the monitoring terminal and sent to the blockchain to be deployed as a contract in the blockchain.

8. A digital asset issuance monitoring device, comprising: A generation module, configured to generate and send a compliance information acquisition request to at least one issuer terminal in response to a compliance information verification request sent by a blockchain; wherein the compliance information verification request is generated and sent by the blockchain in response to a monitoring request sent by a monitoring terminal based on a pre-deployed monitoring smart contract; and the compliance information acquisition request includes a pre-generated oracle public key; A determination module, configured to receive the zero-knowledge proof fed back by the issuer terminal, and determine the compliance information verification result corresponding to the issuer terminal according to the zero-knowledge proof and the pre-generated oracle private key; wherein the zero-knowledge proof is the proof information generated by the issuer terminal according to the oracle public key and the compliance information in response to the compliance information acquisition request; A processing module is used to send the compliance information verification result to the blockchain, so that the blockchain sends the compliance information verification result to the monitoring terminal based on the pre-deployed monitoring smart contract.

9. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

11. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 7 when being executed by a processor.

Images