An evidence credible evidence storage method, device, medium and equipment

Abstract

The application relates to the technical field of data storage, in particular to an evidence credible storage method and device, medium and equipment. The method comprises the following steps: obtaining a storage request sent by an evidence provider, wherein the storage request comprises an evidence fingerprint of evidence, an evidence chain rule identifier and a credible proof of the evidence; determining a public input of zero-knowledge proof according to the evidence chain rule corresponding to the evidence fingerprint and the evidence chain rule identifier of the evidence; determining whether the evidence meets the evidence chain rule according to the public input of the zero-knowledge proof, the verification secret key corresponding to the evidence chain rule identifier and the credible proof of the evidence, and if yes, storing the evidence; and through the above method, the evidence is verified before being stored, and the zero-knowledge proof is used to verify the evidence without disclosing the private information of the evidence, so that it is ensured that the stored evidence meets the evidence chain rule, and the convenience of calling the evidence in the later stage is improved.

Description

Technical Field

[0001] This application relates to the field of data storage technology, and in particular to a method, apparatus, medium and device for reliable evidence storage. Background Technology

[0002] Trusted evidence storage refers to individuals or organizations storing hashed fingerprints of evidence content, documents, images, etc., on the blockchain. This method of evidence storage can connect to the judicial system (courts, notary offices, etc.), ensuring that all parties requesting the evidence can verify its authenticity, thereby guaranteeing the usability, trustworthiness, and reliability of the evidence, forming a complete evidence loop. Currently, there are many trusted evidence storage services, but these services do not define a standardized evidence format for evidence providers, resulting in the stored evidence being unusable.

[0003] Therefore, there is an urgent need for a reliable evidence preservation method, device, medium, and equipment to verify evidence and improve the convenience of evidence retrieval. Summary of the Invention

[0004] This application provides a method, apparatus, product, medium, and device for verifying evidence and improving the ease of accessing evidence.

[0005] In a first aspect, embodiments of this application provide a method for credible evidence preservation, comprising: obtaining a preservation request sent by an evidence provider, wherein the preservation request includes an evidence fingerprint, an evidence chain rule identifier, and a credible proof of the evidence; the credible proof of the evidence is determined based on a proof key corresponding to the evidence chain rule identifier, the public input of the evidence, and the private input of the evidence; the public input of the evidence is used to characterize the public information of the evidence; the private input of the evidence is used to characterize the privacy information of the evidence; and the evidence fingerprint of the evidence is obtained through the private input of the evidence.

[0006] The common input for zero-knowledge proof is determined based on the evidence fingerprint of the evidence and the evidence chain rule corresponding to the evidence chain rule identifier.

[0007] Based on the public input of the zero-knowledge proof, the verification key corresponding to the evidence chain rule identifier, and the credible proof of the evidence, determine whether the evidence conforms to the evidence chain rule. If it does, then the evidence is stored as evidence.

[0008] The proof key and the verification key corresponding to the evidence chain rule identifier are generated based on zero-knowledge proof according to the evidence chain rule corresponding to the evidence chain rule identifier.

[0009] By using the above methods, evidence is verified before it is stored. Combined with zero-knowledge proofs, the evidence is verified without disclosing private information, thereby ensuring that the stored evidence complies with the rules of the evidence chain and improving the convenience of subsequent evidence retrieval.

[0010] In one possible implementation, before obtaining the evidence preservation request sent by the evidence provider, the following steps are also included:

[0011] Obtain the evidence chain rule identifier and the corresponding evidence chain rule provided by the evidence chain rule maker;

[0012] A zero-knowledge proof circuit is generated based on the evidence chain rule identifier corresponding to the evidence chain rule.

[0013] The zero-knowledge proof circuit generates a proof key corresponding to the evidence chain rule identifier and a verification key corresponding to the evidence chain rule identifier.

[0014] In the above manner, the evidence chain rules provided by the evidence rule maker are transformed into a zero-knowledge proof problem, and a proof key is generated to generate a credible proof of the evidence, and a verification key is generated to verify the credible proof.

[0015] In one possible implementation, after generating the proof key corresponding to the evidence chain rule identifier and the verification key corresponding to the evidence chain rule identifier based on the zero-knowledge proof circuit, the method further includes:

[0016] The evidence chain rule identifier, the evidence chain rule corresponding to the evidence chain rule identifier, the proof key corresponding to the evidence chain rule identifier, and the verification key corresponding to the evidence chain rule identifier are stored in the blockchain.

[0017] In the above method, the information stored in the blockchain can be accessed by participants in multiple blockchains, which improves the ease of obtaining evidence rules.

[0018] In one possible implementation, the evidence includes an evidence key name and an evidence key value; the evidence key value is the secret input of the evidence.

[0019] The evidence chain rule identifier includes the key name and the restriction conditions of the evidence chain rule;

[0020] The common inputs for zero-knowledge proofs are determined based on the evidence fingerprint of the evidence and the evidence chain rule corresponding to the evidence chain rule identifier, including:

[0021] The evidence fingerprint is determined based on the evidence key name and the evidence key value;

[0022] Based on the evidence fingerprint of the evidence, the key name and constraints of the evidence chain rule corresponding to the evidence chain rule identifier, determine the common input of the zero-knowledge proof;

[0023] The credible proof of the evidence is determined based on the evidence chain rules, identifying the corresponding proof key, the public input of the evidence, and the secret input of the evidence, including:

[0024] Based on the evidence fingerprint of the evidence, the key name and constraints of the evidence chain rule corresponding to the evidence chain rule identifier, determine the common input of the evidence;

[0025] The credible proof of the evidence is determined based on the proof key corresponding to the evidence chain rule identifier, the secret input of the evidence, and the public input of the evidence.

[0026] In one possible implementation, determining the evidence fingerprint based on the evidence key name and the evidence key value includes:

[0027] Determine the hash value corresponding to the evidence key name and the evidence key value, and use the hash value as the evidence fingerprint of the evidence.

