Immutable Ledger Data Destruction via Segmented Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current blockchain systems face challenges in efficiently deleting data while maintaining the integrity and availability of immutable distributed ledgers, particularly in compliance with data retention policies and regulations like GDPR, which require the deletion of personally identifiable information.

Innovation Solution

The system introduces a method to render data inaccessible on a distributed ledger by using transient data fields and side databases, allowing smart contracts to process and delete data without storing it on the blockchain, while maintaining the ledger's integrity and allowing for data restoration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is stored on an immutable distributed ledger, then the integrity and availability of the ledger is maintained, but the ability to delete data according to data retention policies is compromised

Engineering Contradiction:
Improveledger integrityVSAvoiddata deletion capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system segments data storage into two distinct locations: the immutable distributed ledger stores only cryptographic hashes and metadata, while the actual data is stored in a separate mutable database. This segmentation allows the ledger to maintain integrity while enabling data deletion through manipulation of the separate database and hash references.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system extracts the actual data from the immutable ledger by storing only cryptographic hashes on the ledger and keeping the full data in a separate mutable database. This extraction enables data deletion capability while preserving ledger immutability, as deleting data in the mutable database does not affect the hash references on the immutable ledger.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If data is deleted from a distributed ledger, then compliance with data retention policies is achieved, but the integrity and availability of the ledger is compromised

Engineering Contradiction:
Improvedata deletion capabilityVSAvoidledger integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments data storage into two distinct locations: the immutable distributed ledger stores only cryptographic hashes and metadata, while the actual data is stored in a separate mutable database. This segmentation allows the ledger to maintain integrity while enabling data deletion through manipulation of the separate database and hash references.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces cryptographic hashes as intermediaries between the immutable ledger and the mutable database. The hashes serve as references that link data in the mutable database to records on the immutable ledger, enabling deletion of data in the mutable database without affecting the immutable ledger's integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If data is stored on the blockchain, then the system provides tamper-proof storage, but the system cannot efficiently respond to data destruction requests

Engineering Contradiction:
Improvetamper-proof storageVSAvoiddata destruction efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system segments data storage into two distinct locations: the immutable distributed ledger stores only cryptographic hashes and metadata, while the actual data is stored in a separate mutable database. This segmentation allows efficient data deletion by operating on the mutable database without requiring system-wide operations or disrupting the tamper-proof storage mechanism.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system extracts the actual data from the immutable ledger by storing only cryptographic hashes on the ledger and keeping the full data in a separate mutable database. This extraction enables efficient data deletion through direct manipulation of the mutable database, while the immutable ledger maintains its tamper-proof characteristics through hash verification.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11860822B2Immutable ledger with efficient and secure data destruction, system and method
Publication Date: 2024.01.02 KESS PAUL L INC
  • US11860822B2 patent drawing
  • US11860822B2 patent drawing
  • US11860822B2 patent drawing

AI summary

A system and method for destroying data stored on an immutable distributed ledger utilizes technology from the following fields: encryption, digital signatures, data structures, distributed storage, distributed ledger technology, and smart contracts. Immutable distributed ledgers provide benefits for sensitive data, including availability, integrity, and data processing visibility. The system and method places sensitive data on an immutable distributed ledger and maintains these advantages of immutable distributed ledgers. The system and method also supports the efficient deletion of this sensitive data without compromising the integrity of the ledger.