Blockchain-based data processing method, device, terminal and storage medium

Abstract

The embodiment of the present application discloses a data processing method, device, terminal and storage medium based on blockchain, the method comprising: receiving a fiscal bill verification request sent by a client corresponding to an approval agency, the fiscal bill verification request carries an identifier of a target fiscal bill and first detailed data, obtaining second detailed data corresponding to the target fiscal bill from a trusted execution environment according to the identifier of the target fiscal bill; verifying the first detailed data using the second detailed data to obtain a verification result; writing the verification result into the blockchain, and sending the verification result to the client corresponding to the approval agency, so that the client corresponding to the approval agency uses the verification result to approve the reimbursement request. By implementing the above method, the blockchain and the trusted execution environment can be used to control the verification process of fiscal data, thereby improving the privacy and reliability of the data verification process.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a blockchain-based data processing method, device, terminal, and medium. Background Art

[0002] Blockchain is a new application of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, and encryption algorithm. It is essentially a decentralized database, that is, a string of data blocks generated using cryptographic methods. Each data block contains a batch of transaction information, which is used to verify the validity of the transaction information and generate the next block.

[0003] With the development of blockchain technology, blockchain will gradually be applied to various fields of life. For example, in the financial field, blockchain fiscal receipts can be issued through blockchain, which can ensure the transparency and openness of financial support and the use of funds, and achieve fairness and justice. However, in this system, fiscal receipts correspond to detailed information (such as timeliness and background). In many cases, the detailed information behind the fiscal receipts needs to be verified in order to perform the corresponding approval operations. Therefore, how to safely and reliably verify the detailed information of fiscal receipts has become an urgent problem to be solved. Summary of the Invention

[0004] The embodiments of the present application provide a blockchain-based data processing method, device, terminal, and medium, which can use blockchain and a trusted execution environment to manage and control the verification process of financial data, thereby improving the privacy and reliability of the data verification process.

[0005] The present invention provides a data processing method based on blockchain, which includes:

[0006] Receiving a fiscal bill verification request sent by a client corresponding to the approval authority, the fiscal bill verification request carrying an identifier of a target fiscal bill and first detailed data, the fiscal bill verification request being generated by the client corresponding to the approval authority upon receiving a reimbursement request submitted by a reimbursement requester for the target fiscal bill;

[0007] Acquiring second detailed data corresponding to the target fiscal note from the trusted execution environment according to the identifier of the target fiscal note;

[0008] Verifying the first detailed data using the second detailed data to obtain a verification result;

[0009] The verification result is written into the blockchain, and the verification result is sent to the client corresponding to the approval agency, so that the client corresponding to the approval agency uses the verification result to approve the reimbursement request.

[0010] The present invention provides a data processing device based on blockchain, comprising:

[0011] a receiving module, configured to receive a fiscal bill verification request sent by a client corresponding to an approval authority, the fiscal bill verification request carrying an identifier of a target fiscal bill and first detailed data, the fiscal bill verification request being generated by the client corresponding to the approval authority upon receiving a reimbursement request submitted by a reimbursement requester for the target fiscal bill;

[0012] an acquisition module, configured to acquire second detailed data corresponding to the target fiscal note from a trusted execution environment according to an identifier of the target fiscal note;

[0013] a verification module, configured to verify the first detailed data using the second detailed data to obtain a verification result;

[0014] A writing module, configured to write the verification result into the blockchain;

[0015] The sending module is used to send the verification result to the client corresponding to the approval agency, so that the client corresponding to the approval agency uses the verification result to approve the reimbursement request.

[0016] An embodiment of the present application provides a terminal, comprising a processor, an input interface, an output interface, and a memory, wherein the processor, input interface, output interface, and memory are interconnected, wherein the memory is used to store a computer program, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the blockchain-based data processing method.

[0017] An embodiment of the present application provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, and the computer program includes program instructions, which, when executed by a processor, enable the processor to perform the blockchain-based data processing method.

[0018] The present invention provides a data processing method based on blockchain, which includes:

[0019] receiving a reimbursement request submitted by a reimbursement requester for a target fiscal bill;

[0020] Sending a fiscal bill verification request to a client corresponding to the fiscal institution according to the reimbursement request, the fiscal bill verification request carrying an identifier of the target fiscal bill and first detailed data, the fiscal bill verification request being used to instruct the client corresponding to the fiscal institution to obtain a verification result of the first detailed data using a trusted execution environment and the identifier of the target fiscal bill;

[0021] The verification result sent by the client corresponding to the financial institution is received, and the reimbursement request is approved by using the verification result.

[0022] The present invention provides a data processing device based on blockchain, comprising:

[0023] A receiving module, configured to receive a reimbursement request submitted by a reimbursement requester for a target fiscal bill;

[0024] a sending module, configured to send a fiscal bill verification request to a client corresponding to the fiscal institution based on the reimbursement request, the fiscal bill verification request carrying an identifier of the target fiscal bill and first detailed data, the fiscal bill verification request being used to instruct the client corresponding to the fiscal institution to obtain a verification result of the first detailed data using a trusted execution environment and the identifier of the target fiscal bill;

[0025] The receiving module is further configured to receive the verification result sent by the client corresponding to the financial institution;

[0026] An approval module is used to use the verification result to approve the reimbursement request.

[0027] An embodiment of the present application provides a terminal, comprising a processor, an input interface, an output interface, and a memory, wherein the processor, input interface, output interface, and memory are interconnected, wherein the memory is used to store a computer program, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the blockchain-based data processing method.

[0028] An embodiment of the present application provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, and the computer program includes program instructions, which, when executed by a processor, enable the processor to perform the blockchain-based data processing method.

[0029] In an embodiment of the present application, the client corresponding to the financial institution receives the financial bill verification request sent by the client corresponding to the approval agency, and obtains the second detailed data corresponding to the target financial bill from the trusted execution environment according to the identifier of the target financial bill; the client corresponding to the financial institution uses the second detailed data to verify the first detailed data to obtain a verification result; the client corresponding to the financial institution writes the verification result into the blockchain, and sends the verification result to the client corresponding to the approval agency, so that the client corresponding to the approval agency uses the verification result to approve the reimbursement request. Among them, the client can be specifically carried in the terminal. By implementing the above method, the blockchain and the trusted execution environment can be used to control the financial data verification process, thereby improving the privacy and reliability of the data verification process. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0031] Figure 1a This is a schematic diagram of the structure of a blockchain provided by an embodiment of the present application;

[0032] Figure 1b This is a schematic diagram of a blockchain-based data processing system architecture provided by an embodiment of the present application;

[0033] Figure 1c This is a schematic diagram of the interactive process of a blockchain-based data processing method provided in an embodiment of the present application;

[0034] Figure 2 This is a flowchart of a blockchain-based data processing method provided in an embodiment of the present application;

