Blockchain Lifecycle Management via Segmented Closure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Blockchain scalability is constrained by CPU, network, and storage limitations, with existing solutions like pruning and side chains providing limited storage optimization and being complex to implement.

Innovation Solution

A method for identifying attributes of a blockchain to determine when to close it and create a new one, involving self-analysis, archiving transactions, and creating carry-over transactions to preserve continuity, using hash-based processing and social network modeling to manage the lifecycle.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the blockchain continuously stores all transactions, then transaction history and continuity are maintained, but storage requirements increase indefinitely

Engineering Contradiction:
Improvetransaction history continuityVSAvoidstorage requirements
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent divides the blockchain into multiple segments (blocks) that can be independently managed. Older blocks are identified as candidates for closure when they meet certain criteria (e.g., no unspent transactions), allowing the system to segment and manage storage more effectively while preserving the integrity of active transaction chains.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a mechanism to identify and close older blocks that no longer contain unspent transactions, effectively discarding unnecessary historical data from active storage while recovering and preserving only the essential transaction history needed for continuity. This allows the system to reduce storage requirements while maintaining reliability through selective data retention.

Inventive Principle:
Principle #34Discarding and recovering

2Loss of information

If all transactions are stored indefinitely, then complete transaction history is preserved, but bandwidth consumption increases

Engineering Contradiction:
Improvetransaction history preservationVSAvoidbandwidth consumption
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The system identifies transactions and blocks that can be safely discarded (closed) based on whether they contain unspent transactions. By recovering and retaining only the essential transaction information needed for continuity rather than all historical data, the system reduces bandwidth consumption for data transmission and storage while preserving critical transaction history.

Inventive Principle:
Principle #34Discarding and recovering

3Quantity of substance

If blockchain data is pruned to reduce storage, then storage optimization is achieved, but transaction data loss occurs

Engineering Contradiction:
Improvestorage optimizationVSAvoidtransaction data
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The patent implements a feedback mechanism that continuously monitors transaction states to determine whether blocks should be closed. By analyzing whether transactions are spent or unspent, the system provides feedback on which data can be safely pruned and which must be retained, enabling storage optimization without loss of critical transaction information.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system selectively discards only those transaction data elements that are confirmed to be fully spent and no longer needed, while recovering and preserving transactions that remain unspent or are essential for maintaining the blockchain's continuity and integrity, thus avoiding data loss while optimizing storage.

Inventive Principle:
Principle #34Discarding and recovering

4Quantity of substance

If side chains or alternative chains are used to reduce storage, then storage constraints are addressed, but implementation complexity increases

Engineering Contradiction:
Improvestorage constraint optimizationVSAvoidimplementation complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent implements a self-service mechanism where the blockchain automatically identifies and closes older blocks based on predefined criteria (such as all transactions being spent), eliminating the need for complex external systems like side chains. The system manages its own data retention policies through built-in monitoring and decision-making algorithms, reducing implementation complexity while achieving storage optimization.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10833844B2Blockchain lifecycle management
Publication Date: 2020.11.10 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10833844B2 patent drawing
  • US10833844B2 patent drawing
  • US10833844B2 patent drawing

AI summary

An example operation may include one or more of identifying one or more attributes of a blockchain, determining the blockchain should be closed based on the one or more attributes, closing the blockchain, creating a new blockchain, identifying one or more assets from the blockchain, and creating a carry-over transaction based on the one or more assets of the blockchain.