Data credential processing method, device, blockchain node, and storage medium

Abstract

The present invention provides a data voucher processing method, device, blockchain node, and computer-readable storage medium. The method includes: upon receiving a voucher application request from a first node corresponding to a transaction seller, generating first data voucher information; upon receiving a first voucher query request from a second node corresponding to a transaction buyer, feeding back the first data voucher information to the second node; upon receiving verification information from the second node indicating that the first transaction information has been verified, updating the first data voucher information to obtain second data voucher information; upon receiving a second voucher query request from a third node corresponding to a notary, feeding back the second data voucher information to the third node; and upon receiving an audit result from the third node indicating that the second transaction information has been audited, updating the voucher status from an inactive state to an active state to obtain third data voucher information.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of blockchain technology, and in particular, to a data credential processing method, device, blockchain node, and computer-readable storage medium. Background Art

[0002] Data vouchers refer to business vouchers issued and received by businesses and individuals when purchasing and selling goods, providing and receiving services, or engaging in other business activities. They serve as the primary basis for accounting calculations and are also an important basis for law enforcement inspections by auditing and tax authorities. For example, if a company's employees lease an IoT cloud platform to store IoT data uploaded by IoT devices, the IoT cloud platform can process billing and generate data vouchers. Employees can use these data vouchers to claim reimbursement from the company, and the company can use these data vouchers to apply for tax deductions.

[0003] Currently, data certificates can be created based on the transaction information of both parties. However, when issuing data certificates, only the legitimacy of the transaction terminal is usually verified, resulting in low credibility of the generated data certificates. Summary of the Invention

[0004] Embodiments of the present invention provide a data credential processing method, device, blockchain node, and computer-readable storage medium to address the problem of low credibility of data credentials in the prior art.

[0005] In a first aspect, an embodiment of the present invention provides a data credential processing method, which is applied to a blockchain node, and the method includes:

[0006] Upon receiving a credential application request sent by a first node corresponding to a transaction seller, generating first data credential information, the first data credential information including a first credential identifier and first transaction information carried in the credential application request;

[0007] Upon receiving a first credential query request sent by a second node corresponding to the transaction buyer, feeding back the first data credential information to the second node, wherein the first credential query request carries the first credential identifier;

[0008] Upon receiving verification information sent by the second node indicating that the first transaction information has been verified, updating the first data credential information to obtain second data credential information, where the second data credential information includes a second credential identifier, second transaction information, and a credential status, where the credential status is inactive, and the second transaction information includes at least the first transaction information;

[0009] Upon receiving a second credential query request from a third node corresponding to the notary party, feeding back the second data credential information to the third node, wherein the second credential query request carries the second credential identifier;

[0010] When the audit result indicating that the second transaction information has passed the audit is received from the third node, the certificate state is updated from the inactivated state to the activated state to obtain third data certificate information.

[0011] In a second aspect, an embodiment of the present invention provides a data voucher processing device, which is applied to a blockchain node, and the device includes:

[0012] a generating module configured to generate first data credential information upon receiving a credential application request sent by a first node corresponding to a transaction seller, the first data credential information including a first credential identifier and first transaction information carried in the credential application request;

[0013] a first feedback module configured to feedback the first data credential information to the second node upon receiving a first credential query request sent by the second node corresponding to the transaction buyer, wherein the first credential query request carries the first credential identifier;

[0014] a first updating module, configured to, upon receiving verification information sent by the second node indicating that the first transaction information has been verified, update the first data credential information to obtain second data credential information, where the second data credential information includes a second credential identifier, second transaction information, and a credential status, where the credential status is inactive, and the second transaction information includes at least the first transaction information;

[0015] a second feedback module, configured to feedback the second data credential information to the third node upon receiving a second credential query request sent by the third node corresponding to the notary party, wherein the second credential query request carries the second credential identifier;

[0016] The second updating module is configured to update the certificate state from the inactivated state to the activated state upon receiving the audit result sent by the third node indicating that the second transaction information has passed the audit, so as to obtain third data certificate information.

[0017] In a third aspect, an embodiment of the present invention provides a blockchain node, comprising a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the above-mentioned data credential processing method when executed by the processor.

[0018] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above-mentioned data voucher processing method are implemented.

[0019] In an embodiment of the present invention, upon receiving a credential application request sent by a first node corresponding to a transaction seller, first data credential information is generated, the first data credential information including a first credential identifier and the first transaction information carried by the credential application request; upon receiving a first credential query request sent by a second node corresponding to a transaction buyer, the first data credential information is fed back to the second node, the first credential query request carrying the first credential identifier; upon receiving verification information sent by the second node indicating that the first transaction information has been verified, the first data credential information is updated to obtain second data credential information, the second data credential information including a second credential identifier, second transaction information and a credential status, the credential status being an inactivated state, and the second transaction information including at least the first transaction information; upon receiving a second credential query request sent by a third node corresponding to a notary party, the second data credential information is fed back to the third node, the second credential query request carrying the second credential identifier; upon receiving an audit result sent by the third node indicating that the second transaction information has been audited, the credential status is updated from the inactivated state to the activated state, to obtain third data credential information. In this way, the verification of transaction information by the transaction buyer and the notary party is gradually introduced during the generation of data certificates. Only when both the transaction buyer and the notary party have verified or reviewed it can the final valid data certificate be generated, thereby ensuring the reliability of the data certificate and improving its credibility. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in describing the embodiments of the present invention. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0021] Figure 1 This is one of the architectural diagrams of the data credential processing system in the IoT scenario;

[0022] Figure 2 This is the second architectural diagram of the data credential processing system in the IoT scenario;

[0023] Figure 3 1 is a flow chart of a data voucher processing method provided by an embodiment of the present invention;

[0024] Figure 4 It is a schematic diagram of the process interaction of generating data vouchers using the data voucher processing system;

[0025] Figure 5 It is a schematic diagram of generating data summary;

[0026] Figure 6 This is a diagram of the interaction process for data credential transfer;

[0027] Figure 7 It is a process interaction diagram presented by the data voucher;

