TWI812510B - Blockchain audit system - Google Patents

Abstract

A blockchain audit system includes: an audit control interface that receives a transaction data written to a transaction database; an audit blockchain that is used to store multiple successfully audited transaction records and is connected to the audit control interface; The audit control interface generates a transaction record based on the received transaction data and adds the transaction record to a database transaction record summary table; if the transaction record exists in a database transaction record omission summary table, then Remove the transaction record from the database's missing transaction record list. Otherwise, if the transaction record exists in a blockchain transaction record list, add the transaction record to an audited successful transaction record. summary table, and write back a transaction block number of the transaction record to the corresponding transaction data in the transaction database.

Description

Blockchain audit system

A system for auditing, especially a blockchain auditing system, which is used to audit the operation of the blockchain.

Blockchain distributed ledger technology has been successfully used for many years since its inception in 2009, which proves that blockchain technology is feasible. In the application of general blockchain technology, due to the limitations of distributed ledger technology, efficient queries cannot be carried out. Therefore, in practice, traditionally used specific databases such as relational databases are used to assist distributed ledger technology. so that it can operate effectively. And the database and the distributed ledger of the blockchain exist at the same time, so that the original process of the application can not be restricted by the blockchain, and the distributed ledger of the blockchain can be used to confirm the data. The contents of the library have not been tampered with.

Please refer to Figure 5. Figure 5 is a schematic diagram of a blockchain 20 to explain the basic structure and operation of a general blockchain. The blockchain 20 has multiple nodes (Node) such as node A, node B and node C. Each node stores a ledger (Ledger). For example, node A stores ledger a, node B stores ledger a, and node B stores ledger a. Ledger b is saved, and node C saves ledger c; the physical device that constitutes the node can be a server, computer equipment or mobile phone that can be connected to the Internet, and the entity that constitutes the ledger can be an electronic file. Electronic files are stored in a memory device such as a semiconductor memory device such as dynamic memory (DRAM), static memory (SRAM), flash memory (Flash memory), solid state disk (SSD), or magnetic memory such as hard drive. CD player, or CD, etc.

However, in order for the blockchain to ensure the reliability of its data, it takes some time when a data is written into a blockchain block and a new block is generated, and all nodes in the blockchain must synchronize the data to achieve consensus. , which takes more time; and is limited by blockchain technical specifications and is not efficient in querying transaction records. Therefore, blockchain application systems are usually used in conjunction with blockchain technology and database technology. Therefore, there are some differences in speed and writing methods between the linked use of the blockchain and the database. These differences, coupled with the potential problems that the blockchain and the database themselves may have, make the data Writing to the blockchain or writing data to the database may not be successful. For example, in the application architecture shown in Figure 6, consider the scenario of first uploading to the chain and then recording (hereinafter referred to as scenario 1). First, a transaction data 30 is recorded to a blockchain 31 through an application interface 34 (hereinafter referred to as "data uploading"). "Chain"), if the data uploading fails, the transaction process needs to be re-executed. If the data is successfully uploaded, the transaction data 30 is then recorded to a database 32 through another application interface 33 (hereinafter referred to as "data record") , if the data recording fails at this time, only the blockchain 31 has records, which will cause the records of the database 32 and the blockchain 31 to be inconsistent. Consider the scenario of recording data first and then uploading the data to the chain (hereinafter referred to as Scenario 2). First, the transaction data 30 is recorded to the database 32 through the application interface 33. If the database recording fails, the transaction process needs to be re-executed. If The data recording is successful, and then the transaction data 30 is recorded to the blockchain 31 through the application interface 34. At this time, if the data fails to be uploaded to the chain, only the database 32 has records, which will also cause the database 32 to be The records of the two blockchains 31 are inconsistent. Consider the scenario of simultaneous data recording and data uploading (hereinafter referred to as scenario three). The transaction data 30 is recorded to the database 32 through the application interface 33. If the database recording fails, this has nothing to do with the blockchain 31. At the same time, the transaction data 30 is recorded to the blockchain 31 through the application interface 34. If the upload fails, this has nothing to do with the database 32, which will also cause records in both the database 32 and the blockchain 31. Inconsistent.

