Universal Ledger for Cross-Asset Event Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current ledgers are tied to underlying assets, leading to onerous transaction tracking and data transfer issues, resulting in incorrect or hard-to-correlate summaries when events occur across different ledgers.
Innovation Solution
An extensible, universal ledger that records abstract tracking units, using a template-based, event-driven, self-referential system with a bitemporal journal and journal manager engine, allowing dynamic instruction updates and deterministic replay of events.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate ledgers are used for different assets, then each ledger can be specialized for its asset type, but transaction tracking becomes onerous and data transfer between ledgers is complex and error-prone
Solution Approach 1:
The patent implements a universal ledger system where a single ledger can handle multiple asset types through configurable event sources and subscription mechanisms. The ledger engine processes events from various sources (exchanges, OTC desks, corporate actions) and allows subscribers to filter and process events relevant to their specific assets, combining the benefits of specialization with the simplicity of a unified system.
2Adaptability or versatility
If data is transferred between different ledgers, then events can be tracked across multiple assets, but the resulting data becomes incorrect, differently summarized or hard to correlate
Solution Approach 1:
The patent introduces an event subscription mechanism as an intermediary layer between the universal ledger and application-specific processing. Subscribers define filtering criteria and processing logic that operate on the standardized event stream, ensuring that each application receives accurate, relevant data without direct manipulation or transformation that could introduce errors or inconsistencies.
3Ease of operation
If a universal ledger is implemented, then transaction tracking across multiple applications becomes seamless, but the system complexity increases
Solution Approach 1:
The patent segments the universal ledger system into distinct functional components: an event source layer that generates standardized events, a ledger engine layer that processes and stores events, and a subscription layer that delivers filtered events to applications. This segmentation allows each component to remain simple while the integrated system provides seamless cross-application tracking.
4Reliability
If ledgers are tied to underlying assets, then asset-specific requirements are met, but runtime extensibility is limited
Solution Approach 1:
The patent implements a dynamic event subscription model where filtering criteria, processing logic, and subscriber configurations can be modified at runtime without requiring system reconfiguration or code changes. Subscribers can dynamically subscribe to, unsubscribe from, or modify their event processing rules based on changing asset requirements while the ledger continues to operate with full compliance.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
Methods and systems for an extensible, universal ledger. One of the methods includes receiving at a journal manager engine a register transaction type request for a first transaction type, the journal manager engine reading and writing to a journal that stores a history of object state and of code by which object state is changed, wherein the register transaction type request is based at least in part on a template and specifies at least one action that can be performed as part of the first transaction type; writing the transaction type request to the journal including an operation definition for the first transaction type; receiving a transaction request of the first transaction type; obtaining the operation definition from the journal; executing an operation in response to the transaction request to produce a transaction result; and recording the transaction result in the journal.