[0028] Figure 8 It is a schematic diagram of the content of the data voucher;

[0029] Figure 9 Schematic diagram of the structure of a data voucher processing device provided by an embodiment of the present invention;

[0030] Figure 10 It is a schematic diagram of the structure of a blockchain node provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0031] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. All other embodiments derived by ordinary technicians in this field based on the embodiments of the present invention without creative work are within the scope of protection of the present invention.

[0032] The technical terms involved in the embodiments of the present invention are explained below.

[0033] Data vouchers refer to business vouchers issued and collected by enterprises and individuals when purchasing and selling goods, providing services, receiving services or engaging in other business activities. They are the original basis for accounting and an important basis for law enforcement inspections by auditing and tax authorities.

[0034] In actual applications, this data certificate has the same effect as a real-life invoice. In business activities involving online transactions, this data certificate is a legally binding business certificate issued by the seller to the buyer for the online transaction. It can be used in multiple scenarios.

[0035] For example, in an IoT scenario, company employees lease an IoT cloud platform to store IoT data uploaded by IoT devices. The IoT cloud platform can implement billing and generate data vouchers. Company employees can use the data vouchers to claim reimbursement from the company, and the company can use the data vouchers to apply for deductions from the tax department.

[0036] For example, in an Internet scenario, corporate employees or users can rent an Internet cloud platform to store files uploaded by terminal devices. The Internet cloud platform can charge based on the file size and generate data vouchers. Corporate employees can use the data vouchers to claim reimbursement from the company, and the company can use the data vouchers to apply for deductions from the tax department.

[0037] For example, in the database search scenario 1, users can purchase database search permissions to search and download documents in the database. Accordingly, the database can charge according to the usage time or the number of documents downloaded and generate data vouchers.

[0038] In short, data credentials may be involved in any scenario involving online transactions and sales.

[0039] Blockchain is a new application model for computer technologies, including distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. In a narrow sense, blockchain is a chained data structure composed of sequentially linked data blocks in chronological order, and a distributed ledger that is cryptographically guaranteed to be tamper-proof and unforgeable.

[0040] In a broad sense, blockchain technology is a new distributed infrastructure and computing method that uses block chain data structures to verify and store data, distributed node consensus algorithms to generate and update data, cryptography to ensure the security of data transmission and access, and smart contracts composed of automated script code to program and operate data.

[0041] From a data perspective, blockchain is a chain data structure that combines data blocks in a sequential manner in chronological order. The data structure is cryptographically guaranteed to be tamper-proof and non-forgeable.

[0042] From a technical perspective, blockchain technology integrates a variety of different technologies. By building a blockchain network, each node within the network is allowed to obtain a complete copy of the data block. Consensus mechanisms and competitive computing are used to maintain updates to the blockchain-based data blocks. This achieves decentralized and trustless data storage and management through an end-to-end network composed of multi-node communication.

[0043] The InterPlanetary File System (IPFS) is a network transmission protocol designed to create persistent and distributed file storage and sharing. It is a content-addressable, peer-to-peer hypermedia distribution protocol. Nodes in the IPFS network form a distributed file system. It is a peer-to-peer distributed file system that connects all computing devices to the same file system. Its core features are content-based addressing, elimination of redundant block data, and high throughput.

[0044] A Merkle tree is a binary hash tree that stores data in leaf nodes of a tree structure and ensures data immutability through a step-by-step hashing operation. Any changes to leaf node data are propagated to the previous node and ultimately reflected in the root of the tree.

[0045] The following describes the application scenario of the data voucher processing method provided by the embodiment of the present invention by taking the Internet of Things scenario as an example.

[0046] It should be noted that the data voucher processing method provided in the embodiments of the present invention relates to the field of blockchain technology and can be widely applied to data voucher processing systems. The method can be executed by the data voucher processing device of the embodiments of the present invention, and the data voucher processing device can be configured in a blockchain node to execute the data voucher processing method. The blockchain node can be a blockchain gateway.

[0047] The data certificate processing system may include a blockchain system, an IoT cloud platform, IoT devices and a business terminal. Its main function is to realize the trusted generation, secure transfer and reading authorization of data certificates in IoT scenarios. The main processes include the data certificate generation process, the data certificate transfer process and the data certificate presentation process, which are explained in detail below.

[0048] Exemplarily, the method for handling IoT data vouchers mainly describes a scenario in which a transaction buyer, such as a corporate employee, leases an IoT cloud platform owned by a transaction seller to store IoT data uploaded by IoT devices. The IoT cloud platform charges and generates data vouchers. Corporate employees use the data vouchers to claim reimbursement from the company, and the company can use the data vouchers to apply for deductions from the tax department. The main scenario is that the IoT cloud platform and the tax department system form a blockchain system; enterprises or individual users lease resources from the IoT cloud platform to store IoT data uploaded by IoT devices. The IoT cloud platform uses blockchain smart contracts to generate data vouchers and grants them to enterprises or individual users; enterprises or individual users can use the data vouchers to apply for financial processes such as reimbursement and tax deductions. At the same time, the data vouchers can be transferred between different business entities such as different enterprises, individual users or tax departments.

[0049] The architectural diagram of the data credential processing system in the IoT scenario is as follows: Figure 1 and Figure 2 As shown, Figure 1 and Figure 2 The following are typical architecture deployments of data credential processing systems, but not all possible system architecture deployments are enumerated. Figure 1 As shown, the blockchain nodes are deployed in the tax bureau system, business access system and IoT cloud platform respectively. The tax bureau system, business access system and IoT cloud platform can respectively call blockchain services to realize data certificate processing.

[0050] like Figure 2 As shown, blockchain nodes are separated from the tax bureau system, business terminals, and IoT cloud platform. These systems, business terminals, and IoT cloud platform can access blockchain services via the Hypertext Transfer Protocol (HTTP). Furthermore, the data credential processing system can also include IPFS to store payment credential images, such as transfer records and shopping lists.

[0051] The following describes the data voucher processing method provided by the embodiment of the present invention using the Internet of Things scenario as an example.

