CN117251883B - Data reliability verification method, device, computer equipment and storage medium - Google Patents
Data reliability verification method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN117251883B CN117251883B CN202311449833.1A CN202311449833A CN117251883B CN 117251883 B CN117251883 B CN 117251883B CN 202311449833 A CN202311449833 A CN 202311449833A CN 117251883 B CN117251883 B CN 117251883B
- Authority
- CN
- China
- Prior art keywords
- data
- certificate
- chain
- verification result
- verification
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012795 verification Methods 0.000 title claims abstract description 318
- 238000000034 method Methods 0.000 title claims abstract description 58
- 238000013524 data verification Methods 0.000 claims abstract description 65
- 230000004044 response Effects 0.000 claims abstract description 16
- 230000001960 triggered effect Effects 0.000 claims abstract description 11
- 238000004590 computer program Methods 0.000 claims description 21
- 238000004891 communication Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000008520 organization Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000012512 characterization method Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000012800 visualization Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 238000013079 data visualisation Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Storage Device Security (AREA)
Abstract
The application relates to a data reliability verification method, a data reliability verification device, computer equipment and a storage medium. The method comprises the following steps: responding to a data acquisition request triggered by a user, and synchronizing the data acquisition request to a target block chain; receiving the data on the chain, which is returned by the target block chain in response to the data acquisition request and contains target data, a certificate signature and a node certificate; according to a preset root certificate, verifying the data on the chain to obtain a data verification result corresponding to the data on the chain; and acquiring a block verification result aiming at the target block chain, and determining a reliability verification result aiming at the data acquisition request according to the data verification result and the block verification result. By adopting the method, the component parts of the data on the chain can be verified step by step, and by combining with the verification result corresponding to the blockchain, whether the data on the chain is the real data which is not tampered from the target blockchain or not can be judged, so that the reliability of the acquired data on the chain is improved while the data on the chain is acquired rapidly.
Description
Technical Field
The present application relates to the field of blockchain technologies, and in particular, to a data reliability verification method, apparatus, computer device, storage medium, and computer program product.
Background
The blockchain browser can be used as a main window for visualization of data on a chain, and is used for recording and counting information such as blocks, transactions, addresses and the like of different blockchain networks, and along with the wide application of the blockchain technology, a user can acquire related data and information by accessing the blockchain browser.
Conventional techniques often rely entirely on the server, i.e., the default determines that the data on the chain obtained by the blockchain browser is correct and does not verify the correctness of the data.
However, the risk of tampering the data exists in the process of acquiring the data by the user through the blockchain browser, so that the data cannot be ensured to be completely reliable, and the reliability of the data on the chain cannot be improved.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a data reliability verification method, apparatus, computer device, computer-readable storage medium, and computer program product that enable reliability verification of on-chain data.
In a first aspect, the present application provides a data reliability verification method, the method comprising:
Responding to a data acquisition request triggered by a user, and synchronizing the data acquisition request to a target block chain; the data acquisition request is used for controlling the blocks of the target block chain to simultaneously request data from the corresponding nodes;
Receiving on-chain data returned by the target blockchain in response to the data acquisition request; the on-chain data comprises target data, a certificate signature corresponding to the target data and a node certificate corresponding to the certificate signature; the target data are data obtained from nodes corresponding to the blocks of the target block chain; nodes corresponding to all blocks of the target block chain are different from each other;
Verifying the data on the chain according to at least one preset root certificate to obtain a data verification result corresponding to the data on the chain;
Acquiring a block verification result aiming at the target block chain, and determining a reliability verification result aiming at the data acquisition request according to the data verification result and the block verification result; the block verification result represents whether each block in the target block chain passes hash verification or not; the reliability verification result characterizes whether the on-chain data is real data from the target blockchain.
In one embodiment, the verifying the on-chain data according to the preset root certificate, to obtain a data verification result corresponding to the on-chain data, includes:
according to the preset root certificate and a preset certificate decryption mode, verifying a node certificate in the on-chain data to obtain a certificate verification result of the node certificate;
Under the condition that the certificate verification result represents that the node certificate passes verification, verifying a certificate signature corresponding to the node certificate according to the node certificate and a preset signature verification mode to obtain a signature verification result corresponding to the certificate signature;
and determining a data verification result corresponding to the data on the chain according to the certificate verification result and the signature verification result.
In one embodiment, the verifying the node certificate in the on-chain data according to the preset root certificate and the preset certificate decryption mode to obtain a certificate verification result of the node certificate includes:
Determining a public key corresponding to the node certificate in the on-chain data according to the preset root certificate;
Decrypting the node certificate in the data on the chain according to the public key to obtain a decryption result corresponding to the node certificate;
Determining a certificate verification result of the node certificate according to the decryption result; the certificate verification result characterizes whether the node certificate is legal or not.
In one embodiment, when the certificate verification result characterizes that the node certificate passes verification, verifying, according to the node certificate, a certificate signature corresponding to the node certificate according to a preset signature verification mode, to obtain a signature verification result corresponding to the certificate signature, including:
determining signature verification reference data corresponding to the node certificate according to the node certificate;
Determining data to be verified corresponding to the certificate signature according to the preset signature verification mode;
and comparing the signature verification reference data with the data to be verified to obtain a signature verification result corresponding to the certificate signature.
In one embodiment, the obtaining the block verification result for the target blockchain includes:
Acquiring a first hash value corresponding to a target block in the target block chain; the target block comprises any one block in the target block chain;
Acquiring a second hash value of an adjacent block corresponding to the target block;
Determining a block verification result for the target block according to the first hash value and the second hash value;
and obtaining block verification results corresponding to all blocks in the target block chain, and determining the block verification results aiming at the target block chain according to the block verification results corresponding to all blocks in the target block chain.
In one embodiment, the method further comprises:
Acquiring a data identifier corresponding to the data on the chain under the condition that the reliability verification result aiming at the data acquisition request characterizes the data on the chain as real data from the target blockchain;
at least one of the on-chain data or the data identification is presented.
In one embodiment, the method further comprises:
the on-chain data is presented in parallel, with a reliability verification result for the data acquisition request characterizing the on-chain data as real data from the target blockchain.
In a second aspect, the present application also provides a data reliability verification apparatus, the apparatus comprising:
The request synchronization module is used for responding to a data acquisition request triggered by a user and synchronizing the data acquisition request to a target block chain; the data acquisition request is used for controlling the blocks of the target block chain to simultaneously request data from the corresponding nodes;
The data receiving module is used for receiving the on-chain data returned by the target blockchain in response to the data acquisition request; the on-chain data comprises target data, a certificate signature corresponding to the target data and a node certificate corresponding to the certificate signature; the target data are data obtained from nodes corresponding to the blocks of the target block chain; nodes corresponding to all blocks of the target block chain are different from each other;
The data verification module is used for verifying the data on the chain according to a preset root certificate to obtain a data verification result corresponding to the data on the chain;
The reliable verification module is used for acquiring a block verification result aiming at the target block chain and determining a reliable verification result aiming at the data acquisition request according to the data verification result and the block verification result; the reliability verification result characterizes whether the on-chain data is real data from the target blockchain.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory and a processor, the memory storing a computer program which, when executed by the processor, implements the steps of the method described above.
In a fourth aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the method described above.
In a fifth aspect, the present application also provides a computer program product. The computer program product comprising a computer program which, when executed by a processor, implements the steps of the method described above.
According to the data reliability verification method, the device, the computer equipment, the storage medium and the computer program product, the data acquisition request is synchronized to the target blockchain by responding to the data acquisition request triggered by the user, so that the data acquisition request is timely transmitted to the target blockchain, the blocks of the target blockchain are controlled to simultaneously request data to the corresponding nodes, and the response speed of the data acquisition operation is improved; receiving the on-chain data returned by the target block chain in response to the data acquisition request, so as to obtain the on-chain data consisting of the target data, the certificate signature corresponding to the target data and the node certificate corresponding to the certificate signature, acquiring the certificate signature and the node certificate corresponding to the target data while acquiring the on-chain data from the nodes corresponding to the blocks (the nodes corresponding to the blocks of the target block chain are different from each other) by the block of the target block chain, and providing a basis for the subsequent data reliability verification; according to at least one preset root certificate, verifying the data on the chain to obtain a data verification result corresponding to the data on the chain, so that each component of the data on the chain is verified step by step based on the preset root certificate, and the accuracy and the strictness of the data verification process are ensured; the method comprises the steps of obtaining a block verification result representing whether each block in a target block chain passes hash verification, determining a reliability verification result aiming at a data obtaining request according to the data verification result and the block verification result, verifying whether data on the chain is real data from the target block chain based on the block verification result and the data verification result, obtaining the data on the chain returned by the target block chain after synchronizing the data obtaining request to the target block chain, based on a preset root certificate, obtaining the data verification result of the data on the chain according to a preset verification mode, and determining the reliability verification result aiming at the data obtaining request by combining the data verification result and the block verification result corresponding to the target block chain, so that the authenticity of the data on the chain is determined by utilizing the reliability verification result, and judging whether the data on the chain is the untampered real data from the target block chain by gradually verifying the component part of the data on the chain and combining the verification result corresponding to the block chain.
Drawings
FIG. 1 is an application environment diagram of a data reliability verification method in one embodiment;
FIG. 2 is a flow chart of a data reliability verification method according to one embodiment;
FIG. 3 is a flow chart of a method for verifying and displaying data reliability in one embodiment;
FIG. 4 is a block diagram of a data reliability verification device in one embodiment;
fig. 5 is an internal structural diagram of a computer device in one embodiment.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
The data reliability verification method provided by the embodiment of the application can be applied to an application environment shown in fig. 1. Wherein the terminal 102 communicates with the target blockchain 104 over a network. The terminal 102 synchronizes the data acquisition request to the target blockchain in response to the user-triggered data acquisition request; the data acquisition request is used for controlling the blocks of the target block chain and simultaneously requesting data from the corresponding nodes; the terminal 102 receives the on-chain data returned by the target blockchain in response to the data acquisition request; the on-chain data comprises target data, a certificate signature corresponding to the target data and a node certificate corresponding to the certificate signature; the target data is data obtained from nodes corresponding to the blocks of the target block chain; nodes corresponding to each block of the target block chain are different from each other; the terminal 102 verifies the data on the chain according to at least one preset root certificate to obtain a data verification result corresponding to the data on the chain; the terminal 102 acquires a block verification result aiming at a target block chain, and determines a reliability verification result aiming at a data acquisition request according to the data verification result and the block verification result; the block verification result represents whether each block in the target block chain passes the hash verification or not; the reliability verification results characterize whether the on-chain data is real data from the target blockchain. The terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices, and portable wearable devices. The portable wearable device may be a smart watch, smart bracelet, headset, or the like.
In some embodiments, as shown in fig. 2, a data reliability verification method is provided, where this embodiment is applied to a server for illustration, it is understood that the method may also be applied to a terminal, and may also be applied to a system including a terminal and a server, and implemented through interaction between the terminal and the server. In this embodiment, the method includes the steps of:
Step S202, responding to a data acquisition request triggered by a user, and synchronizing the data acquisition request to a target blockchain.
The user may refer to an object that sends a data acquisition request to the target blockchain through the terminal, and in practical application, the user may refer to a user or an operator of the terminal.
The data acquisition request may refer to data with a specific format or specific content, specifically, the data acquisition request is used for controlling a block of the target blockchain and simultaneously requesting data from a corresponding node, and in practical application, the content and format of the data acquisition request may include a request row, a request header, a request body, and the like.
The target blockchain may refer to a blockchain in which data that a user needs to acquire is located.
As an example, since the blockchain browser may be the primary window for visualization of data on the chain, a user may obtain desired data from a target blockchain through the blockchain browser on the terminal, and in particular, the user may operate the blockchain browser through the terminal, e.g., by clicking a data acquisition button on the blockchain browser on the terminal, to trigger a data acquisition request, the blockchain browser synchronizes the data acquisition request to the target blockchain in response to the data acquisition request, so that the target blockchain searches for or acquires data corresponding to the data acquisition request in response to the data acquisition request.
In step S204, the on-chain data returned by the target blockchain in response to the data acquisition request is received.
The on-chain data may refer to data that the target blockchain returns to the blockchain browser or the terminal, and in practical application, the on-chain data may include, but is not limited to, target data, a certificate signature corresponding to the target data, and a node certificate corresponding to the certificate signature.
The target data may refer to data obtained by a block of the target blockchain from a node corresponding to the block, and specifically, the nodes corresponding to each block of the target blockchain may be different nodes, that is, each block of the target blockchain corresponds to a different node.
As an example, after the target block link receives the data acquisition request, each block in the target block chain may acquire data from the node corresponding to each block at the same time, for example, the node corresponding to the block Q1 in the target block chain is a, the node corresponding to the block Q2 in the target block chain is B, the node corresponding to the block Q3 in the target block chain is C, after the target block link receives the data acquisition request, the target block chain acquires the first block data required by the user in the node a from the node a, the target block chain signs the first block data by using the certificate 1 of the node a to obtain the first block signed data, the first block signed data and the certificate 1 as the first block data to be returned corresponding to the block Q1, the target block Q2 acquires the second block data required by the user in the node B from the node B, the target block chain signs the second block data by using the certificate 2 of the node B to obtain the second block signed data, the target block chain signs the second block data, the second block signed data and the certificate 2 as the second block data required by the user in the node C corresponding to the third block Q2, the target block chain signs the third block C data required by the third block chain to be returned by using the third block C3 as the data required by the third block chain, the second block data and the third block data can be used as target data, the first block signed data, the second block signed data and the third block signed data can be used as certificate signatures, certificate 1, certificate 2 and certificate 3 can be used as node certificates, a block chain browser can acquire block data from different nodes, and generally adjacent blocks are required to be acquired from different nodes, and then the block chain browser can check whether the previous block is correct or not through a hash pointer based on the next block; the preset root certificates can be one or a plurality of different institutions, the different institutions can directly acquire the blocks from the nodes of the different institutions, then the nodes and the blocks are verified through the trusted root certificates, and meanwhile, the blocks are verified through the front hash pointers and the back hash pointers, so that the authenticity of the acquired blocks can be greatly enhanced; on the other hand, the block chain is acquired from different nodes, so that concurrency capability can be improved, block data can be acquired rapidly, and the block data can be displayed in time.
Step S206, verifying the data on the chain according to at least one preset root certificate to obtain a data verification result corresponding to the data on the chain.
The preset root certificate may refer to data conforming to a preset trust level or a security level, and in practical application, the preset root certificate may include data such as information of a user, a public key of the user, and the like.
The data verification result may refer to data representing the authenticity of the data on the chain, in practical application, the data verification result may include 1 and 0, specifically, the data verification result is that the authenticity of the data on the chain is represented by 0 and does not meet a preset authenticity requirement, and the data verification result is that the authenticity of the data on the chain is represented by 1 and meets the preset authenticity requirement.
As an example, after receiving the on-chain data returned by the target blockchain browser, the blockchain browser needs to verify the on-chain data by using a preset root certificate (or a preset root certificate) in order to verify the authenticity of the on-chain data, specifically, because the on-chain data may include the target data, a certificate signature and a node certificate, the blockchain browser may verify the target data according to a preset target data verification mode based on the preset root certificate to obtain a target data verification result, verify the certificate signature according to a preset certificate signature verification mode to obtain a certificate signature verification result, and verify the node certificate according to a preset node certificate verification mode to obtain a node certificate verification result, the blockchain browser may combine the target data verification result, the certificate signature verification result and the node certificate verification result to determine the data verification result corresponding to the on-chain data, for example, the target data verification result represents that the target data passes verification, the certificate signature passes the verification, and the node certificate verification result represents that the node certificate passes the verification, the data verification result corresponding to the on-chain data verification result is 1, and the node certificate verification result represents that the data verification result corresponding to the on the chain data is verified to satisfy the authenticity requirement of the preset on the link certificate; when any one of the target data verification result, the certificate signature verification result and the node certificate verification result does not pass the verification, the blockchain browser can judge that the authenticity of the data on the chain does not meet the preset authenticity requirement.
Step S208, obtaining a block verification result aiming at the target block chain, and determining a reliability verification result aiming at the data acquisition request according to the data verification result and the block verification result.
The block verification result may include information characterizing whether each block in the target blockchain passes the hash verification.
The block verification result may refer to data representing whether the block in the target block chain and the blocks before and after the block pass the chain verification, specifically, whether the block in the target block chain and the blocks before and after the block pass the chain verification may be used to determine whether node tampering or block data falsification exists in the target block chain, in practical application, the block verification result may include 1 and 0, the block verification result is 1, the block in the target block chain and the blocks before and after the block pass the chain verification, and the block verification result is 0, the block in the target block chain and the blocks before and after the block do not pass the chain verification.
The reliability verification result may refer to data that represents whether the data on the chain is real data from the target blockchain, and in practical application, the reliability verification result may include 1 and 0, specifically, the reliability verification result of 1 represents that the data on the chain is real data from the target blockchain, the reliability verification result of 0 represents that the data on the chain is not real data from the target blockchain or that the data on the chain is tampered or that the data on the chain is false.
As an example, a blockchain browser obtains blockattribute data (e.g., hash values) corresponding to each block in a target blockchain, the blockchain browser determines a blocky verification result for the target blockchain according to the blocky attribute data corresponding to each block in the target blockchain, the blockchain browser determines a reliability verification result for a data obtaining request according to the data verification result and the blocky verification result, specifically, the data verification result represents that the on-chain data passes verification, and the blocky verification result represents that each blocky attribute data passes verification, the blocky browser determines that the reliability verification result for the data obtaining request is 1, determines that the on-chain data is real data from the target blockchain, namely, the on-chain data is reliable, and if any one of the data verification result or the blocky verification result represents that the corresponding data does not pass verification, the blocky chain browser determines that the reliability verification result for the data obtaining request is 0, and determines that the on-chain data is not real data from the target blocky chain, namely, the on-chain data is unreliable
In the data reliability verification method, the data acquisition request is synchronized to the target block chain by responding to the data acquisition request triggered by the user, so that the data acquisition request is timely transmitted to the block chain, and the response speed of data acquisition operation is improved; receiving the on-chain data returned by the target block chain in response to the data acquisition request, so as to obtain the on-chain data consisting of the target data, the certificate signature corresponding to the target data and the node certificate corresponding to the certificate signature, acquiring the certificate signature corresponding to the target data and the node certificate when acquiring the data acquired from the node corresponding to the block by the block of the target block chain, and providing a basis for the subsequent data reliability verification; according to at least one preset root certificate, verifying the data on the chain to obtain a data verification result corresponding to the data on the chain, so that each component of the data on the chain is verified step by step based on the preset root certificate, and the accuracy and the strictness of the data verification process are ensured; the method comprises the steps of obtaining a block verification result representing whether each block in a target block chain passes hash verification, determining a reliability verification result aiming at a data obtaining request according to the data verification result and the block verification result, verifying whether data on the chain is real data from the target block chain based on the block verification result and the data verification result, obtaining the data on the chain returned by the target block chain after synchronizing the data obtaining request to the target block chain, based on a preset root certificate, obtaining the data verification result of the data on the chain according to a preset verification mode, and determining the reliability verification result aiming at the data obtaining request by combining the data verification result and the block verification result corresponding to the target block chain, so that the authenticity of the data on the chain is determined by utilizing the reliability verification result, and judging whether the data on the chain is the untampered real data from the target block chain by gradually verifying the component part of the data on the chain and combining the verification result corresponding to the block chain.
In some embodiments, verifying the on-chain data according to the preset root certificate to obtain a data verification result corresponding to the on-chain data includes: according to a preset root certificate and a preset certificate decryption mode, verifying a node certificate in the data on the chain to obtain a certificate verification result of the node certificate; under the condition that the certificate verification result characterizes that the node certificate passes verification, verifying the certificate signature corresponding to the node certificate according to a preset signature verification mode according to the node certificate, and obtaining a signature verification result corresponding to the certificate signature; and determining a data verification result corresponding to the data on the chain according to the certificate verification result and the signature verification result.
The preset certificate decryption method may refer to a method of analyzing a node certificate to obtain basic data corresponding to the node certificate, and in practical application, the preset certificate decryption method may include dividing the node certificate into a plurality of segments of fields containing basic data (such as a certificate authority, a certificate validity time, etc.) according to a preset field division basis, and determining the basic data corresponding to the fields from the above segments.
The certificate verification result may refer to data representing whether the node certificate is legal, and in practical application, the certificate verification result may refer to data whether an issuing authority of the node certificate accords with a preset authority limit condition, whether the valid time of the node certificate accords with a preset time limit condition, and the like.
The preset signature verification method may be a method for verifying correctness of a signature by using specific data, and in practical application, the preset signature verification method may include comparing whether the specific data and reference data corresponding to the specific data are consistent.
The signature verification result may refer to data indicating whether the signature of the characterization certificate passes verification, in practical application, the signature verification result may include 0 and 1, the signature verification result is that the signature of the 0 characterization certificate fails verification, and the signature verification result is that the signature of the 1 characterization certificate fails verification.
As an example, according to a preset root certificate and a preset certificate decryption mode, the blockchain browser obtains certificate basic data corresponding to the node certificate, and verifies the node certificate in the data on the chain by verifying whether the certificate basic data meets the preset certificate basic data verification requirement or not to obtain a certificate verification result of the node certificate; when the certificate verification result represents that the node certificate passes verification, namely, after the node certificate passes verification, the blockchain browser verifies the certificate signature corresponding to the node certificate according to the node certificate and a preset signature verification mode by comparing specific data with reference data corresponding to the specific data to obtain a signature verification result corresponding to the certificate signature; the block chain browser determines a data verification result corresponding to the data on the chain according to the certificate verification result and the signature verification result, specifically, the certificate verification result represents that the node certificate passes verification, and the signature verification result represents that the data on the chain is 1 when the certificate signature passes verification, and the authenticity of the data on the chain is judged to meet preset authenticity requirements.
In the embodiment, the node certificate in the data on the chain is verified according to a preset root certificate and a preset certificate decryption mode, so that a certificate verification result of the node certificate is obtained; under the condition that the certificate verification result characterizes that the node certificate passes verification, verifying the certificate signature corresponding to the node certificate according to a preset signature verification mode according to the node certificate, and obtaining a signature verification result corresponding to the certificate signature; according to the certificate verification result and the signature verification result, the data verification result corresponding to the data on the chain is determined, and the node certificate and the certificate signature in the data on the chain can be verified step by utilizing the root certificate, so that the reliability of the data verification process on the chain is improved.
In some embodiments, according to a preset root certificate and a preset certificate decryption mode, verifying a node certificate in data on a chain to obtain a certificate verification result of the node certificate, including: determining a public key corresponding to a node certificate in the data on the chain according to a preset root certificate; decrypting the node certificate in the data on the chain according to the public key to obtain a decryption result corresponding to the node certificate; and determining a certificate verification result of the node certificate according to the decryption result.
Where public key may refer to a key used to encrypt a session key, verify a digital signature, or encrypt data that may be decrypted with a corresponding private key.
The decryption result may refer to data of basic information of the node certificate, and in practical application, the decryption result may include an issuing authority of the node certificate, an expiration time, and the like.
As an example, since each node certificate is cryptographically signed with a private key corresponding to a preset root certificate, the root certificate may include a public key corresponding to each node certificate, and when the node certificate needs to be verified, the blockchain browser may determine, according to the preset root certificate, the public key corresponding to the node certificate in the on-chain data; according to the public key, decrypting the node certificate in the data on the chain to obtain a decryption result corresponding to the node certificate, for example, decrypting the node certificate according to a preset decryption algorithm to obtain a decrypted character string corresponding to the node certificate, comparing and dividing the decrypted character string corresponding to the node certificate according to the content distribution (such as an issuing organization number, expiration time and the like) of the character string in the public key to obtain a decryption result (such as basic data including the issuing organization, expiration time and the like) corresponding to the node certificate, and verifying whether the issuing organization of the node certificate accords with preset organization limiting conditions, whether the effective time of the node certificate accords with preset time limiting conditions and the like by the blockchain browser according to the decryption result, so as to further determine the certificate verification result of the node certificate.
In this embodiment, a public key corresponding to a node certificate in the on-chain data is determined according to a preset root certificate; decrypting the node certificate in the data on the chain according to the public key to obtain a decryption result corresponding to the node certificate; and determining a certificate verification result of the node certificate according to the decryption result, decrypting the node certificate by using the root certificate, and obtaining the certificate verification result of the node certificate by judging whether the decrypted result meets the preset requirement or not, thereby realizing accurate verification of the node certificate.
In some embodiments, when the node certificate is represented by the certificate verification result and passes verification, verifying, according to a preset signature verification manner, a certificate signature corresponding to the node certificate to obtain a signature verification result corresponding to the certificate signature, including: determining signature verification reference data corresponding to the node certificate according to the node certificate; determining data to be verified corresponding to the certificate signature according to a preset signature verification mode; and comparing the signature verification reference data with the data to be verified to obtain a signature verification result corresponding to the certificate signature.
The signature verification reference data may refer to data for verifying specific data corresponding to the certificate bookmark name, and in practical application, the signature verification reference data may include a document digest corresponding to the node certificate.
The data to be verified may be data for comparison verification with the signature verification reference data, and in practical application, the data to be verified may include data obtained after specific processing is performed on the node certificate.
As an example, according to the node certificate, the blockchain browser obtains a digital signature, a public key and a document (target data or block data) sent by a node corresponding to the node certificate, and according to the public key sent by the node corresponding to the node certificate, the blockchain browser decrypts the digital signature sent by the node corresponding to the node certificate to obtain a first document abstract (namely signature verification reference data) corresponding to the node certificate; the blockchain browser generates a second document abstract (data to be verified) corresponding to a document sent by a node corresponding to the node certificate by utilizing a hash algorithm, compares signature verification reference data with the data to be verified according to a preset signature verification mode to obtain a signature verification result corresponding to the certificate signature, and specifically, if the signature verification reference data is identical to the data to be verified, signature verification is successful, and the signature verification result is determined to be 1, namely, the certificate signature passes verification.
In the embodiment, signature verification reference data corresponding to the node certificate is determined according to the node certificate; determining data to be verified corresponding to the certificate signature according to a preset signature verification mode; and comparing the signature verification reference data with the data to be verified to obtain a signature verification result corresponding to the certificate signature, and verifying the correctness of the signature based on signature verification by comparing the reference data with the data to be verified so as to realize accurate verification of the signature.
In some embodiments, obtaining a block verification result for a target blockchain includes: acquiring a first hash value corresponding to a target block in a target block chain; acquiring a second hash value of an adjacent block corresponding to the target block; determining a block verification result for the target block according to the first hash value and the second hash value; and obtaining block verification results corresponding to all blocks in the target block chain, and determining the block verification results aiming at the target block chain according to the block verification results corresponding to all blocks in the target block chain.
The target block may be any block in a target block chain.
The first hash value may refer to a hash value of a block preceding a target block included in the target block.
Wherein, the neighboring block may refer to a block preceding the target block in the target block chain.
Wherein the second hash value may refer to a hash value of the neighboring block itself.
As an example, since the target block has the first hash value of the previous block in the adjacent blocks, the first hash value can be used to perform a comparison verification with the second hash value of the previous block, and by verifying whether the two hash values are identical, the block verification result for the previous block is obtained, so as to determine whether the data returned by the previous block is reliable, further, a plurality of block verification results for all blocks in the target block chain can be obtained, and the block chain browser can determine the block verification result for the target block chain according to the plurality of block verification results, specifically, when each block verification result in the plurality of block verification results represents that the block corresponding to the block verification result passes the verification (specifically, can be represented as the same as two hash values), the block chain browser determines that the target block chain passes the chain verification.
In this embodiment, a first hash value corresponding to a target block in a target block chain is obtained; acquiring a second hash value of an adjacent block corresponding to the target block; according to the first hash value and the second hash value, block verification results for the target blocks are determined, block verification results corresponding to all blocks in the target block chain are obtained, block verification results for the target block chain are determined according to the block verification results corresponding to all blocks in the target block chain, adjacent blocks can be verified based on the characteristics of the block chain, the block verification results are used as one of the basis for judging the authenticity of data on the chain, reliability of all block data is enhanced, multi-angle full verification of reliability of the data on the chain is achieved, and reliability of the verification results of the data on the chain is improved.
In some embodiments, the above method further comprises: under the condition that the reliability verification result aiming at the data acquisition request characterizes that the data on the chain is real data from the target blockchain, acquiring a data identifier corresponding to the data on the chain; at least one of the data or the data identification on the chain is displayed.
The data identifier may refer to an identifier that characterizes whether the data on the chain is real data, and in practical application, the data identifier may include an icon with a security symbology meaning, such as a website icon similar to a secure socket layer (ssl) icon.
As an example, after the blockchain browser judges that the data on the chain corresponding to the data acquisition request is the real data from the target blockchain, in order to prominently prompt or inform the user, the blockchain browser can generate a data security identification icon for the data on the chain, the blockchain browser can display the data security identification icon corresponding to the data on the chain while displaying the data on the chain to the user, in practical application, the user can send an information consulting request to the blockchain browser by clicking the data security identification icon, the blockchain browser can respond to the information consulting request triggered by the user, signature information and node certificate information of the data on the chain (returned by the blockchain node) are displayed near the data security identification icon, and because the source code of the blockchain browser is usually open, the front-end page can directly check the source code verification, which is favorable for improving the trust degree of the information displayed by the user on the blockchain browser, and if the blockchain browser verifies the data such as the block and the like, the blockchain browser can display the verification passing identification, such as the verification passing of the credibility of the user data can be clearly displayed.
In the embodiment, under the condition that the reliability verification result aiming at the data acquisition request represents that the data on the chain is the real data from the target blockchain, the data identifier corresponding to the data on the chain is acquired; at least one of the data or the data identifier on the chain is displayed, so that the authenticity of the data on the chain can be intuitively displayed to a user in the form of an icon or an identifier, and the visualization degree of the verification result of the data on the chain is improved.
In some embodiments, the above method further comprises: the on-chain data is presented in parallel, with the reliability verification result for the data acquisition request characterizing the on-chain data as real data from the target blockchain.
As an example, each block of the target blockchain requests data from a corresponding node at the same time, so as to obtain the data on the chain corresponding to the partition block, the data on the chain is verified according to a preset root certificate, so as to obtain a data verification result, the blockchain browser performs chain verification on the target blockchain according to a preset chain verification mode, so as to obtain a block verification result, and the data on the chain is displayed in parallel under the condition that the reliability verification result aiming at the data acquisition request represents that the data on the chain is real data from the target blockchain.
In this embodiment, the display speed of the blockchain browser for displaying the blockdata can be improved based on the parallel display mode by displaying the data on the chain in parallel under the condition that the reliability verification result for the data acquisition request indicates that the data on the chain is the real data from the target blockchain.
In some embodiments, as shown in fig. 3, a flow chart of a data reliability verification and display method is provided, a user accesses and browses a blockchain browser through a terminal, the blockchain browser pre-prepares a root certificate of a corresponding target blockchain for verifying signature information of a node, the user sends a data acquisition request through the terminal, the blockchain browser synchronizes the data acquisition request to the target blockchain, different blocks in the target blockchain acquire data from different nodes (e.g., block n-1 acquires data from node a, block n acquires data from node B, block n+1 acquires data from node C in fig. 3), the target blockchain signs the block data required to be returned to the blockchain browser with certificates of the respective corresponding blockchain nodes to obtain a certificate signature, the target blockchain verifies the block data (namely the target data), the certificate signature and the node certificate return value blockchain browser corresponding to each certificate signature, the blockchain browser performs signature verification on different blocks to verify the correctness of the returned data of different nodes, specifically, the blockchain browser verifies whether each node certificate is legal or not by using the root certificate, each node certificate is encrypted and issued by using a private key corresponding to the root certificate, so the blockchain browser prepares the root certificate to actually contain a corresponding public key, can decrypt and verify whether each node certificate is legal or not, the blockchain browser then verifies the returned block data signature information by using each node certificate of verification legitimacy, verifies whether the correct signature is proved to be correct, thereby obtaining a data verification result, the blockchain browser performs chain verification on the front and rear blocks of different blocks to verify whether the node is tampered or not or counterfeited with the block data, because the next block has the hash (hash) of the previous block in the adjacent blocks, the hash (hash) of the previous block in the next block can be used for consistency verification with the hash (hash) of the previous block, so that whether the data on the chain is reliable or not is judged, a block verification result is obtained, the block chain browser determines the reliability verification result aiming at the data acquisition request or the data on the chain according to the data verification result and the block verification result, if the reliability verification result passes, the data is displayed in the block chain browser, and a similar ssl website icon is displayed to indicate that the data on the chain received by the block chain browser is actually from the block chain, the source code of the block chain browser can be oriented to a user, the user can clearly know that only the data on the real chain can display the corresponding effective icon, and the obtained data is fed back to the user.
In this embodiment, compared with the prior art that the centralized server is completely trusted and depends on the processing capability, the pressure on the centralized server can be reduced by rapidly acquiring and displaying the on-chain data, and the displayed on-chain data can be ensured to be real and effective, namely, if all the on-chain data pass verification, a user can recognize the authenticity of the on-chain data displayed by the blockchain browser only through vision by adding a ssl-like website icon, so that the data display intuitiveness of the blockchain browser as an on-chain data visualization window is improved.
Based on the same inventive concept, the embodiment of the application also provides a data reliability verification device for realizing the data reliability verification method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in the embodiments of the data reliability verification device or devices provided below may refer to the limitation of the data reliability verification method hereinabove, and will not be repeated herein.
In one embodiment, as shown in fig. 4, there is provided a data reliability verification apparatus, comprising: a request synchronization module 402, a data receiving module 404, a data verification module 406, and a validation module 408, wherein:
A request synchronization module 402, configured to synchronize a data acquisition request to a target blockchain in response to a user-triggered data acquisition request; the data acquisition request is used for controlling the blocks of the target blockchain to simultaneously request data from the corresponding nodes.
A data receiving module 404, configured to receive on-chain data returned by the target blockchain in response to the data acquisition request; the on-chain data comprises target data, a certificate signature corresponding to the target data and a node certificate corresponding to the certificate signature; the target data are data obtained from nodes corresponding to the blocks of the target block chain; nodes corresponding to blocks of the target block chain are different from each other.
And the data verification module 406 is configured to verify the on-chain data according to at least one preset root certificate, and obtain a data verification result corresponding to the on-chain data.
A reliability verification module 408, configured to obtain a block verification result for the target blockchain, and determine a reliability verification result for the data acquisition request according to the data verification result and the block verification result; the block verification result represents whether each block in the target block chain passes hash verification or not; the reliability verification result characterizes whether the on-chain data is real data from the target blockchain.
In an exemplary embodiment, the data verification module 406 is specifically further configured to verify, according to the preset root certificate and a preset certificate decryption manner, a node certificate in the on-chain data, so as to obtain a certificate verification result of the node certificate; under the condition that the certificate verification result represents that the node certificate passes verification, verifying a certificate signature corresponding to the node certificate according to the node certificate and a preset signature verification mode to obtain a signature verification result corresponding to the certificate signature; and determining a data verification result corresponding to the data on the chain according to the certificate verification result and the signature verification result.
In an exemplary embodiment, the data verification module 406 is specifically further configured to determine, according to the preset root certificate, a public key corresponding to a node certificate in the on-chain data; decrypting the node certificate in the data on the chain according to the public key to obtain a decryption result corresponding to the node certificate; determining a certificate verification result of the node certificate according to the decryption result; the certificate verification result characterizes whether the node certificate is legal or not.
In an exemplary embodiment, the data verification module 406 is specifically further configured to determine signature verification reference data corresponding to the node certificate according to the node certificate; determining data to be verified corresponding to the certificate signature according to the preset signature verification mode; and comparing the signature verification reference data with the data to be verified to obtain a signature verification result corresponding to the certificate signature.
In an exemplary embodiment, the above-mentioned reliable verification module 408 is specifically further configured to obtain a first hash value corresponding to a target block in the target blockchain; the target block comprises any one block in the target block chain; acquiring a second hash value of an adjacent block corresponding to the target block; determining a block verification result for the target block according to the first hash value and the second hash value; and obtaining block verification results corresponding to all blocks in the target block chain, and determining the block verification results aiming at the target block chain according to the block verification results corresponding to all blocks in the target block chain.
In an exemplary embodiment, the apparatus further includes a first data display module, where the first data display module is specifically configured to obtain a data identifier corresponding to the on-chain data when the reliability verification result for the data acquisition request indicates that the on-chain data is real data from the target blockchain; at least one of the on-chain data or the data identification is presented.
In an exemplary embodiment, the above apparatus further includes a second data presentation module, specifically configured to present the on-chain data in parallel if the reliability verification result for the data acquisition request characterizes the on-chain data as real data from the target blockchain.
The respective modules in the above-described data reliability verification apparatus may be implemented in whole or in part by software, hardware, and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a terminal, and the internal structure of which may be as shown in fig. 5. The computer device includes a processor, a memory, an input/output interface, a communication interface, a display unit, and an input means. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a data reliability verification method. The display unit of the computer device is used for forming a visual picture, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be a key, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in FIG. 5 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
In an embodiment, there is also provided a computer device comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, carries out the steps of the method embodiments described above.
In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.
It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are both information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data are required to meet the related regulations.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magneto-resistive random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (PHASE CHANGE Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in various forms such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), etc. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, or the like, but is not limited thereto.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The foregoing examples illustrate only a few embodiments of the application and are described in detail herein without thereby limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.
Claims (9)
1. A method of verifying data reliability, the method comprising:
Responding to a data acquisition request triggered by a user, and synchronizing the data acquisition request to a target block chain; the data acquisition request is used for controlling the blocks of the target block chain to simultaneously request data from the corresponding nodes;
Receiving on-chain data returned by the target blockchain in response to the data acquisition request; the on-chain data comprises target data, a certificate signature corresponding to the target data and a node certificate corresponding to the certificate signature; the target data are data obtained from nodes corresponding to the blocks of the target block chain; nodes corresponding to all blocks of the target block chain are different from each other;
Verifying the data on the chain according to at least one preset root certificate to obtain a data verification result corresponding to the data on the chain; according to the preset root certificate and a preset certificate decryption mode, verifying a node certificate in the on-chain data to obtain a certificate verification result of the node certificate; under the condition that the certificate verification result represents that the node certificate passes verification, verifying a certificate signature corresponding to the node certificate according to the node certificate and a preset signature verification mode to obtain a signature verification result corresponding to the certificate signature; determining a data verification result corresponding to the on-chain data according to the certificate verification result and the signature verification result;
Acquiring a block verification result aiming at the target block chain, and determining a reliability verification result aiming at the data acquisition request according to the data verification result and the block verification result; the block verification result represents whether each block in the target block chain passes hash verification or not; the reliability verification result characterizes whether the on-chain data is real data from the target blockchain.
2. The method according to claim 1, wherein the verifying the node certificate in the on-chain data according to the preset root certificate and the preset certificate decryption mode to obtain the certificate verification result of the node certificate includes:
Determining a public key corresponding to the node certificate in the on-chain data according to the preset root certificate;
Decrypting the node certificate in the data on the chain according to the public key to obtain a decryption result corresponding to the node certificate;
Determining a certificate verification result of the node certificate according to the decryption result; the certificate verification result characterizes whether the node certificate is legal or not.
3. The method according to claim 1, wherein, when the certificate verification result indicates that the node certificate passes verification, according to the node certificate, according to a preset signature verification manner, verifying a certificate signature corresponding to the node certificate, to obtain a signature verification result corresponding to the certificate signature, including:
determining signature verification reference data corresponding to the node certificate according to the node certificate;
Determining data to be verified corresponding to the certificate signature according to the preset signature verification mode;
and comparing the signature verification reference data with the data to be verified to obtain a signature verification result corresponding to the certificate signature.
4. The method of claim 1, wherein the obtaining the block verification result for the target blockchain comprises:
Acquiring a first hash value corresponding to a target block in the target block chain; the target block comprises any one block in the target block chain;
Acquiring a second hash value of an adjacent block corresponding to the target block;
Determining a block verification result for the target block according to the first hash value and the second hash value;
and obtaining block verification results corresponding to all blocks in the target block chain, and determining the block verification results aiming at the target block chain according to the block verification results corresponding to all blocks in the target block chain.
5. The method according to claim 1, wherein the method further comprises:
Acquiring a data identifier corresponding to the data on the chain under the condition that the reliability verification result aiming at the data acquisition request characterizes the data on the chain as real data from the target blockchain;
at least one of the on-chain data or the data identification is presented.
6. The method according to claim 1, wherein the method further comprises:
the on-chain data is presented in parallel, with a reliability verification result for the data acquisition request characterizing the on-chain data as real data from the target blockchain.
7. A data reliability verification apparatus, the apparatus comprising:
The request synchronization module is used for responding to a data acquisition request triggered by a user and synchronizing the data acquisition request to a target block chain; the data acquisition request is used for controlling the blocks of the target block chain to simultaneously request data from the corresponding nodes;
The data receiving module is used for receiving the on-chain data returned by the target blockchain in response to the data acquisition request; the on-chain data comprises target data, a certificate signature corresponding to the target data and a node certificate corresponding to the certificate signature; the target data are data obtained from nodes corresponding to the blocks of the target block chain; nodes corresponding to all blocks of the target block chain are different from each other;
The data verification module is used for verifying the data on the chain according to at least one preset root certificate to obtain a data verification result corresponding to the data on the chain; according to the preset root certificate and a preset certificate decryption mode, verifying a node certificate in the on-chain data to obtain a certificate verification result of the node certificate; under the condition that the certificate verification result represents that the node certificate passes verification, verifying a certificate signature corresponding to the node certificate according to the node certificate and a preset signature verification mode to obtain a signature verification result corresponding to the certificate signature; determining a data verification result corresponding to the on-chain data according to the certificate verification result and the signature verification result;
The reliable verification module is used for acquiring a block verification result aiming at the target block chain and determining a reliable verification result aiming at the data acquisition request according to the data verification result and the block verification result; the block verification result represents whether each block in the target block chain passes hash verification or not; the reliability verification result characterizes whether the on-chain data is real data from the target blockchain.
8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 6 when the computer program is executed.
9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202311449833.1A CN117251883B (en) | 2023-11-02 | 2023-11-02 | Data reliability verification method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202311449833.1A CN117251883B (en) | 2023-11-02 | 2023-11-02 | Data reliability verification method, device, computer equipment and storage medium |
Publications (2)
Publication Number | Publication Date |
---|---|
CN117251883A CN117251883A (en) | 2023-12-19 |
CN117251883B true CN117251883B (en) | 2024-06-04 |
Family
ID=89126543
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202311449833.1A Active CN117251883B (en) | 2023-11-02 | 2023-11-02 | Data reliability verification method, device, computer equipment and storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN117251883B (en) |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109472164A (en) * | 2018-09-13 | 2019-03-15 | 远光软件股份有限公司 | The verification method and its network and electronic equipment of contract dataset |
CN109508563A (en) * | 2018-12-11 | 2019-03-22 | 南京大学 | Electronic document authenticity guarantee method based on block chain |
CN110011988A (en) * | 2019-03-21 | 2019-07-12 | 平安科技(深圳)有限公司 | Based on the certification authentication method and device of block chain, storage medium, electronic device |
CN110083620A (en) * | 2019-03-21 | 2019-08-02 | 深圳壹账通智能科技有限公司 | Based on the data query method and device of block chain, storage medium, electronic device |
CN110611569A (en) * | 2019-09-24 | 2019-12-24 | 腾讯科技(深圳)有限公司 | Authentication method and related equipment |
CN110781509A (en) * | 2019-10-28 | 2020-02-11 | 腾讯科技(深圳)有限公司 | Data verification method and device, storage medium and computer equipment |
CN110995446A (en) * | 2019-12-05 | 2020-04-10 | 腾讯科技(深圳)有限公司 | Evidence verification method, device, server and storage medium |
CN111010367A (en) * | 2019-11-07 | 2020-04-14 | 深圳市电子商务安全证书管理有限公司 | Data storage method and device, computer equipment and storage medium |
CN113221166A (en) * | 2021-05-11 | 2021-08-06 | 支付宝(杭州)信息技术有限公司 | Method and device for acquiring block chain data, electronic equipment and storage medium |
WO2022042301A1 (en) * | 2020-08-26 | 2022-03-03 | 腾讯科技(深圳)有限公司 | Data processing method and apparatus, smart device and storage medium |
CN114201781A (en) * | 2021-12-14 | 2022-03-18 | 深圳市电子商务安全证书管理有限公司 | Block chain-based storage verification method and device, computer equipment and medium |
-
2023
- 2023-11-02 CN CN202311449833.1A patent/CN117251883B/en active Active
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109472164A (en) * | 2018-09-13 | 2019-03-15 | 远光软件股份有限公司 | The verification method and its network and electronic equipment of contract dataset |
CN109508563A (en) * | 2018-12-11 | 2019-03-22 | 南京大学 | Electronic document authenticity guarantee method based on block chain |
CN110011988A (en) * | 2019-03-21 | 2019-07-12 | 平安科技(深圳)有限公司 | Based on the certification authentication method and device of block chain, storage medium, electronic device |
CN110083620A (en) * | 2019-03-21 | 2019-08-02 | 深圳壹账通智能科技有限公司 | Based on the data query method and device of block chain, storage medium, electronic device |
CN110611569A (en) * | 2019-09-24 | 2019-12-24 | 腾讯科技(深圳)有限公司 | Authentication method and related equipment |
CN110781509A (en) * | 2019-10-28 | 2020-02-11 | 腾讯科技(深圳)有限公司 | Data verification method and device, storage medium and computer equipment |
CN111010367A (en) * | 2019-11-07 | 2020-04-14 | 深圳市电子商务安全证书管理有限公司 | Data storage method and device, computer equipment and storage medium |
CN110995446A (en) * | 2019-12-05 | 2020-04-10 | 腾讯科技(深圳)有限公司 | Evidence verification method, device, server and storage medium |
WO2022042301A1 (en) * | 2020-08-26 | 2022-03-03 | 腾讯科技(深圳)有限公司 | Data processing method and apparatus, smart device and storage medium |
CN113221166A (en) * | 2021-05-11 | 2021-08-06 | 支付宝(杭州)信息技术有限公司 | Method and device for acquiring block chain data, electronic equipment and storage medium |
CN114201781A (en) * | 2021-12-14 | 2022-03-18 | 深圳市电子商务安全证书管理有限公司 | Block chain-based storage verification method and device, computer equipment and medium |
Non-Patent Citations (1)
Title |
---|
一种基于区块链的数据完整性验证解决方案;魏艳;毛燕琴;沈苏彬;;计算机技术与发展;20201231(第01期);全文 * |
Also Published As
Publication number | Publication date |
---|---|
CN117251883A (en) | 2023-12-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11361089B2 (en) | Method, apparatus, and electronic device for blockchain-based recordkeeping | |
EP3741082B1 (en) | Proof chaining and decomposition | |
US11258612B2 (en) | Method, apparatus, and electronic device for blockchain-based recordkeeping | |
US20200294048A1 (en) | Blockchain-based data verification method and apparatus, and electronic device | |
CN108540459B (en) | Data storage method, device, system, electronic equipment and computer readable medium | |
KR101948721B1 (en) | Method and apparatus for examining forgery of file by using file hash value | |
CN114172659B (en) | Message transmission method, device, equipment and storage medium in block chain system | |
US20220045866A1 (en) | Method and system for authentication seal deployment in networked immutable transactions | |
CN108920971A (en) | The method of data encryption, the method for verification, the device of encryption and verification device | |
CN116049802B (en) | Application single sign-on method, system, computer equipment and storage medium | |
CN117251883B (en) | Data reliability verification method, device, computer equipment and storage medium | |
CN113407213B (en) | Resource package updating method, device, equipment and storage medium | |
CN111078569A (en) | Method and device for testing optical character recognition application and storage medium | |
CN114896313B (en) | Data transmission method, device, equipment and medium | |
CN117521040A (en) | Service data calling method, device, computer equipment and storage medium | |
CN116112268A (en) | Data processing method, device, computer equipment and storage medium | |
CN115757310A (en) | Credit information sharing method and device, computer equipment and storage medium | |
CN115174260A (en) | Data verification method, data verification device, computer, storage medium and program product | |
CN117493335A (en) | Report processing method, report processing device, report processing equipment, storage medium and computer program product | |
CN117251865A (en) | Resource interaction method, device, computer equipment and storage medium | |
CN118282669A (en) | Certificate processing method, device, equipment and storage medium | |
CN118540115A (en) | Page access method, page access device, computer device, readable storage medium, and program product | |
CN117313140A (en) | Information query method, device, computer equipment and storage medium | |
CN117411871A (en) | Image material uploading method, device, equipment, storage medium and program product |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |