Hierarchic Blockchain for High-Frequency Trading Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Blockchain-based open-ledger systems are ill-suited for high-frequency applications like electronic trading due to slow transaction validation times, which can exceed the requirements of financial institutions needing rapid transaction processing.

Innovation Solution

A hierarchic blockchain system is implemented, where lower-level blockchains process high-frequency transactions quickly, and higher-level blockchains validate transactions at slower frequencies, with multiple levels in between to bridge the speed gap, using 256-bit SSL encryption to secure and validate transactions efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a traditional blockchain ledger is used to ensure transaction validity and immutability, then transaction integrity is improved, but transaction processing speed deteriorates

Engineering Contradiction:
Improvetransaction integrityVSAvoidtransaction processing speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent divides the blockchain system into multiple hierarchical levels (Level 0, Level 1, Level 2, etc.), where each level processes transactions at different speeds. Level 0 provides the highest speed for time-sensitive transactions, while higher levels provide increasing validation thoroughness. This segmentation allows the system to simultaneously offer both fast transaction processing and strong integrity guarantees by routing transactions to appropriate levels based on their requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediate validation layers between the transaction source and the main blockchain ledger. These intermediate layers perform preliminary validation and grouping of transactions before they are committed to the main ledger, acting as mediators that reduce the validation burden on all nodes while maintaining security. This intermediary approach speeds up processing by distributing validation work across multiple hierarchical levels.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If all transactions are validated by all existing blockchain nodes, then transaction security is improved, but processing time increases significantly

Engineering Contradiction:
Improvetransaction securityVSAvoidvalidation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The validation process is segmented across multiple hierarchical levels. Not all nodes validate all transactions at all levels. Instead, nodes at different levels perform validation appropriate to their level's security requirements and processing capabilities. This segmentation of validation responsibilities reduces the time each transaction spends in the system while maintaining overall security through layered validation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial validation at intermediate levels rather than requiring full validation by all nodes for every transaction. Transactions receive sufficient validation at each hierarchical level to ensure security appropriate to that level's risk profile, without requiring the complete validation process to occur at every level. This partial action approach reduces total validation time while maintaining adequate security.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11978118B2Event management and validation platform using a recursive hierarchic blockchain
Publication Date: 2024.05.07 BANK OF AMERICA CORP
  • US11978118B2 patent drawing
  • US11978118B2 patent drawing
  • US11978118B2 patent drawing

AI summary

Aspects of the disclosure relate to implementation of a recursive hierarchic blockchain for event validation and processing. A computing platform may receive event data from first and second data sources. The computing platform may store, in a first distributed ledger, an event record for each event from the first data source and may store, in a second distributed ledger, an event record for each event from both data sources. In response to determining that a validation condition for a current block of the second distributed ledger has been satisfied, the computing platform may compute a hash and generate a numeric representation of the first distributed ledger. In a new block of the second distributed ledger, the computing platform may store the hash and the numeric representation. The computing platform may write, to the new block of the second distributed ledger, additional event data from both data sources.