[0052] This method is applied to blockchain nodes, see Figure 3 , the figure shows a flow chart of the data voucher processing method provided by an embodiment of the present invention. Figure 3 As shown, the method may include the following steps:

[0053] Step 301: upon receiving a certificate application request sent by a first node corresponding to a transaction seller, generate first data certificate information, wherein the first data certificate information includes a first certificate identifier and first transaction information carried in the certificate application request.

[0054] In this embodiment, the data voucher processing process involves three parties: the transaction buyer (which can be called a shopper), the transaction seller (which can be called a merchant), and the notary (which can be called a regulator). The first node corresponding to the transaction seller can be any electronic device or platform used by the transaction seller, the second node corresponding to the transaction buyer can be any electronic device or platform used by the transaction buyer, and the third node corresponding to the notary can be any electronic device or platform used by the notary. For example, in an IoT scenario, the first node corresponding to the transaction seller can be an IoT cloud platform, the second node corresponding to the transaction buyer can be a business end access system, and the third node corresponding to the notary can be a tax bureau system.

[0055] See also Figure 4 , Figure 4This is a flow chart of how to use the data voucher processing system to generate data vouchers. Figure 4 As shown, an enterprise or individual leases an IoT cloud platform through a business end to store IoT resources uploaded by IoT devices. The IoT cloud platform generates consumption during the billing cycle. Accordingly, the IoT cloud platform submits a request for data voucher issuance through blockchain smart contract 1, sending a voucher request to the blockchain.

[0056] The voucher application request carries the first transaction information, which includes at least the identification IDs of the buyer and seller, the data voucher generation method, a data summary, the amount information, and a timestamp. The data voucher generation method refers to the method by which the IoT cloud platform generates data vouchers, which can be periodic, fixed-time, or fixed-data-volume generation. Periodic generation refers to triggering a data voucher issuance application at regular intervals, such as once a month. Fixed-time generation refers to triggering a data voucher issuance application at a fixed time, such as 12:00 a.m. every day. Fixed-data-volume generation refers to triggering a data voucher issuance application when the billing resource data reaches a certain volume.

[0057] The data summary is the value obtained by hashing the billing resource data generated by the IoT cloud platform. For example, it can be a string directly obtained by hashing the billing resource data through a hash function, or the billing resource data can be segmented, and then a hash function is used to construct a hash number based on the M segments of target data after segmentation. The data summary is the hash value of the root node of the constructed hash tree.

[0058] In an optional embodiment, the first transaction information includes a data summary of the billing resource data of the first node, and the data summary is the second hash value of the root node of the hash tree. The second hash value is constructed based on the hash value of M segments of target data, and the M segments of target data are obtained by segmenting the billing resource data, where M is a positive integer.

[0059] Specifically, in order to make the billing resource data of the IoT cloud platform more auditable, the data voucher can contain data summary information of the billing resource data. The IoT cloud platform can segment the IoT data within the billing cycle, i.e., the billing resource data, according to a fixed time or fixed data volume. The billing resource data can be divided into M segments to obtain M segments of target data, such as D1, D2, D3...D M .

[0060] Afterwards, see Figure 5 , Figure 5 A schematic diagram of generating a data summary is shown, as Figure 5As shown, each target data segment is hashed and the hash numbers are obtained, such as the hash values ​​of the leaf nodes of the Merkle tree, which are Hash1, Hash2, Hash3...Hash M , hash values ​​are calculated using a Merkle tree, ultimately obtaining the hash value of the Merkle tree's root node, or Merkle root, as the data summary. This allows for segmented hash calculations to reduce the single computational load, allowing for faster hash recalculations and ensuring data immutability.

[0061] Accordingly, when a blockchain node receives a certificate application request from the first node corresponding to the seller, the blockchain smart contract generates first data certificate information based on the first transaction information. This first data certificate information can be a temporary data certificate and is stored in a blockchain distributed database (such as the aforementioned IPFS). This improves system resource utilization and universality. Furthermore, data will not be lost due to loss on the business end, thereby improving data storage security.

[0062] A temporary data voucher can be in the form of a key value (abbreviated as K) - content Value (abbreviated as V), where K is the temporary data voucher number, i.e., the first voucher identifier, which is calculated using a cyclic redundancy check (CRC) algorithm based on the IDs of the buyer and seller, the data voucher generation method, the data summary, the amount information, and the timestamp. V contains the first transaction information, which includes data information such as the buyer and seller IDs, the data voucher generation method, the data summary, the amount information, and the timestamp.

[0063] At the same time, first tampering protection information of the temporary data credential may be generated. The first tampering protection information corresponds to the temporary data credential. Any change in the first data credential information will cause the first tampering protection information of the temporary data credential to change.

[0064] In an optional implementation, a hash value of a temporary data credential can be generated based on the first data credential information. If the first data credential information is tampered with, the hash value regenerated based on the first data credential information will change. Therefore, to record the data credential processing process, prevent tampering with the first data credential information, verify whether the first data credential information has been tampered with, and ensure data security, the hash value of the temporary data credential can be stored in the blockchain (i.e., distributed ledger).

[0065] Step 302: upon receiving a first credential query request sent by a second node corresponding to the transaction buyer, the first data credential information is fed back to the second node, where the first credential query request carries the first credential identifier.

[0066] like Figure 4 As shown, after a blockchain node generates a temporary data voucher, it can feed the temporary data voucher number back to the IoT cloud platform, which can then pass it on to the transaction buyer. This can be done via off-chain methods like SMS or email, or by sharing it with a business access system via the blockchain, which then passes it on to the transaction buyer's corresponding business terminal. This is not specifically limited here.

[0067] The business end applies for querying the temporary data certificate through the blockchain smart contract 2, that is, sending a first certificate query request to the blockchain node. The first certificate query request may include the transaction buyer's ID and the temporary data certificate number, etc.

[0068] Correspondingly, the blockchain smart contract obtains the temporary data voucher information corresponding to the temporary data voucher number from the blockchain distributed database based on the content carried in the first voucher query request, and feeds back the temporary data voucher information to the business end.

