Autonomous Blockchain Sets for Immutable, Cancellable Data Archiving
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain technologies lack data cancellation capabilities, are vulnerable to single points of failure, have scalability issues, and do not comply with regulations like GDPR and HIPAA, limiting their adoption in non-financial applications.
Innovation Solution
A distributed cryptographic system comprising autonomous data and control blockchains, where each participant manages their own blockchains independently, with inter-blockchain cryptographic links ensuring immutability and verifiability, and a control blockchain for secure data management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is recorded in a blockchain block, then data immutability is achieved, but data cancellation becomes impossible
Solution Approach 1:
The patent segments the blockchain system into multiple independent chains (first blockchain, second blockchain, third blockchain) where each chain can independently manage different aspects of data. This allows the first blockchain to maintain immutability while the second blockchain enables controlled cancellation through its own consensus mechanism, resolving the contradiction between immutability and cancellability.
Solution Approach 2:
The patent introduces a third blockchain as an intermediary that stores cryptographic links (hashes) of data from the first blockchain. This intermediary structure allows verification of original data immutability while enabling the second blockchain to independently manage data cancellation through its own consensus process, without directly altering the immutable first blockchain.
2Measurement precision
If all participants validate each block in a distributed blockchain, then data verifiability is improved, but processing speed and scalability deteriorate
Solution Approach 1:
The patent divides the validation process across multiple specialized blockchains. The first blockchain handles data recording with its own validation, the second blockchain handles cancellation validation separately, and the third blockchain validates cryptographic links independently. This segmentation allows parallel processing and improves overall throughput while maintaining verifiability through cryptographic proofs.
Solution Approach 2:
Instead of requiring all participants to validate all blocks across all blockchains, the patent implements partial validation where each blockchain validates only its specific data type and purpose. Participants can choose which blockchain to join and validate based on their needs, reducing the excessive validation burden while maintaining security through cryptographic links between chains.
3Device complexity
If a single entity controls the entire blockchain database, then system simplicity is maintained, but single point of failure and security vulnerabilities increase
Solution Approach 1:
The patent segments the centralized database into multiple distributed blockchains, each controlled by different participants or consortium members. This segmentation eliminates the single point of failure by distributing control across independent chains while maintaining relative simplicity through standardized cryptographic interfaces and protocols for inter-chain communication.
Solution Approach 2:
The patent creates a composite blockchain system where multiple different blockchain types (public, private, consortium) are combined into a unified architecture. Each blockchain type contributes its strengths (immutability, privacy, consensus efficiency) while the composite structure provides overall system reliability through cryptographic links and redundant validation across chains.
4Stability of the object's composition
If each node maintains a complete copy of all blockchain data, then data consistency is ensured, but storage requirements and network bandwidth increase
Solution Approach 1:
The patent extracts only the essential cryptographic elements (hashes, cryptographic links, consensus proofs) from the full blockchain data and stores these extracted elements in specialized blockchains. Nodes only need to store and validate these compact cryptographic representations rather than complete transaction histories, significantly reducing storage requirements while maintaining data consistency through cryptographic verification.
Solution Approach 2:
Instead of requiring nodes to store complete copies of all blockchain data, the patent uses cryptographic copying where nodes store hash copies and cryptographic proofs that verify data integrity without duplicating the actual data. This allows lightweight nodes to verify consistency across chains without maintaining large local copies of all transaction data.
Data Source
AI summary
A method for archiving data in a distributed cryptographic database includes writing data to a data archive of a data block of an autonomous data blockchain, linking the data block with a control block of an autonomous control blockchain, the control block including a time stamp more recent than a time stamp of the data block with which it is linked, and, when the written data is to be cancelled, inserting a first status value and a second status value inside a following data block linked to the data block including data by a pair of cryptographic links, thus defining that, from a certain block of the autonomous data blockchain onwards, a valid second status value indicates that the data archive is empty, and validating the second status value in a following control block of the autonomous control blockchain with a time stamp.