[0035] Figure 3 This is a flowchart of another blockchain-based data processing method provided in an embodiment of the present application;

[0036] Figure 4 This is a flowchart of another blockchain-based data processing method provided in an embodiment of the present application;

[0037] Figure 5 This is a schematic diagram of the interaction flow of another blockchain-based data processing method provided in an embodiment of the present application;

[0038] Figure 6 This is a schematic diagram of the structure of a blockchain-based data processing device provided in an embodiment of the present application;

[0039] Figure 7 This is a schematic diagram of the structure of another blockchain-based data processing device provided in an embodiment of the present application;

[0040] Figure 8 This is a schematic diagram of the structure of a terminal provided in an embodiment of the present application;

[0041] Figure 9 This is a schematic diagram of the structure of another terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application.

[0043] The data stored on the blockchain is highly reliable and cannot be tampered with, making it suitable for storing various types of data. Users can easily query various types of data on the blockchain. However, the data stored on the blockchain is public and transparent, and users may not want to store some private information (such as financial information) on the blockchain. For example, in a financial blockchain fiscal bill, the reimbursement requester needs to use the blockchain fiscal bill and the corresponding financial detailed data as approval information. Correspondingly, the approver needs to verify and obtain the financial detailed data based on the fiscal bill, and then approve the reimbursement request. However, for the sake of the privacy of financial information, the financial institution does not want to upload the above financial detailed data to the blockchain, resulting in the approver being unable to safely and reliably verify the user's financial information.

[0044] Based on the above description, an embodiment of the present application provides a data processing method based on blockchain, which is mainly implemented based on blockchain technology and Trusted Execution Environment (TEE) technology. Blockchain is a new application of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, etc. It is essentially a decentralized database, that is, a string of data blocks generated by cryptographic methods. Each data block contains a batch of transaction information, which is used to verify the validity of the transaction information and generate the next block. The underlying blockchain platform can include processing modules such as user management, basic services, smart contracts, and operation monitoring. Among them, the user management module is responsible for the identity information management of all blockchain participants, including maintaining public and private key generation (account management), key management, and maintaining the correspondence between the user's real identity and the blockchain address (authority management). Figure 1aTaking the blockchain structure diagram shown above as an example, whenever new data needs to be written to the blockchain, it is aggregated into a block and added to the end of the existing blockchain. A consensus algorithm ensures that the newly added blocks are identical on every node. Each block records platform protocol data and / or event announcement data, and also contains the hash value of the previous block. All blocks, in this way, store the hash value of the previous block and are sequentially connected to form the blockchain. The header of the next block in the blockchain stores the hash value of the previous block. When the data in the previous block changes, the hash value of the current block also changes. Therefore, data uploaded to the blockchain is difficult to tamper with. Performing random number prediction on the blockchain ensures transparency and improves the reliability of the prediction results. A trusted execution environment, as opposed to a standard execution environment, is an independent secure executable environment with security capability controls and compliance with specific security requirements. This protects resources within the trusted execution environment from common software attacks and various types of security threats. A trusted execution environment (TEE) is a secure area that provides an execution space through an isolated execution environment. This space has stronger security than a trusted execution environment and more functions than a security chip, providing confidentiality and integrity protection for its code and data.

[0045] based on Figure 1a The blockchain structure described in this application embodiment provides a data processing system based on blockchain, see Figure 1b ,like Figure 1b As shown, the blockchain-based data processing system architecture includes a client corresponding to the approval agency, a client corresponding to the reimbursement requester, a client corresponding to the financial institution, nodes, and a blockchain. The client corresponding to the financial institution is configured with a trusted execution environment. The client can be any of the following: a terminal, a standalone application, an API (Application Programming Interface), or an SDK (Software Development Kit). Nodes can include, but are not limited to, smartphones (such as Android phones and iOS phones), tablets, portable personal computers, mobile internet devices (MIDs), and other devices, which are not limited in this embodiment.

[0046] based on Figure 1b The data processing system based on blockchain described herein provides a method for each device to interact in the data processing system, such as Figure 1cAs shown, this is a schematic diagram of the interactive process of the blockchain-based data processing method provided in an embodiment of the present application. 101. The client corresponding to the reimbursement requester submits a reimbursement request for the target fiscal bill to the client corresponding to the approval agency. 102. The client corresponding to the approval agency sends a fiscal bill verification request to the client corresponding to the financial institution based on the reimbursement request. The fiscal bill verification request carries the identifier of the target fiscal bill and first detailed data. 103. The client corresponding to the financial institution obtains the second detailed data corresponding to the target fiscal bill from the trusted execution environment based on the identifier of the target fiscal bill, and uses the second detailed data to verify the first detailed data to obtain a verification result. 104. The client corresponding to the financial institution sends the verification result to the node. 105. The node writes the verification result to the blockchain. 106. The client corresponding to the financial institution sends the verification result to the client corresponding to the approval agency. 107. The client corresponding to the approval agency uses the verification result to approve the reimbursement request. In the above method, the blockchain and the trusted execution environment fiscal bill verification process are used for management and control, which improves the privacy and reliability of the data verification process.

[0047] Based on the above description, this embodiment of the application provides a data processing method based on blockchain, see Figure 2 The blockchain-based data processing process may include the following steps S201-S204:

[0048] S201. A client corresponding to a financial institution receives a financial bill verification request sent by a client corresponding to an approval agency. The financial bill verification request carries an identifier of a target financial bill and first detailed data.

[0049] In an embodiment of the present application, a fiscal bill verification request is generated by a client corresponding to an approval agency upon receiving a reimbursement request for a target fiscal bill submitted by a reimbursement requester. Specifically, the reimbursement requester may send a reimbursement request to the client corresponding to the approval agency through the client corresponding to the reimbursement requester. The client corresponding to the approval agency then sends a fiscal bill verification request to the client corresponding to the financial institution based on the reimbursement request. The identification of the target fiscal bill carried in the verification request may specifically be a blockchain fiscal bill number, code, etc. The first detailed data may be the fiscal detailed data to be verified provided by the reimbursement requester, such as the background information and timeliness information to be verified corresponding to the target fiscal bill. The client corresponding to the financial institution is internally configured with a trusted execution environment. The trusted execution environment includes a protected area created within a processor. The memory within the protected area is encrypted and decrypted only within the trusted execution environment. The trusted execution environment can receive the corresponding verification request, verify the information carried in the request using internally stored data, and return the verification result. The client corresponding to the financial institution can pre-upload the trusted execution environment address to the blockchain, so that other clients can send corresponding fiscal bill verification requests based on the trusted execution environment address.

