Blockchain Data Management for Distributed Binary Objects

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current blockchain systems face limitations in handling large binary objects and complex data structures, leading to network congestion, increased transaction fees, and scalability issues, which hinder their application in enterprise-level data management and storage.

Innovation Solution

The implementation of blockchain-based data management for distributed binary objects, which allows for the secure and scalable storage of any size or format of data by using a blockchain engine to manage consensus, encryption keys, and hash comparisons, enabling the creation of an abstraction layer for data management and linking parent to child blocks with the same encryption keys, while maintaining immutability and integrity through periodic monitoring and logging.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If large binary objects are stored directly in blockchain blocks, then data integrity and immutability are maintained, but network congestion increases and scalability deteriorates

Engineering Contradiction:
Improvedata integrityVSAvoidscalability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments binary objects into fixed-size chunks (e.g., 5MB each) and stores them across multiple contiguous blocks in the blockchain. This segmentation allows large files to be stored without overwhelming network capacity in a single transaction, while maintaining data integrity through distributed storage across multiple blocks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transitions from storing complete binary objects within single blockchain blocks to storing segmented chunks across multiple blocks and utilizing distributed file system layers. This dimensional shift from block-internal storage to block-distributed storage resolves the contradiction between maintaining integrity and achieving scalability.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Quantity of substance

If blockchain block size is increased to accommodate larger data, then more data can be stored per block, but network congestion worsens and transaction processing time increases

Engineering Contradiction:
Improvedata storage capacityVSAvoidtransaction processing time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

Instead of increasing individual block sizes, the patent segments large binary objects into smaller chunks that fit within standard block size limits. Multiple chunks are distributed across multiple blocks, maintaining efficient transaction processing times while achieving large-scale data storage capacity through aggregation across the blockchain.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If binary objects are distributed across multiple data stores, then storage flexibility and scalability improve, but data integrity and immutability become harder to maintain

Engineering Contradiction:
Improvestorage flexibilityVSAvoiddata integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces cryptographic hashes and merkle tree structures as intermediaries between distributed binary object chunks and the blockchain. These intermediaries verify data integrity across distributed storage locations, ensuring that even though objects are split and stored flexibly across multiple data stores, their immutability and integrity are maintained through cryptographic verification.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12261934B2Blockchain-based data management of distributed binary objects
Publication Date: 2025.03.25 EMTRUTH INC
  • US12261934B2 patent drawing
  • US12261934B2 patent drawing
  • US12261934B2 patent drawing

AI summary

A method of blockchain-based data management of distributed binary objects. The method includes identifying a binary object associated with a blockchain. The method includes storing the binary object in a first data store responsive to identifying the binary object. The method includes storing a reference to the binary object on the blockchain. The method includes generating, responsive to an interaction with the reference to the binary object and based on the binary object and a different binary object from a different data store, an additional binary object having a data size that exceeds a maximum data size associated with each block of the blockchain.