[0028] In one possible implementation, determining the hash value corresponding to the evidence key name and the evidence key value includes:

[0029] The evidence key name and the evidence key value are used to determine the hash value using a Merkle tree hash algorithm.

[0030] Merkle tree algorithm was chosen because it has a better zero-knowledge proof circuit when performing selective disclosure. Other hash algorithms can also be used, such as directly calculating the hash value.

[0031] One possible implementation involves storing the evidence, including:

[0032] Obtain a trusted token; the trusted token is a timestamp and / or a trusted signature;

[0033] The trusted marker, the trusted proof of the evidence, the evidence chain rule identifier, and the evidence fingerprint of the evidence are stored in the blockchain.

[0034] A timestamp can be issued by an institution certified by the National Time Service Center, providing a trusted timestamp and a trusted signature for the evidence-preserving event. After obtaining the trusted token, the trusted token, the trusted proof of the evidence, the evidence chain rule identifier, and the evidence fingerprint of the evidence are stored in the blockchain.

[0035] In one possible implementation, the trusted marker, the trusted proof of the evidence, the evidence chain rule identifier, and the evidence fingerprint of the evidence are stored in a blockchain, including:

[0036] The verification smart contract deployed through the blockchain verifies whether the evidence conforms to the evidence chain rules based on the verification key corresponding to the evidence chain rule identifier. If it does, the trusted marker, the trusted proof of the evidence, the evidence chain rule identifier, and the evidence fingerprint of the evidence are stored in the blockchain.

[0037] By using the above method, the verification is performed again through a smart contract before storing the data in the blockchain. This allows the verification process to be consensus-based through the blockchain, thereby improving the security of the verification process.

[0038] Secondly, embodiments of this application provide another method for credible evidence storage, applied to a credible evidence storage system, wherein the credible evidence storage system includes a credible evidence storage application, an evidence provider, and a blockchain; the method includes:

[0039] The evidence provider sends an evidence storage request to the trusted evidence storage application. The evidence storage request includes the evidence fingerprint, evidence chain rule identifier, and trusted proof of the evidence. The trusted proof of the evidence is determined based on the proof key corresponding to the evidence chain rule identifier, the public input of the evidence, and the secret input of the evidence. The public input of the evidence is used to characterize the public information of the evidence. The secret input of the evidence is used to characterize the private information of the evidence. The evidence fingerprint of the evidence is obtained through the secret input of the evidence.

[0040] The trusted evidence storage application obtains the evidence storage request.

[0041] The trusted evidence storage application determines the common input for zero-knowledge proof based on the evidence fingerprint of the evidence and the evidence chain rule corresponding to the evidence chain rule identifier.

[0042] The trusted evidence storage application determines whether the evidence conforms to the evidence chain rule based on the public input of the zero-knowledge proof, the verification key corresponding to the evidence chain rule identifier, and the trusted proof of the evidence. If it does, the evidence is sent to the blockchain. The proof key and the verification key corresponding to the evidence chain rule identifier are generated based on the zero-knowledge proof according to the evidence chain rule corresponding to the evidence chain rule identifier.

[0043] The blockchain is used to store the evidence.

[0044] In one possible implementation, the trusted evidence storage system further includes an evidence chain rule maker, and before the evidence provider sends an evidence storage request to the trusted evidence storage application, it also includes:

[0045] The party that formulates the chain of evidence rules sends a chain of evidence rule identifier and the chain of evidence rule corresponding to the chain of evidence rule identifier to the trusted evidence storage application.

[0046] The trusted evidence storage application obtains the evidence chain rule identifier provided by the evidence chain rule maker and the evidence chain rule corresponding to the evidence chain rule identifier;

[0047] The trusted evidence storage application generates a zero-knowledge proof circuit based on the evidence chain rule identifier corresponding to the evidence chain rule.

[0048] The trusted evidence storage application generates a proof key and a verification key corresponding to the evidence chain rule identifier based on the zero-knowledge proof circuit.

[0049] In one possible implementation, after the trusted evidence storage application generates the proof key corresponding to the evidence chain rule identifier and the verification key corresponding to the evidence chain rule identifier based on the zero-knowledge proof circuit, it further includes:

[0050] The trusted evidence storage application sends the evidence chain rule identifier, the evidence chain rule corresponding to the evidence chain rule identifier, the proof key corresponding to the evidence chain rule identifier, and the verification key corresponding to the evidence chain rule identifier to the blockchain;

[0051] The blockchain stores the evidence chain rule identifier, the evidence chain rule corresponding to the evidence chain rule identifier, the proof key corresponding to the evidence chain rule identifier, and the verification key corresponding to the evidence chain rule identifier.

[0052] In one possible implementation, the evidence includes an evidence key name and an evidence key value; the evidence key value is the secret input of the evidence; the evidence chain rule identifier includes a key name and a restriction condition.

[0053] The trusted evidence storage application determines the common inputs for zero-knowledge proofs based on the evidence fingerprint of the evidence and the evidence chain rule corresponding to the evidence chain rule identifier, including:

[0054] The trusted evidence storage application determines the evidence fingerprint of the evidence based on the evidence key name and the evidence key value;

[0055] The trusted evidence storage application determines the common input for zero-knowledge proof based on the evidence fingerprint of the evidence, the key name of the evidence chain rule corresponding to the evidence chain rule identifier, and the restriction conditions.

[0056] The credible proof of the evidence is determined based on the evidence chain rules, identifying the corresponding proof key, the public input of the evidence, and the secret input of the evidence, including:

[0057] The evidence provider determines the common input of the evidence based on the evidence fingerprint, the key name of the evidence chain rule corresponding to the evidence chain rule identifier, and the restriction conditions.

[0058] The evidence provider determines the credible proof of the evidence based on the proof key corresponding to the evidence chain rule identifier, the secret input of the evidence, and the public input of the evidence.