[0050] In one implementation scenario, the client of the financial institution stores detailed data corresponding to the financial bills issued by the financial institution in an internal trusted execution environment; after the trusted execution environment is established, the client of the financial institution uploads the registration information of the trusted execution environment to the blockchain. The registration information includes the address of the trusted execution environment, the financial institution corresponding to the trusted execution environment, and the digital signature corresponding to the trusted execution environment. Specifically, the registration information can be written into the smart contract as a parameter in the smart contract, and the smart contract is sent to the node in the blockchain, so that after the node passes the consensus verification of the above-mentioned smart contract, the smart contract is uploaded to the blockchain. The node can specifically perform consensus verification based on the digital signature, that is, verify whether the digital signature is a legal digital signature issued by the digital certificate authority.

[0051] In one implementation, due to the wide variety and number of blockchains, before uploading registration information to a blockchain, the client of a financial institution needs to verify whether the blockchain is reliable. Only after confirming that the blockchain is reliable can the registration information be uploaded. Specifically, the financial institution obtains the number of authenticated nodes in the blockchain. If the number of authenticated nodes is greater than a preset number, the client sends the registration information of the trusted execution environment to the nodes in the blockchain. The authenticated nodes carry a digital signature issued by a digital certificate authority, which can be stored in the blockchain. After obtaining the digital signature of the authenticated node, the financial institution can verify the digital signature based on a special identifier in the digital signature, or send the digital signature to the digital certificate authority to obtain a verification result from the digital certificate authority. Through this approach, the client corresponding to the financial institution can determine the reliability of the blockchain, preventing malicious nodes in an unreliable blockchain from attacking the trusted execution environment based on the registration information, and preventing the leakage of registration information. Furthermore, after receiving the registration information, the node in the blockchain can broadcast the registration information to other nodes in the blockchain, and each node in the blockchain can perform a consensus check on the registration information, wherein the consensus check can specifically check at least one of the following: whether the digital signature corresponding to the trusted execution environment is issued by the digital certificate issuing authority, whether the address of the trusted execution environment is a valid address, and whether the financial institution corresponding to the trusted execution environment is a real financial institution. If the check passes, the node in the blockchain writes the registration information into the blockchain and returns the upload result to the client of the financial institution. The client of the financial institution receives the upload result for the registration information, wherein the upload result indicates the registration information. The location of the corresponding block in the blockchain, such as the block number of the registration information and the block number in the blockchain, can be used by the financial institution's client to query the blockchain for the block corresponding to the registration information based on the location. If the block corresponding to the registration information is detected to be connected to at least N other blocks, the registration information is determined to have been successfully uploaded. N is a positive integer that can be pre-set by the user. For example, if N is 10 and the block corresponding to the registration information is located at block 105 in the blockchain and is numbered 105, the financial institution's client will determine that the registration information has been successfully uploaded if it detects that blocks numbered 106 to 115 are connected to block 105 corresponding to the registration information. Because the blockchain may generate two blocks numbered 105 simultaneously, if a later block in the blockchain is connected to a block not corresponding to 105, the registration information upload will fail. By checking whether the block corresponding to the registration information is connected to at least N other blocks, the registration information upload failure caused by blockchain forks can be prevented, ensuring that the registration information can be queried by all nodes in the blockchain.

[0052] S202. The client corresponding to the financial institution obtains second detailed data corresponding to the target financial bill from the trusted execution environment according to the identifier of the target financial bill.

[0053] In an embodiment of the present application, after the client corresponding to the fiscal institution receives the fiscal bill verification request sent by the client corresponding to the approval agency, it can obtain the second detailed data corresponding to the target fiscal bill from the trusted execution environment based on the identifier of the target fiscal bill. Among them, the identifier of the target fiscal bill can specifically be the blockchain fiscal bill number, code, etc., and the trusted execution environment stores the detailed data corresponding to the fiscal bill issued by the fiscal institution. Each detailed data has a corresponding relationship with the fiscal bill. The client corresponding to the fiscal institution can obtain the second detailed data corresponding to the target fiscal bill from the trusted execution environment based on the corresponding relationship. The second detailed data is trusted detailed data, which can specifically include trusted background information and trusted timeliness information corresponding to the target fiscal bill.

[0054] In one implementation, a fiscal bill verification request carries the private key signature of the approval authority. After receiving the fiscal bill verification request sent by the client corresponding to the approval authority, the client corresponding to the fiscal institution obtains the public key corresponding to the approval authority from the blockchain, and uses the public key corresponding to the approval authority to verify the private key signature. After the verification passes, the second detailed data corresponding to the target fiscal bill is obtained from the trusted execution environment. The approval authority can complete registration in the blockchain in advance and upload its own identification and public key so that other clients can verify the identity of the approval authority from the blockchain. The specific process for the client corresponding to the fiscal institution to obtain the public key corresponding to the approval authority from the blockchain can be: the client corresponding to the fiscal institution sends a public key acquisition request to the node, and the public key acquisition request carries the identification of the approval authority. The node obtains the public key of the approval authority from the blockchain based on the identification of the approval authority and sends the public key to the client corresponding to the fiscal institution.

[0055] S203. The client corresponding to the financial institution verifies the first detailed data using the second detailed data to obtain a verification result.

[0056] In this embodiment of the present application, after the client corresponding to the financial institution obtains the second detailed data corresponding to the target financial document from the trusted execution environment, it uses the second detailed data to verify the first detailed data to obtain a verification result. Specifically, the client corresponding to the financial institution compares the second detailed data with the first detailed data to determine whether the second detailed data matches the first detailed data; if so, the verification result for the first detailed data is determined to be passed. If not, the verification result for the first detailed data is determined to be failed.

[0057] In one implementation, the first detailed data includes the amount of expenditure to be verified in the target fiscal bill, and the second detailed data includes the credible amount of expenditure corresponding to the target fiscal bill. The specific method in which the client corresponding to the fiscal institution compares the second detailed data with the first detailed data is that the client corresponding to the fiscal institution compares the credible amount of expenditure with the amount of expenditure to be verified. If the credible amount of expenditure matches the amount of expenditure to be verified, the verification result is determined to be verification passed. If they do not match, the verification result is determined to be verification failed. For example, the first detailed data records a total expenditure of 20,000 yuan. If the second detailed data records a total expenditure of 20,000 yuan, it is determined that the first detailed data matches the second detailed data, and the verification result is verification passed. If the second detailed data records a total expenditure of 10,000 yuan, it is determined that the first detailed data does not match the second detailed data, and the verification result is verification failed.