Based on the above content, if the database and blockchain are used in conjunction, data inconsistency may occur in the above three scenarios. In practice, it was found that in scenario 1, first upload to the chain and then record, the transaction data correction operation will generate three blockchain records, which will increase the audit load. Scenario 2: Record first and then upload it to the chain. Uploading the chain will affect the transaction time. Canceled transactions must be updated in the ledger block before they can be recorded consistently. Scenario 3: Simultaneous uploading and recording, the transaction confirmation time is longer, the transaction failure rate increases, re-transactions generate multiple blockchain update records, and the database record does not contain the transaction block number. Based on the analysis of the above three scenarios, it can be seen that after the introduction of blockchain, there may still be problems with inconsistent records between the database and the blockchain distributed ledger. In view of this, and in the face of the continued development of blockchain applications, With the rapid development, how to effectively avoid the inconsistency in the records between the above-mentioned database and the blockchain distributed ledger is an urgent problem that needs to be solved.

In order to solve the above problems, the present invention provides a blockchain audit system, which is used in a transaction database and a transaction blockchain to audit and confirm the data consistency between a transaction database and a transaction blockchain. , the transaction database is used to store multiple transaction data; the transaction blockchain is used to store multiple transaction data and make the transaction data unmodifiable;

In one embodiment, the main technical means include: An audit control interface receives multiple transaction data that have been written to a transaction database, and receives multiple transaction data that has been uploaded to a transaction blockchain; An audit blockchain is connected to the audit control interface. The audit blockchain is used to store multiple successfully audited transaction records; The audit control interface compares the received multiple transaction data that has been written to the transaction database and the received multiple transaction data that has been uploaded to the transaction blockchain. The same transaction data in the audit control interface is recorded as a successful transaction record, and when the audit control interface receives a transaction block number of a new transaction block from the transaction block chain, the audit control interface Record these successfully audited transactions to generate a new audit block in the audit blockchain; And the different transaction data in the two are recorded by the audit control interface to reflect the differences in the transaction data in the transaction database and the transaction blockchain.

In one embodiment, the main technical means include: An audit control interface receives a transaction data that has been written to a transaction database; An audit blockchain is connected to the audit control interface. The audit blockchain is used to store multiple successfully audited transaction records; the audit control interface also performs the following steps: Step 1A: Generate a transaction record based on the received transaction data and add the transaction record to a database transaction record summary table; Step 2A: If the transaction record does not exist in a database transaction record omission summary table, go to step 4A; Step 3A: Remove the transaction record from the total list of missing transaction records in the database; Step 4A: If the transaction record does not exist in a blockchain transaction record summary table, go to step 7A; Step 5A: Add the transaction record to a summary list of successfully audited transaction records; Step 6A: Upload the transaction record to the audit blockchain and go to step 1A; Step 7A: Add the transaction record to a blockchain transaction record omission list, and go to step 1A; Among them, the database transaction record summary table records all relevant transaction records of the transaction database, the blockchain transaction record summary table records all relevant transaction records of a transaction blockchain, and the database transaction record omission summary table Record transaction records that exist in the blockchain transaction record summary table but do not exist in the database transaction record summary table. The blockchain transaction record omission summary table records exist in the database transaction record summary table but do not exist in the database transaction record summary table. For transaction records that do not exist in the blockchain transaction record summary table, the successfully audited transaction record summary table records all transaction records that exist in both the database transaction record summary table and the blockchain transaction record summary table; Each transaction record in the database transaction record summary has a transaction sequence number, each transaction record in the blockchain transaction record summary has a transaction sequence number and a transaction block number, and the audited successful transaction record summary Each transaction record in the database has a transaction sequence number and a transaction block number. Each transaction record in the database's transaction record omission summary table has a transaction sequence number. Each transaction record in the blockchain transaction record omission summary table has a transaction sequence number. Each transaction record has a transaction sequence number.

