Cross-Blockchain Event Matching to Prevent Transaction Breaks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems fail to efficiently and accurately process large transaction datasets across multiple parties due to transaction breaks caused by miscommunication, typographical errors, and differences in computing systems, leading to unreliable data and potential financial losses.
Innovation Solution
A blockchain-based method that authenticates transactions by ensuring both parties agree on terms, generating transaction blocks only when terms match, and maintaining privacy by using hash values and private channels to prevent transaction breaks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual entry methods are used to record transaction data in respective databases, then each party can independently enter transaction terms, but human error and network error cause transaction breaks and data inconsistency
Solution Approach 1:
The patent merges the independent transaction entry capabilities of multiple parties into a single blockchain ledger. Instead of each party maintaining separate databases that may diverge, all parties write to a shared, immutable ledger that ensures data consistency across the network while preserving independent entry through decentralized validation.
Solution Approach 2:
The blockchain acts as an intermediary between transacting parties, mediating the recording of transaction terms. Rather than parties directly comparing their separate records, the blockchain provides a neutral, trusted platform that automatically reconciles differences through consensus mechanisms, preventing transaction breaks.
2Extent of automation
If computers generate transaction data based on internal calendars or clocks, then transaction timing can be automatically recorded, but unsynchronized clocks cause different time periods to be identified leading to transaction breaks
Solution Approach 1:
The patent applies equipotentiality by establishing a unified time reference across all participating computers through the blockchain network. All nodes operate from the same time基准 (reference), eliminating time synchronization issues. The blockchain's consensus mechanism ensures that transaction timing is recorded consistently across all parties regardless of their local clock settings.
3Reliability
If the computer identifies many transaction breaks daily, then data integrity can be monitored, but processing speed decreases due to determining which terms to process
Solution Approach 1:
The patent implements preliminary action by validating transaction terms before they are committed to the blockchain. Through pre-validation and consensus checks, potential transaction breaks are prevented before they occur, rather than being detected and resolved after the fact. This eliminates the need for post-hoc analysis of conflicting terms.
Solution Approach 2:
The blockchain system provides immediate feedback on transaction validity through its consensus mechanism. When a transaction is proposed, the network quickly validates it and provides feedback on acceptance or rejection, enabling real-time detection and correction of data integrity issues without slowing down overall processing.
4Adaptability or versatility
If conventional methods are used to process transaction data, then existing systems can handle transactions, but they fail to provide fast, efficient, and continuous analysis of transaction data
Solution Approach 1:
The patent replaces conventional mechanical processing systems with a blockchain-based distributed system. Instead of centralized databases that require sequential processing and reconciliation, the blockchain uses cryptographic validation and consensus mechanisms that enable parallel, continuous processing of transactions across multiple nodes simultaneously.
Data Source
AI summary
A computer-implemented method comprising receiving a first plurality of event requests each corresponding to a pending event, the pending event corresponding to a transfer of a digital asset between blockchains; appending a seller block instance to a blockchain for each of the first plurality of event requests, each seller block instance comprising a different seller set of event attributes of the first plurality of event requests; receiving a second plurality of event requests; appending a buyer block instance to the blockchain for each of the second plurality of event requests, each buyer block instance comprising different a buyer set of event attributes of the second plurality of event requests; and responsive to a seller set of event attributes from a seller block instance matching a buyer set of event attributes from a buyer block instance corresponding to the seller block instance, appending a match block instance to the blockchain.