[0058] In one implementation, the first detailed data includes the background information to be verified and the timeliness information to be verified corresponding to the target fiscal bill, and the second detailed data includes the trusted background information and the trusted timeliness information corresponding to the target fiscal bill. The specific method for the client corresponding to the fiscal institution to compare the second detailed data with the first detailed data is that the client corresponding to the fiscal institution compares the trusted background information with the background information to be verified. If the trusted background information matches the background information to be verified, the verification result of the first detailed data is determined to be passed, wherein the background information can specifically be the issuing place, issuing time, etc. of the target fiscal bill. Specific characters, corresponding events, etc.; or, the client corresponding to the financial institution compares the credible timeliness information with the timeliness information to be verified. If the credible timeliness information matches the timeliness information to be verified, the verification result of the first detailed data is determined to be passed, wherein the timeliness information can specifically be the issuance time of the target financial bill, the validity period of the target bill, etc., or, the client corresponding to the financial institution compares the credible background information with the background information to be verified, and compares the credible timeliness information with the timeliness information to be verified; if they match, the verification result of the first detailed data is determined to be passed. Optionally, if the second detailed data does not match the first detailed data, the client corresponding to the financial institution can verify the similarity between the first detailed data and the second detailed data, and use the calculated similarity as the verification result for the first detailed data, wherein the specific calculation method of the similarity can be to obtain the number of identical items in the first detailed data and the second detailed data, and determine the ratio between the number of identical items and the total number of items in the first detailed data as the similarity between the first detailed data and the second detailed data. Furthermore, the client corresponding to the financial institution can also write the second detailed data used for verification into the verification result.

[0059] S204. The client corresponding to the financial institution writes the verification result into the blockchain and sends the verification result to the client corresponding to the approval agency, so that the client corresponding to the approval agency uses the verification result to approve the reimbursement request.

[0060] In an embodiment of the present application, after the client corresponding to the financial institution obtains the verification result, the verification result can be written into the blockchain. In a specific implementation, the client corresponding to the financial institution sends the verification result to a target node in the blockchain, so that the node broadcasts the verification result. Each node in the blockchain then performs a consensus check on the broadcasted verification result. If the consensus check passes, the target node packages the verification result into a block and links the block to the blockchain, thereby completing the step of writing the verification result into the blockchain. Optionally, the verification result carries the private key signature of the trusted execution environment. The specific process of each node performing the consensus check on the verification result can be that the node obtains the public key of the trusted execution environment from the blockchain and verifies the private key signature using the public key of the trusted execution environment. If the verification passes, the consensus check result is determined to be a verification pass.

[0061] Furthermore, the client corresponding to the financial institution sends the verification result to the client corresponding to the approval institution, so that the client corresponding to the approval institution approves the reimbursement request using the verification result.

[0062] In an embodiment of the present application, the client corresponding to the financial institution receives a financial bill verification request sent by the client corresponding to the approval agency, and obtains the second detailed data corresponding to the target financial bill from the trusted execution environment according to the identifier of the target financial bill; the client corresponding to the financial institution uses the second detailed data to verify the first detailed data to obtain a verification result; the client corresponding to the financial institution writes the verification result into the blockchain, and sends the verification result to the client corresponding to the approval agency, so that the client corresponding to the approval agency uses the verification result to approve the reimbursement request. In the above method, before the client uploads the registration information, the signature of the node in the blockchain is verified to ensure that the registration information is uploaded to a reliable blockchain. In addition, a trusted execution environment is used to provide a secure area for the second detailed data corresponding to the financial bill issued by the financial institution, thereby ensuring the confidentiality and integrity of the detailed data. The second detailed data is used to verify the first detailed data through the interface provided by the trusted execution environment, thereby ensuring that the first detailed data and the second detailed data will not be tampered with during the verification process, thereby improving the privacy and reliability of the data verification process.

[0063] Based on the above description, this embodiment of the application provides another data processing method based on blockchain, see Figure 3 The blockchain-based data processing process may include the following steps S301-S306:

[0064] S301. The client corresponding to the financial institution sends the registration information of the trusted execution environment to the node of the blockchain, so that the node broadcasts the registration information to other nodes in the blockchain and writes the registration information into the blockchain after the consensus verification of the registration information is passed.

[0065] In an embodiment of the present application, the registration information includes the address of the trusted execution environment and the financial institution corresponding to the trusted execution environment. The trusted execution environment stores detailed data corresponding to the financial bills issued by the financial institution. After the client corresponding to the financial institution generates the trusted execution environment, it can send the registration information of the trusted execution environment to the node of the blockchain. Specifically, the client corresponding to the financial institution sends the registration information to the node in the blockchain. After receiving the registration information, the node broadcasts the registration information to other nodes in the blockchain. The other nodes perform a consensus check on the registration information. Specifically, they can check whether the address of the trusted execution environment is a valid address, whether the trusted execution environment has a corresponding relationship with the financial institution, and whether the digital signature carried by the client of the financial institution is a legal digital signature issued by the digital certificate issuing authority. If the consensus check of other nodes passes, the node in the blockchain can write the registration information into the blockchain, so that other clients and the address of the trusted execution environment stored in the blockchain send corresponding request information.

[0066] S302: The client corresponding to the financial institution receives a financial bill verification request sent by the client corresponding to the approval agency. The financial bill verification request carries an identifier of a target financial bill and first detailed data.

[0067] In the embodiment of the present application, the fiscal bill verification request is generated by the client corresponding to the approval agency when receiving the reimbursement request submitted by the reimbursement requester for the target fiscal bill.

[0068] S303: The client corresponding to the financial institution obtains second detailed data corresponding to the target financial bill from the trusted execution environment according to the identifier of the target financial bill.

[0069] S304: The client corresponding to the financial institution verifies the first detailed data using the second detailed data to obtain a verification result.

[0070] S305. The client corresponding to the financial institution signs the verification result using the private key of the trusted execution environment to obtain a verification result with a digital signature.

[0071] S306. The client corresponding to the financial institution writes the verification result into the blockchain and sends the verification result with the digital signature to the client corresponding to the approval agency, so that the client corresponding to the approval agency can use the verification result to approve the reimbursement request after the digital signature is verified.

[0072] In an embodiment of the present application, after the client corresponding to the financial institution obtains the verification result, the verification result can be written into the blockchain. In a specific implementation, the client corresponding to the financial institution sends the verification result to the target node in the blockchain, so that the node broadcasts the verification result, and each node in the blockchain performs a consensus check on the broadcast verification result. If the consensus check passes, the target node packages the verification result into a block and links the block to the blockchain to complete the step of writing the verification result into the blockchain.

[0073] Furthermore, the client corresponding to the financial institution sends the digitally signed verification result to the client corresponding to the approval agency, so that the client corresponding to the approval agency, after successfully verifying the digital signature, uses the verification result to approve the reimbursement request. In a specific implementation, the client corresponding to the financial institution can pre-upload the public key of the trusted execution environment to the blockchain. The client corresponding to the approval agency can obtain the public key of the trusted execution environment from the blockchain to verify the digital signature, ensuring that the sender of the verification result is trustworthy. After successfully verifying the digital signature, the client corresponding to the approval agency uses the verification result to approve the reimbursement request.

