Blockchain-based storage evidence verification method and device, computer device, and medium

Abstract

This application relates to the field of blockchain technology and provides a blockchain-based method, apparatus, computer device, and medium for evidence verification. The method includes: obtaining on-chain data of the evidence to be verified from the document to be verified; determining associated digest information of the on-chain data based on the digest information to be verified in the document to be verified; performing digest verification on the document to be verified based on the digest information to be verified and the associated digest information; if the digest verification is successful, performing signature verification and timestamp verification on the on-chain data; if both signature verification and timestamp verification are successful, determining that the document to be verified is successful and generating an evidence verification report. This application performs digest verification on the document to be verified, and, while ensuring that the document to be verified has not been tampered with, further verifies that the document to be verified has not been tampered with since being uploaded to the blockchain based on signature verification and timestamp verification, thereby improving the accuracy of evidence verification.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular to a blockchain-based method, apparatus, computer equipment, and medium for evidence storage and verification. Background Technology

[0002] Using blockchain for electronic document notarization has become a standard notarization solution for many manufacturers. Leveraging the immutability of blockchain, it typically employs a collaborative approach between on-chain and off-chain data, separating the file from its hash value. The blockchain stores only the file's hash value, while the original file remains off-chain. By calculating the file's hash value and comparing it with the hash value on the blockchain, a corresponding verification report can be generated.

[0003] The existing evidence verification process only verifies the evidence files based on hash values, resulting in low accuracy. Summary of the Invention

[0004] In view of this, embodiments of this application provide a blockchain-based method, apparatus, computer equipment, and medium for evidence verification, in order to solve the problem of low verification accuracy of evidence documents in existing evidence verification processes.

[0005] The first aspect of this application provides a blockchain-based evidence verification method, including:

[0006] Based on the file identifier of the evidence to be verified, the blockchain information is determined, and the evidence storage data is obtained based on the determined blockchain information.

[0007] Obtain the digest information to be verified from the evidence file to be verified, and determine the associated digest information of the evidence-on-chain data based on the digest information to be verified;

[0008] The digest verification of the evidence storage file to be verified is performed based on the digest information to be verified and the associated digest information. If the digest verification of the evidence storage file to be verified is qualified, the signature verification of the evidence storage data on the blockchain is performed.

[0009] If the signature verification of the evidence-stored data on the blockchain is successful, then the timestamp verification of the evidence-stored data on the blockchain is performed. If the timestamp verification of the evidence-stored data on the blockchain is successful, then the evidence-stored file to be verified is deemed successful, and an evidence verification report is generated.

[0010] Furthermore, the method also includes:

[0011] Receive the file to be stored and obtain the digital certificate of the target user who uploaded the file;

[0012] The hash value of the file to be stored is signed based on the obtained digital certificate to obtain signature data, which includes a signature timestamp and the signature information of the digital certificate.

[0013] The file identifier, hash value, and signature data of the file to be stored are packaged together to obtain the stored evidence on the blockchain, and the obtained stored evidence on the blockchain is uploaded to the blockchain.

[0014] The file identifier of the document to be certified and its signature timestamp are stored in the timestamp lookup table.

[0015] Furthermore, the signature verification of the stored evidence data on the blockchain includes:

[0016] The target digital certificate is determined based on the file identifier of the evidence-stored file to be verified.

[0017] If the number of the target digital certificates is determined to be one, then the determined target digital certificate is compared with the digital certificates stored in the evidence storage blockchain data;

[0018] If the target digital certificate is found to be compatible with the digital certificate stored in the on-chain evidence storage data, then the signature verification of the on-chain evidence storage data is deemed successful.

[0019] Furthermore, after determining the target digital certificate based on the file identifier of the evidence-stored file to be verified, the process further includes:

[0020] If the number of target digital certificates is greater than one, then the target user for each target digital certificate is determined separately.

[0021] Based on the evidence to be verified, a verification broadcast is sent to each target user, and a broadcast response from each target user to the verification broadcast is received.

[0022] If the received broadcast response meets the preset verification and authorization conditions, then each target digital certificate is compared with the digital certificate stored in the evidence storage on-chain data.

[0023] If each target digital certificate is matched with the digital certificate stored in the on-chain evidence storage data, then the signature verification of the on-chain evidence storage data is deemed successful.

[0024] Furthermore, the timestamp verification of the stored evidence data includes:

[0025] The file identifier of the evidence to be verified is matched with the timestamp lookup table to obtain the target timestamp;

[0026] Compare the target timestamp with the signature timestamp in the on-chain evidence storage data;

[0027] If the target timestamp is the same as the signature timestamp in the on-chain evidence storage data, then the timestamp verification of the on-chain evidence storage data is deemed successful.

