Consortium Blockchain Validation via Cloud Storage Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional blockchain systems face limitations in transaction throughput, particularly in consortium blockchains spanning multiple organizations, due to varying computational processing abilities of nodes, leading to security and performance issues, with existing solutions like Hyperledger Fabric struggling to meet high transaction per second requirements in e-commerce and banking environments.

Innovation Solution

The proposed solution involves utilizing high-performance cloud storage arrays to augment transaction throughput in consortium blockchains by performing data block validation, with on-site storage arrays handling preliminary checks and cloud storage arrays handling more intensive validation operations, leveraging smart contracts and cryptographic hash functions to ensure data integrity and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional blockchain nodes perform full validation operations, then security is maintained, but transaction throughput is limited due to varying computational processing abilities

Engineering Contradiction:
Improvetransaction throughputVSAvoidvalidation security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The validation operation is divided into two distinct portions: a first portion executed by party storage nodes and a second portion executed by cloud storage nodes. This segmentation allows each node type to perform specialized validation tasks, improving overall throughput while maintaining security through distributed validation across multiple nodes with different computational capabilities.

Inventive Principle:
Principle #1Segmentation

2Reliability

If more nodes participate in validation, then security and decentralization improve, but latency increases due to coordination overhead

Engineering Contradiction:
Improvevalidation securityVSAvoidvalidation latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Party storage nodes execute the first portion of the validation operation preliminarily before submitting data blocks to the cloud storage nodes. This preliminary validation filters out obviously invalid blocks early in the process, reducing the coordination overhead and latency for full validation while maintaining security through the two-stage approach.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If high-performance computing resources are concentrated in few nodes, then transaction processing capacity increases, but system vulnerability to failures increases

Engineering Contradiction:
Improvetransaction processing capacityVSAvoidsystem fault tolerance
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system merges the computational resources of party storage nodes and cloud storage nodes into a unified validation architecture. Both node types contribute to validation, distributing the processing capacity across multiple entities while maintaining fault tolerance through the decentralized nature of the consortium blockchain and the requirement for successful completion of both validation portions.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12131324B2Storage systems to perform data validation in blockchains
Publication Date: 2024.10.29 DELL PROD LP
  • US12131324B2 patent drawing
  • US12131324B2 patent drawing
  • US12131324B2 patent drawing

AI summary

A method comprises receiving at one or more cloud storage nodes a data block to be validated in connection with adding the data block to a digital ledger. The data block is received from a party storage node corresponding to a party of a plurality of parties that are members of a blockchain computing environment. The party storage node executes a first portion of a validation operation for the data block. The one or more cloud storage nodes execute a second portion of the validation operation for the data block. In the method, the data block is added to the digital ledger responsive to validating the data block, and at least a portion of the digital ledger is stored in the one or more cloud storage nodes.