Metadata-Driven DLT Application with Hybrid Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain and distributed ledger technologies face challenges such as fixed, immutable, and static data storage, inefficient data retrieval due to lack of metadata, and poor access control, making them unsuitable for applications requiring data deletion or restricted access.
Innovation Solution
Implementing a metadata-driven application using Distributed Ledger Technology (DLT) in conjunction with a cloud-based computing environment, allowing for dynamic metadata management, efficient data storage, and controlled access through a blockchain interface that supports multiple tenants and non-customers, enabling flexible data retrieval and access permissions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is stored in a fixed, immutable manner in blockchain, then security and immutability are improved, but adaptability and ability to delete or modify data deteriorate
Solution Approach 1:
The patent segments data storage into two distinct layers: immutable blockchain storage for critical verification data and hashes, and mutable off-chain storage (IPFS, cloud databases) for the actual data content. This segmentation allows the blockchain to maintain its immutability guarantee while the overall system gains flexibility through separate mutable storage locations.
Solution Approach 2:
The patent introduces metadata as an intermediary layer between the immutable blockchain and the mutable data storage. This metadata contains pointers, access control information, and contextual data that enables flexible data management while the blockchain maintains its immutable ledger of references and verification data.
2Reliability
If all data is stored on the blockchain, then data security and trust are improved, but data retrieval efficiency and storage costs deteriorate
Solution Approach 1:
The patent extracts large volumes of data from the blockchain storage and places them in off-chain storage systems like IPFS and cloud databases. Only essential verification data, hashes, and metadata remain on the blockchain, dramatically improving retrieval efficiency while maintaining security through cryptographic verification.
Solution Approach 2:
The patent moves data storage from a single dimension (blockchain only) to multiple dimensions by introducing hybrid storage architecture. Data can be stored across blockchain, IPFS, and cloud databases simultaneously, with the blockchain providing verification and the other systems providing efficient retrieval, thus optimizing both security and efficiency.
3Loss of information
If blockchain stores complete data records, then data completeness is improved, but storage efficiency and scalability deteriorate
Solution Approach 1:
The patent creates cryptographic copies (hashes) of data on the blockchain rather than storing complete data records. These cryptographic copies serve as verification tokens that prove data integrity and completeness without requiring the actual data to reside on-chain, thus maintaining data completeness verification while minimizing storage volume.
Solution Approach 2:
The patent segments data into critical verification components stored on-chain and non-critical content stored off-chain. This segmentation allows the blockchain to maintain a complete and verifiable record of data existence and integrity while the bulk data resides in more efficient storage systems.
Data Source
AI summary
Exemplary systems, implement Distributed Ledger Technology (DLT) in conjunction with a cloud based computing environment. The system operates receives input for adding a plurality of authorized network participants to a declared application, in which the network participants are granted access rights to the declared application. The system further deploys an executable install package to each of the plurality of authorized network participants for the declared application; in which the executable install package retrieves the metadata for the declared application from the blockchain and displays GUIs specific to the declared application which are auto generated by the executable install package based on the retrieved metadata.