Relational DLT Data Layer for SQL Access Without Lock-In
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing relational database management systems (RDBMS) are not compatible with distributed ledger technology (DLT), leading to program/data lock-in and inefficiencies in managing and accessing data on distributed ledgers, particularly for smart contracts.
Innovation Solution
A relational data management and organization system that enables data to be managed and organized according to relational principles, allowing storage on a distributed ledger platform and accessed using SQL, with support for Hyperledger Fabric and Node.js, and includes features like OPSTAT, QUERYLEVEL, and BOOKMARK to facilitate secure and auditable data storage and retrieval.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is stored using program-specific storage approaches in distributed ledgers, then data can be stored on the ledger, but program/data lock-in increases and data becomes inextricably linked to the smart contract
Solution Approach 1:
The patent segments the data storage system into two independent components: a relational database management layer that handles data organization and access using SQL, and a distributed ledger layer that provides immutable storage. This segmentation allows data to be stored on the distributed ledger while maintaining adaptability through the relational abstraction layer, preventing program/data lock-in.
Solution Approach 2:
The patent introduces an intermediary relational database management system that sits between the user applications and the distributed ledger. This intermediary translates SQL queries into distributed ledger operations, allowing data to be stored on the ledger while maintaining flexibility and independence from specific smart contract implementations.
2Ease of operation
If existing RDBMS platforms are used with distributed ledger technology, then relational data management capabilities are available, but compatibility issues arise between RDBMS tools and DLT constraints
Solution Approach 1:
The patent modifies the operational parameters of the relational database management system to be compatible with distributed ledger constraints. Specifically, it adapts the SQL interface and data persistence mechanisms to work within the immutable and distributed nature of ledger technology, enabling seamless integration without sacrificing relational data management capabilities.
3Ease of operation
If data is managed according to relational principles before storage on distributed ledger, then developer knowledge can be leveraged and data access is simplified, but system complexity increases
Solution Approach 1:
The patent implements a self-service architecture where the relational database management layer automatically handles data organization, querying, and access patterns. The system autonomously manages the translation between SQL operations and distributed ledger operations, eliminating the need for developers to manually implement complex data management logic and reducing the perceived system complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A set of both smart contract and off-chain tools is described that enable the management and organization of data so as to enable storage of that data in a distributed ledger according to relational database principles. A cross-distributed-ledger-platform specification plus reusable core components together create a system that may be implemented on distributed ledger platforms to enable storage and retrieval of data to/from the distributed ledger governed by relational principles. A realization of this system enables addition of system chaincode to Hyperledger® Fabric and uses schemas and data represented as JSON. In use, the user may create, update, and query data from code, a console, or a smart contract where every update is a distributed ledger transaction.