[0059] Thirdly, embodiments of this application provide a reliable evidence storage device, comprising: an acquisition module, configured to acquire a storage request sent by an evidence provider, wherein the storage request includes an evidence fingerprint, an evidence chain rule identifier, and a reliable proof of the evidence; the reliable proof of the evidence is determined based on a proof key corresponding to the evidence chain rule identifier, the public input of the evidence, and the private input of the evidence; the public input of the evidence is used to characterize the public information of the evidence; the private input of the evidence is used to characterize the privacy information of the evidence; and the evidence fingerprint of the evidence is obtained through the private input of the evidence.

[0060] The determination module is used to determine the common input of the zero-knowledge proof based on the evidence fingerprint of the evidence and the evidence chain rule corresponding to the evidence chain rule identifier;

[0061] The determining module is specifically used to determine whether the evidence conforms to the evidence chain rule based on the public input of the zero-knowledge proof, the verification key corresponding to the evidence chain rule identifier, and the credible proof of the evidence; if it does, the evidence is stored as evidence.

[0062] The proof key and the verification key corresponding to the evidence chain rule identifier are generated based on zero-knowledge proof according to the evidence chain rule corresponding to the evidence chain rule identifier.

[0063] The acquisition module is specifically used to: acquire the evidence chain rule identifier and the evidence chain rule corresponding to the evidence chain rule provided by the evidence chain rule maker; generate a zero-knowledge proof circuit according to the evidence chain rule corresponding to the evidence chain rule identifier; and generate a proof key and a verification key corresponding to the evidence chain rule identifier according to the zero-knowledge proof circuit.

[0064] The device further includes an evidence storage module, which is used to store the evidence chain rule identifier, the evidence chain rule corresponding to the evidence chain rule identifier, the proof key corresponding to the evidence chain rule identifier, and the verification key corresponding to the evidence chain rule identifier into the blockchain.

[0065] The evidence includes an evidence key name and an evidence key value; the evidence key value is the secret input of the evidence; the evidence chain rule corresponding to the evidence chain rule identifier includes a key name and a restriction condition; the determining module is further configured to: determine the evidence fingerprint of the evidence based on the evidence key name and the evidence key value; determine the common input of the zero-knowledge proof based on the evidence fingerprint of the evidence, the key name of the evidence chain rule corresponding to the evidence chain rule identifier, and the restriction condition; determine the common input of the evidence based on the evidence fingerprint of the evidence, the key name of the evidence chain rule corresponding to the evidence chain rule identifier, and the restriction condition; and determine the credible proof of the evidence based on the proof key corresponding to the evidence chain rule identifier, the secret input of the evidence, and the common input of the evidence.

[0066] The determining module is further configured to determine the hash value corresponding to the evidence key name and the evidence key value, and use the hash value as the evidence fingerprint of the evidence.

[0067] The determining module is further configured to determine the hash value by using the evidence key name and the evidence key value through a Merkle tree hash algorithm.

[0068] The evidence storage module is specifically used to obtain a trusted marker; the trusted marker is a timestamp and / or a trusted signature; and to store the trusted marker, the trusted proof of the evidence, the evidence chain rule identifier, and the evidence fingerprint of the evidence in the blockchain.

[0069] The acquisition module is specifically used to verify whether the evidence conforms to the evidence chain rules based on the verification key corresponding to the evidence chain rule identifier through the verification smart contract deployed on the blockchain. If it conforms, the trusted marker, the trusted proof of the evidence, the evidence chain rule identifier, and the evidence fingerprint of the evidence are stored in the blockchain.

[0070] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when run, executes any of the methods described in the first aspect.

[0071] Fifthly, embodiments of this application provide a computing device, including: a memory for storing program instructions; and a processor for calling the program instructions stored in the memory and executing the method in any of the designs in the first aspect above according to the obtained program.

[0072] Sixthly, embodiments of this application provide a computer program product that, when run on a processor, implements the method as described in any of the designs in the first aspect above.

[0073] The beneficial effects of the second to sixth aspects mentioned above can be specifically referred to the beneficial effects that can be achieved by any of the designs in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0074] Figure 1 An exemplary flowchart illustrates a method for credible evidence preservation provided in an embodiment of this application;

[0075] Figure 2 This illustration shows a flowchart of a method for generating proof keys and verification keys according to an embodiment of this application;

[0076] Figure 3 An exemplary illustration shows a schematic diagram of a Merkle tree hash algorithm provided in an embodiment of this application;

[0077] Figure 4 An exemplary flowchart of a method for credible evidence preservation provided in an embodiment of this application is shown.

[0078] Figure 5 The following is an exemplary flowchart of an evidence credibility preservation device provided in an embodiment of this application. Detailed Implementation

[0079] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this invention, and not all of them. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0080] Trusted evidence storage refers to individuals or organizations storing hashed fingerprints of evidence such as content, documents, and images on the blockchain, along with a reliable timestamp and an electronic signature from an authoritative institution. This method of evidence storage can connect to the judicial system (courts, notary offices, etc.), ensuring that all parties requesting the evidence can verify its authenticity, thereby guaranteeing the usability, trustworthiness, and reliability of the evidence, forming a complete evidence loop.

[0081] For example, in the internet age, information spreads extremely quickly, and the probability of digital works being infringed is very high. Furthermore, the time and financial costs of protecting rights are relatively high. Through trusted evidence preservation services, ownership registration of digital works can be carried out, including original images, videos, audio, text, and code. After registration, electronic data evidence of the digital work can be generated, thereby protecting the copyright of the digital work.

[0082] Furthermore, electronic certificates, transaction vouchers, electronic contracts, and electronic invoices can be permanently preserved through trusted evidence storage services. This avoids the problems of these documents being easily lost, difficult to circulate, and difficult to verify their authenticity.

[0083] Furthermore, with the increasing prevalence of online shopping, trusted evidence storage can be used to store transaction data generated during online shopping. Because a single order contains many easily overlooked details, this data is prone to loss over time. When disputes arise, it becomes difficult to reconstruct the transaction data completely. Trusted evidence storage services can preserve transaction data intact, providing comprehensive evidence for disputes. Moreover, it allows for data analysis based on the complete transaction data.