[0074] In this application, blockchain and a trusted execution environment (TEE) are used to manage and control the financial data verification process, enhancing privacy and reliability during data verification. Furthermore, private key signatures are incorporated into the data transmission process to ensure secure and reliable information transmission, enhancing the security of the data transmission process.

[0075] Based on the above description, this embodiment of the application provides another data processing method based on blockchain, see Figure 4 The blockchain-based data processing process may include the following steps S401-S403:

[0076] S401: The client corresponding to the approval agency receives a reimbursement request submitted by a reimbursement requester for a target fiscal bill.

[0077] In this embodiment of the present application, the approval authority can provide reimbursement approval for blockchain fiscal documents and reimburse the corresponding amount after approval. The reimbursement requester can send a reimbursement request for the target fiscal document to the approval authority through the client. The reimbursement request can include the fiscal document and corresponding detailed information (such as the amount of expenditure, time, location, etc.). The client corresponding to the approval authority receives the reimbursement request.

[0078] In one implementation, the reimbursement request carries the private key signature of the reimbursement requester. The approval agency can obtain the public key of the reimbursement requester from the blockchain and use the public key to verify the private key signature. After the verification is passed, step S402 is executed. In this way, the identity of the reimbursement requester can be verified.

[0079] S402: The client corresponding to the approval agency sends a financial bill verification request to the client corresponding to the financial agency according to the reimbursement request.

[0080] In an embodiment of the present application, a fiscal bill verification request carries an identifier of a target fiscal bill and first detailed data. The fiscal bill verification request is used to instruct the client corresponding to the fiscal institution to obtain a verification result of the first detailed data using a trusted execution environment and the identifier of the target fiscal bill. The address of the trusted execution environment of the fiscal institution is stored in the blockchain. In a specific implementation, the client corresponding to the approval agency can query the fiscal institution corresponding to the identifier of the target fiscal bill and the address of the trusted execution environment of the fiscal institution from the blockchain; and send a fiscal bill verification request to the client corresponding to the fiscal institution according to the address of the trusted execution environment of the fiscal institution.

[0081] S403: The client corresponding to the approval agency receives the verification result sent by the client corresponding to the financial agency, and uses the verification result to approve the reimbursement request.

[0082] In an embodiment of the present application, after the client corresponding to the approval agency sends a fiscal bill verification request to the client corresponding to the financial agency based on the reimbursement request, the client corresponding to the financial agency can use the trusted execution environment and the identifier of the target fiscal bill to verify the first detailed data in the fiscal bill verification request. Specifically, the client corresponding to the financial agency obtains the second detailed data corresponding to the target fiscal bill from the trusted execution environment based on the identifier of the target fiscal bill; and compares the second detailed data with the first detailed data to determine whether the second detailed data matches the first detailed data; if they match, the verification result of the first detailed data is determined to be verification passed. If the verification result is verification passed, the client corresponding to the approval agency determines that the reimbursement approval result of the reimbursement request is approval passed, and pays the amount corresponding to the target fiscal bill to the reimbursement requester.

[0083] In one implementation, the verification result carries the digital signature of the financial institution's trusted execution environment. After receiving the digital signature, the client corresponding to the approval agency can obtain the public key of the financial institution's trusted execution environment from the blockchain and verify the digital signature based on the public key of the trusted execution environment; if the verification passes, the verification result is used to approve the reimbursement request.

[0084] In an embodiment of the present application, the client corresponding to the approval agency receives a reimbursement request submitted by the reimbursement requester for the target fiscal bill, and sends a fiscal bill verification request to the client corresponding to the financial institution based on the reimbursement request. The fiscal bill verification request carries the identifier of the target fiscal bill and the first detailed data. The fiscal bill verification request is used to instruct the client corresponding to the financial institution to use the trusted execution environment and the identifier of the target fiscal bill to obtain a verification result of the first detailed data; receive the verification result sent by the client corresponding to the financial institution, and use the verification result to approve the reimbursement request. By implementing the above method, the blockchain and the trusted execution environment can be used to control the verification process of financial data, thereby improving the privacy and reliability of the data verification process.

[0085] In one implementation scenario, the reimbursement requester is a school, and the school applies to the approval agency for reimbursement of financial receipts. The financial receipts can be issued by the school from the financial agency for a certain project (such as school expansion, etc.) and uploaded to the chain. When the financial agency issues the receipts, it will write some detailed information (such as project content, contractors, project cycles, etc.) into the local trusted execution environment; when the school needs to reimburse the approval agency for the expenses used in the project, it can provide the approval agency with the corresponding financial receipts and detailed data. The approval agency sends a verification request to the financial agency based on the financial receipts, so that the financial agency verifies the request based on the detailed data stored in the trusted execution environment, and returns the verification result to the approval agency, such as Figure 5The following is a schematic diagram of the specific process for this scenario: 501. The financial institution uploads registration information to a node in the blockchain. The registration information includes the address of the trusted execution environment (TEE). 502. After the registration information passes consensus verification, the node uploads the registration information to the blockchain. 503. The financial institution issues a receipt and stores the corresponding trusted detailed data in the TEE. This could be a school's receipt for project funds. 504. The school sends the financial receipt and detailed data to the approval authority. 505. The approval authority sends a request to the blockchain to obtain the TEE address. 506. The blockchain returns the TEE address corresponding to the financial institution to the approval authority. 507. Based on the TEE address, the approval authority sends a data verification request to the financial institution. The data verification request includes the detailed data to be verified, provided by the school. 508. The financial institution verifies the detailed data to be verified based on the trusted detailed data stored in the TEE. 509. The financial institution returns the verification result to the approval authority. 510. The approval authority uses the verification result to approve the reimbursement request from the school. 511. The approval authority sends the approval authority to the school. By implementing the above method, a verification scheme for blockchain fiscal receipts is provided, and the detailed information of the fiscal receipts does not need to be uploaded to the blockchain, which increases the confidentiality of the detailed information. In addition, the blockchain and trusted execution environment fiscal receipt verification process are used for management and control, which improves the privacy and reliability of the data verification process.

[0086] Based on the description of the above-mentioned data processing method embodiment based on blockchain, the embodiment of the present application also discloses a data processing device based on blockchain, which can be a computer program (including program code) running on the client corresponding to the financial institution, or a physical device included in the client corresponding to the financial institution. The data processing device based on blockchain can execute Figure 2-Figure 3 See the method shown in Figure 6 The blockchain-based data processing device 60 includes: a receiving module 601, an acquisition module 602, a verification module 603, a writing module 604, and a sending module 605.