[0028] Further, after matching the file identifier of the evidence-providing document to be verified with the timestamp lookup table to obtain the target timestamp, the process also includes:

[0029] If the number of matched target timestamps is greater than one, then the number of matched target timestamps is compared with the number of signature timestamps in the on-chain evidence storage data;

[0030] If the number of the target timestamps matched is the same as the number of signature timestamps in the on-chain data of the evidence storage, then the digital certificate corresponding to each target timestamp is obtained respectively.

[0031] Based on the obtained digital certificate, determine the corresponding comparison timestamp in the on-chain data of the evidence storage for each target timestamp, and compare each target timestamp with the corresponding comparison timestamp.

[0032] If each target timestamp is the same as the corresponding timestamp to be compared, then the timestamp verification of the evidence-stored on-chain data is deemed qualified.

[0033] Furthermore, the generation of the evidence verification report includes:

[0034] The notarization time point is generated based on the signature timestamp in the notarized on-chain data, and the block hash value of the blockchain corresponding to the notarized on-chain data is determined.

[0035] The evidence verification report is generated based on the file hash value, signature information, evidence storage time point, and block hash value in the evidence storage on-chain data.

[0036] A second aspect of this application provides a blockchain-based evidence verification device, comprising:

[0037] The on-chain data acquisition unit is used to determine the blockchain on-chain information based on the file identifier of the evidence storage file to be verified, and to acquire the evidence storage on-chain data based on the determined blockchain on-chain information.

[0038] The summary information acquisition unit is used to acquire the summary information to be verified in the evidence storage file to be verified, and to determine the associated summary information of the evidence storage on-chain data based on the summary information to be verified.

[0039] The signature verification unit is used to perform digest verification on the evidence storage file to be verified based on the digest information to be verified and the associated digest information. If the digest verification of the evidence storage file to be verified is qualified, the signature verification is performed on the evidence storage data on the blockchain.

[0040] The verification report generation unit is used to perform timestamp verification on the evidence-stored on-chain data if the signature verification of the evidence-stored on-chain data is qualified, and if the timestamp verification of the evidence-stored on-chain data is qualified, determine that the evidence-stored file to be verified is qualified and generate an evidence-stored verification report.

[0041] A third aspect of this application provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the computer device, wherein the processor executes the computer program to implement the steps of the blockchain-based evidence verification method provided in the first aspect.

[0042] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the blockchain-based evidence verification method provided in the first aspect.

[0043] This application provides a blockchain-based evidence verification method, apparatus, computer equipment, and medium. By performing signature verification on the blockchain data, it verifies whether the blockchain data was uploaded by the holder of the document to be verified. By performing timestamp verification on the blockchain data, it verifies the timestamp time of the corresponding document, improving the accuracy of the evidence verification. By combining signature verification and timestamp verification steps, when the document to be verified is issued, a digest verification is performed on the document based on the digest information to be verified and the associated digest information. While ensuring that the document to be verified has not been tampered with, the signature verification and timestamp verification further verify that the document has not been tampered with since being uploaded to the blockchain, improving the credibility and public trust of the evidence verification report. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0045] Figure 1 This is a flowchart illustrating the implementation of a blockchain-based evidence verification method provided in this application embodiment;

[0046] Figure 2 This is a flowchart illustrating the implementation of a blockchain-based evidence verification method according to another embodiment of this application.

[0047] Figure 3 This is a structural block diagram of a blockchain-based evidence verification device provided in an embodiment of this application;

[0048] Figure 4 This is a structural block diagram of a computer device provided in an embodiment of this application. Detailed Implementation

[0049] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0050] A blockchain is a continuously growing list of records (blocks) linked together using cryptographic methods. These blocks are immutable, public, and transparent. Nodes in a blockchain can construct real-world data into a standard transaction format supported by the blockchain and publish it. The blockchain's nodes then process these transactions through consensus. Once consensus is reached, the ledger nodes package the transaction into a block for persistent storage within the blockchain.

[0051] In this embodiment of the application, a blockchain-based evidence verification method is implemented. The method performs digest verification on the evidence file to be verified based on the digest information to be verified and the associated digest information. Under the premise of ensuring that the evidence file to be verified has not been tampered with, the method further verifies that the evidence file to be verified has not been tampered with since it was uploaded to the blockchain based on signature verification and timestamp verification, thereby improving the credibility and public trust of the evidence verification report.

[0052] Please see Figure 1 , Figure 1 This document illustrates a flowchart of an implementation of a blockchain-based evidence verification method according to an embodiment of this application. This blockchain-based evidence verification method is applicable to any computer device, such as a server, mobile phone, tablet, or wearable smart device. The blockchain-based evidence verification method includes:

