Light Client Verification Using Registry Blockchain Validator Sets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing blockchain systems face resource-intensive operations and reliability issues with full nodes, and data indexing providers can surface incorrect information or cause delays, making it challenging to verify transactions across multiple blockchains efficiently.
Innovation Solution
Implementing a registry blockchain network that stores validator data from various transaction blockchains and uses a light client to independently verify transaction proofs, reducing the need for full nodes and conserving resources while ensuring accurate transaction verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full nodes are deployed to execute every transaction and store the entire blockchain state, then trustless access to the blockchain is achieved, but resource-intensive operations occur
Solution Approach 1:
The system segments the blockchain verification function into two parts: a registry blockchain that stores validator set data, and light clients that verify transactions using this data. This segmentation allows light clients to achieve trustless verification without the resource burden of full nodes.
Solution Approach 2:
The registry blockchain acts as an intermediary between transaction blockchains and light clients. It provides validator set data that enables light clients to independently verify transactions, eliminating the need for light clients to rely on full nodes or untrusted third parties.
2Ease of operation
If data indexing providers are used to surface blockchain information through APIs, then lightweight access is provided, but reliability issues occur due to potential compromises or downtime
Solution Approach 1:
The registry blockchain serves as a trusted intermediary that light clients can query directly for validator set data. This eliminates reliance on potentially compromised data indexing providers while maintaining lightweight access through API-like interfaces.
Solution Approach 2:
Light clients independently query the registry blockchain for validator set data and perform verification themselves, rather than relying on third-party data indexing providers to supply and verify information. This self-service approach ensures reliability while maintaining ease of operation.
3Adaptability or versatility
If multiple transaction blockchains are supported to facilitate transactions with various users, then versatility is improved, but complexity of verifying transactions across blockchains increases
Solution Approach 1:
The registry blockchain provides a universal interface for verifying transactions across multiple different transaction blockchains. Light clients can verify transactions from any supported blockchain using the same verification mechanism and registry data structure, simplifying multi-blockchain support.
Solution Approach 2:
The registry blockchain acts as a universal intermediary that standardizes verification across multiple transaction blockchains. It stores validator set data from various blockchains in a consistent format, allowing light clients to verify transactions from any supported blockchain without dealing with individual blockchain complexities.
Data Source
AI summary
In some implementations, a method for processing state transition proofs in multi-blockchain ecosystems is provided. A registry blockchain network receives validator data that represents a validator set of a transaction blockchain network that is different from the registry blockchain network. The registry blockchain network stores the validator data on a registry blockchain, among validator data that represents other validator sets of other transaction blockchain networks. A registry client of the registry blockchain network receives a transaction identifier of a transaction that is purported to have been submitted by a transaction client to the transaction blockchain network, and evidence data of a committed state that indicates that the transaction has been included in a block that has been added to the transaction blockchain. The registry client independently verifies the evidence data of the committed state, based at least in part on the stored validator data.