Blockchain Reliability Database for External 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
Implementing a reliability database on a distributed ledger within a blockchain network that allows peer nodes to determine and store reliability values for external data sources through consensus, enabling tracking and updating of reliability information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If blockchain systems rely on external data sources without verification mechanisms, then data access and transaction processing are simplified, but data reliability and trustworthiness deteriorate
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 through multiple checks (data consistency, source reputation, cross-validation) before accepting data, thereby maintaining simplicity for users while ensuring reliability through the intermediary verification layer.
Solution Approach 2:
The patent implements feedback mechanisms where the blockchain system continuously monitors and evaluates external data sources based on data quality, consistency, and reliability metrics. This feedback is used to dynamically adjust trust levels and verification requirements, improving reliability while maintaining operational simplicity through automated adjustments.
2Reliability
If a centralized database is used to maintain data, then data integrity and consistency are maximized, but single point of failure and network dependency increase
Solution Approach 1:
The patent segments the centralized database architecture into a distributed blockchain network where data is replicated across multiple nodes. Each node maintains a copy of the ledger, eliminating the single point of failure while preserving data integrity through cryptographic verification and consensus mechanisms. The system divides responsibilities among nodes for data storage, validation, and consensus.
Solution Approach 2:
The patent applies local quality by allowing different nodes in the distributed network to have specialized functions (e.g., some nodes focus on data storage, others on validation, others on consensus). Each node maintains local data integrity checks while contributing to overall system reliability, reducing vulnerability through functional distribution across the network.
3Device complexity
If external data sources are used without reliability tracking, then system complexity is reduced, but trust verification and fraud prevention capabilities deteriorate
Solution Approach 1:
The patent applies preliminary action by establishing reliability tracking mechanisms and verification protocols before external data sources are utilized. The system pre-establishes trust levels, verification requirements, and monitoring frameworks for external data sources, enabling accurate reliability assessment before transactions occur rather than attempting to evaluate reliability after potential fraud has occurred.
Data Source
AI summary
An example operation may include one or more of receiving a request for trust information of an off-chain data source from a client, determining a category type of the off-chain data source from among a plurality of category types based on the request, retrieving a reliability value of the off-chain data source linked to one or more of an identity of the off-chain data source and the determined category type from a reliability database implemented via a distributed ledger shared among a plurality of peer nodes, and transmitting the retrieved reliability value linked to the category type to the client.