[0053] Step S10: Determine the blockchain on-chain information based on the file identifier of the evidence to be verified, and obtain the evidence on-chain data based on the determined blockchain on-chain information.

[0054] The blockchain-based evidence verification method is applied to a server that communicates with a pre-set blockchain. The number of pre-set blockchains can be set according to requirements. The file identifier can be stored in the form of text, numbers, numbers or images, and can also be encoded based on any encoding algorithm. Each file identifier represents a corresponding evidence file.

[0055] In this step, the blockchain information is obtained by matching the file identifier of the document to be verified with the pre-stored blockchain on-chain table. The blockchain on-chain table stores the correspondence between different file identifiers and corresponding blockchain on-chain information. The blockchain on-chain information is used to characterize the storage address of the corresponding on-chain data in the blockchain. Therefore, in this step, the on-chain data corresponding to the document to be verified can be effectively obtained by using the blockchain on-chain information.

[0056] Optionally, in this step, the method further includes:

[0057] Receive the file to be stored and obtain the digital certificate of the target user who uploaded the file;

[0058] Specifically, by obtaining the user identifier of the target user corresponding to the file to be stored, and matching the user identifier with the pre-stored certificate lookup table, the digital certificate of the target user is obtained. The target user is the file uploader corresponding to the file to be stored. The certificate lookup table stores the correspondence between different user identifiers and corresponding digital certificates.

[0059] The hash value of the file to be stored is signed based on the obtained digital certificate to obtain signature data, which includes a signature timestamp and the signature information of the digital certificate.

[0060] The signature data includes a signature timestamp and signature information from a digital certificate. The hash value of the document to be stored is signed using the obtained digital certificate to achieve digital signature authentication of the document.

[0061] The file identifier, hash value, and signature data of the file to be stored are packaged together to obtain the stored evidence on the blockchain, and the obtained stored evidence on the blockchain is uploaded to the blockchain.

[0062] In particular, by packaging the file identifier, hash value and signature data of the file to be stored, the uploading operation of the stored data on the blockchain is facilitated, and by uploading the stored data on the blockchain, modification of the stored data on the blockchain is prevented.

[0063] The file identifier of the document to be certified is stored in a timestamp lookup table in correspondence with the signature timestamp. By storing the file identifier of the document to be certified in correspondence with the signature timestamp, it is convenient to determine the target timestamp in the future.

[0064] Step S20: Obtain the digest information to be verified in the evidence storage file to be verified, and determine the associated digest information of the evidence storage on-chain data based on the digest information to be verified.

[0065] Specifically, a hash value algorithm can be used to obtain the digest information of the evidence to be verified in the evidence file to be verified. The digest information and file identifier of the evidence file to be verified are then matched with a pre-stored irreversible algorithm lookup table to obtain the target irreversible algorithm. Based on the matched target irreversible algorithm, the evidence file to be verified in the evidence-on-chain data is decrypted to obtain the associated digest information of the evidence-on-chain data.

[0066] It should be noted that the irreversible algorithm lookup table stores the correspondence between different unverified digest information, file identifiers and corresponding irreversible algorithms. In this step, if the unverified digest information and file identifier of the evidence-preserving file do not match the irreversible algorithm lookup table, the unverified file in the evidence-preserving data on the blockchain is decrypted and calculated according to the default irreversible algorithm pre-stored locally on the server to obtain the associated digest information of the evidence-preserving data on the blockchain. The default irreversible algorithm pre-stored locally on the server can be set according to requirements.

[0067] Step S30: Perform digest verification on the evidence storage file to be verified based on the digest information to be verified and the associated digest information;

[0068] Among them, similarity matching, entity matching or correspondence matching can be used to verify the information between the summary information to be verified and the associated summary information. If the information verification between the summary information to be verified and the associated summary information is qualified, the summary verification of the evidence storage file to be verified is deemed qualified.

[0069] In this step, the information similarity between the summary information to be verified and the associated summary information is calculated, and it is determined whether the calculated information similarity is the preset similarity. If the calculated information similarity is the preset similarity, the information verification between the summary information to be verified and the associated summary information is deemed to be qualified.

[0070] Optionally, entity recognition can be performed on the summary information to be verified and the associated summary information separately to obtain the first entity and the second entity, and it can be determined whether the first entity and the second entity are the same. If the first entity and the second entity are the same, it is determined that the information verification between the summary information to be verified and the associated summary information is qualified.