[0084] Currently, there are many trusted evidence storage services, such as Baidu Super Chain, AntChain, Yeebaoquan, and Zhixin Chain. However, these trusted evidence storage services do not define a standardized evidence format for the evidence provider. In other words, any evidence provided by the provider can be stored on the blockchain. However, much of the evidence uploaded to the chain does not conform to the specifications stipulated by the evidence user, rendering the stored evidence unusable. This not only wastes storage resources but also makes subsequent evidence retrieval more complex.

[0085] Based on this, this application provides a method for credible evidence preservation, which is used to verify evidence and improve the convenience of evidence retrieval.

[0086] Figure 1 This illustration shows a flowchart of a reliable evidence preservation method provided in an embodiment of this application. Figure 1 As shown, the method includes:

[0087] Step 101: The trusted evidence storage application obtains the evidence storage request sent by the evidence provider.

[0088] The aforementioned evidence providers are institutions or individuals with a need for evidence storage. For example, an individual might store their bank card transaction records as evidence after obtaining them from the bank, for use in resolving subsequent disputes. Similarly, large trading platforms generate massive amounts of transaction data daily, but these records are often short-lived and complex, with potentially usable evidence mixed in, making retrieval difficult in case of disputes. Therefore, it is necessary to store usable evidence-based transaction data for efficient retrieval and use.

[0089] When evidence is preserved, the evidence provider sends a preservation request to a trusted evidence preservation application, which then receives this request. The preservation request includes the evidence fingerprint, the evidence chain rule identifier, and the credible proof of the evidence.

[0090] The credible proof of evidence is determined by identifying the corresponding proof key, the public input, and the secret input of the evidence according to the rules of the evidence chain. The public input represents the publicly available information of the evidence; the secret input represents the private information. A complete piece of evidence contains both publicly available and private information that cannot be disclosed. For example, the key names in an piece of evidence can be disclosed, but the key values ​​cannot. For instance, key names like "ID number" and "age" are public information; anyone can know that a piece of evidence contains these two. However, the specific ID number (401289552) and age (28) are private information, known only to the evidence provider and not publicly disclosed. However, this private information can be processed to hide the information itself, serving as a kind of evidence fingerprint. The evidence fingerprint is obtained through the secret input of the evidence.

[0091] Step 102: The trusted evidence storage application determines the common input of the zero-knowledge proof based on the evidence fingerprint and the evidence chain rule identifier corresponding to the evidence chain rule.

[0092] The trusted evidence storage application can obtain the corresponding evidence chain rule based on the evidence chain rule identifier. The evidence chain rule is predetermined and can be stored in the trusted evidence storage application in advance.

[0093] Step 103: The trusted evidence storage application determines whether the evidence conforms to the evidence chain rule based on the public input of the zero-knowledge proof, the verification key corresponding to the evidence chain rule identifier, and the trusted proof of the evidence. If it conforms, proceed to step 104; otherwise, proceed to step 105. The proof key and the verification key corresponding to the evidence chain rule identifier are generated based on the zero-knowledge proof according to the evidence chain rule corresponding to the evidence chain rule identifier.

[0094] Step 104: The trusted evidence storage application stores the evidence.

[0095] Step 105: The trusted evidence storage application does not store the evidence.

[0096] The following describes the process of generating the proof key and the verification key in step 103 above. Figure 2 This illustration shows a flowchart of a method for generating proof keys and verification keys according to an embodiment of this application. Figure 2 As shown, the method includes:

[0097] Step 201: The trusted evidence storage application obtains the evidence chain rule identifier and the evidence chain rule corresponding to the evidence chain rule identifier provided by the evidence chain rule maker.

[0098] In this step, the rules governing the chain of evidence can be established by judicial institutions such as prosecutors, courts, and notary offices. These institutions, in their daily case handling, need to investigate and collect evidence based on the specific circumstances of the case as the basis for their judgments. To improve efficiency, these institutions generally have specific format and content requirements for the evidence provided by the parties involved, such as specifying the types of evidence and their grouping. The parties provide appropriate evidence according to these format and content requirements. This application embodiment involves the storage of electronic evidence, and therefore must also comply with specific rules governing the chain of evidence. Two examples are given below to illustrate these rules:

[0099] Chain of Evidence Rule 1:

[0100] 1:{certifId:String:length

[18] }

[0101] 2:{age:Integer:range[18,200]}

[0102] 3:{record:String:null}

[0103] In the aforementioned evidence chain rule one, there are a total of three pieces of evidence. The key of the first piece is "ID number certifId", the key of the second piece is "age", and the key of the third piece is "record". The ID number is restricted to an immutable type (String) and a length of 18; the age is restricted to an integer type (Integer) with a range of 18 to 200; and the record is restricted to a String type with no range restriction (null).

[0104] Rule 2 of the chain of evidence:

[0105] 1:{unit price:float:range[1,10000]}

[0106] 2:{Quantity:Integer:range[0,999]}

[0107] 3:{Total Price:float:range[0,9990000]}

[0108] Constraint: Unit price * Quantity = Total price

[0109] In the aforementioned evidence chain rule two, there are three pieces of evidence. The key for the first piece is "Unit Price," the key for the second piece is "Quantity," and the key for the third piece is "Total Price." The restrictions on the ID number are floating-point numbers ranging from 1 to 10000; the restrictions on the quantity are integers ranging from 0 to 999; and the restrictions on the record are floating-point numbers ranging from 0 to 9990000. The constraint is: Unit Price * Quantity = Total Price.

[0110] The above two chain of evidence rules can be abstracted into the following chain of evidence rules:

[0111]

[0112] key i Let i represent the i-th piece of evidence, and type i Indicates the type of the i-th piece of evidence, condition i Let N represent the limiting condition of the i-th piece of evidence, and let N represent the number of pieces of evidence in this rule of evidence.

