Local Blockchain Execution for Low-Latency Consensus Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing blockchain networks experience significant latency in performing operations such as executing chaincode, which affects user experience and efficiency.

Innovation Solution

A Low-latency Blockchain Processing System (LBPS) maintains a local copy of the blockchain and performs operations on this copy to provide near-instant results, while simultaneously requesting the same operation on the main network, ensuring validation and recording on the blockchain, thus achieving low-latency processing with decentralized security and immutability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If blockchain operations are performed through the main network with consensus mechanisms, then security and decentralization are ensured, but operation latency increases significantly

Engineering Contradiction:
Improveblockchain securityVSAvoidoperation latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs blockchain operations in advance on a local copy of the blockchain before submitting them to the main network. This preliminary execution allows the system to obtain operation results immediately while still ensuring eventual consistency with the main blockchain through subsequent submission and verification.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system maintains a local copy of the blockchain that can be used for executing operations without affecting the main network. This copy enables fast local processing while the main blockchain remains intact for security and consensus purposes. The local copy is periodically synchronized with the main blockchain to maintain consistency.

Inventive Principle:
Principle #26Copying

2Productivity

If operations are executed on the main blockchain network, then decentralized validation occurs, but processing speed decreases due to consensus requirements

Engineering Contradiction:
Improveprocessing speedVSAvoidconsensus mechanism complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments blockchain operations into two parts: local execution on a copied blockchain for fast processing, and submission to the main network for decentralized validation. This segmentation allows the system to benefit from both fast local processing and the security of decentralized consensus without the full overhead of running consensus for every operation.

Inventive Principle:
Principle #1Segmentation

3Loss of time

If a local copy of the blockchain is maintained for fast processing, then operation latency is reduced, but system complexity increases

Engineering Contradiction:
Improveoperation latencyVSAvoidsystem architecture complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system creates and maintains a local copy of the blockchain that can be used for executing operations without affecting the main network. This copy enables fast local processing while the main blockchain remains intact for security and consensus purposes. The local copy is periodically synchronized with the main blockchain to maintain consistency, reducing the need for complex real-time synchronization mechanisms.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12556604B2Systems and methods for low-latency blockchain processing
Publication Date: 2026.02.17 VERIZON PATENT & LICENSING INC
  • US12556604B2 patent drawing
  • US12556604B2 patent drawing
  • US12556604B2 patent drawing

AI summary

A system described herein may maintain a local copy of a blockchain that is associated with a blockchain network, receive a first request to perform a blockchain operation with respect to the blockchain, perform the requested blockchain operation with respect to the local copy of the blockchain to generate a first result, and output the first result in response to the first request. The system may output a second request to the blockchain network to perform the blockchain operation, receive a second result from the blockchain network in response to the second request, wherein the second result is generated by the blockchain network based on the blockchain network performing the blockchain operation with respect to the blockchain, wherein the second result is received from the blockchain network after outputting the first result in response to the first request, and maintain information indicating whether the first result matches the second result.