[0087] Receiving module 601 is configured to receive a fiscal bill verification request sent by a client corresponding to an approval authority, the fiscal bill verification request carrying an identifier of a target fiscal bill and first detailed data. The fiscal bill verification request is generated by the client corresponding to the approval authority upon receiving a reimbursement request for the target fiscal bill submitted by a reimbursement requester;

[0088] An acquisition module 602 is configured to acquire second detailed data corresponding to the target fiscal note from a trusted execution environment according to the identifier of the target fiscal note;

[0089] Verification module 603, configured to verify the first detailed data using the second detailed data to obtain a verification result;

[0090] A writing module 604 is used to write the verification result into the blockchain;

[0091] The sending module 605 is configured to send the verification result to the client corresponding to the approval agency, so that the client corresponding to the approval agency can use the verification result to perform reimbursement approval on the reimbursement request.

[0092] In one implementation, the acquisition module 602 is further configured to acquire the number of authenticated nodes in the blockchain, wherein the authenticated nodes carry a digital signature issued by a digital certificate authority;

[0093] A sending module 605 is configured to send the registration information of the trusted execution environment to a node in the blockchain if the number of authenticated nodes is greater than a preset number, so that the node broadcasts the registration information to other nodes in the blockchain and writes the registration information into the blockchain after consensus verification of the registration information is passed; wherein the registration information includes the address of the trusted execution environment, the financial institution corresponding to the trusted execution environment, and the digital signature corresponding to the trusted execution environment; the trusted execution environment stores detailed data corresponding to financial bills issued by the financial institution; and the consensus verification includes verifying whether the digital signature corresponding to the trusted execution environment is issued by the digital certificate authority;

[0094] The receiving module 601 is further configured to:

[0095] receiving an upload result for the registration information, the upload result indicating a location of a block corresponding to the registration information in the blockchain;

[0096] If it is detected according to the position that the block corresponding to the registration information is connected to at least N other blocks, it is determined that the registration information is uploaded successfully, and the step of receiving the fiscal bill verification request sent by the client corresponding to the approval agency is executed, and N is a positive integer.

[0097] Comparing the second detailed data with the first detailed data to determine whether the second detailed data matches the first detailed data;

[0098] In one implementation, the first detailed data includes the to-be-verified background information and the to-be-verified timeliness information corresponding to the target fiscal bill, and the second detailed data includes the credible background information and the credible timeliness information corresponding to the target fiscal bill. The verification module 603 is specifically configured to:

[0099] Comparing the second detailed data with the first detailed data to determine whether the second detailed data matches the first detailed data, wherein the comparison includes comparing the trusted background information with the background information to be verified, and / or comparing the trusted timeliness information with the timeliness information to be verified;

[0100] If there is a match, the verification result of the first detailed data is determined to be passed.

[0101] In one implementation, the sending module 605 is specifically configured to:

[0102] Signing the verification result using the private key of the trusted execution environment to obtain a verification result with a digital signature;

[0103] The verification result with the digital signature is sent to the client corresponding to the approval agency, so that the client corresponding to the approval agency can use the verification result to approve the reimbursement request after verifying the digital signature.

[0104] In the embodiment of the present application, the receiving module 601 receives a fiscal bill verification request sent by a client corresponding to the approval agency, and the obtaining module 602 obtains the second detailed data corresponding to the target fiscal bill from the trusted execution environment according to the identifier of the target fiscal bill; the verification module 603 uses the second detailed data to verify the first detailed data to obtain a verification result; the writing module 604 writes the verification result into the blockchain, and the sending module 605 sends the verification result to the client corresponding to the approval agency, so that the client corresponding to the approval agency uses the verification result to approve the reimbursement request. By implementing the above method, the blockchain and the trusted execution environment can be used to control the verification process of fiscal data, thereby improving the privacy and reliability of the data verification process.

[0105] Based on the description of the above-mentioned data processing method embodiment based on blockchain, the embodiment of the present application also discloses a data processing device based on blockchain, which can be a computer program (including program code) running on the client corresponding to the approval agency, or a physical device included in the client corresponding to the approval agency. The data processing device based on blockchain can execute Figure 4 See the method shown in Figure 7 The blockchain-based data processing device 70 includes: a receiving module 701, a sending module 702, an approval module 703, an acquisition module 704, and a verification module 705.

[0106] Receiving module 701, configured to receive a reimbursement request submitted by a reimbursement requester for a target fiscal bill;

[0107] A sending module 702 is configured to send a fiscal bill verification request to a client corresponding to the fiscal institution based on the reimbursement request, wherein the fiscal bill verification request carries an identifier of the target fiscal bill and first detailed data, and instructs the client corresponding to the fiscal institution to obtain a verification result of the first detailed data using a trusted execution environment and the identifier of the target fiscal bill;

[0108] The receiving module 701 is further configured to receive the verification result sent by the client corresponding to the financial institution;

[0109] The approval module 703 is configured to use the verification result to perform reimbursement approval on the reimbursement request.

[0110] In one implementation, the reimbursement request carries the identifier of the target fiscal document, and the sending module 702 is specifically configured to:

[0111] Querying the blockchain for the financial institution corresponding to the identifier of the target financial instrument and the address of the trusted execution environment of the financial institution;

[0112] A fiscal bill verification request is sent to a client corresponding to the fiscal institution according to the address of the trusted execution environment of the fiscal institution.

[0113] In one implementation, the verification result carries a digital signature of the financial institution's trusted execution environment, and the acquisition module 704 is configured to obtain the public key of the financial institution's trusted execution environment from the blockchain;

[0114] The verification module 705 is used to verify the digital signature based on the public key of the trusted execution environment;

[0115] If the verification is passed, the step of using the verification result to approve the reimbursement request is performed.

[0116] In one implementation, the approval module 703 is specifically configured to:

[0117] If the verification result is passed, the reimbursement approval result of the reimbursement request is determined to be passed, and the amount corresponding to the target fiscal bill is paid to the reimbursement requester.

[0118] In an embodiment of the present application, the receiving module 701 receives a reimbursement request submitted by the reimbursement requesting party for the target fiscal bill, and the sending module 702 sends a fiscal bill verification request to the client corresponding to the financial institution based on the reimbursement request. The fiscal bill verification request carries the identifier of the target fiscal bill and the first detailed data. The fiscal bill verification request is used to instruct the client corresponding to the financial institution to obtain a verification result of the first detailed data using a trusted execution environment and the identifier of the target fiscal bill; the receiving module 701 receives the verification result sent by the client corresponding to the financial institution, and the approval module 703 uses the verification result to approve the reimbursement request. By implementing the above method, the blockchain and the trusted execution environment can be used to manage and control the verification process of financial data, thereby improving the privacy and reliability of the data verification process.

