Segregated Database for Distributed Ledger Privacy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Distributed ledger systems, such as blockchain, face security and privacy concerns due to their public nature, particularly in high-risk and sensitive environments, where sensitive transaction information may be exposed, and scalability issues hinder efficient transaction verification.
Innovation Solution
Implementing a segregated database architecture within a multiple distributed ledger system, where each profile or account has its own ledger, with a central administrator maintaining a ledger of inter-ledger communications, ensuring privacy and security by isolating transaction data and using tokens for secure data exchanges.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a public distributed ledger system is used to ensure transparency and verification, then system robustness and fraud resistance are improved, but security and privacy of sensitive transaction data deteriorate
Solution Approach 1:
The patent divides the single public ledger into multiple segregated ledgers, each dedicated to a specific account or entity. This segmentation allows each ledger to maintain its own transaction history privately while still being part of the distributed system, thus preserving security and privacy while maintaining system robustness through distributed verification.
Solution Approach 2:
The patent introduces a segregated database that acts as an intermediary layer between the distributed ledger system and sensitive transaction data. This intermediary maintains profile balance data and validates transactions without exposing detailed transaction information, thereby protecting privacy while enabling verification.
2Device complexity
If a single public ledger is used to track all transactions, then system simplicity is maintained, but scalability and transaction verification efficiency deteriorate
Solution Approach 1:
The patent segments the monolithic ledger into multiple smaller, account-specific ledgers. This reduces the size of data each node needs to process and store, improving verification efficiency and scalability while maintaining distributed ledger benefits. The segregated database further optimizes this by maintaining only essential balance information.
Solution Approach 2:
The patent implements local quality by allowing each segregated ledger to be optimized for its specific account's transaction patterns and volume. This enables tailored verification processes for different accounts, improving overall system efficiency while maintaining simplicity through standardized access protocols.
3Speed
If all transaction data is stored centrally for easy access, then data retrieval speed is improved, but system security and decentralization benefits deteriorate
Solution Approach 1:
The patent segments transaction data across multiple distributed ledgers rather than centralizing it. Each ledger stores only relevant transactions for its associated account, enabling fast local retrieval while maintaining distributed security. The segregated database provides rapid access to balance information without centralizing sensitive transaction details.
Solution Approach 2:
The patent creates distributed copies of essential account information across multiple nodes through the segregated database, enabling fast data retrieval from multiple locations simultaneously. This copying approach maintains security by distributing data rather than centralizing it, and improves speed through parallel access capabilities.
Data Source
AI summary
An apparatus maintains a segregated database in a multiple distributed ledger system. The apparatus includes a storage device that stores software instructions for controlling a processor that when executed by the processor configure the processor to: create distributed ledgers, each created distributed ledger being associated with a respective individual profile; maintain a segregated database apart from the distributed ledgers including, for each individual profile, profile balance data; and process a data exchange between exchanging profiles. To process the data exchange, the processor is configured to receive data exchange data regarding parameters of the data exchange; approve the data exchange based on a check of the data exchange data against profile balance data in the database; access the distributed ledgers associated with the exchanging profiles; and cause a distributed ledger data exchange corresponding to the data exchange to be added to the accessed distributed ledgers when the data exchange is approved.