[0071] Furthermore, entity recognition can be performed on the summary information to be verified and the associated summary information separately to obtain the first entity and the second entity. Then, it can be determined whether there is a preset correspondence between the first entity and the second entity according to the pre-stored relationship matching lookup table. The relationship matching lookup table stores the preset correspondence between different entities. If there is a preset correspondence between the first entity and the second entity, then the information verification between the summary information to be verified and the associated summary information is deemed to be qualified.

[0072] Step S40: If the digest verification of the evidence-stored document to be verified is qualified, then the signature verification of the evidence-stored data on the blockchain is performed.

[0073] If the information verification between the digest information to be verified and the associated digest information is successful, the digest verification of the evidence storage file to be verified is deemed successful. If the digest verification of the evidence storage file to be verified is successful, the on-chain data of the evidence storage is signed and verified to further verify whether the evidence storage file to be verified has been tampered with.

[0074] Optionally, in this step, if the digest verification of the evidence document to be verified fails, it is determined that the evidence document to be verified has been tampered with, that is, the evidence document to be verified is an invalid document.

[0075] Step S50: If the signature verification of the evidence-stored data on the blockchain is qualified, then the timestamp verification of the evidence-stored data on the blockchain is performed.

[0076] If the signature verification of the evidence-stored data on the blockchain is qualified, the timestamp verification of the evidence-stored data on the blockchain is performed to verify the timestamp time of the file corresponding to the evidence-stored data on the blockchain, which further improves the accuracy of the evidence verification of the evidence-stored file to be verified.

[0077] Optionally, in this step, the timestamp verification of the stored evidence data includes:

[0078] The file identifier of the evidence to be verified is matched with the timestamp lookup table to obtain the target timestamp, and the target timestamp is compared with the signature timestamp in the evidence on-chain data.

[0079] If the target timestamp is the same as the signature timestamp in the evidence-on-chain data, then the timestamp verification of the evidence-on-chain data is deemed qualified.

[0080] Specifically, by matching the file identifier of the evidence to be verified with the timestamp lookup table, the target timestamp corresponding to the evidence to be verified is determined. Then, by comparing the target timestamp with the signature timestamp in the evidence-on-chain data, it is determined whether there has been any tampering between the evidence-on-chain data and the evidence to be verified in the corresponding evidence-on-chain data.

[0081] Further, in this step, after matching the file identifier of the evidence-providing document to be verified with the timestamp lookup table to obtain the target timestamp, the method further includes:

[0082] If the number of matched target timestamps is greater than one, then the number of matched target timestamps is compared with the number of signature timestamps in the on-chain evidence storage data;

[0083] If the number of matched target timestamps is greater than one, it is determined that multiple signature objects have digitally signed the document to be verified. In this step, the number of matched target timestamps is compared with the number of signature timestamps in the on-chain data to determine whether the document to be verified has been tampered with.

[0084] If the number of the target timestamps matched is the same as the number of signature timestamps in the on-chain data of the evidence storage, then the digital certificate corresponding to each target timestamp is obtained respectively.

[0085] Based on the obtained digital certificate, determine the corresponding comparison timestamp in the on-chain data of the evidence storage for each target timestamp, and compare each target timestamp with the corresponding comparison timestamp.

[0086] Among them, based on the obtained digital certificate, the corresponding comparison timestamp in the on-chain data of the evidence storage is determined for each target timestamp, which improves the accuracy of the comparison between each target timestamp and the corresponding comparison timestamp. Furthermore, by comparing each target timestamp with the corresponding comparison timestamp, the correctness of the target timestamp is detected. Based on the detection results of the target timestamp, it is determined whether the evidence storage file to be verified has been tampered with.

[0087] If each target timestamp is the same as the corresponding timestamp to be compared, then the timestamp verification of the evidence-stored on-chain data is deemed qualified.

[0088] If each target timestamp is the same as the corresponding timestamp to be compared, the timestamp verification of the evidence stored on the blockchain is deemed to be qualified, that is, the target timestamps on the evidence storage file to be verified are accurate and have not been tampered with.

[0089] Furthermore, in this step, if the signature verification and / or timestamp verification of the document to be verified fails, it is determined that the document to be verified has been tampered with, that is, the document to be verified is an invalid document.

[0090] Step S60: If the timestamp verification of the evidence storage data is qualified, the evidence storage file to be verified is determined to be qualified, and an evidence storage verification report is generated.

[0091] If the digest verification, signature verification, and / or timestamp verification of the document to be verified are all qualified, then the document to be verified is determined to be untampered and the verification of the document to be verified is qualified. Optionally, generating the document verification report includes:

[0092] The notarization time point is generated based on the signature timestamp in the notarized on-chain data, and the block hash value of the blockchain corresponding to the notarized on-chain data is determined.