[0113] After determining the chain of evidence rule, it can be assigned a number as the identifier of the chain of evidence rule. For example, the chain of evidence rule above can be numbered 001.

[0114] Step 202: The trusted evidence storage application generates a zero-knowledge proof circuit based on the evidence chain rule identifier corresponding to the evidence chain rule.

[0115] Continuing with the example of evidence chain rule one in step 201 above, the secret input and common input of the zero-knowledge proof circuit are defined as follows:

[0116]

[0117]

[0118] The secret input w defines the key value, while the public input defines the evidence fingerprint D, along with the constraints and limitations. In the example above, with constraints, the first piece of evidence is determined to have constraints l1, u1, the second piece of evidence is determined to have constraints l2, u2, and the third piece of evidence is determined to have constraints l3, u3.

[0119] A zero-knowledge proof circuit can be generated based on the aforementioned secret input and public input. It should be noted that different chain of evidence rules may correspond to the same zero-knowledge proof circuit. For example, if two chain of evidence rules have the same number of pieces of evidence, and the same constraints and limitations on each piece of evidence, then the zero-knowledge proof circuits corresponding to these two chain of evidence rules can be reused.

[0120] Based on the above, after obtaining an evidence chain rule in step 201, the trusted evidence storage application can query in the memory or blockchain whether there is a reusable zero-knowledge proof circuit. If so, there is no need to redefine the public input and secret input.

[0121] Step 203: The trusted evidence storage application generates a proof key and a verification key corresponding to the evidence chain rule identifier based on the zero-knowledge proof circuit.

[0122] In one possible implementation, the proof key and verification key are generated using the KeyGen algorithm in zero-knowledge proof algorithms. The KeyGen algorithm includes a security parameter λ, and the proof key and verification key are generated according to the following formula:

[0123] KeyGen(1 λ ,C)→(pk,vk)

[0124] In this context, pk is the proof key and vk is the verification key.

[0125] After step 203 above, the evidence chain rule identifier, the evidence chain rule corresponding to the evidence chain rule identifier, the proof key corresponding to the evidence chain rule identifier, and the verification key corresponding to the evidence chain rule identifier can also be stored in the blockchain.

[0126] In this way, all participants in the blockchain can obtain the proof key and the verification key corresponding to the evidence chain rule identifier based on the evidence chain rule identifier, which can be used to generate trusted proofs and verify the trusted proofs.

[0127] The following section uses specific evidence to explain how the evidence fingerprint, the secret input of evidence, the public input of evidence, and the public input of zero-knowledge proof are defined.

[0128] Based on the above discussion, evidence includes evidence key name and evidence key value; based on the evidence key name and evidence key value, the evidence fingerprint can be determined.

[0129] In one possible implementation, the hash value corresponding to the evidence key name and the evidence key value can be determined, and the hash value can be used as the evidence fingerprint.

[0130] When determining the corresponding hash value based on the evidence key name and evidence key value, the Merkle tree hash algorithm can be used to determine the hash value. Figure 3 An exemplary diagram illustrating a Merkle tree hash algorithm provided in an embodiment of this application is shown. Figure 3As shown, taking a specific piece of evidence from the above evidence chain rule one as an example. The ID number is: 8798709; the age is: 25; the record is: somerecord. The final calculated hash value MRH is:

[0131] MRH=hash{hash[hash(age25||certifId8798709)]||hash[hash(recordssomerecord)]]}

[0132] Other hash algorithms can also be used, such as d = sha256(v1||k1||v2||k2…||vn||kn), where || represents simple string concatenation.

[0133] Merkle tree algorithm was chosen because it allows for selective disclosure. For example, it can prove that the age in the evidence is 25, but not disclose other key values, including the ID number 8798709 or the record `somerecord`. In the example above, the evidence provider only needs to provide the values ​​of `Hash01` and `Hash1` to disclose the age of 25, without needing to provide the ID number or record content. The verifier can perform the following verification:

[0134] Hash_00 = hash(age25)

[0135] Hash_0=hash(Hash_00||Hash_01)

[0136] MRH? ==hash(Hash_0||Hash_1)

[0137] If the left side of the last equation equals the right side, the trusted evidence storage application can verify that the plaintext age given by the evidence provider is 25 years old, which is consistent with the hash value of the evidence storage.

[0138] Secret Input of Evidence

[0139] Optionally, the key value of the evidence can be determined as the secret input of the evidence. Let's take a specific piece of evidence from Rule 1 of the evidence chain as an example. The ID number is: 8798709; the age is: 25; the record is: somerecord. Therefore, the secret input of the evidence can be determined as follows:

[0140]

[0141] Public input of evidence

[0142] Optionally, the common inputs of evidence can be determined based on the evidence fingerprint, the key name of the evidence chain rule, and the constraints of the corresponding evidence chain rule. Let's continue with the example of determining the secret inputs of evidence.

[0143]

[0144] Public inputs for zero-knowledge proofs

[0145] Optionally, since the public input of zero-knowledge proof is determined according to the specific chain of evidence rules, and the public input of specific evidence is the part of the evidence excluding the private information, the public input of evidence and the public input of zero-knowledge proof are basically the same, and will not be elaborated here.

[0146] Once the secret input and public input of the evidence are determined, a credible proof of the evidence can be generated by combining the proof key. A credible proof is a proof that the evidence conforms to specific evidence chain rules and can be verified by trusted evidence storage applications.

[0147] One possible implementation is to use the Prove algorithm from the zero-knowledge proof algorithm to generate a trusted proof as follows:

[0148] Prove(pk,x,w)→π

[0149] Where pk is the proof key, x is the public input of the evidence, w is the secret input of the evidence, and π is the credible proof.

[0150] In some scenarios involving illegal evidence storage, credible proofs may be forged. That is, credible proofs can be generated based on evidence that does not conform to the chain of evidence rules. For example, in a piece of evidence, the key value corresponding to the age key is 1000, which completely exceeds the range specified by the constraints. However, if the constraints are modified, a credible proof can still be generated. Therefore, before applying credible evidence storage, the credible proof must be verified.