[0119] See Figure 8 , is a schematic diagram of the structure of a terminal provided in an embodiment of the present application. Figure 8 As shown, the terminal includes: at least one processor 801, an input device 803, an output device 804, a memory 805, and at least one communication bus 802, which can be used to carry the client corresponding to the financial institution. The communication bus 802 is used to realize the connection and communication between these components. The memory 805 can be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 805 can also be at least one storage device located away from the aforementioned processor 801. The processor 801 can be combined with Figure 6 In the described apparatus, a set of program codes is stored in the memory 805, and the processor 801, the input device 803, and the output device 804 call the program codes stored in the memory 805. The apparatus is used to perform the following operations:

[0120] Processor 801 is configured to receive a fiscal bill verification request sent by a client corresponding to an approval authority, the fiscal bill verification request carrying an identifier of a target fiscal bill and first detailed data, the fiscal bill verification request being generated by the client corresponding to the approval authority upon receiving a reimbursement request for the target fiscal bill submitted by a reimbursement requester;

[0121] Processor 801 is configured to obtain second detailed data corresponding to the target fiscal note from a trusted execution environment according to the identifier of the target fiscal note;

[0122] Processor 801 is configured to verify the first detailed data using the second detailed data to obtain a verification result;

[0123] Processor 801, configured to write the verification result into the blockchain;

[0124] The processor 801 is configured to send the verification result to a client corresponding to the approval agency, so that the client corresponding to the approval agency approves the reimbursement request based on the verification result.

[0125] In one implementation, the processor 801 is specifically configured to:

[0126] Obtaining the number of authenticated nodes in the blockchain, each authenticated node carrying a digital signature issued by a digital certificate authority;

[0127] If the number of authenticated nodes is greater than a preset number, the registration information of the trusted execution environment is sent to a node in the blockchain, so that the node broadcasts the registration information to other nodes in the blockchain, and writes the registration information into the blockchain after consensus verification of the registration information is passed; wherein the registration information includes the address of the trusted execution environment, the financial institution corresponding to the trusted execution environment, and the digital signature corresponding to the trusted execution environment, the trusted execution environment stores detailed data corresponding to financial bills issued by the financial institution, and the consensus verification includes verifying whether the digital signature corresponding to the trusted execution environment is issued by the digital certificate issuing authority;

[0128] receiving an upload result for the registration information, the upload result indicating a location of a block corresponding to the registration information in the blockchain;

[0129] If it is detected according to the position that the block corresponding to the registration information is connected to at least N other blocks, it is determined that the registration information is uploaded successfully, and the step of receiving the fiscal bill verification request sent by the client corresponding to the approval agency is executed, and N is a positive integer.

[0130] In one implementation, the first detailed data includes to-be-verified background information and to-be-verified timeliness information corresponding to the target fiscal bill, and the second detailed data includes trusted background information and trusted timeliness information corresponding to the target fiscal bill. The processor 801 is specifically configured to:

[0131] Comparing the second detailed data with the first detailed data to determine whether the second detailed data matches the first detailed data, wherein the comparison includes comparing the trusted background information with the background information to be verified, and / or comparing the trusted timeliness information with the timeliness information to be verified;

[0132] If there is a match, the verification result of the first detailed data is determined to be passed.

[0133] In one implementation, the processor 801 is specifically configured to:

[0134] Signing the verification result using the private key of the trusted execution environment to obtain a verification result with a digital signature;

[0135] The verification result with the digital signature is sent to the client corresponding to the approval agency, so that the client corresponding to the approval agency can use the verification result to approve the reimbursement request after verifying the digital signature.

[0136] In the embodiments of the present application, the financial data verification process is managed and controlled by adopting blockchain and a trusted execution environment, thereby improving the privacy and reliability of the data verification process.

[0137] See Figure 9 , is a structural diagram of another terminal provided in an embodiment of the present application. Figure 9 As shown, the terminal includes: at least one processor 901, an input device 903, an output device 904, a memory 905, and at least one communication bus 902, which can be used to carry the client corresponding to the approval agency. The communication bus 902 is used to realize the connection and communication between these components. The memory 905 can be a high-speed RAM memory or a non-volatile memory, such as at least one disk memory. The memory 905 can also be at least one storage device located away from the aforementioned processor 901. The processor 901 can be combined with Figure 7 In the described apparatus, a set of program codes is stored in the memory 905, and the processor 901, the input device 903, and the output device 904 call the program codes stored in the memory 905. The program codes are used to perform the following operations:

[0138] Processor 901 is configured to receive a reimbursement request submitted by a reimbursement requester for a target fiscal bill;

[0139] Processor 901 is configured to send a fiscal bill verification request to a client corresponding to a fiscal institution based on the reimbursement request, the fiscal bill verification request carrying an identifier of the target fiscal bill and first detailed data, the fiscal bill verification request being configured to instruct the client corresponding to the fiscal institution to obtain a verification result of the first detailed data using a trusted execution environment and the identifier of the target fiscal bill;

[0140] Processor 901 is configured to receive the verification result sent by the client corresponding to the financial institution;

[0141] Processor 901 is configured to perform reimbursement approval on the reimbursement request using the verification result.

[0142] In one implementation, the processor 901 is specifically configured to:

[0143] Querying the blockchain for the financial institution corresponding to the identifier of the target financial instrument and the address of the trusted execution environment of the financial institution;

[0144] A fiscal bill verification request is sent to a client corresponding to the fiscal institution according to the address of the trusted execution environment of the fiscal institution.

[0145] In one implementation, the processor 901 is specifically configured to:

[0146] Obtaining a public key of the financial institution's trusted execution environment from the blockchain;

[0147] verifying the digital signature based on the public key of the trusted execution environment;

[0148] If the verification is passed, the step of using the verification result to approve the reimbursement request is performed.

[0149] In one implementation, the processor 901 is specifically configured to:

[0150] If the verification result is passed, the reimbursement approval result of the reimbursement request is determined to be passed, and the amount corresponding to the target fiscal bill is paid to the reimbursement requester.

[0151] In the embodiments of the present application, the financial data verification process is managed and controlled by adopting blockchain and a trusted execution environment, thereby improving the privacy and reliability of the data verification process.

[0152] The modules described in the embodiments of the present application may be implemented by a general-purpose integrated circuit, such as a CPU (Central Processing Unit), or by an ASIC (Application Specific Integrated Circuit).

[0153] It should be understood that in the embodiments of the present application, the processor referred to may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0154] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 8 or Figure 9 Just one thick line is used, but that does not mean there is only one bus or one type of bus.

