Blockchain State Database Checkpointing for Node Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Blockchain networks face inefficiencies in node bootstrapping, disk corruption recovery, and storage management due to lack of data redundancy and verification mechanisms, leading to prolonged synchronization times and storage capacity issues.

Innovation Solution

Implementing a system where peer nodes in a blockchain network periodically generate and consensus-validate state database checkpoints, allowing for efficient retrieval and reconstruction of the state database in case of corruption or fork, and enabling new nodes to quickly sync by using these checkpoints.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a new node validates and commits each transaction from block 1 to the current block, then the node achieves full synchronization with the blockchain, but the bootstrapping duration becomes extremely long (hours/days)

Engineering Contradiction:
Improvefull synchronizationVSAvoidbootstrapping duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-computing and storing state database checkpoints at predetermined block intervals before they are needed. These checkpoints contain pre-calculated state information that new nodes can use to jump-start their synchronization process, eliminating the need to process every single transaction from block 1. The checkpoints are prepared in advance and made available to nodes joining the network.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating replicated state database snapshots at checkpoint blocks and distributing these copies to peer nodes. Instead of requiring each node to independently reconstruct the entire state from raw transactions, nodes can obtain pre-computed state copies from other peers, dramatically reducing bootstrapping time while maintaining synchronization reliability.

Inventive Principle:
Principle #26Copying

2Reliability

If peer nodes store all committed transactions and state database information, then the blockchain maintains full history and state, but storage capacity consumption increases significantly

Engineering Contradiction:
Improvefull history retentionVSAvoidstorage capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts and separates checkpoint data from the main transaction ledger. By isolating state database snapshots at checkpoint blocks into distinct stored structures, the system allows peers to retain essential historical state information without storing complete transaction details for every block. This extraction enables selective retention of critical state data while reducing overall storage requirements.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements discarding and recovering by allowing nodes to discard detailed transaction data after state information has been extracted and stored in checkpoint structures. The essential state can be recovered from these compact checkpoints when needed, eliminating the need to permanently retain all raw transaction data while maintaining the ability to reconstruct state information.

Inventive Principle:
Principle #34Discarding and recovering

3Reliability

If the state database is updated continuously without checkpoints, then the blockchain maintains current state accuracy, but recovery from disk corruption requires reconstructing state from all previous transactions

Engineering Contradiction:
Improvestate accuracyVSAvoidrecovery speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by pre-establishing checkpoint markers at predetermined block intervals that capture validated state information. These checkpoints serve as pre-prepared recovery points that allow the system to quickly restore state accuracy without reprocessing all transactions. The checkpoints are created in advance and stored in a manner that enables rapid retrieval during recovery operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses checkpoints as intermediary structures between the transaction ledger and the state database. These checkpoint markers serve as mediators that bridge transaction data and state information, allowing the system to verify state convergence and perform recovery operations by referencing intermediate checkpoint states rather than reconstructing everything from raw transactions.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If peer nodes verify state convergence after each block commit, then the blockchain ensures consistency, but the verification process increases computational overhead and time

Engineering Contradiction:
Improvestate consistencyVSAvoidverification speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies partial action by implementing verification at selective checkpoint intervals rather than after every single block commit. Instead of verifying state convergence continuously, the system performs comprehensive verification at predetermined checkpoint blocks while using lighter-weight mechanisms between checkpoints. This partial verification approach maintains reliability at critical points while reducing overall computational overhead.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11334439B2Checkpointing for increasing efficiency of a blockchain
Publication Date: 2022.05.17 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11334439B2 patent drawing
  • US11334439B2 patent drawing
  • US11334439B2 patent drawing

AI summary

An example operation may include one or more of retrieving, into a new node to be instantiated in a blockchain network, a state database checkpoint of a state database created at a block number of a blockchain of the blockchain network, retrieving, into the new node, blocks of the blockchain from the checkpoint block number to a current block number, constructing an initial state database from the received state database checkpoint, and executing, at the new node, the transactions of the retrieved blocks on the initial state database to generate a current state database.