[0069] Step 303: Upon receiving verification information sent by the second node indicating that the first transaction information has been verified, the first data credential information is updated to obtain second data credential information. The second data credential information includes a second credential identifier, second transaction information, and a credential status. The credential status is inactive, and the second transaction information includes at least the first transaction information.

[0070] like Figure 4 As shown, the buyer verifies off-chain whether the first transaction information, i.e., the temporary data voucher, matches the actual situation. For example, the buyer and seller IDs, the data voucher generation method, the data summary, the amount, and the timestamp all match the actual situation. If they match, the business end can be controlled to request confirmation of the temporary data voucher through blockchain smart contract 3, i.e., send verification information to the blockchain node, indicating that the first transaction information has been verified.

[0071] Accordingly, upon receiving verification information from the second node indicating that the first transaction information has been verified, the blockchain node may update the temporary data credential in the blockchain distributed database to the second data credential information, which may be formal data credential information. The formal data credential information may include a second credential identifier, second transaction information, and a credential status, where the credential status is inactive.

[0072] The second transaction information can be the first transaction information, or it can be the first transaction information with the first hash value appended to it. The credential status can be located in V of the official data credential, i.e., the temporary data credential is updated to append the credential status to the data credential content to obtain the official data credential. The second credential identifier can be the same as or different from the first credential identifier, and this is not specifically limited here.

[0073] In an optional embodiment, the verification information may further include a payment credential image file, and the updating of the first data credential information to obtain the second data credential information includes:

[0074] Generate a first hash value of the payment credential image file and the second credential identifier;

[0075] The first hash value is added to the first data credential information, and the first credential identifier in the first data credential information is updated to the second credential identifier.

[0076] The blockchain smart contract generates a first hash value for the payment voucher image file through hashing, and then generates a formal data voucher number (second voucher identifier) ​​according to the tax bureau's preset logic. The first hash value is then added to V in the first data voucher information, updating the first voucher identifier in the first data voucher information to the second voucher identifier, ultimately obtaining the formal data voucher information. The payment voucher image file can also be distributed stored on IPFS, where it can be retrieved using the first hash value.

[0077] Thus, the second data voucher information differs from the first data voucher information in that the data voucher identifier in K is different, and V is appended with the voucher status and the first hash value of the payment voucher image file. At this point, the temporary data voucher requested by the IoT cloud platform has been verified by the buyer, generating a formal data voucher. The voucher status in this formal data voucher can be inactive, indicating that the data voucher has not yet been reviewed by the tax bureau. Furthermore, the formal data voucher is appended with the first hash value of the buyer's payment voucher image file, further enhancing the credibility of the generated data voucher.

[0078] At the same time, second tampering protection information of the second data credential information may be generated. The second tampering protection information corresponds to the second data credential information. Any change in the second data credential information will cause the second tampering protection information of the second data credential information to change.

[0079] In an optional embodiment, a hash value of the second data credential information can be generated based on the second data credential information. If the second data credential information is tampered with, the hash value regenerated based on the second data credential information will change. Therefore, to record the data credential processing process, prevent tampering with the second data credential information, verify whether the second data credential information has been tampered with, and ensure data security, the hash value of the second data credential information can be stored in the blockchain (i.e., distributed ledger).

[0080] Step 304: upon receiving a second credential query request sent by a third node corresponding to the notary party, the second data credential information is fed back to the third node, where the second credential query request carries the second credential identifier.

[0081] like Figure 4 As shown, the blockchain node can transmit the official data voucher number to the tax bureau system via a blockchain event. The tax bureau system then requests a query for the official data voucher through blockchain smart contract 4, i.e., sends a second voucher query request to the blockchain node. The second voucher query request can include the tax bureau ID and the official data voucher number (i.e., the second voucher identifier).

[0082] Correspondingly, the blockchain smart contract obtains the official data certificate corresponding to the official data certificate number from the blockchain distributed database based on the second certificate query request, and feeds it back to the tax bureau system.

[0083] Step 305: upon receiving the audit result sent by the third node indicating that the second transaction information has passed the audit, the certificate state is updated from the inactivated state to the activated state to obtain third data certificate information.

[0084] like Figure 4 As shown, the tax bureau system reviews the information in the official data voucher through manual review or automated means such as smart contracts. It also reviews the payment voucher image file obtained from IPFS based on the first hash value in the official data voucher, generates an audit result, and sends the audit result to the blockchain node. The audit result can be either passed or failed.

[0085] Accordingly, the blockchain node confirms or rejects the official data certificate based on the audit result through the blockchain smart contract 5. Specifically, if the audit result indicates that the second transaction information has passed the audit, the certificate status in the official data certificate is updated from inactive to active, and the third data certificate information is obtained. Otherwise, the official data certificate is invalidated.

[0086] At the same time, third tampering protection information of the third data credential information may be generated. The third tampering protection information corresponds to the third data credential information. Any change in the third data credential information will cause the third tampering protection information of the third data credential information to change.

[0087] In an optional embodiment, a hash value of the third data credential information can be generated based on the third data credential information. If the third data credential information is tampered with, the hash value regenerated based on the third data credential information will change. Therefore, to record the data credential processing process, prevent tampering of the third data credential information, verify whether the third data credential information has been tampered with, and ensure data security, the hash value of the third data credential information can be stored in the blockchain (i.e., distributed ledger).

[0088] In this embodiment, upon receiving a credential application request sent by a first node corresponding to the transaction seller, first data credential information is generated, the first data credential information including a first credential identifier and the first transaction information carried by the credential application request; upon receiving a first credential query request sent by a second node corresponding to the transaction buyer, the first data credential information is fed back to the second node, the first credential query request carrying the first credential identifier; upon receiving verification information sent by the second node indicating that the first transaction information has been verified, the first data credential information is updated to obtain second data credential information, the second data credential information including a second credential identifier, second transaction information, and a credential status, the credential status being in an inactivated state, and the second transaction information including at least the first transaction information; upon receiving a second credential query request sent by a third node corresponding to the notary party, the second data credential information is fed back to the third node, the second credential query request carrying the second credential identifier; upon receiving an audit result sent by the third node indicating that the second transaction information has been audited, the credential status is updated from the inactivated state to the activated state, to obtain third data credential information. In this way, the verification of transaction information by the transaction buyer and the notary party is gradually introduced during the generation of data certificates. Only when both the transaction buyer and the notary party have verified or reviewed it can the final valid data certificate be generated, thereby ensuring the reliability of the data certificate and improving its credibility.