In another embodiment, the main technical means include the following steps: An audit control interface receives a transaction data that has been uploaded to a transaction blockchain; An audit blockchain is connected to the audit control interface. The audit blockchain is used to store multiple successfully audited transaction records; the audit control interface also performs the following steps: Step 1B: Generate a transaction record based on the received transaction data and add the transaction record to a blockchain transaction record summary table; Step 2B: If the transaction record does not exist in a blockchain transaction record missing list, go to step 4B; Step 3B: Remove the transaction record from the total list of missing transaction records in the blockchain; Step 4B: If the transaction record does not exist in a database transaction record summary table, go to step 7B; Step 5B: Add the transaction record to a summary list of successfully audited transaction records; Step 6B: Upload the transaction record to the audit blockchain and go to step 1B; Step 7B: Add the transaction record to the total list of missing transaction records in a database and go to step 1B;

Preferably, the blockchain audit system further includes the following steps: When the audit control interface receives a transaction block number of a new transaction block from the transaction block chain, the audit control interface will add the transaction block number with the data of the new transaction block in the audit successful transaction record summary table. All successfully audited transaction records with the same transaction block number generate a new audit block in the audit blockchain.

Preferably, the blockchain audit system further includes the following steps: When the transaction record is uploaded to the audit blockchain, the audit control interface further writes back a transaction block number of the transaction record to the corresponding transaction data in the transaction database.

Please refer to Figure 1, which is a schematic diagram of the architecture of the blockchain audit system 1 of the present invention. The blockchain audit system 1 of the present invention includes a transaction database 2 that can store multiple transaction data, a transaction block chain 3 that can store multiple transaction data, an audit block chain 4, an audit control interface 5, and a transaction Input interface 11, a data uploading interface 12 and a database recording interface 14. The transaction input interface 11 may be a computer device or an application program executed on the computer device. The entity of the transaction database 2 may be a computer device with the ability to run a database software and a physical or virtual storage device with the ability to store data and information. The transaction blockchain 3 can be a plurality of physical or virtual computer devices with networking capabilities (hereinafter referred to as multiple transaction chain nodes) and multiple storage devices corresponding to the multiple transaction chain nodes, all of which have storage capabilities. A ledger file capability. The audit blockchain 4 can be a plurality of physical or virtual computer devices with networking capabilities (hereinafter referred to as multiple audit chain nodes) and multiple storage devices corresponding to the multiple audit chain nodes, all of which have the ability to store a Ledger archive capabilities. The entity of the audit control interface 5 may be an application program that is executed by a computer device with networking capabilities to obtain information on one or more transaction data from the transaction database 2 and obtain information from the transaction blockchain 3 Obtain information about one or more transaction data. The entity of the data uploading interface 12 can be an application program that is executed on an external computer device with networking capabilities to upload information of a transaction data 10 to the transaction blockchain 3, and can retrieve information from the transaction. The blockchain 3 obtains information on one or more transaction data. Similarly, the entity of the database recording interface 14 can be an application program executed on the external computer device with networking capabilities to store the transaction data 10 Information is written into the transaction database 2.

Following the above, a transaction data 10 is uploaded to the transaction blockchain 3 through the data uplink interface 12, and at the same time, the transaction data 10 is also written into the transaction data 10 through the database recording interface 14. The transaction database2. When the transaction data 10 is successfully uploaded to the transaction blockchain 3, the transaction blockchain 3 will provide a transaction record of the transaction data 10 to the audit control interface 5 for audit purposes. The record has a unique transaction sequence number and a transaction block number of the transaction block to which the transaction record belongs; similarly, when the transaction data 10 is successfully written to the transaction database 2, the transaction database 2 2 will also provide the transaction record of the transaction data 10 to the audit control interface 5 for audit purposes. At this time, the transaction record has the transaction serial number.

