Blockchain World State Integrity Validation via Checkpoint Hashing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized databases face issues such as single points of failure, dependency on network connectivity, limited data access, and difficulty in retrieving lost data due to lack of redundancy, necessitating a solution for enhanced reliability and integrity validation.

Innovation Solution

A blockchain network is employed for decentralized database management, utilizing a system with blockchain users, endorser nodes, and orderer nodes to create and validate world state checkpoint transactions, calculate and sign hashes, and verify world state integrity through consensus among peers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a centralized database is used to store and maintain data at a single location, then data redundancy is minimized and security control is simplified, but the system suffers from a single point of failure and limited data access

Engineering Contradiction:
Improvedata security controlVSAvoiddata access capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the centralized database into multiple distributed nodes across a network. Each node maintains a copy of the database, transforming a single centralized storage system into multiple distributed storage points. This segmentation enables simultaneous data access from multiple locations while maintaining data integrity through cryptographic hashing and consensus mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a spatial dimension to data storage by distributing database copies across multiple physical locations and network nodes. This dimensional transformation from single-point to multi-point distribution enables parallel access paths and eliminates the single point of failure inherent in centralized systems.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Ease of operation

If data is stored in a centralized database at a single location, then management and maintenance are simplified, but the system has a single point of failure and limited fault tolerance

Engineering Contradiction:
Improvedatabase managementVSAvoidfault tolerance
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent creates multiple identical copies of the database across different network nodes. Each node maintains a complete replica of the database, ensuring that if one node fails, the data remains accessible from other nodes. This copying strategy provides inherent fault tolerance while maintaining data consistency through cryptographic verification.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent changes the operational parameters of the database system by introducing distributed consensus protocols and cryptographic hashing mechanisms. These parameter changes enable automatic fault detection and recovery without centralized management, maintaining ease of operation while dramatically improving reliability.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If a centralized database experiences high traffic, then all data is accessible from one location, but bottlenecks occur and performance degrades

Engineering Contradiction:
Improvedata access efficiencyVSAvoidaccess time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the database access load across multiple nodes by distributing data copies throughout the network. Users can access data from the nearest or least-loaded node, dividing the centralized access bottleneck into multiple parallel access paths. This segmentation maintains high productivity while reducing access time through load distribution.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces dynamic load balancing and node selection mechanisms that adapt to changing traffic conditions. The system dynamically routes access requests to optimal nodes based on current load, distance, and availability, maintaining efficient data access even under high traffic conditions.

Inventive Principle:
Principle #15Dynamics

4Quantity of substance

If minimal data redundancy is maintained in a centralized database, then storage efficiency is improved, but lost data is difficult to retrieve

Engineering Contradiction:
Improvestorage efficiencyVSAvoiddata retrieval capability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent implements multiple copies of the database across distributed nodes, creating redundancy without wasting storage space. Each node stores a complete database copy, and the network collectively maintains many replicas. This copying approach ensures that lost data can be retrieved from any remaining node while maintaining storage efficiency through selective replication.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent applies local quality by allowing different nodes to store different portions or versions of the database based on local requirements and data access patterns. This enables optimized storage distribution where each node maintains data most relevant to its function, improving both storage efficiency and retrieval capability.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11526487B2Database world state integrity validation
Publication Date: 2022.12.13 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11526487B2 patent drawing
  • US11526487B2 patent drawing
  • US11526487B2 patent drawing

AI summary

An example operation may include one or more of creating, by a blockchain user of a blockchain network, a world state checkpoint transaction requesting world state validation, endorsing, by one or more endorser nodes or peers, the world state checkpoint transaction, transferring endorsements to the blockchain user, recording, by an orderer node or peer, the endorsed world state checkpoint transaction into a block, validating and committing all transactions in the block, calculating and signing a hash of a current world state, by all blockchain nodes or peers of the blockchain network, and verifying, by the blockchain user, world state integrity from the calculated and signed hashes of the current world state.