[0151] In step 103 above, the trusted proof is verified based on the public input of the zero-knowledge proof, the verification key corresponding to the evidence chain rule identifier, and the trusted proof of the evidence. Specifically, the Verify algorithm in the zero-knowledge proof algorithm can be used for verification, using the following formula:

[0152] Verify(vk,x,π)→b

[0153] If the output b = 1, it means the trusted proof verification passed; if the output b = 0, it means the trusted proof verification failed.

[0154] Optionally, in step 104 above, when storing evidence, it is also necessary to obtain a trusted marker, which may be a timestamp and / or a trusted signature. The timestamp may be a trusted timestamp issued and a trusted signature provided by an institution certified by the National Time Service Center for the evidence storage event. After obtaining the trusted marker, the trusted marker, the trusted proof of the evidence, the evidence chain rule identifier, and the evidence fingerprint of the evidence are stored in the blockchain.

[0155] In one possible implementation, the blockchain is deployed with a verification smart contract. This contract verifies whether the evidence conforms to the evidence chain rules based on the verification key corresponding to the evidence chain rule identifier. The specific verification process can refer to step 103 above. If it conforms, the trusted marker, the trusted proof of the evidence, the evidence chain rule identifier, and the evidence fingerprint of the evidence are stored in the blockchain.

[0156] By using the above method, the verification is performed again through a smart contract before storing the data in the blockchain. This allows the verification process to be consensus-based through the blockchain, thereby improving the security of the verification process.

[0157] Based on the same technical concept, this application also provides a method for credible evidence storage, which is applied to a credible evidence storage system. The credible evidence storage system includes a credible evidence storage application, an evidence provider, an evidence chain rule maker, and a blockchain. Figure 4 The following is an exemplary flowchart illustrating a method for credible evidence preservation provided in an embodiment of this application. Figure 4 As shown, the method includes:

[0158] Step 401: The party that formulates the chain of evidence rules sends the chain of evidence rule identifier and the chain of evidence rule corresponding to the chain of evidence rule identifier to the trusted evidence storage application.

[0159] Step 402, trusted evidence storage application, obtain the evidence chain rule identifier and the evidence chain rule corresponding to the evidence chain rule identifier provided by the evidence chain rule maker;

[0160] Step 403, Trusted Evidence Storage Application: Generate a zero-knowledge proof circuit based on the evidence chain rule identifier corresponding to the evidence chain rule.

[0161] Step 404, Trusted Evidence Storage Application: Generate the proof key and the verification key corresponding to the evidence chain rule identifier based on the zero-knowledge proof circuit;

[0162] Step 405, Trusted Evidence Storage Application: Send the evidence chain rule identifier, the evidence chain rule corresponding to the evidence chain rule identifier, the proof key corresponding to the evidence chain rule identifier, and the verification key corresponding to the evidence chain rule identifier to the blockchain;

[0163] Step 406: The blockchain stores the evidence chain rule identifier, the evidence chain rule corresponding to the evidence chain rule identifier, the proof key corresponding to the evidence chain rule identifier, and the verification key corresponding to the evidence chain rule identifier.

[0164] Step 407: The evidence provision direction trusted evidence storage application queries the evidence chain rules;

[0165] Step 408: The trusted evidence storage application sends the queried evidence chain rule identifier, the evidence chain rule corresponding to the evidence chain rule identifier, the proof key corresponding to the evidence chain rule identifier, and the verification key corresponding to the evidence chain rule identifier to the evidence provider.

[0166] Step 409: The evidence provider determines the common input of the evidence based on the evidence fingerprint, the key name of the evidence chain rule corresponding to the evidence chain rule identifier, and the restriction conditions.

[0167] Step 410: The evidence provider determines the credible proof of the evidence based on the evidence chain rules, identifying the corresponding proof key, the secret input of the evidence, and the public input of the evidence.

[0168] Step 411: The evidence provider sends an evidence storage request to the trusted evidence storage application. The evidence storage request includes the evidence fingerprint, evidence chain rule identifier, and trusted proof of the evidence.

[0169] Step 412, Trusted Evidence Preservation Application, obtain evidence preservation request; the evidence preservation request includes the evidence fingerprint, evidence chain rule identifier and trusted proof of the evidence;

[0170] Step 413, Trusted Evidence Storage Application: Determine the common input for zero-knowledge proof based on the evidence fingerprint and the evidence chain rule identifier corresponding to the evidence chain rule;

[0171] Step 414: The trusted evidence storage application determines that the evidence conforms to the evidence chain rules based on the public input of the zero-knowledge proof, the verification key corresponding to the evidence chain rule identifier, and the trusted proof of the evidence, and sends the evidence to the blockchain.

[0172] Step 415, blockchain, to preserve the evidence.

[0173] Based on the same technical concept, this application also provides an evidence credible storage device. Figure 5 The following is an exemplary flowchart of an evidence trust preservation device provided in an embodiment of this application, such as... Figure 5 As shown, the device includes:

[0174] The acquisition module is used to acquire a storage request sent by the evidence provider. The storage request includes the evidence fingerprint, evidence chain rule identifier, and credible proof of the evidence. The credible proof of the evidence is determined based on the proof key corresponding to the evidence chain rule identifier, the public input of the evidence, and the secret input of the evidence. The public input of the evidence is used to characterize the public information of the evidence. The secret input of the evidence is used to characterize the private information of the evidence. The evidence fingerprint of the evidence is obtained through the secret input of the evidence.

[0175] The determination module is used to determine the common input of the zero-knowledge proof based on the evidence fingerprint of the evidence and the evidence chain rule corresponding to the evidence chain rule identifier;

[0176] The determining module is specifically used to determine whether the evidence conforms to the evidence chain rule based on the public input of the zero-knowledge proof, the verification key corresponding to the evidence chain rule identifier, and the credible proof of the evidence; if it does, the evidence is stored as evidence.