[0093] The evidence verification report is generated based on the file hash value, signature information, evidence storage time point, and block hash value in the evidence storage on-chain data.

[0094] Specifically, the evidence verification report is generated by outputting the file hash value, signature information, evidence storage time point, and block hash value from the evidence storage data on the blockchain.

[0095] In this embodiment, signature verification is performed on the on-chain data to verify whether the on-chain operation was performed by the holder of the document to be verified. Timestamp verification is performed on the on-chain data to verify the timestamp time of the document to be verified, thus improving the accuracy of the verification of the document to be verified. By combining signature verification and timestamp verification steps, when the document to be verified is issued, a digest verification is performed on the document to be verified based on the digest information to be verified and the associated digest information. Under the premise of ensuring that the document to be verified has not been tampered with, signature verification and timestamp verification are used to further verify that the document to be verified has not been tampered with since it was uploaded to the chain, thereby improving the credibility and public trust of the verification report.

[0096] Please see Figure 2 , Figure 2 This is a flowchart illustrating the implementation of a blockchain-based evidence verification method according to another embodiment of this application. Compared to... Figure 1 This embodiment provides a blockchain-based evidence verification method for... Figure 1 Step S40 in the embodiment is further refined, including:

[0097] Step S41: Determine the target digital certificate based on the file identifier of the evidence-stored file to be verified;

[0098] Specifically, the target digital certificate is obtained by matching the file identifier of the evidence-stored file to be verified with the certificate lookup table. Optionally, one file identifier in the certificate lookup table can correspond to multiple target digital certificates, that is, multiple users can digitally sign the same evidence-stored file to be verified.

[0099] Step S42: If the number of the target digital certificates is determined to be one, then the determined target digital certificate is compared with the digital certificates stored in the evidence storage blockchain data.

[0100] If the number of target digital certificates is one, the target digital certificate is compared with the digital certificate stored in the on-chain evidence storage data to determine whether the evidence storage file to be verified has been tampered with.

[0101] Step S43: If the target digital certificate is matched with the digital certificate stored in the evidence-on-chain data, then the signature verification of the evidence-on-chain data is deemed to be qualified.

[0102] Optionally, after determining the target digital certificate based on the file identifier of the document to be verified, this step further includes:

[0103] If the number of target digital certificates is greater than one, then the target user for each target digital certificate is determined separately.

[0104] If the number of target digital certificates is greater than one, the target user of each target digital certificate is determined separately, which facilitates the subsequent sending of the evidence verification broadcast.

[0105] Based on the evidence to be verified, a verification broadcast is sent to each target user, and a broadcast response from each target user to the verification broadcast is received.

[0106] Specifically, the method involves sending a verification broadcast to each target user based on the evidence file to be verified, in order to prompt each target user whether to authorize the verification of the evidence file to be verified.

[0107] If the received broadcast response meets the preset verification and authorization conditions, then each target digital certificate is compared with the digital certificate stored in the evidence storage on-chain data.

[0108] If the received broadcast response meets the preset verification and authorization conditions, the signature verification of the evidence-on-chain data is determined by comparing each target digital certificate with the digital certificate stored in the evidence-on-chain data.

[0109] If each target digital certificate is matched with the digital certificate stored in the evidence-on-chain data, then the signature verification of the evidence-on-chain data is deemed to be qualified.

[0110] In this embodiment, the target digital certificate is obtained by matching the file identifier of the evidence storage file to be verified with the certificate lookup table. If the number of target digital certificates is one, the target digital certificate is compared with the digital certificates stored in the evidence storage blockchain data to determine whether the evidence storage file to be verified has been tampered with. If the number of target digital certificates is more than one, the target users of each target digital certificate are determined separately, which facilitates the subsequent sending of evidence storage verification broadcasts. Evidence storage verification broadcasts are sent to each target user according to the evidence storage file to be verified to prompt each target user whether to authorize the verification of the evidence storage file to be verified.

[0111] Please see Figure 3 , Figure 3 This is a structural block diagram of a blockchain-based evidence verification device 100 provided in this application embodiment. In this embodiment, the blockchain-based evidence verification device 100 includes units used for performing... Figure 1 , Figure 2 The steps in the corresponding embodiments. Please refer to the details. Figure 1 , Figure 2 as well as Figure 1 , Figure 2 The relevant descriptions in the corresponding embodiments are shown below. For ease of explanation, only the parts relevant to this embodiment are shown. See also... Figure 3 The blockchain-based evidence verification device 100 includes: an on-chain data acquisition unit 10, a digest information acquisition unit 11, a signature verification unit 12, and a verification report generation unit 13, wherein:

[0112] The on-chain data acquisition unit 10 is used to determine the on-chain information of the blockchain based on the file identifier of the evidence storage file to be verified, and to acquire the on-chain data of the evidence storage based on the determined on-chain information of the blockchain.

[0113] Optionally, the on-chain data acquisition unit 10 is further configured to: receive the file to be stored and acquire the digital certificate of the target user corresponding to the file to be stored;

[0114] The hash value of the file to be stored is signed based on the obtained digital certificate to obtain signature data, which includes a signature timestamp and the signature information of the digital certificate.

[0115] The file identifier, hash value, and signature data of the file to be stored are packaged to obtain the storage data on the blockchain, and the storage data on the blockchain is uploaded to the blockchain.

[0116] The file identifier of the document to be certified and its signature timestamp are stored in the timestamp lookup table.

[0117] The summary information acquisition unit 11 is used to acquire the summary information to be verified in the evidence storage file to be verified, and to determine the associated summary information of the evidence storage on-chain data based on the summary information to be verified.

[0118] The signature verification unit 12 is used to perform digest verification on the evidence storage file to be verified based on the digest information to be verified and the associated digest information. If the digest verification of the evidence storage file to be verified is qualified, the signature verification is performed on the evidence storage data on the blockchain.

[0119] Optionally, the signature verification unit 12 is further configured to: determine the target digital certificate based on the file identifier of the document to be verified;

[0120] If the number of the target digital certificates is determined to be one, then the determined target digital certificate is compared with the digital certificates stored in the evidence storage blockchain data;

[0121] If the target digital certificate is found to be compatible with the digital certificate stored in the on-chain evidence storage data, then the signature verification of the on-chain evidence storage data is deemed successful.

[0122] Furthermore, the signature verification unit 12 is also used to: if the number of the determined target digital certificates is greater than one, then determine the target user of each target digital certificate respectively;

[0123] Based on the evidence to be verified, a verification broadcast is sent to each target user, and a broadcast response from each target user to the verification broadcast is received.

[0124] If the received broadcast response meets the preset verification and authorization conditions, then each target digital certificate is compared with the digital certificate stored in the evidence storage on-chain data.

[0125] If each target digital certificate is matched with the digital certificate stored in the on-chain evidence storage data, then the signature verification of the on-chain evidence storage data is deemed successful.

[0126] The verification report generation unit 13 is used to perform timestamp verification on the evidence-on-chain data if the signature verification of the evidence-on-chain data is qualified, and to determine that the evidence-on-chain file to be verified is qualified if the timestamp verification of the evidence-on-chain data is qualified, and to generate an evidence verification report.

[0127] Optionally, the verification report generation unit 13 is further configured to: match the file identifier of the evidence to be verified with the timestamp lookup table to obtain the target timestamp;

[0128] Compare the target timestamp with the signature timestamp in the on-chain evidence storage data;

[0129] If the target timestamp is the same as the signature timestamp in the on-chain evidence storage data, then the timestamp verification of the on-chain evidence storage data is deemed successful.

[0130] Furthermore, the verification report generation unit 13 is also used to: if the number of matched target timestamps is greater than one, compare the number of matched target timestamps with the number of signature timestamps in the evidence storage on-chain data;

[0131] If the number of the target timestamps matched is the same as the number of signature timestamps in the on-chain data of the evidence storage, then the digital certificate corresponding to each target timestamp is obtained respectively.

[0132] Based on the obtained digital certificate, determine the corresponding comparison timestamp in the on-chain data of the evidence storage for each target timestamp, and compare each target timestamp with the corresponding comparison timestamp.

[0133] If each target timestamp is the same as the corresponding timestamp to be compared, then the timestamp verification of the evidence-stored on-chain data is deemed qualified.

[0134] Furthermore, the verification report generation unit 13 is also used to: generate a storage time point based on the signature timestamp in the storage data, and determine the block hash value of the blockchain corresponding to the storage data;

[0135] The evidence verification report is generated based on the file hash value, signature information, evidence storage time point, and block hash value in the evidence storage on-chain data.

[0136] In this embodiment, signature verification is performed on the on-chain data to verify whether the on-chain operation was performed by the holder of the document to be verified. Timestamp verification is performed on the on-chain data to verify the timestamp time of the document to be verified, thus improving the accuracy of the verification of the document to be verified. By combining signature verification and timestamp verification steps, when the document to be verified is issued, a digest verification is performed on the document to be verified based on the digest information to be verified and the associated digest information. Under the premise of ensuring that the document to be verified has not been tampered with, signature verification and timestamp verification are used to further verify that the document to be verified has not been tampered with since it was uploaded to the chain, thereby improving the credibility and public trust of the verification report.

