Distributed Ledger Event Blocks for Duplicate Processing Prevention

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current systems within enterprise organizations individually post events without communication, leading to the potential for duplicate event postings, which can result in inaccuracies and loss of reputation.

Innovation Solution

A computing platform with a machine learning engine trained on historical data to determine whether to post an event to a user account, using a distributed ledger to validate and store event blocks, and an invalid key database to prevent duplicate postings.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If systems individually post events without communication, then each system operates independently and simply, but duplicate events are posted leading to inaccuracies and reputation loss

Engineering Contradiction:

Improveaccuracy of event postingVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

A distributed ledger acts as an intermediary between multiple systems, enabling them to share event information without direct communication. The ledger validates event hashes and maintains a consensus record, preventing duplicate postings while preserving system independence. This resolves the contradiction by introducing a mediating structure that ensures accuracy without requiring complex direct inter-system communication protocols.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where event hashes are validated against the distributed ledger before posting. If an event hash matches an existing record, the posting is prevented. This feedback loop ensures accuracy by continuously checking against previously posted events, resolving the contradiction through automated verification rather than complex coordination protocols.

Inventive Principle:

Principle #23Feedback

2Reliability

If a distributed ledger is used to validate events, then duplicate postings are prevented, but system complexity and validation time increase

Engineering Contradiction:

Improveprevention of duplicate eventsVSAvoidevent validation time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

Event hashes are generated and validated against the distributed ledger before actual event posting occurs. This preliminary validation prevents duplicate events from being posted in the first place, eliminating the need for post-processing checks or corrections. The time investment in preliminary validation is offset by preventing costly duplicate processing and maintaining system integrity.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Instead of copying and communicating entire event data between systems, the patent uses cryptographic hashes of events as compact representations. These hash copies are stored in the distributed ledger and used for validation, dramatically reducing data transmission and processing time while maintaining the ability to detect duplicates with high reliability.

Inventive Principle:

Principle #26Copying

3Measurement precision

If machine learning is used to assess events, then posting accuracy improves, but computational resources and processing time increase

Engineering Contradiction:

Improveevent assessment accuracyVSAvoidcomputational energy consumption

Core Design Contradiction:

Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The machine learning model performs partial assessment by evaluating only critical features of events rather than comprehensive analysis of all data. This selective assessment achieves sufficient accuracy for duplicate detection and event validation without the full computational overhead of complete event analysis, balancing precision with energy efficiency.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The machine learning model is trained in advance on historical event data to learn patterns of duplicate events and anomalies. This preliminary training enables the model to make rapid assessments during actual event processing without requiring intensive real-time computation, as the heavy computational work was performed during the offline training phase.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS20250293888A1Intelligent Method to Prevent Duplicate Event Processing Using a Distributed Ledger

Publication Date: 2025.09.18 BANK OF AMERICA CORP

AI summary

Arrangements for preventing duplicate event processing are provided. A computing platform may train a machine learning engine to determine whether to post an event to a corresponding user account. The computing platform may receive a first event hash corresponding to a first event. The computing platform may query a database to determine whether information in the first event hash matches an invalid key stored in the database. The computing platform may generate a first event block based on the first event hash. The computing platform may validate the first event block by establishing a consensus with one or more event assessment systems. The computing platform may use the machine learning engine to output an even exception score and compare the event exception score to a threshold. The computing platform may post the first event based on the event exception score meeting or exceeding the threshold.