[0177] The proof key and the verification key corresponding to the evidence chain rule identifier are generated based on zero-knowledge proof according to the evidence chain rule corresponding to the evidence chain rule identifier.

[0178] The acquisition module is specifically used to: acquire the evidence chain rule identifier and the evidence chain rule corresponding to the evidence chain rule provided by the evidence chain rule maker; generate a zero-knowledge proof circuit according to the evidence chain rule corresponding to the evidence chain rule identifier; and generate a proof key and a verification key corresponding to the evidence chain rule identifier according to the zero-knowledge proof circuit.

[0179] The device further includes an evidence storage module, which is used to store the evidence chain rule identifier, the evidence chain rule corresponding to the evidence chain rule identifier, the proof key corresponding to the evidence chain rule identifier, and the verification key corresponding to the evidence chain rule identifier into the blockchain.

[0180] The evidence includes an evidence key name and an evidence key value; the evidence key value is the secret input of the evidence; the evidence chain rule corresponding to the evidence chain rule identifier includes a key name and a restriction condition; the determining module is further configured to: determine the evidence fingerprint of the evidence based on the evidence key name and the evidence key value; determine the common input of the zero-knowledge proof based on the evidence fingerprint of the evidence, the key name of the evidence chain rule corresponding to the evidence chain rule identifier, and the restriction condition; determine the common input of the evidence based on the evidence fingerprint of the evidence, the key name of the evidence chain rule corresponding to the evidence chain rule identifier, and the restriction condition; and determine the credible proof of the evidence based on the proof key corresponding to the evidence chain rule identifier, the secret input of the evidence, and the common input of the evidence.

[0181] The determining module is further configured to determine the hash value corresponding to the evidence key name and the evidence key value, and use the hash value as the evidence fingerprint of the evidence.

[0182] The determining module is further configured to determine the hash value by using the evidence key name and the evidence key value through a Merkle tree hash algorithm.

[0183] The evidence storage module is specifically used to obtain a trusted marker; the trusted marker is a timestamp and / or a trusted signature; and to store the trusted marker, the trusted proof of the evidence, the evidence chain rule identifier, and the evidence fingerprint of the evidence in the blockchain.

[0184] The acquisition module is specifically used to verify whether the evidence conforms to the evidence chain rules based on the verification key corresponding to the evidence chain rule identifier through the verification smart contract deployed on the blockchain. If it conforms, the trusted marker, the trusted proof of the evidence, the evidence chain rule identifier, and the evidence fingerprint of the evidence are stored in the blockchain.

[0185] Based on the same technical concept, this embodiment of the invention also provides a computer program product that, when run on a processor, implements the method shown in the above embodiments.

[0186] Based on the same technical concept, embodiments of the present invention also provide a computing device, including: a memory for storing program instructions;

[0187] The processor is used to call program instructions stored in the memory and execute the methods shown in the above embodiments according to the obtained program.

[0188] Based on the same technical concept, embodiments of the present invention also provide a computer-readable storage medium that implements the method shown in the above embodiments when the computer program product is run on a processor.

[0189] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied 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.

[0190] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0191] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0192] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0193] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. An evidence credible storage method, characterized in that, an evidence storage request sent by an evidence provider is acquired, the evidence storage request comprising an evidence fingerprint of the evidence, an evidence chain rule identifier, and a credible proof of the evidence; the credible proof of the evidence is obtained in the following manner: determining a public input of the evidence according to the evidence fingerprint, a key name of an evidence chain rule corresponding to the evidence chain rule identifier, and a restriction condition; determining the credible proof of the evidence according to a proof key corresponding to the evidence chain rule identifier, a secret input of the evidence, and the public input of the evidence; the public input of the evidence is used to represent public information of the evidence; the secret input of the evidence is used to represent private information of the evidence; the evidence comprises an evidence key name and an evidence key value; the evidence key value is the secret input of the evidence; an evidence fingerprint of the evidence is determined according to the evidence key name and the evidence key value; a public input of a zero-knowledge proof is determined according to the evidence fingerprint of the evidence, the key name of the evidence chain rule corresponding to the evidence chain rule identifier, and the restriction condition; whether the evidence meets the evidence chain rule is determined according to the public input of the zero-knowledge proof, a verification key corresponding to the evidence chain rule identifier, and the credible proof of the evidence; if yes, the evidence is stored; the proof key corresponding to the evidence chain rule identifier and the verification key corresponding to the evidence chain rule identifier are generated based on the zero-knowledge proof according to the evidence chain rule corresponding to the evidence chain rule identifier.

2. The method of claim 1, wherein, Before the evidence storage request sent by the evidence provider is acquired, the method further comprises: an evidence chain rule identifier and an evidence chain rule corresponding to the evidence chain rule identifier provided by an evidence chain rule maker are acquired; a zero-knowledge proof circuit is generated according to the evidence chain rule corresponding to the evidence chain rule identifier; the proof key corresponding to the evidence chain rule identifier and the verification key corresponding to the evidence chain rule identifier are generated according to the zero-knowledge proof circuit.

3. The method of claim 2, wherein, After the proof key corresponding to the evidence chain rule identifier and the verification key corresponding to the evidence chain rule identifier are generated according to the zero-knowledge proof circuit, the method further comprises: the evidence chain rule identifier, the evidence chain rule corresponding to the evidence chain rule identifier, the proof key corresponding to the evidence chain rule identifier, and the verification key corresponding to the evidence chain rule identifier are stored in a block chain.

4. The method of claim 1, characterized in that, the evidence fingerprint of the evidence is determined according to the evidence key name and the evidence key value, comprising: a hash value corresponding to the evidence key name and the evidence key value is determined, and the hash value is taken as the evidence fingerprint of the evidence.

5. The method of claim 4, wherein, the hash value corresponding to the evidence key name and the evidence key value is determined, comprising: the evidence key name and the evidence key value are subjected to a Merkle tree hash algorithm to determine the hash value.