[0089] Optionally, the first credential query request carries a service password and digital signature information of the first credential identifier. Before feeding back the first data credential information to the second node, the method further includes:

[0090] Verify the digital signature information based on the public key corresponding to the transaction buyer to obtain a verification result;

[0091] Transforming the service password to obtain a verification transformation result;

[0092] The feeding back the first data credential information to the second node includes:

[0093] When the signature verification result indicates that the signature verification is passed and the verification transformation result matches the pre-stored transformation result corresponding to the transaction buyer, the first data credential information is fed back to the second node.

[0094] In this embodiment, before the second node calls the blockchain service, the legitimacy of the identity of the second node can be verified. Specifically, the blockchain node can store the ID of the business end corresponding to each transaction buyer, the identity public key and the unique password transformation (such as information digest such as Hash or MD5), the identity private key locally stored by the business end corresponding to each transaction buyer, and the service password.

[0095] When applying for blockchain services, the business end can carry the service password and a digital signature signed with the identity private key in the parameter field, which can ensure the legitimacy of the transaction buyer's identity and the integrity of the data. That is, the first credential query request carries the service password and the digital signature information of the first credential identifier.

[0096] Correspondingly, the blockchain node can use the public identity key of the business end corresponding to the transaction buyer to verify the digital signature information to obtain the signature verification result, and use the preset unique transformation algorithm (such as Hash, MD5 and other information digests) to transform the service password to obtain the verification transformation result.

[0097] Afterwards, the transformation result can be verified to see whether it is the same as the pre-stored transformation result corresponding to the transaction buyer, that is, the cryptographically unique transformation, and whether the signature verification result indicates that the signature verification is passed. When both verifications of the blockchain node are passed, the service application will be accepted.

[0098] In this way, when an illegal operator operates a legitimate business end, he or she will not be able to successfully call the blockchain service because he or she does not know the service password, thus achieving higher security.

[0099] Optionally, after step 305, the method further includes:

[0100] Upon receiving the credential transfer request sent by the second node, adding the first credential transfer information carried in the credential transfer request to the third data credential information to obtain fourth data credential information;

[0101] When a credential transfer request is received from the fourth node and the first credential transfer information matches the second credential transfer information carried in the credential transfer request, the fourth data credential information is updated based on the second credential transfer information to obtain the fifth data credential information.

[0102] After the data voucher is generated in the above embodiment, its owner is the transaction buyer, who can transfer it. In this case, the transaction buyer can be the transferor. This embodiment describes the transfer process of the data voucher, such as the financial process of reimbursement or deduction. The transfer of the data voucher depends on the confirmation of both the transferor and the transferee. Figure 6 , Figure 6 The diagram of the process interaction of data credential transfer is shown as follows: Figure 6 As shown, the following steps are included:

[0103] The second node corresponding to the transferor can submit a data certificate transfer request through the blockchain smart contract 6. That is, the second node sends a certificate transfer request to the blockchain node. The certificate transfer request carries the first certificate transfer information, which may include the transferor's ID, the transferee's ID, the official data certificate number, the transfer type, and a timestamp.

[0104] Accordingly, upon receiving the credential transfer request from the second node, the blockchain node appends the first credential transfer information to the official data credential in the blockchain distributed database, based on the first credential transfer information. This means that the KV is updated by appending the first credential transfer information, including the transferor's ID, the transferee's ID, the official data credential number, the transfer type, and the timestamp, to V, ultimately generating the fourth data credential information.

[0105] At the same time, fourth tampering protection information of the fourth data credential information may be generated. The fourth tampering protection information corresponds to the fourth data credential information. Any change in the fourth data credential information will cause the fourth tampering protection information of the fourth data credential information to change.

[0106] In an optional embodiment, a hash value of the fourth data credential information can be generated based on the fourth data credential information. If the fourth data credential information is tampered with, the hash value regenerated based on the fourth data credential information will change. Therefore, to record the data credential processing process, prevent tampering with the fourth data credential information, verify whether the fourth data credential information has been tampered with, and ensure data security, the hash value of the fourth data credential information can be stored in the blockchain (i.e., distributed ledger).

[0107] Afterwards, the fourth node corresponding to the transferee submits a data voucher transfer request through the blockchain smart contract 7, i.e., sends a voucher transfer request to the blockchain node. The voucher transfer request may carry second voucher transfer information, which may include the transferee's ID, the official data voucher number, an image file of the reimbursement or deduction record, and a timestamp.

[0108] Accordingly, the blockchain node can generate a hash of the image file of the reimbursement record or deduction record and store the image file of the reimbursement record or deduction record in a distributed manner on IPFS. At the same time, based on the second credential transfer information, it can verify whether the second credential transfer information matches the first credential transfer information (that is, verify whether the transferee ID in the second credential transfer information is consistent with the transferee ID in the first credential transfer information, and whether the reimbursement record or deduction record exists).

[0109] If the first credential transfer information matches the second credential transfer information, the second credential transfer information can be appended to the official data credential in the blockchain distributed database, ultimately obtaining the fifth data credential information. This means updating the KV and appending the second credential transfer information, such as the transfer request timestamp, to V, completing the data credential ownership transfer.

[0110] At the same time, fifth tampering protection information of the fifth data credential information may be generated. The fifth tampering protection information corresponds to the fifth data credential information. Any change in the fifth data credential information will cause the fifth tampering protection information of the fifth data credential information to change.

[0111] In an optional embodiment, a hash value of the fifth data credential information can be generated based on the fifth data credential information. If the fifth data credential information is tampered with, the hash value regenerated based on the fifth data credential information will change. Therefore, to record the data credential processing process, prevent tampering with the fifth data credential information, verify whether the fifth data credential information has been tampered with, and ensure data security, the hash value of the fifth data credential information can be stored in the blockchain (i.e., distributed ledger).

