Blockchain Notification Board for Resource Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Decentralized blockchain systems face challenges in managing network location information and resources due to issues like fraud, hijacking of peer nodes, and the lack of uniqueness and authenticity of network resources, which can lead to fraudulent activities and data inconsistencies.
Innovation Solution
Implementing a blockchain notification board within a distributed ledger that stores blockchain-based Uniform Resource Indicators (URIs) and chaincode information, allowing for the re-instantiation of chaincode versions to ensure data integrity and authenticity, and using a unique genesis value to validate blockchain identifiers and transmit certificates of authenticity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a centralized database is used to store blockchain resources, then data integrity and consistency are maximized, but the system has a single point of failure and limited access to data
Solution Approach 1:
The patent segments the centralized database storage into multiple distributed peer nodes, each maintaining copies of the blockchain ledger. This segmentation eliminates the single point of failure while maintaining data integrity through distributed consensus mechanisms.
Solution Approach 2:
The patent implements copying by replicating the blockchain ledger across multiple peer nodes. Each node maintains a copy of the immutable ledger, ensuring data availability and integrity without relying on a single centralized storage location.
2Speed
If network address information is stored internally by client nodes, then access speed is improved, but fraud and hijacking of peer nodes can occur
Solution Approach 1:
The patent introduces an intermediary verification mechanism where the blockchain ledger acts as a trusted mediator. Before accessing network resources, clients verify the authenticity of peer nodes through the immutable ledger, which serves as a mediator between the client's speed requirements and the need for fraud prevention.
Solution Approach 2:
The patent implements preliminary action by pre-storing authenticated network address information and peer node identities in the blockchain ledger before actual resource access occurs. This allows clients to quickly verify and access resources without compromising security, as the authentication has already been performed and recorded immutably.
3Adaptability or versatility
If chaincode versions are updated at computing nodes, then system adaptability is improved, but data consistency and authenticity are compromised
Solution Approach 1:
The patent implements feedback by requiring that all chaincode version updates be recorded and verified through the blockchain ledger. When a computing node updates chaincode, the change is propagated to the ledger, and other nodes can verify the authenticity of the update through consensus mechanisms, ensuring data consistency while allowing adaptability.
Solution Approach 2:
The patent uses preliminary action by requiring chaincode updates to be pre-authenticated and recorded in the blockchain ledger before being executed at computing nodes. This ensures that all nodes can verify the authenticity of updates before applying them, maintaining data consistency while enabling system adaptability through controlled version updates.
Data Source
AI summary
An example operation may include one or more of receiving a resource request from a client, identifying a unique chaincode identifier associated with the resource request, re-instantiating a version of chaincode based on the unique chaincode identifier, the re-instantiation configured to disregard any subsequently implemented versions of the chaincode at the computing node, executing the resource request based on the re-instantiated version of the chaincode to generate a result, and transmitting the result to the client.