Please refer to Figures 2A and 2B. Figures 2A and 2B illustrate the first embodiment of the blockchain audit system of the present invention. As shown in Figure 2A, the audit control interface 5 also has a database transaction record queue. The database transaction record queue is a first-in-first-out queue, and the following steps are performed: Receive and store a transaction data provided by the transaction database 2: Step 10A: The audit control interface 5 determines whether a transaction data 10 is successfully written into the transaction database 2. When no transaction data 10 is successfully written into the transaction database 2, return to step 10A; when a transaction data 10 is successfully written into the transaction database 2, 10. When the transaction database 2 is successfully written, go to step 11A; Step 11A: Generate a transaction record based on the transaction data 10 and add the transaction record to a database transaction record queue, and return to step 10A.

As shown in Figure 2B, the audit control interface 5 processes and audits the transaction records provided by the database transaction record queue in the following steps: Step 0A: The audit control interface 5 determines whether the transaction record queue of the transaction database is empty. If the transaction record queue of the transaction database is empty, return to step 0A; Step 1A: The audit control interface 5 retrieves the oldest transaction record from the transaction record queue of the transaction database, and adds the transaction record to a database transaction record summary table; Step 2A: Determine whether the transaction record is found in the missing transaction record table of a database. When the transaction record is not found in the missing transaction record table of the database, go to step 4A; Step 3A: Remove the transaction record from the total list of missing transaction records in the database; Step 4A: Determine whether the transaction record is found in the blockchain transaction record summary table. When the transaction record is not found in the blockchain transaction record summary table, go to step 7A; Step 5A: Add the transaction record to a summary list of successfully audited transaction records; Step 6A: Upload the transaction record to an audit blockchain 5, and write back a transaction block number of the transaction record to the corresponding transaction record in the transaction database 2, to step 0A; Step 7A: Add the transaction record to a block chain transaction record omission list, and go to step 0A.

Among them, the database transaction record summary table records all relevant transaction records of the transaction database 2, the blockchain transaction record summary table records all relevant transaction records of the transaction block chain 3, and the database transaction record is missing The master table records transaction records that exist in the blockchain transaction record master table but do not exist in the database transaction record master table. The blockchain transaction record omission master table records exist in the database transaction record master table. However, for transaction records that do not exist in the blockchain transaction record summary table, the successfully audited transaction record summary table records all transaction records that exist in both the database transaction record summary table and the blockchain transaction record summary table.

Among them, each transaction record in the database transaction record summary table has a transaction sequence number, and each transaction record in the blockchain transaction record summary table has a transaction sequence number and a transaction block number. The audited successful transaction record Each transaction record in the master list has a transaction sequence number and a transaction block number. Each transaction record in the database transaction record omission master table has a transaction sequence number. The block chain transaction record omission master table has a transaction sequence number. Each transaction record has a transaction sequence number.

Please refer to Figures 3A and 3B. Figures 3A and 3B show the second embodiment of the blockchain audit system of the present invention. As shown in Figure 3A, the audit control interface 5 also has a blockchain transaction record queue. The blockchain transaction record queue is a first-in-first-out queue, and is The following steps receive and store a transaction record provided by the transaction blockchain 3: Step 10B: The audit control interface 5 determines whether a transaction data 10 is successfully uploaded to the transaction blockchain 3. When no transaction data 10 is successfully uploaded to the transaction blockchain 3, return to step 10B; Step 11B: Generate a transaction record based on the transaction data 10 and add the transaction record to a blockchain transaction record queue, and return to step 10B.

As shown in Figure 3B, the audit control interface 5 processes and audits the transaction records provided by the blockchain transaction record queue in the following steps: Step 0B: The audit control interface 5 determines whether the transaction blockchain transaction record queue is empty. If the transaction blockchain transaction record queue is empty, return to step 0B; Step 1B: The audit control interface 5 retrieves the oldest transaction record from the transaction blockchain transaction record queue, and adds the transaction record to a blockchain transaction record summary table; Step 2B: Determine whether the transaction record is found in a blockchain transaction record omission summary list. When the transaction record is not found in the blockchain transaction record omission summary table, go to step 4B; Step 3B: Remove the transaction record from the total list of missing transaction records in the blockchain; Step 4B: Determine whether the transaction record is found in the database transaction record summary table. When the transaction record is not found in the database transaction record summary table, go to step 7B; Step 5B: Add the transaction record to a summary list of successfully audited transaction records; Step 6B: Upload the transaction record to an audit blockchain 3, and write back a transaction block number of the transaction record to the corresponding transaction record in the transaction database 2, to step 0B; Step 7B: Add the transaction record to a database transaction record missing list, and go to step 0B.