[0137] Figure 4 This is a structural block diagram of a computer device 2 provided in another embodiment of this application. For example... Figure 4As shown, the computer device 2 in this embodiment includes: a processor 20, a memory 21, and a computer program 22 stored in the memory 21 and executable on the processor 20, such as a program for a blockchain-based evidence verification method. When the processor 20 executes the computer program 22, it implements the steps in the various embodiments of the blockchain-based evidence verification methods described above, for example... Figure 1 S10 to S60 as shown, or Figure 2 S41 to S43 are shown. Alternatively, the processor 20 implements the above when executing the computer program 22. Figure 3 The functions of each unit in the corresponding embodiments, for example, Figure 3 For details on the functions of units 10 to 13 shown, please refer to [link / reference needed]. Figure 3 The relevant descriptions in the corresponding embodiments are not repeated here.

[0138] For example, the computer program 22 can be divided into one or more units, which are stored in the memory 21 and executed by the processor 20 to complete this application. The one or more units can be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program 22 in the computer device 2. For example, the computer program 22 can be divided into an on-chain data acquisition unit 10, a digest information acquisition unit 11, a signature verification unit 12, and a verification report generation unit 13, with the specific functions of each unit as described above.

[0139] The computer device may include, but is not limited to, a processor 20 and a memory 21. Those skilled in the art will understand that... Figure 4 This is merely an example of computer device 2 and does not constitute a limitation on computer device 2. It may include more or fewer components than shown, or combine certain components, or different components. For example, the computer device may also include input / output devices, network access devices, buses, etc.

[0140] The processor 20 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0141] The memory 21 can be an internal storage unit of the computer device 2, such as a hard disk or memory of the computer device 2. The memory 21 can also be an external storage device of the computer device 2, such as a plug-in hard disk, SmartMedia Card (SMC), Secure Digital (SD) card, or Flash Card equipped on the computer device 2. Furthermore, the memory 21 can include both internal and external storage units of the computer device 2. The memory 21 is used to store the computer program and other programs and data required by the computer device. The memory 21 can also be used to temporarily store data that has been output or will be output.

[0142] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0143] If an integrated module is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. This computer-readable storage medium can be non-volatile or volatile. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable storage medium can include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the contents of a computer-readable storage medium may be appropriately added to or subtracted from the contents as required by the legislation and patent practice in a jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, a computer-readable storage medium may not include electrical carrier signals and telecommunication signals.

[0144] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A blockchain-based method for evidence storage and verification, characterized in that, include: Based on the file identifier of the evidence to be verified, it is matched with the pre-stored blockchain on-chain list to determine the blockchain on-chain information, and the evidence on-chain data is obtained based on the determined blockchain on-chain information. The blockchain on-chain information is used to characterize the storage address of the corresponding evidence on-chain data in the blockchain. Obtain the digest information to be verified from the file to be verified, and match the digest information to be verified and the file identifier with a pre-stored irreversible algorithm lookup table to obtain the target irreversible algorithm. Decrypt the file to be verified in the on-chain data of the evidence storage according to the matched target irreversible algorithm to determine the associated digest information of the on-chain data of the evidence storage. The digest verification of the evidence storage file to be verified is performed based on the digest information to be verified and the associated digest information. If the digest verification of the evidence storage file to be verified is qualified, the signature verification of the evidence storage data on the blockchain is performed. If the signature verification of the evidence-stored data on the blockchain is qualified, then the timestamp verification of the evidence-stored data on the blockchain is performed. If the timestamp verification of the evidence-stored data on the blockchain is qualified, then the evidence-stored file to be verified is determined to be qualified, and an evidence-stored verification report is generated. Specifically, the file identifier of the document to be certified is stored in a timestamp lookup table along with the signature timestamp; The timestamp verification of the stored evidence data includes: The file identifier of the evidence to be verified is matched with the timestamp lookup table to obtain the target timestamp; Compare the target timestamp with the signature timestamp in the on-chain evidence storage data; After matching the file identifier of the evidence-providing file to be verified with the timestamp lookup table to obtain the target timestamp, the method further includes: If the number of matched target timestamps is greater than one, then the number of matched target timestamps is compared with the number of signature timestamps in the on-chain evidence storage data; If the number of the target timestamps matched is the same as the number of signature timestamps in the on-chain data of the evidence storage, then the digital certificate corresponding to each target timestamp is obtained respectively. Based on the obtained digital certificate, the corresponding timestamp to be compared in the on-chain data of the evidence storage is determined for each target timestamp, and each target timestamp is compared with the corresponding timestamp to be compared.