[0112] In this embodiment, the two parties can jointly confirm and transfer the data certificate, ensuring the credibility of the data certificate transfer and the reimbursement or deduction business in the physical world.

[0113] Optionally, after updating the credential status from the inactivated status to the activated status and obtaining the third data credential information, the method further includes:

[0114] Upon receiving the credential presentation request sent by the second node, adding the authorization information carried in the credential presentation request to the third data credential information to obtain sixth data credential information;

[0115] Upon receiving the credential viewing request sent by the fifth node, and in a case where the viewing information carried in the credential viewing request matches the authorization information, the sixth data credential information is fed back to the fifth node.

[0116] After the data voucher is generated in the above embodiment, its owner is the transaction buyer, who can show it to other parties for viewing. This embodiment describes the process of presenting the data voucher, in which the presentation of the data voucher is the process of the data voucher owner showing it to the data voucher viewer. Figure 7 , Figure 7 The following is a flow chart showing the interaction of the data voucher presentation process: Figure 7 As shown, the following steps are included:

[0117] The owner of the data certificate submits an application for data certificate presentation through the blockchain smart contract 8, that is, sends a certificate presentation request to the blockchain node. The certificate presentation request can carry authorization information, which may include the presenter ID, viewer ID, official data certificate number, authorization period / authorization times and timestamp, etc.

[0118] The blockchain node attaches the authorization information to the official data certificate of the blockchain distributed database based on the certificate presentation request, that is, updates KV, and appends authorization information to V, such as the viewer ID and authorization period / number of authorizations, to obtain the sixth data certificate information.

[0119] At the same time, sixth tampering protection information of the sixth data credential information may be generated. The sixth tampering protection information corresponds to the sixth data credential information. Any change in the sixth data credential information will cause the sixth tampering protection information of the sixth data credential information to change.

[0120] In an optional embodiment, a hash value of the sixth data credential information can be generated based on the sixth data credential information. If the sixth data credential information is tampered with, the hash value regenerated based on the sixth data credential information will change. Therefore, to record the data credential processing process, prevent tampering with the sixth data credential information, verify whether the sixth data credential information has been tampered with, and ensure data security, the hash value of the sixth data credential information can be stored in the blockchain (i.e., distributed ledger).

[0121] The fifth node corresponding to the data certificate viewer can submit a data certificate viewing application through the blockchain smart contract 9, that is, send a certificate viewing request to the blockchain node. The certificate viewing request can carry viewing information, which may include the viewer ID, official data certificate number and timestamp, etc.

[0122] The blockchain node can match the authorization information added to the formal data certificate with the viewing information to determine whether the data certificate viewer has authorization. Specifically, it can verify whether the viewer ID in the viewing information is consistent with the viewer ID in the authorization information, and whether the authorization period / authorization times are consistent. If they match, it means that the data certificate viewer has authorization, and the formal data certificate information is returned to the fifth node. If they do not match, it means that the data certificate viewer does not have authorization, and a rejection response message is returned to the fifth node.

[0123] In this embodiment, upon receiving a credential presentation request from the second node, the authorization information carried in the credential presentation request is added to the third data credential information to obtain the sixth data credential information. Upon receiving a credential review request from the fifth node, if the review information carried in the credential review request matches the authorization information, the sixth data credential information is fed back to the fifth node. This allows for data credential viewing authorization while ensuring data credential security.

[0124] In addition, the embodiment of the present invention also provides an example of a data voucher, see Figure 8 , Figure 8 This is a schematic diagram of the content of the data certificate, such as Figure 8 As shown, the data voucher may include the official data voucher number and data voucher information, and the data voucher information may include transaction information, voucher status, voucher transfer information, authorization information, etc.

[0125] When the data of the certificate transfer information in the transfer record is empty, the lessee ID, that is, the transaction buyer, is the current owner of the data certificate. When the data of the certificate transfer information in the transfer record is not empty, the transferee ID corresponding to the most recent timestamp in the transfer record is the current owner of the data certificate.

[0126] Regulators can complete a complete audit of the capital flow, reimbursement, deduction and other financial behaviors corresponding to the data voucher in one stop from KV, which improves supervision and auditing capabilities.

[0127] The data voucher processing device provided by an embodiment of the present invention is described below.

[0128] See also Figure 9 , the figure shows a schematic diagram of the structure of the data voucher processing device provided by an embodiment of the present invention. The device is applied to a blockchain node, such as Figure 9 As shown, the data voucher processing device 900 includes:

[0129] A generating module 901 is configured to generate first data voucher information upon receiving a voucher application request sent by a first node corresponding to a transaction seller, wherein the first data voucher information includes a first voucher identifier and first transaction information carried in the voucher application request;

[0130] A first feedback module 902 is configured to feedback the first data credential information to a second node corresponding to a transaction buyer upon receiving a first credential query request sent by the second node, wherein the first credential query request carries the first credential identifier;

[0131] A first updating module 903 is configured to, upon receiving verification information sent by the second node indicating that the first transaction information has been verified, update the first data credential information to obtain second data credential information, where the second data credential information includes a second credential identifier, second transaction information, and a credential status, where the credential status is inactive, and the second transaction information includes at least the first transaction information;

[0132] A second feedback module 904 is configured to feedback the second data credential information to a third node corresponding to the notary upon receiving a second credential query request sent by the third node, wherein the second credential query request carries the second credential identifier;

[0133] The second updating module 905 is configured to update the certificate state from the inactivated state to the activated state upon receiving the audit result sent by the third node indicating that the second transaction information has passed the audit, so as to obtain third data certificate information.

[0134] Optionally, the verification information includes a payment credential image file. The first updating module 903 is specifically configured to:

[0135] Generate a first hash value of the payment credential image file and the second credential identifier;

[0136] The first hash value is added to the first data credential information, and the first credential identifier in the first data credential information is updated to the second credential identifier.

[0137] Optionally, the device further includes:

[0138] A first adding module is configured to, upon receiving a credential transfer request sent by the second node, add the first credential transfer information carried in the credential transfer request to the third data credential information to obtain fourth data credential information;

