Blockchain Notification Board for Resource Authenticity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Decentralized blockchain systems face challenges in managing network location information and resource authenticity due to potential hijacking or replacement of peer nodes, leading to issues with fraud and dangling references, as existing solutions lack sufficient trust and redundancy mechanisms.
Innovation Solution
Implementing a blockchain notification board on a distributed ledger that stores unique identifiers and blockchain IDs independently of the blockchain, allowing for secure storage and retrieval of peer node information, ensuring authenticity and preventing fraudulent activities by using a blockchain-based uniform resource indicator (BURI) mechanism.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If network address information is stored internally by client nodes from peer nodes, then communication between clients and blockchain peer nodes is enabled, but fraud and dangling references occur due to hijacking or replacement of peer nodes
Solution Approach 1:
The patent introduces a notification board as an intermediary component that mediates between peer nodes and client nodes. The notification board stores and manages network address information, chaincode information, and other resource identifiers in a transparent and verifiable manner. Client nodes query the notification board to obtain resource identifiers rather than relying on peer node-provided information, preventing fraud from hijacked peer nodes while maintaining communication capability.
2Device complexity
If a centralized database is used to store blockchain resources, then management and control are simplified, but single point of failure and limited access occur
Solution Approach 1:
The patent segments the blockchain system into multiple independent components: peer nodes that generate and broadcast resource identifiers, notification boards that store and manage these identifiers, and client nodes that query the notification boards. This segmentation distributes the functionality across multiple nodes rather than relying on a single centralized database, eliminating single points of failure while maintaining manageable complexity through clear role separation.
3Adaptability or versatility
If peer nodes are allowed to change network addresses dynamically, then adaptability to network changes is improved, but fraudulent activity and dangling references increase
Solution Approach 1:
The notification board implements a feedback mechanism where peer nodes broadcast resource identifiers (network addresses, chaincode information) to the notification board, which then makes this information available to client nodes. When peer nodes change their network addresses or other resource identifiers, they update the notification board, which propagates the changes to all client nodes. This feedback loop ensures that adaptability to network changes is maintained while reference integrity is preserved through verifiable updates.
4Stability of the object's composition
If blockchain resources are stored on the blockchain itself, then data consistency is maintained, but access efficiency decreases due to blockchain immutability and consensus requirements
Solution Approach 1:
The patent extracts resource identifier storage from the blockchain itself and places it in notification boards that operate independently from the blockchain's immutable ledger. The notification boards store resource identifiers (network addresses, chaincode information) that are broadcast by peer nodes and queried by client nodes. This extraction allows fast read/write operations for resource identifiers without requiring blockchain consensus, while the blockchain continues to maintain data consistency for actual transactions and state changes.
Data Source
AI summary
An example operation may include one or more of receiving a unique identifier of a blockchain system resource from among a plurality of blockchain system resources associated with a blockchain, generating a notification board for the blockchain which is implemented independently from the blockchain and stored on a distributed ledger including the blockchain, and storing the unique identifier of the blockchain resource and a blockchain ID within the notification board on the distributed ledger.