[0155] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing related hardware through a computer program. The program can be stored in a computer-readable storage medium, and when executed, the program can include the processes in the above-described method embodiments. The computer-readable storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0156] The above disclosure is only a preferred embodiment of the present application, and certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A data processing method based on blockchain, characterized in that: Applied to a client corresponding to a financial institution, wherein the client corresponding to the financial institution is internally configured with a trusted execution environment, the method includes: Obtaining the number of authenticated nodes in a blockchain, wherein the authenticated nodes carry digital signatures issued by a digital certificate authority; if the number of authenticated nodes is greater than a preset number, sending registration information of the trusted execution environment to nodes in the blockchain, so that the nodes broadcast the registration information to other nodes in the blockchain, and writing the registration information into the blockchain after a consensus check on the registration information is passed; wherein the registration information includes the address of the trusted execution environment, the financial institution corresponding to the trusted execution environment, and the digital signature corresponding to the trusted execution environment, and the consensus check includes verifying at least one of the following: whether the digital signature corresponding to the trusted execution environment is issued by the digital certificate authority, whether the address of the trusted execution environment is a valid address, and whether the financial institution corresponding to the trusted execution environment is a real financial institution; receiving an upload result for the registration information, the upload result indicating a location of a block corresponding to the registration information in the blockchain; and determining that the registration information has been successfully uploaded if it is detected, based on the location, that the block corresponding to the registration information is connected to at least N other blocks, where N is a positive integer; Receiving a fiscal bill verification request sent by a client corresponding to the approval authority based on the address of the trusted execution environment stored in the blockchain, the fiscal bill verification request carrying an identifier of a target fiscal bill and first detailed data, the fiscal bill verification request being generated by the client corresponding to the approval authority upon receiving a reimbursement request submitted by a reimbursement requester for the target fiscal bill; Obtaining second detailed data corresponding to the target fiscal bill from the trusted execution environment based on the identifier of the target fiscal bill; wherein the trusted execution environment stores detailed data corresponding to the fiscal bill issued by the financial institution, the detailed data corresponding to the fiscal bill including background information and timeliness information of the fiscal bill; Verifying the first detailed data using the second detailed data to obtain a verification result; The verification result is written into the blockchain, and the verification result is sent to the client corresponding to the approval agency, so that the client corresponding to the approval agency uses the verification result to approve the reimbursement request.

2. The method according to claim 1, characterized in that The first detailed data includes the to-be-verified background information and the to-be-verified timeliness information corresponding to the target fiscal bill, and the second detailed data includes the credible background information and the credible timeliness information corresponding to the target fiscal bill. The verification of the first detailed data using the second detailed data to obtain a verification result includes: Comparing the second detailed data with the first detailed data to determine whether the second detailed data matches the first detailed data, wherein the comparison includes comparing the trusted background information with the background information to be verified, and / or comparing the trusted timeliness information with the timeliness information to be verified; If there is a match, the verification result of the first detailed data is determined to be passed.

3. The method according to claim 1, characterized in that Before sending the verification result to the client corresponding to the approval agency so that the client corresponding to the approval agency uses the verification result to approve the reimbursement request, the method further includes: Signing the verification result using the private key of the trusted execution environment to obtain a verification result with a digital signature; The sending of the verification result to the client corresponding to the approval agency so that the client corresponding to the approval agency uses the verification result to approve the reimbursement request includes: The verification result with the digital signature is sent to the client corresponding to the approval agency, so that the client corresponding to the approval agency can use the verification result to approve the reimbursement request after verifying the digital signature.

4. A data processing method based on blockchain, characterized in that: Applied to a client corresponding to an approval agency, the method includes: receiving a reimbursement request submitted by a reimbursement requester for a target fiscal bill; A fiscal bill verification request is sent to the client corresponding to the financial institution according to the reimbursement request and the address of the trusted execution environment stored in the blockchain, the fiscal bill verification request carries the identifier of the target fiscal bill and the first detailed data, the client corresponding to the financial institution is internally configured with the trusted execution environment, and the fiscal bill verification request is used to instruct the client corresponding to the financial institution to obtain the second detailed data corresponding to the target fiscal bill from the trusted execution environment according to the identifier of the target fiscal bill, and use the second detailed data to verify the first detailed data to obtain a verification result; wherein, the detailed data corresponding to the fiscal bill issued by the financial institution is stored in the trusted execution environment, and the detailed data corresponding to the fiscal bill includes the background information and timeliness information of the fiscal bill; wherein, the registration process of the client corresponding to the financial institution for the trusted execution environment includes: obtaining the number of authenticated nodes in the blockchain, and the authenticated nodes carry a digital signature issued by a digital certificate issuing authority; if If the number of authenticated nodes is greater than a preset number, the registration information of the trusted execution environment is sent to the node of the blockchain, so that the node broadcasts the registration information to other nodes in the blockchain, and writes the registration information into the blockchain after passing the consensus check on the registration information; wherein the registration information includes the address of the trusted execution environment, the financial institution corresponding to the trusted execution environment, and the digital signature corresponding to the trusted execution environment, and the consensus check includes verifying at least one of the following: whether the digital signature corresponding to the trusted execution environment is issued by the digital certificate issuing authority, whether the address of the trusted execution environment is a valid address, and whether the financial institution corresponding to the trusted execution environment is a real financial institution; receiving an upload result for the registration information, the upload result indicating the position of the block corresponding to the registration information in the blockchain; if it is detected that the block corresponding to the registration information is connected to at least N other blocks based on the position, it is determined that the registration information has been uploaded successfully, where N is a positive integer; The verification result sent by the client corresponding to the financial institution is received, and the reimbursement request is approved by using the verification result.

5. The method according to claim 4, characterized in that The reimbursement request carries the identifier of the target fiscal bill, and sending a fiscal bill verification request to a client corresponding to the fiscal institution based on the reimbursement request and the address of the trusted execution environment stored in the blockchain includes: Querying the blockchain for the financial institution corresponding to the identifier of the target financial instrument and the address of the trusted execution environment of the financial institution; A fiscal bill verification request is sent to a client corresponding to the fiscal institution according to the address of the trusted execution environment of the fiscal institution.

6. The method according to claim 4 or 5, characterized in that The verification result carries a digital signature of the trusted execution environment of the financial institution. Before using the verification result to approve the reimbursement request, the method further includes: Obtaining a public key of the trusted execution environment of the financial institution from the blockchain, and verifying the digital signature based on the public key of the trusted execution environment; If the verification is passed, the step of using the verification result to approve the reimbursement request is performed.

7. The method according to claim 4, characterized in that The using the verification result to perform reimbursement approval on the reimbursement request includes: If the verification result is passed, the reimbursement approval result of the reimbursement request is determined to be passed, and the amount corresponding to the target fiscal bill is paid to the reimbursement requester.

8. A terminal, characterized in that: The method comprises a processor, an input interface, an output interface and a memory, wherein the processor, the input interface, the output interface and the memory are interconnected, wherein the memory is used to store a computer program, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method according to any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the processor is caused to perform the method according to any one of claims 1 to 7.

Images