Please refer to Figure 4, which shows the third embodiment of the blockchain audit system of the present invention. When the audit control interface 5 receives a transaction block number of a new transaction block from the transaction block chain 3, the audit control interface 5 will record all transactions in the audited successful transaction record table that are related to the new transaction area. A new audit block is generated in the audit block chain 4 for successfully audited transaction records with the same transaction block number of the block data. See the steps below: Step 1C: The audit control interface 5 determines whether a transaction block number of a new transaction block is received from the transaction block chain 3. When the audit control interface 5 does not receive a new transaction block number from the transaction block chain 3, When adding a transaction block number of the transaction block, go to step 1C; Step 2C: Generate a new audit block in the audit block chain 4 for all audited successful transaction records in the total list of audited successful transaction records that have the same transaction block number as the new transaction block. Step 1C.

It can be seen from the above that the audit blockchain 4 is used to audit the successful login of "simultaneous recording and uploading", and when the transaction blockchain 3 generates a new transaction block, the corresponding transaction block will also be generated. The audit block simultaneously uses a database transaction record omission summary table and a blockchain transaction record omission summary table to record transaction records that have not yet been successfully audited. In this way, the invention can use the audit blockchain to audit whether a transaction data is " has been successfully recorded in a database 2 and successfully uploaded to a transaction chain 3".

1: Blockchain audit system 2: Transaction database 3: Transaction Blockchain 4: Audit Blockchain 5: Audit control interface 10:A transaction information 11: Transaction input interface 12:Data uploading interface 14: Database recording interface 20:Blockchain 30:A transaction information 31:Blockchain 32:Database 33: Application interface 34: Application interface

Figure 1 is a schematic diagram of the blockchain audit system of the present invention. Figures 2A and 2B are flow diagrams of the first embodiment of the blockchain audit system of the present invention. Figures 3A and 2B are flow diagrams of the second embodiment of the blockchain audit system of the present invention. Figure 4 is a schematic flow chart of the third embodiment of the blockchain audit system of the present invention. Figure 5 is a schematic diagram of the architecture of Xizhi Blockchain. Figure 6 is a schematic diagram of the application architecture of Xizhi Blockchain.

1: Blockchain audit system

2: Transaction database

3: Transaction Blockchain

4: Audit Blockchain

5: Audit control interface

10:A transaction information

11: Transaction input interface

12:Data uploading interface

14: Database recording interface

Claims (8)

