Blockchain Data Disposal via Consensus and Hashing

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 lack of data redundancy, which can lead to data loss and management challenges, particularly in ensuring secure and defensible data disposal.

Innovation Solution

A blockchain-based system is implemented, where a processor connects to a network of user and device nodes to manage data disposal through consensus algorithms, smart contracts, and hashing functions, ensuring secure, decentralized, and auditable data disposal processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized database is used to store and manage data, then data management and control are simplified, but the system has a single point of failure and limited access capability

Engineering Contradiction:
Improvedata management and controlVSAvoidsingle point of failure
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the centralized database into multiple distributed nodes across a network. Each node maintains a copy of the data, eliminating the single point of failure. The system divides the database functionality across multiple independent entities that can operate autonomously while maintaining consistency through consensus mechanisms.

Inventive Principle:
Principle #1Segmentation

2Quantity of substance

If data is stored in a centralized location, then data redundancy is minimized, but data loss is difficult to retrieve

Engineering Contradiction:
Improvedata redundancyVSAvoiddata loss retrieval
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The patent implements multiple copies of the data distributed across different nodes in the network. Each node maintains an identical or equivalent copy of the data, ensuring that if one node fails, the data can be retrieved from any other node. This copying mechanism provides both redundancy and fault tolerance.

Inventive Principle:
Principle #26Copying

3Speed

If a centralized database experiences high traffic, then network connectivity dependency increases, but bottlenecks occur at the single location

Engineering Contradiction:
Improvenetwork connectivityVSAvoidtransaction speed
Core Design Contradiction:
SpeedVSProductivity

Solution Approach 1:

The patent segments the database traffic handling across multiple distributed nodes rather than concentrating all traffic at a single location. Each node can independently handle transactions and queries, distributing the load and eliminating bottlenecks. This segmentation allows the system to scale horizontally by adding more nodes to handle increased traffic.

Inventive Principle:
Principle #1Segmentation

4Quantity of substance

If only one copy of data is maintained, then storage efficiency is improved, but multiple devices cannot access the same data simultaneously

Engineering Contradiction:
Improvedata copy quantityVSAvoidsimultaneous access capability
Core Design Contradiction:
Quantity of substanceVSEase of operation

Solution Approach 1:

The patent segments the data access functionality across multiple nodes, allowing simultaneous access from multiple devices. Each node can serve access requests independently, enabling parallel operations without contention. The segmentation of access paths through different nodes eliminates the limitation of single-copy databases while maintaining data consistency through consensus protocols.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11176093B2Defensible disposition of data
Publication Date: 2021.11.16 KYNDRYL INC
  • US11176093B2 patent drawing
  • US11176093B2 patent drawing
  • US11176093B2 patent drawing

AI summary

An example operation may include one or more of connecting, by a disposition node, to a blockchain comprised of a plurality of user nodes connected to a plurality of device nodes that store user data of the plurality of the user nodes, receiving, by the disposition node, a request from a user node of the plurality of the user nodes to dispose of user data (D) on at least one of the device nodes of the plurality of the device nodes, the request contains a disposal policy (P) and a disposal method (M) of the D, executing, by the disposition node, a consensus algorithm to validate the request based on the D, P and M, in response to a validation of the request, accessing, by the disposition node, the D on the at least one of the device nodes of the plurality of the device nodes, generating, by the disposition node, a location sensitive hash of the D (LSH(D)) and a crypto hash of the D (SHA256(D)), storing, by the disposition node, the LSH(D), the SHA256(D), the P and the M on the blockchain, executing, by the disposition node, a smart contract to dispose of the D on the at least one of the device nodes of the plurality of the device nodes by the M based on the P, and recording an execution of the smart contract on the blockchain.