Blockchain Ledger Size Management via Encrypted Digest Storage

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 access, and inefficient management of large ledger sizes in blockchain systems, particularly with private data distribution concerns.

Innovation Solution

A system that connects nodes via a blockchain network to manage ledger size by storing encrypted digests instead of actual data blocks, allowing for secure reduction and compression of ledger data, and masking private data during transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all data blocks are stored on every blockchain node to ensure data integrity and immutability, then security and reliability are improved, but the volume of data stored and network bandwidth consumption increase significantly

Engineering Contradiction:
Improvedata integrityVSAvoiddata volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential verification element (hash value) from the complete data block and stores/transmits this condensed representation across the network. Each node stores the hash of the entire ledger rather than all raw transaction data, enabling verification of data integrity while minimizing data volume. This extraction principle directly resolves the contradiction by keeping only the critical security component distributed while centralizing the full data storage.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent transforms the data representation from storing complete transaction records to storing cryptographic hash values. This parameter change in data format (from raw data to hashed data) maintains the ability to verify integrity through hash comparison while dramatically reducing the quantity of data that must be stored and transmitted across the network.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If complete data blocks are transmitted to all nodes for validation, then data security is improved, but network bandwidth consumption and transaction speed deteriorate

Engineering Contradiction:
Improvedata securityVSAvoidtransaction speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent extracts only the hash value from complete data blocks for network transmission and validation. Nodes receive and validate these compact hash representations rather than full transaction records, enabling rapid verification of data integrity without the network overhead of transmitting and processing large volumes of raw transaction data, thus improving transaction speed while maintaining security.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If private data is distributed to all blockchain nodes for transaction validation, then transaction verification is improved, but data privacy and security compliance worsen

Engineering Contradiction:
Improvetransaction verificationVSAvoiddata privacy risk
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts only non-sensitive hash representations from transactions containing private data and distributes these to all nodes for validation. The actual private transaction data remains stored only on the submitting node or in private storage, while nodes validate transactions by comparing hash values. This extraction approach enables transaction verification productivity while eliminating the privacy harm of distributing sensitive data to all participants.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11637691B2Management of a size of a ledger
Publication Date: 2023.04.25 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11637691B2 patent drawing
  • US11637691B2 patent drawing
  • US11637691B2 patent drawing

AI summary

An example operation may include one or more of connecting, by a recipient node, to a source node via a blockchain network, receiving, by the recipient node, a data block, a digest of the data block encrypted by a private key of the source node, a public key paired to the private key and an IP address of the source node, calculating, by the recipient node, a digest of the data block, decrypting, by the recipient node, the digest of the data block by the public key, comparing, by the recipient node, the decrypted digest against the digest, and in response to a match, storing the encrypted digest, the public key and the IP address of the source node onto a ledger of the recipient node.