Blockchain Transaction Verification to Prevent Booking Breaks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems fail to efficiently and accurately process large transaction datasets across computing systems, leading to transaction breaks due to miscommunication, typographical errors, and differences in computing systems and transaction booking practices, which can cause erroneous results and financial losses.
Innovation Solution
A blockchain-based method for authenticating transactions by ensuring both parties agree on transaction terms, generating transaction blocks only when terms match, and maintaining privacy to prevent transaction breaks, while ensuring compliance with internal rules and avoiding renegotiation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual entry methods are used to input transaction data into computer systems, then flexibility in handling different transaction terms is maintained, but human error and network error increase leading to transaction breaks
Solution Approach 1:
The system enables automatic self-verification of transaction terms between trading parties. Each party's computer system automatically compares its transaction terms with the counterparty's terms, identifying mismatches without human intervention. This self-service approach eliminates manual entry errors while maintaining the flexibility to handle diverse transaction types and terms.
Solution Approach 2:
The system implements automatic feedback loops where transaction terms are continuously verified and compared between parties. When mismatches are detected, the system provides immediate feedback to identify specific disputed terms, allowing for automated resolution or targeted human review. This feedback mechanism significantly reduces transaction breaks caused by entry errors.
2Productivity
If computers automatically process large volumes of transactions, then processing speed and efficiency increase, but the ability to detect and resolve term mismatches becomes more complex
Solution Approach 1:
The system segments the complex task of transaction verification into discrete, manageable components. Each transaction term (e.g., price, quantity, delivery date) is independently verified and compared between parties. This segmentation allows computers to efficiently process large volumes of transactions while systematically detecting mismatches in each individual term, reducing overall complexity.
Solution Approach 2:
The system introduces an intermediary verification layer that automatically compares transaction terms between trading parties before final processing. This intermediary mechanism acts as a buffer that simplifies the detection of term mismatches by providing a standardized comparison framework, enabling high-speed processing without increasing detection complexity.
3Use of energy by stationary object
If transaction breaks are allowed to occur and be processed later, then continuous processing of transactions is maintained, but erroneous results and unreliable data counters are generated
Solution Approach 1:
The system performs preliminary verification of transaction terms before transactions are finalized and recorded. By checking for term mismatches in advance and requiring resolution before processing completes, the system prevents erroneous transactions from entering the system. This preliminary action ensures both continuous processing capability and high measurement precision, as only verified accurate transactions are processed.
Data Source
AI summary
A computer-implemented method comprising receiving a transaction request from a first computing device, the transaction request corresponding to a pending transaction between the first computing device and a second computing device and comprising a first set of transaction attributes; appending block instances to blockchains of the first and second computing devices, retrieving or receiving, from the second computing device, a second set of transaction attributes; when the first set of transaction attributes match, identifying a second blockchain associated with the pending transaction; automatically executing a protocol to compare the first set of transaction attributes with data stored onto a ledger of the identified second blockchain; and, in response to determining that the first set of transaction attributes complies with data of the ledger of the identified second blockchain, appending block instance to the blockchain comprising data corresponding to the transaction request to blockchains of the first and second computing devices.