[0139] The third update module is used to update the fourth data credential information based on the second credential transfer information to obtain the fifth data credential information when the credential transfer request sent by the fourth node is received and the first credential transfer information matches the second credential transfer information carried in the credential transfer request.

[0140] Optionally, the device further includes:

[0141] a second adding module configured to, upon receiving a credential presentation request sent by the second node, add the authorization information carried in the credential presentation request to the third data credential information to obtain sixth data credential information;

[0142] The third feedback module is configured to feed back the sixth data credential information to the fifth node upon receiving a credential viewing request sent by the fifth node and when the viewing information carried in the credential viewing request matches the authorization information.

[0143] Optionally, the first credential query request carries a service password and digital signature information of the first credential identifier, and the apparatus further includes:

[0144] A signature verification module is used to verify the digital signature information based on the public key corresponding to the transaction buyer to obtain a signature verification result;

[0145] A transformation module, configured to transform the service password to obtain a verification transformation result;

[0146] The first feedback module is specifically configured to feed back the first data credential information to the second node when the signature verification result indicates that the signature verification has passed and the verification transformation result matches the pre-stored transformation result corresponding to the transaction buyer.

[0147] Optionally, the first transaction information includes a data summary of the billing resource data of the first node, where the data summary is the second hash value of the root node of the hash tree, and the second hash value is constructed based on the hash value of M segments of target data, where the M segments of target data are segmented based on the billing resource data, and M is a positive integer.

[0148] The data voucher processing device 900 can implement each process implemented in the above method embodiment. To avoid repetition, it will not be described here.

[0149] The following describes the blockchain node provided by an embodiment of the present invention.

[0150] See also Figure 10 , the figure shows a schematic diagram of the structure of the blockchain node provided by an embodiment of the present invention. Figure 10As shown, the blockchain node 1000 includes: a processor 1001, a memory 1002, a user interface 1003 and a bus interface 1004.

[0151] Processor 1001 is configured to read the program in memory 1002 and execute the following process:

[0152] Upon receiving a credential application request sent by a first node corresponding to a transaction seller, generating first data credential information, the first data credential information including a first credential identifier and first transaction information carried in the credential application request;

[0153] Upon receiving a first credential query request sent by a second node corresponding to the transaction buyer, feeding back the first data credential information to the second node, wherein the first credential query request carries the first credential identifier;

[0154] Upon receiving verification information sent by the second node indicating that the first transaction information has been verified, updating the first data credential information to obtain second data credential information, where the second data credential information includes a second credential identifier, second transaction information, and a credential status, where the credential status is inactive, and the second transaction information includes at least the first transaction information;

[0155] Upon receiving a second credential query request from a third node corresponding to the notary party, feeding back the second data credential information to the third node, wherein the second credential query request carries the second credential identifier;

[0156] When the audit result indicating that the second transaction information has passed the audit is received from the third node, the certificate state is updated from the inactivated state to the activated state to obtain third data certificate information.

[0157] exist Figure 10 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1001 and memory represented by memory 1002. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and therefore will not be further described herein. The bus interface 1004 provides an interface. For different user devices, the user interface 1003 may also be an interface capable of connecting external or internal devices as required, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

[0158] The processor 1001 is responsible for managing the bus architecture and general processing, and the memory 1002 can store data used by the processor 1001 when performing operations.

[0159] Optionally, the verification information includes a payment credential image file, and the processor 1001 is further configured to:

[0160] Generate a first hash value of the payment credential image file and the second credential identifier;

[0161] The first hash value is added to the first data credential information, and the first credential identifier in the first data credential information is updated to the second credential identifier.

[0162] Optionally, the processor 1001 is further configured to:

[0163] Upon receiving the credential transfer request sent by the second node, adding the first credential transfer information carried in the credential transfer request to the third data credential information to obtain fourth data credential information;

[0164] When a credential transfer request is received from the fourth node and the first credential transfer information matches the second credential transfer information carried in the credential transfer request, the fourth data credential information is updated based on the second credential transfer information to obtain the fifth data credential information.

[0165] Optionally, the processor 1001 is further configured to:

[0166] Upon receiving the credential presentation request sent by the second node, adding the authorization information carried in the credential presentation request to the third data credential information to obtain sixth data credential information;

[0167] Upon receiving the credential viewing request sent by the fifth node, and in a case where the viewing information carried in the credential viewing request matches the authorization information, the sixth data credential information is fed back to the fifth node.

[0168] Optionally, the first credential query request carries a service password and digital signature information of the first credential identifier. The processor 1001 is further configured to:

[0169] Verify the digital signature information based on the public key corresponding to the transaction buyer to obtain a verification result;

[0170] Transforming the service password to obtain a verification transformation result;

[0171] The feeding back the first data credential information to the second node includes:

[0172] When the signature verification result indicates that the signature verification is passed and the verification transformation result matches the pre-stored transformation result corresponding to the transaction buyer, the first data credential information is fed back to the second node.

[0173] Optionally, the first transaction information includes a data summary of the billing resource data of the first node, where the data summary is the second hash value of the root node of the hash tree, and the second hash value is constructed based on the hash value of M segments of target data, where the M segments of target data are segmented based on the billing resource data, and M is a positive integer.

[0174] Preferably, an embodiment of the present invention further provides a blockchain node, comprising a processor 1001, a memory 1002, and a computer program stored in the memory 1002 and executable on the processor 1001. When the computer program is executed by the processor 1001, the various processes of the above-mentioned data voucher processing method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0175] The present invention also provides a computer-readable storage medium having a computer program stored thereon. When executed by a processor, the computer program implements the various processes of the aforementioned data voucher processing method embodiment and achieves the same technical effects. To avoid repetition, the details are not described here. The computer-readable storage medium may be, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0176] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0177] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0178] In the embodiments provided in this application, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0179] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.

[0180] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0181] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes various media that can store program code, such as a USB flash drive, a mobile hard drive, ROM, RAM, a magnetic disk, or an optical disk.

