Minimal Verification Clients for Trustless Blockchain Node Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Lightweight devices, such as IoT devices, face challenges in processing blockchain interactions due to processing, bandwidth, and power constraints, leading to compromises in decentralization and trustlessness when using remote clients, which also introduce single points of failure.
Innovation Solution
Implementing a minimal verification client on lightweight devices that interacts with a decentralized network through a trustless, stateless remote client system, allowing unsynchronized devices to validate blockchain transactions using a list of synchronized nodes and validation indicia, such as Merkle proofs, while maintaining decentralization and preventing fraudulent behavior.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a remote client is used to process blockchain interactions for lightweight devices, then processing capacity requirements are reduced, but decentralization and trustlessness are compromised
Solution Approach 1:
The patent introduces a remote client as an intermediary component that runs on external servers rather than on the lightweight device itself. This remote client acts as a mediator between the resource-constrained device and the blockchain network, allowing the device to interact with blockchain networks without running resource-intensive blockchain clients locally. The remote client handles complex validation and interaction logic while the lightweight device simply sends requests and receives results, thus reducing local processing requirements while maintaining system security through the remote client's verification capabilities.
Solution Approach 2:
The system segments the blockchain client functionality into two parts: a lightweight interface component running on the constrained device and a full-featured remote client running on external servers. This segmentation allows the lightweight device to have minimal software installed while the heavy lifting of blockchain protocol implementation, validation, and state tracking is performed by the remote client instances distributed across multiple servers.
2Device complexity
If a remote client is used to process blockchain interactions for lightweight devices, then processing capacity requirements are reduced, but single points of failure are introduced
Solution Approach 1:
The patent implements local quality by making each remote client instance independent and self-contained on its host server. Each remote client maintains its own blockchain state and validation capabilities, so that the failure of one remote client instance does not affect others. The system distributes multiple remote client instances across different servers, creating a portfolio of independent processing units that can be selectively used based on availability and performance.
Solution Approach 2:
The system dynamically selects which remote client instance to use for processing requests based on current server availability, load conditions, and performance metrics. The lightweight device can switch between different remote client instances as needed, and the system can dynamically provision new remote client instances on demand. This dynamic approach ensures continuous service availability even when individual servers experience failures or maintenance issues.
Data Source
AI summary
A system and a method are disclosed for using a client that is unsynchronized with a blockchain network to validate blockchain transactions for IoT devices, web apps, mobile apps, and other applications. The client retrieves a register of nodes (acting as information provider or validator) that are synchronized with the blockchain network, selects a node from the register, and transmits an information request to the selected node. The client receives a response to the request, the response including the requested information and validation indicia (e.g., proofs), and determines whether the response is valid based on the validation indicia. The client transmits, in response to determining that the response is valid, a confirmation to the IoT device, web app, mobile app or other applications.