Distributed Ledger Node Block Segmentation and Hash Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing blockchain systems face challenges in efficiently managing and storing large amounts of data for extended periods, requiring continuous resource maintenance and tamper resistance.

Innovation Solution

A distributed ledger management method that divides a blockchain into groups held by organizations, with each node storing signatures, hash values, and verification frequencies, allowing for efficient data storage and tamper verification, and deleting unnecessary blocks while maintaining data integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Duration of action of stationary object

If the blockchain is stored for a specified number of years to meet legal requirements, then data retention compliance is improved, but resource requirements (computers, networks, management personnel) increase significantly

Engineering Contradiction:
Improvedata retention periodVSAvoidresource requirements
Core Design Contradiction:
Duration of action of stationary objectVSQuantity of substance

Solution Approach 1:

The patent segments the blockchain data into two distinct parts: active blockchain data stored in the distributed ledger network and archived blockchain data stored in an external storage system. This segmentation allows the system to meet long-term retention requirements while reducing the resource burden on the distributed ledger network by moving historical data to external storage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts archived blockchain data from the main distributed ledger network and stores it in an external storage system. This extraction separates the long-term archival function from the active ledger operations, allowing the ledger to maintain only the data necessary for ongoing operations while external storage handles long-term compliance requirements.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If all blocks are retained in the distributed ledger network to ensure tamper resistance, then data integrity is improved, but storage efficiency deteriorates

Engineering Contradiction:
Improvetamper resistanceVSAvoidstorage efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements preliminary action by storing hash values of archived blockchain data in the distributed ledger network before actually archiving the data. This preliminary storage of cryptographic references ensures that even though the actual data is moved to external storage, the ledger maintains the ability to verify integrity through pre-stored hash values, enabling efficient storage without sacrificing tamper resistance.

Inventive Principle:
Principle #10Preliminary action

3Duration of action of stationary object

If the blockchain administrator continuously maintains resources for long-term storage, then data availability is improved, but operational complexity increases

Engineering Contradiction:
Improvestorage durationVSAvoidmanagement complexity
Core Design Contradiction:
Duration of action of stationary objectVSDevice complexity

Solution Approach 1:

The patent implements self-service by enabling nodes in the distributed ledger network to automatically perform verification operations on archived data using stored hash values. Instead of requiring continuous administrator intervention to verify data integrity, the system automatically compares hash values of archived data against stored references, reducing operational complexity while maintaining verification capabilities over long periods.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11621850B2Distributed ledger management method, distributed ledger system, and node
Publication Date: 2023.04.04 HITACHI LTD
  • US11621850B2 patent drawing
  • US11621850B2 patent drawing
  • US11621850B2 patent drawing

AI summary

A distributed ledger management method performed by each of nodes 211 configuring a distributed ledger system, includes: holding, in an end block 102, signatures of respective organizations operating the respective nodes, hash values of respective groups of blocks into which a blockchain 215 is divided by a number of the operating organizations, information on organizations by which the group of blocks is to be held, and a verification frequency for the hash value between the organizations; specifying a group of blocks to be held by the organization; deleting a block other than the group of blocks in the blockchain 215; and performing a tamper verification of requesting a node 211 of another organization to transmit the hash value of the group of blocks to be held by the other organization at a verification frequency, and collating the hash value with the hash value included in the end block 102.