Hybrid Database and Blockchain Metadata Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional database systems lack secure and scalable solutions for managing digital assets and transactions, particularly in cloud computing environments, where trust in a service provider is required, and public trust ledgers do not provide platforms for enterprise-level digital asset exchange.
Innovation Solution
Integration of an on-demand database system with a public trust ledger, enabling the creation and transfer of non-fungible tokens with dynamic attribute revelation, secure transaction management, and scalable digital asset exchange through smart contracts and metadata storage, using technologies like Layer 2 protocols and DAML for Byzantine fault tolerance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If cloud computing systems are used to manage digital assets, then serviceability and ease of operation are improved, but reliability and trust are worsened due to dependence on service providers
Solution Approach 1:
The patent introduces a hybrid architecture where a cloud-based database system serves as an intermediary for efficient data storage and retrieval, while a public trust ledger (blockchain) acts as a mediator for immutable transaction recording. This separation allows the cloud system to provide ease of operation while the blockchain ensures reliability through its decentralized, tamper-proof nature.
Solution Approach 2:
The system segments functionality between two distinct components: a cloud-based database system for operational efficiency and a public trust ledger for trust verification. This segmentation allows each component to excel at its specific function while mitigating the weaknesses of relying solely on one system.
2Reliability
If public trust ledgers are used for transaction recording, then reliability and security are improved, but productivity and ease of operation are worsened due to lack of platform support
Solution Approach 1:
The patent divides the system into two functional segments: the public trust ledger handles only the critical function of immutable transaction recording to ensure reliability, while the cloud-based database system handles operational tasks like asset management and user interactions to maintain productivity. This segmentation allows each component to optimize for its specific purpose.
Solution Approach 2:
The cloud-based database system acts as an intermediary layer that provides enterprise-level platform support and operational efficiency, while the public trust ledger serves as the underlying mediator for trust verification. This architecture allows public trust ledgers to maintain their reliability without directly handling complex operational tasks.
3Reliability
If all metadata is stored on the blockchain, then reliability is improved, but loss of substance and transaction costs are worsened
Solution Approach 1:
The patent extracts only the essential transactional metadata that requires immutable verification and stores it on the blockchain, while moving non-critical attribute data to off-chain storage. This extraction minimizes the amount of data stored on-chain, reducing transaction costs and blockchain bloat while maintaining reliability for critical operations.
Solution Approach 2:
The system transitions from a single-dimensional storage approach (all data on-chain) to a multi-dimensional architecture where critical transaction data resides on the blockchain and supplementary attribute data is stored off-chain. This dimensional change allows the system to maintain reliability for essential operations while reducing substance loss through selective data placement.
Data Source
AI summary
A plurality of metadata entries may be sent from a database system to a distributed storage system via a communication interface. The metadata entries may correspond with a respective plurality of metadata identifiers. A first function in a smart contract deployed on a blockchain may be executed to mint a designated non-fungible token initially owned by a first blockchain party corresponding with a database system account. A first transaction transferring the designated non-fungible token to a second blockchain party different from the first blockchain party may be identified. A second function in the smart contract may be executed to record a second transaction updating an attribute value associated with the designated non-fungible token to include a designated one of the plurality of metadata identifiers corresponding with a designated one of the metadata entries.