A blockchain audit system including: An audit control interface receives multiple transaction data that have been written to a transaction database, and receives multiple transaction data that has been uploaded to a transaction blockchain; An audit blockchain is connected to the audit control interface. The audit blockchain is used to store multiple successfully audited transaction records; The audit control interface compares the received multiple transaction data that has been written to the transaction database and the received multiple transaction data that has been uploaded to the transaction blockchain. The same transaction data in the audit control interface is recorded as a successful transaction record, and when the audit control interface receives a transaction block number of a new transaction block from the transaction block chain, the audit control interface These successfully audited transactions are recorded in the audit blockchain to generate a new audit block. The blockchain audit system as described in request item 1 further includes the following steps: the different transaction data between the two is recorded by the audit control interface to reflect the transactions between the transaction database and the transaction blockchain. Differences in data. A blockchain audit system including: An audit control interface receives a transaction data that has been written into a transaction database; An audit blockchain is connected to the audit control interface. The audit blockchain is used to store multiple successfully audited transaction records; the audit control interface also performs the following steps: Step 1A: Generate a transaction record based on the received transaction data and add the transaction record to a database transaction record summary table; Step 2A: If the transaction record does not exist in a database transaction record omission summary table, go to step 4A; Step 3A: Remove the transaction record from the total list of missing transaction records in the database; Step 4A: If the transaction record does not exist in a blockchain transaction record summary table, go to step 7A; Step 5A: Add the transaction record to a summary list of successfully audited transaction records; Step 6A: Upload the transaction record to the audit blockchain and go to step 1A; Step 7A: Add the transaction record to a blockchain transaction record omission list, and go to step 1A; Among them, the database transaction record summary table records all relevant transaction records of the transaction database, the blockchain transaction record summary table records all relevant transaction records of a transaction blockchain, and the database transaction record omission summary table Record transaction records that exist in the blockchain transaction record summary table but do not exist in the database transaction record summary table. The blockchain transaction record omission summary table records exist in the database transaction record summary table but do not exist in the database transaction record summary table. For transaction records that do not exist in the blockchain transaction record summary table, the successfully audited transaction record summary table records all transaction records that exist in both the database transaction record summary table and the blockchain transaction record summary table; Among them, each transaction record in the database transaction record summary table has a transaction sequence number, and each transaction record in the blockchain transaction record summary table has a transaction sequence number and a transaction block number. The audited successful transaction record Each transaction record in the master list has a transaction sequence number and a transaction block number. Each transaction record in the database transaction record omission master table has a transaction sequence number. The block chain transaction record omission master table has a transaction sequence number. Each transaction record has a transaction sequence number. A blockchain audit system including: An audit control interface receives a transaction data that has been uploaded to a transaction blockchain; An audit blockchain is connected to the audit control interface. The audit blockchain is used to store multiple successfully audited transaction records; the audit control interface also performs the following steps: Step 1B: Generate a transaction record based on the received transaction data and add the transaction record to a blockchain transaction record summary table; Step 2B: If the transaction record does not exist in a blockchain transaction record missing list, go to step 4B; Step 3B: Remove the transaction record from the total list of missing transaction records in the blockchain; Step 4B: If the transaction record does not exist in a database transaction record summary table, go to step 7B; Step 5B: Add the transaction record to a summary list of successfully audited transaction records; Step 6B: Upload the transaction record to the audit blockchain and go to step 1B; Step 7B: Add the transaction record to the total list of missing transaction records in a database and go to step 1B; Among them, the database transaction record summary table records all relevant transaction records of the transaction database, the blockchain transaction record summary table records all relevant transaction records of a transaction blockchain, and the database transaction record omission summary table Record transaction records that exist in the blockchain transaction record summary table but do not exist in the database transaction record summary table. The blockchain transaction record omission summary table records exist in the database transaction record summary table but do not exist in the database transaction record summary table. For transaction records that do not exist in the blockchain transaction record summary table, the successfully audited transaction record summary table records all transaction records that exist in both the database transaction record summary table and the blockchain transaction record summary table; Among them, each transaction record in the database transaction record summary table has a transaction sequence number, and each transaction record in the blockchain transaction record summary table has a transaction sequence number and a transaction block number. The audited successful transaction record Each transaction record in the master list has a transaction sequence number and a transaction block number. Each transaction record in the database transaction record omission master table has a transaction sequence number. The block chain transaction record omission master table has a transaction sequence number. Each transaction record has a transaction sequence number. The blockchain audit system as described in request item 3 or 4 further includes the following steps: When the audit control interface receives a transaction block number of a new transaction block from the transaction block chain, the audit control interface will add the transaction block number with the data of the new transaction block in the audit successful transaction record summary table. All successfully audited transaction records with the same transaction block number generate a new audit block in the audit blockchain. The blockchain audit system as described in request item 3 or 4 further includes the following steps: When the transaction record is uploaded to the audit blockchain, the audit control interface further writes back a transaction block number of the transaction record to the corresponding transaction data in the transaction database. The blockchain audit system as described in claim 1 or 4, wherein the audit control interface is an application program and is executed on a computer device with networking capabilities. The blockchain audit system as claimed in claim 1 or 4, wherein the audit blockchain includes at least one node, and each of the at least one node has at least one consistent blockchain block.

Images