Blockchain Reliability Database for Off-Chain Data Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Blockchain systems face challenges in verifying the reliability of external data sources, as they typically rely on external sources without mechanisms to assess or update their reliability, leading to potential inaccuracies and fraud.
Innovation Solution
A system that allows for the modification and consensus-driven updating of reliability values for off-chain data sources, storing these values within a distributed ledger on a blockchain, ensuring that changes in reliability are tracked and recorded immutably across peer nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If blockchain systems rely on external data sources without verification mechanisms, then data access simplicity is improved, but data reliability deteriorates
Solution Approach 1:
The patent introduces an intermediary verification mechanism where the blockchain system acts as a mediator between external data sources and users. The system verifies external data sources against stored reliability information in the key-value store before accepting their data, thus maintaining data access simplicity while improving reliability through intermediate verification.
Solution Approach 2:
The patent implements preliminary action by pre-storing reliability information about external data sources in the key-value store before actual data transactions occur. This allows the system to quickly verify data source reliability during transactions without adding complex real-time verification procedures, maintaining simplicity while ensuring reliability.
2Reliability
If reliability information is stored on the blockchain ledger, then data integrity is improved, but storage efficiency deteriorates
Solution Approach 1:
The patent segments the storage system into two parts: a key-value store for storing reliability information and the blockchain ledger for storing only critical verification data. This segmentation allows bulk reliability data to be stored efficiently in the key-value store while maintaining data integrity through selective blockchain storage, thus improving both storage efficiency and data integrity.
Solution Approach 2:
The patent uses copying by storing reliability information in the key-value store and maintaining a reference or hash of this information on the blockchain ledger. This allows the system to verify data integrity through the blockchain while avoiding the inefficiency of storing complete reliability datasets on the blockchain, thus optimizing storage efficiency without compromising integrity.
3Object-affected harmful factors
If external data sources are verified against stored reliability information, then fraud prevention is improved, but system complexity deteriorates
Solution Approach 1:
The patent implements self-service by enabling the system to automatically verify external data sources against pre-stored reliability information in the key-value store. This automated verification process prevents fraud without requiring manual intervention or complex verification procedures, thus improving fraud prevention while keeping system complexity manageable through automation.
4Measurement precision
If reliability updates require consensus among peer nodes, then data accuracy is improved, but processing time deteriorates
Solution Approach 1:
The patent applies partial action by requiring consensus from a threshold number of peer nodes rather than all nodes for reliability updates. This allows the system to achieve sufficient data accuracy through partial consensus, reducing the processing time required compared to requiring unanimous agreement from all peer nodes, thus balancing accuracy and efficiency.
Data Source
AI summary
An example operation may include one or more of receiving a request to modify a reliability value of an off-chain data source to generate a modified reliability value, determining whether a consensus on the modified reliability value has been received among a plurality of peer nodes, and in response to a determination that the consensus has been received, updating a storage to reflect the modified reliability value associated with the off-chain data source, and storing an identification of the modified reliability value within a block among a hash-linked chain of blocks on a distributed ledger shared among the plurality of peer nodes.