Relational Blockchain Database Cross-Chain Referential Integrity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional blockchain systems are stand-alone and independent, lacking the ability to reference foreign blockchains or provide consensus for other networks, resulting in isolated data storage solutions with no referential integrity or ability to join data across different blockchain databases.
Innovation Solution
A relational blockchain database system that allows user-defined blockchains with metadata management, enabling relationships between blockchains through inner, outer, and cartesian joins, and utilizing a distributed network for consensus and data synchronization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional blockchain systems are used as stand-alone independent solutions, then data immutability is maintained, but the ability to reference foreign blockchains and provide cross-chain consensus is lost
Solution Approach 1:
The blockchain database is enhanced with universal capabilities to reference multiple foreign blockchains and participate in cross-chain consensus mechanisms. The system can simultaneously maintain its own blockchain while validating and referencing transactions from other blockchains, making it multi-functional rather than single-purpose.
Solution Approach 2:
A relational layer is introduced as an intermediary between the local blockchain and foreign blockchains. This relational layer manages cross-chain references, validates foreign transactions, and coordinates consensus without requiring direct integration with each foreign blockchain, simplifying the architectural complexity.
2Reliability
If multiple independent blockchains are used for data storage, then data security and immutability are maintained, but referential integrity and ability to join data across databases are lost
Solution Approach 1:
Multiple independent blockchains are merged into a unified relational blockchain database that maintains the security properties of individual blockchains while adding referential integrity. The system combines data from multiple blockchains into a coherent relational structure where foreign key constraints and joins can be enforced across chain boundaries.
Solution Approach 2:
The system skips the traditional approach of requiring centralized databases for referential integrity by directly implementing cross-chain foreign key constraints through cryptographic validation. Transactions can reference data across chains without passing through a centralized authority, maintaining decentralization while ensuring integrity.
3Productivity
If stand-alone blockchain systems are used, then system simplicity is maintained, but scalability and ability to manage data across multiple databases are limited
Solution Approach 1:
The relational blockchain database is segmented into multiple independent blockchain components that can be managed separately. Each blockchain can be optimized for specific data types or purposes while the relational layer provides unified access and management, enabling scalable data growth without monolithic complexity.
Solution Approach 2:
The system adds a relational dimension to the traditional single-dimensional blockchain structure. By introducing foreign key relationships and join capabilities across multiple blockchains, data can be accessed and managed in multiple dimensions simultaneously, greatly enhancing scalability and flexibility.
Data Source
AI summary
A user relational blockchain database includes a set of system-defined user blockchains and user-defined blockchains. The set of system-defined user blockchains includes metadata for managing the user-defined blockchains. Each user-defined blockchain includes a set of fields defined by a user and at least some of the fields are relatable. A command is received to write data that includes an identification of a first user-defined blockchain, a field, and a value. A new block is generated that includes the value set for the field. The new block is transmitted to a network of servers for consensus to add to the first user-defined blockchain. The new block is persisted to the first user-defined blockchain. A command is received to read data from the user relational blockchain database that includes an identification of the first user-defined blockchain and an identification of a field. The value corresponding to the field is accessed and returned.