Blockchain Audit Interface for Transaction Record Reconciliation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Inconsistent data records between transaction databases and transaction blockchains occur due to differences in writing methods and inherent problems, leading to inefficiencies and increased audit loads, especially in scenarios where data is uploaded to the blockchain first, recorded to the database, recorded to both simultaneously, or recorded to the database first and then uploaded to the blockchain.
Innovation Solution
A blockchain audit system that includes an audit control interface to compare and confirm data consistency between transaction databases and blockchains, using audit-confirmed transaction records and generating audit blocks to reconcile discrepancies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is uploaded to the blockchain first and then recorded to the database, then the blockchain record is ensured, but the database record may fail causing data inconsistency
Solution Approach 1:
The system performs preliminary actions by uploading data to the blockchain first to ensure immutable recording, then subsequently records to the database. The audit mechanism proactively checks for inconsistencies and triggers re-upload operations before data loss occurs, preventing the information loss problem rather than reacting to it.
Solution Approach 2:
The audit mechanism continuously monitors and compares records between blockchain and database, providing feedback when inconsistencies are detected. This feedback loop triggers automatic correction operations including re-uploading data to blockchain or database, ensuring data consistency is maintained through continuous verification and correction.
2Reliability
If data is recorded to the database first and then uploaded to the blockchain, then the database record is ensured, but the blockchain upload may fail causing data inconsistency
Solution Approach 1:
The system performs preliminary recording to the database first to ensure reliable storage, then subsequently uploads to the blockchain for immutable verification. The audit mechanism proactively checks upload status and triggers re-upload operations to blockchain if failures occur, preventing data inconsistency.
Solution Approach 2:
The audit mechanism monitors the upload process from database to blockchain, providing feedback when uploads fail or data becomes inconsistent. This triggers automatic correction operations including re-uploading to blockchain, ensuring data consistency through continuous verification and correction loops.
3Productivity
If data is recorded to the database and blockchain simultaneously, then transaction speed is improved, but inconsistencies still occur due to independent failure modes
Solution Approach 1:
The system performs simultaneous preliminary recording to both database and blockchain to maximize transaction speed. The audit mechanism then proactively verifies both records and triggers selective re-upload operations only when inconsistencies are detected, maintaining speed while preventing data loss.
Solution Approach 2:
The audit mechanism provides continuous feedback by comparing simultaneous records in both database and blockchain. When inconsistencies are detected, it triggers targeted correction operations to specific systems, maintaining high productivity while ensuring data consistency through selective re-upload operations.
4Reliability
If multiple transaction data correction operations are performed, then data consistency is restored, but the audit load increases significantly
Solution Approach 1:
The system extracts and isolates only the inconsistent records for correction operations, rather than auditing and correcting all records. The audit mechanism identifies specific mismatched transactions and triggers re-upload operations only for those particular records, reducing overall audit load and time consumption while maintaining data consistency.
Solution Approach 2:
The system performs partial correction operations only on the specific records that show inconsistencies, rather than performing excessive full-system re-auditing and re-uploading. This targeted approach restores data consistency while minimizing the time and resources consumed by audit operations.
5Reliability
If re-uploading data to blockchain is performed, then data consistency is achieved, but transaction time is prolonged
Solution Approach 1:
The system extracts and identifies only the specific records that require re-uploading to blockchain, rather than re-uploading all transaction data. This selective approach achieves data consistency for the inconsistent records while minimizing the time prolongation associated with re-upload operations.
Solution Approach 2:
The system performs partial re-upload operations only on the specific records that show inconsistencies, rather than performing excessive full transaction re-uploads. This restores data consistency while reducing the overall transaction time by avoiding unnecessary re-upload operations on already consistent records.
Data Source
AI summary
A blockchain audit system includes: an audit control interface, receiving a transaction data which is written into a transaction database; an audit blockchain connected to the audit control interface, to record multiple audit-confirmed transaction records. The audit control interface generates a transaction record according to the received transaction data and adds the transaction record to a database transaction record summary table; if the transaction record is in a database transaction record missing list, the transaction record in the database transaction record missing list is removed, otherwise, if the transaction record is in a blockchain transaction record summary table, the transaction record is added to an audit-confirmed transaction record list, and a transaction block number of the transaction record is written back to the corresponding transaction data in the transaction database.