Supernode Consensus for Blockchain Data Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Decentralized blockchain systems face challenges in providing consistent and accurate data due to the lack of synchronization among nodes, leading to user experience issues, scalability problems, and reliability concerns when relying on individual nodes or load balancing.

Innovation Solution

A supernode system is introduced that runs a consensus algorithm across a network of blockchain nodes to determine a canonical head and commitment level, ensuring a consistent view of the blockchain data is provided, using a proprietary coordinator service for optimized reliability and scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If individual nodes or load balancing are used to serve blockchain data, then system simplicity is maintained, but data consistency and reliability deteriorate due to lack of synchronization among nodes

Engineering Contradiction:
Improvesystem structureVSAvoiddata consistency
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent introduces a supernode as an intermediary component that mediates between the blockchain network and users/apps. The supernode receives proposed canonical heads from multiple blockchain nodes, determines the correct state through consensus, and provides a consistent view of blockchain data to users. This mediator approach maintains system simplicity while ensuring data consistency and reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple blockchain nodes are used to improve reliability and scalability, then system robustness increases, but data consistency deteriorates due to synchronization issues among nodes

Engineering Contradiction:
Improvesystem robustnessVSAvoiddata consistency
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

The supernode implements a feedback mechanism by receiving proposed canonical heads from multiple blockchain nodes, evaluating their validity through consensus algorithms, and determining the correct state. This feedback loop ensures that despite multiple nodes operating independently, the system maintains data consistency by continuously validating and synchronizing the blockchain state.

Inventive Principle:
Principle #23Feedback

3Reliability

If a supernode system with consensus algorithm is implemented to ensure data consistency, then reliability improves, but system complexity increases

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the blockchain system into distinct functional components: multiple blockchain nodes that produce blocks, a supernode that performs consensus and determines canonical heads, and users/apps that consume data. This segmentation allows the complex consensus mechanism to be isolated in the supernode layer, maintaining simplicity for the majority of the system while ensuring reliability where needed.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11914616B1Systems and methods for creating a consistent blockchain including block commitment determinations
Publication Date: 2024.02.27 ALCHEMY INSIGHTS INC
  • US11914616B1 patent drawing
  • US11914616B1 patent drawing
  • US11914616B1 patent drawing

AI summary

Systems and methods for creating a consistent blockchain including block commitment determinations are disclosed herein. An example method includes receiving a request for blockchain data from an application or a user, receiving proposed canonical heads from a plurality of blockchain nodes, receiving votes to determine a correct state for a consistent blockchain that includes a canonical head, the blockchain data being included in the consistent view of a blockchain, determining the canonical head based on the votes, determining a commitment level for at least one block in the consistent view of the blockchain, providing the consistent view of the blockchain to the application or the user, and exposing the commitment level for the at least one block.