6. The method of any one of claims 1-5, characterized in that, the evidence is stored, comprising: a credible mark is acquired; the credible mark is a time stamp and / or a credible signature. The trusted mark, the trusted proof of the evidence, the evidence chain rule identification and the evidence fingerprint of the evidence are stored into the blockchain.

7. The method of claim 6, wherein, The trusted mark, the trusted proof of the evidence, the evidence chain rule identification and the evidence fingerprint of the evidence are stored into the blockchain, comprising: The verification smart contract deployed by the blockchain verifies whether the evidence meets the evidence chain rule based on the corresponding verification key of the evidence chain rule identification, and if so, stores the trusted mark, the trusted proof of the evidence, the evidence chain rule identification and the evidence fingerprint of the evidence into the blockchain.

8. An evidence credible storage method, characterized in that, The method is applied to a trusted evidence storage system, which comprises a trusted evidence storage application, an evidence provider and a blockchain; the method comprises: The evidence provider sends a storage request to the trusted evidence storage application, wherein the storage request comprises an evidence fingerprint of the evidence, an evidence chain rule identification and a trusted proof of the evidence; the trusted proof of the evidence is obtained in the following manner: determining a public input of the evidence according to the evidence fingerprint of the evidence, a key name of the corresponding evidence chain rule of the evidence chain rule identification and a restriction condition; determining the trusted proof of the evidence according to a proof key corresponding to the evidence chain rule identification, a secret input of the evidence and the public input of the evidence; The public input of the evidence is used to represent public information of the evidence; the secret input of the evidence is used to represent private information of the evidence; the evidence comprises an evidence key name and an evidence key value; the evidence key value is the secret input of the evidence; The trusted evidence storage application acquires the storage request; The trusted evidence storage application determines the evidence fingerprint of the evidence according to the evidence key name and the evidence key value, and determines a public input of the zero-knowledge proof according to the evidence fingerprint of the evidence, a key name of the corresponding evidence chain rule of the evidence chain rule identification and a restriction condition; The trusted evidence storage application determines whether the evidence meets the evidence chain rule according to the public input of the zero-knowledge proof, a verification key corresponding to the evidence chain rule identification and the trusted proof of the evidence, and if so, sends the evidence to the blockchain; the proof key corresponding to the evidence chain rule identification and the verification key corresponding to the evidence chain rule identification are generated based on the zero-knowledge proof according to the evidence chain rule corresponding to the evidence chain rule identification; The blockchain stores the evidence.

9. The method of claim 8, wherein, The trusted evidence storage system further comprises an evidence chain rule maker, and before the evidence provider sends the storage request to the trusted evidence storage application, the method further comprises: The evidence chain rule maker sends an evidence chain rule identification and the evidence chain rule corresponding to the evidence chain rule identification to the trusted evidence storage application; The trusted evidence storage application acquires the evidence chain rule identification and the evidence chain rule corresponding to the evidence chain rule identification provided by the evidence chain rule maker; The trusted evidence storage application generates a zero-knowledge proof circuit according to the evidence chain rule corresponding to the evidence chain rule identification; and The trusted evidence storage application determines the public input of the evidence according to the evidence fingerprint of the evidence, the key name of the corresponding evidence chain rule of the evidence chain rule identification and the restriction condition, and determines the trusted proof of the evidence according to the proof key corresponding to the evidence chain rule identification, the secret input of the evidence and the public input of the evidence. The trusted evidence application generates a proof key corresponding to the evidence chain rule identifier and a verification key corresponding to the evidence chain rule identifier according to the zero-knowledge proof circuit.

10. The method of claim 9, wherein, After the trusted evidence application generates a proof key corresponding to the evidence chain rule identifier and a verification key corresponding to the evidence chain rule identifier according to the zero-knowledge proof circuit, the method further includes: The trusted evidence application sends the evidence chain rule identifier, the evidence chain rule corresponding to the evidence chain rule identifier, the proof key corresponding to the evidence chain rule identifier, and the verification key corresponding to the evidence chain rule identifier to the blockchain. The blockchain stores the evidence chain rule identifier, the evidence chain rule corresponding to the evidence chain rule identifier, the proof key corresponding to the evidence chain rule identifier, and the verification key corresponding to the evidence chain rule identifier.

11. An evidence trusted evidence storage device, characterized in that, The acquisition module is configured to acquire a storage request sent by an evidence provider, wherein the storage request comprises an evidence fingerprint of evidence, an evidence chain rule identifier, and a trusted proof of the evidence; the trusted proof of the evidence is obtained in the following manner: determining a public input of the evidence according to the evidence fingerprint of the evidence, a key name of an evidence chain rule corresponding to the evidence chain rule identifier, and a restriction condition; determining a trusted proof of the evidence according to a proof key corresponding to the evidence chain rule identifier, a secret input of the evidence, and the public input of the evidence; The public input of the evidence is used to represent public information of the evidence; the secret input of the evidence is used to represent private information of the evidence; the evidence comprises an evidence key name and an evidence key value; and the evidence key value is the secret input of the evidence; The determination module is configured to determine an evidence fingerprint of the evidence according to the evidence key name and the evidence key value, and determine a public input of a zero-knowledge proof according to the evidence fingerprint of the evidence, a key name of an evidence chain rule corresponding to the evidence chain rule identifier, and a restriction condition; The determination module is further configured to determine whether the evidence meets the evidence chain rule according to the public input of the zero-knowledge proof, a verification key corresponding to the evidence chain rule identifier, and the trusted proof of the evidence, and if so, store the evidence; The proof key corresponding to the evidence chain rule identifier and the verification key corresponding to the evidence chain rule identifier are generated based on a zero-knowledge proof according to the evidence chain rule corresponding to the evidence chain rule identifier.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed, performs the method of any one of claims 1 to 10.

13. A computing device, comprising: includes: a memory for storing program instructions; a processor for invoking the program instructions stored in the memory to perform the method of any one of claims 1 to 10 according to the obtained program execution.

Images