2. The blockchain-based evidence verification method according to claim 1, characterized in that, The method further includes: Receive the file to be stored and obtain the digital certificate of the target user who uploaded the file; The hash value of the file to be stored is signed based on the obtained digital certificate to obtain signature data, which includes a signature timestamp and the signature information of the digital certificate. The file identifier, hash value, and signature data of the document to be stored are packaged together to obtain the stored evidence data on the blockchain, and the obtained stored evidence data on the blockchain is uploaded to the blockchain.

3. The blockchain-based evidence verification method according to claim 1, characterized in that, The signature verification of the stored and on-chain data includes: The target digital certificate is determined based on the file identifier of the evidence-stored file to be verified. If the number of the target digital certificates is determined to be one, then the determined target digital certificate is compared with the digital certificates stored in the evidence storage blockchain data; If the target digital certificate is found to be compatible with the digital certificate stored in the on-chain evidence storage data, then the signature verification of the on-chain evidence storage data is deemed successful.

4. The blockchain-based evidence verification method according to claim 3, characterized in that, After determining the target digital certificate based on the file identifier of the evidence-stored file to be verified, the method further includes: If the number of target digital certificates is greater than one, then the target user for each target digital certificate is determined separately. Based on the evidence to be verified, a verification broadcast is sent to each target user, and a broadcast response from each target user to the verification broadcast is received. If the received broadcast response meets the preset verification and authorization conditions, then each target digital certificate is compared with the digital certificate stored in the evidence storage on-chain data. If each target digital certificate is matched with the digital certificate stored in the on-chain evidence storage data, then the signature verification of the on-chain evidence storage data is deemed successful.

5. The blockchain-based evidence verification method according to claim 2, characterized in that, If the target timestamp is the same as the signature timestamp in the on-chain evidence storage data, then the timestamp verification of the on-chain evidence storage data is deemed successful.

6. The blockchain-based evidence verification method according to claim 2, characterized in that, If each target timestamp is the same as the corresponding timestamp to be compared, then the timestamp verification of the evidence-stored on-chain data is deemed qualified.

7. The blockchain-based evidence verification method according to any one of claims 1 to 6, characterized in that, The generation of the evidence verification report includes: The notarization time point is generated based on the signature timestamp in the notarized on-chain data, and the block hash value of the blockchain corresponding to the notarized on-chain data is determined. The evidence verification report is generated based on the file hash value, signature information, evidence storage time point, and block hash value in the evidence storage on-chain data.

8. A blockchain-based evidence storage and verification device, characterized in that, include: The on-chain data acquisition unit is used to match the file identifier of the evidence storage file to be verified with the pre-stored blockchain on-chain table to determine the blockchain on-chain information, and to acquire the evidence storage on-chain data according to the determined blockchain on-chain information. The blockchain on-chain information is used to characterize the storage address of the corresponding evidence storage on-chain data in the blockchain. The digest information acquisition unit is used to acquire the digest information to be verified in the evidence storage file to be verified, and match the digest information to be verified and the file identifier with a pre-stored irreversible algorithm lookup table to obtain the target irreversible algorithm. The unit then performs decryption calculation on the evidence storage file in the evidence storage on-chain data according to the matched target irreversible algorithm to determine the associated digest information of the evidence storage on-chain data. The signature verification unit is used to perform digest verification on the evidence storage file to be verified based on the digest information to be verified and the associated digest information. If the digest verification of the evidence storage file to be verified is qualified, the signature verification is performed on the evidence storage data on the blockchain. The verification report generation unit is used to perform timestamp verification on the evidence-stored on-chain data if the signature verification of the evidence-stored on-chain data is qualified; if the timestamp verification of the evidence-stored on-chain data is qualified, the unit determines that the evidence-stored file to be verified is qualified and generates an evidence-stored verification report. Specifically, the file identifier of the document to be certified is stored in a timestamp lookup table along with the signature timestamp; The verification report generation unit is also used to match the file identifier of the evidence-stored file to be verified with the timestamp lookup table to obtain the target timestamp; and compare the target timestamp with the signature timestamp in the evidence-stored on-chain data; If the number of matched target timestamps is greater than one, then the number of matched target timestamps is compared with the number of signature timestamps in the on-chain evidence storage data; If the number of the target timestamps matched is the same as the number of signature timestamps in the on-chain data of the evidence storage, then the digital certificate corresponding to each target timestamp is obtained respectively. Based on the obtained digital certificate, the corresponding timestamp to be compared in the on-chain data of the evidence storage is determined for each target timestamp, and each target timestamp is compared with the corresponding timestamp to be compared.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 7.

Images