[0182] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A data voucher processing method, characterized in that: Applied to a blockchain node, the method includes: Upon receiving a credential application request sent by a first node corresponding to a transaction seller, generating first data credential information, the first data credential information including a first credential identifier and first transaction information carried in the credential application request; Upon receiving a first credential query request sent by a second node corresponding to the transaction buyer, feeding back the first data credential information to the second node, wherein the first credential query request carries the first credential identifier; Upon receiving verification information sent by the second node indicating that the first transaction information has been verified, updating the first data credential information to obtain second data credential information, where the second data credential information includes a second credential identifier, second transaction information, and a credential status, where the credential status is inactive, and the second transaction information includes at least the first transaction information; Upon receiving a second credential query request from a third node corresponding to the notary party, feeding back the second data credential information to the third node, wherein the second credential query request carries the second credential identifier; Upon receiving the audit result sent by the third node indicating that the second transaction information has passed the audit, updating the credential status from the inactive state to the active state to obtain third data credential information; The verification information includes a payment credential image file, and the updating of the first data credential information to obtain the second data credential information includes: Generate a first hash value of the payment credential image file and the second credential identifier; The first hash value is added to the first data credential information, and the first credential identifier in the first data credential information is updated to the second credential identifier.

2. The method according to claim 1, characterized in that After updating the credential status from the inactivated status to the activated status and obtaining the third data credential information, the method further includes: Upon receiving the credential transfer request sent by the second node, adding the first credential transfer information carried in the credential transfer request to the third data credential information to obtain fourth data credential information; When a credential transfer request is received from the fourth node and the first credential transfer information matches the second credential transfer information carried in the credential transfer request, the fourth data credential information is updated based on the second credential transfer information to obtain the fifth data credential information.

3. The method according to claim 1, characterized in that After updating the credential status from the inactivated status to the activated status and obtaining the third data credential information, the method further includes: Upon receiving the credential presentation request sent by the second node, adding the authorization information carried in the credential presentation request to the third data credential information to obtain sixth data credential information; Upon receiving the credential viewing request sent by the fifth node, and in a case where the viewing information carried in the credential viewing request matches the authorization information, the sixth data credential information is fed back to the fifth node.

4. The method according to claim 1, wherein The first credential query request carries a service password and digital signature information of the first credential identifier. Before feeding back the first data credential information to the second node, the method further includes: Verify the digital signature information based on the public key corresponding to the transaction buyer to obtain a verification result; Transforming the service password to obtain a verification transformation result; The feeding back the first data credential information to the second node includes: When the signature verification result indicates that the signature verification is passed and the verification transformation result matches the pre-stored transformation result corresponding to the transaction buyer, the first data credential information is fed back to the second node.

5. The method according to claim 1, wherein The first transaction information includes a data summary of the billing resource data of the first node, where the data summary is the second hash value of the root node of the hash tree, and the second hash value is constructed based on the hash value of M segments of target data, where the M segments of target data are segmented based on the billing resource data, and M is a positive integer.

6. A data voucher processing device, characterized in that: Applied to a blockchain node, the device includes: a generating module configured to generate first data credential information upon receiving a credential application request sent by a first node corresponding to a transaction seller, the first data credential information including a first credential identifier and first transaction information carried in the credential application request; a first feedback module configured to feedback the first data credential information to the second node upon receiving a first credential query request sent by the second node corresponding to the transaction buyer, wherein the first credential query request carries the first credential identifier; a first updating module, configured to, upon receiving verification information sent by the second node indicating that the first transaction information has been verified, update the first data credential information to obtain second data credential information, where the second data credential information includes a second credential identifier, second transaction information, and a credential status, where the credential status is inactive, and the second transaction information includes at least the first transaction information; a second feedback module, configured to feedback the second data credential information to the third node upon receiving a second credential query request sent by the third node corresponding to the notary party, wherein the second credential query request carries the second credential identifier; a second updating module configured to update the credential status from the inactive state to the active state upon receiving an audit result sent by the third node indicating that the second transaction information has passed the audit, thereby obtaining third data credential information; The verification information includes a payment credential image file, and the first update module is specifically configured to: Generate a first hash value of the payment credential image file and the second credential identifier; The first hash value is added to the first data credential information, and the first credential identifier in the first data credential information is updated to the second credential identifier.

7. The device according to claim 6, characterized in that The device further comprises: A first adding module is configured to, upon receiving a credential transfer request sent by the second node, add the first credential transfer information carried in the credential transfer request to the third data credential information to obtain fourth data credential information; The third update module is used to update the fourth data credential information based on the second credential transfer information to obtain the fifth data credential information when the credential transfer request sent by the fourth node is received and the first credential transfer information matches the second credential transfer information carried in the credential transfer request.

8. The device according to claim 6, characterized in that The device further comprises: a second adding module configured to, upon receiving a credential presentation request sent by the second node, add the authorization information carried in the credential presentation request to the third data credential information to obtain sixth data credential information; The third feedback module is configured to feed back the sixth data credential information to the fifth node upon receiving a credential viewing request sent by the fifth node and when the viewing information carried in the credential viewing request matches the authorization information.

9. The device according to claim 6, characterized in that The first credential query request carries a service password and digital signature information of the first credential identifier, and the apparatus further includes: A signature verification module is used to verify the digital signature information based on the public key corresponding to the transaction buyer to obtain a signature verification result; A transformation module, configured to transform the service password to obtain a verification transformation result; The first feedback module is specifically configured to feed back the first data credential information to the second node when the signature verification result indicates that the signature verification has passed and the verification transformation result matches the pre-stored transformation result corresponding to the transaction buyer.

10. The device according to claim 6, characterized in that The first transaction information includes a data summary of the billing resource data of the first node, where the data summary is the second hash value of the root node of the hash tree, and the second hash value is constructed based on the hash value of M segments of target data, where the M segments of target data are segmented based on the billing resource data, and M is a positive integer.

11. A blockchain node, characterized in that: The blockchain node includes: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the steps of the data credential processing method according to any one of claims 1 to 5 are implemented.

12. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the data voucher processing method according to any one of claims 1 to 5.

Images