Light Client Blockchain Verification via Merkle Proofs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain verification systems, particularly for resource-limited clients, face challenges in efficiently verifying interactions due to the need to download and store large amounts of data, high latency in communication protocols, and vulnerability to malicious nodes, especially as blockchains grow in size.
Innovation Solution
A method and system that allow clients to efficiently verify the validity of a full node's blockchain by downloading a logarithmic number of block headers using a probabilistic verification protocol and a Merkle mountain range data structure, which reduces data requirements and prevents cheating by malicious nodes, while maintaining security and efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a client downloads all blocks in the blockchain to verify interactions, then verification reliability is improved, but data storage requirements and bandwidth consumption increase significantly
Solution Approach 1:
The patent extracts only the essential verification elements from the complete blockchain data. Instead of requiring clients to download and store all blocks, the system extracts block headers and generates cryptographic proofs (Merkle proofs) that contain only the necessary information to verify transaction inclusion. This extraction principle reduces data storage from gigabytes to kilobytes while maintaining verification reliability.
Solution Approach 2:
The verification process is segmented into separate components: block headers are separated from full block data, and verification proofs are separated from the blockchain itself. Clients only need to download segmented portions (headers and proofs) rather than complete blocks. This segmentation enables light clients to verify transactions without storing the entire blockchain.
2Measurement precision
If a client downloads all blocks to verify transactions, then verification accuracy is improved, but verification time increases to days
Solution Approach 1:
The system performs preliminary actions by pre-computing and storing block headers and Merkle roots in the blockchain structure before clients need to verify transactions. Full nodes prepare verification data (headers, Merkle proofs) in advance and make them available for immediate download by clients. This preliminary preparation eliminates the need for clients to perform time-consuming verification computations locally.
Solution Approach 2:
Instead of requiring clients to process original full block data, the system creates simplified copies in the form of block headers and cryptographic proofs. These copies contain condensed verification information that can be processed quickly by light clients. The copying principle maintains verification accuracy while reducing computational time from days to seconds.
3Use of energy by moving object
If light clients use simplified payment verification with block headers, then resource consumption is reduced, but vulnerability to malicious nodes increases
Solution Approach 1:
The patent implements a sampling-based verification approach where clients download a partial set of block headers and verification proofs rather than complete validation data. By strategically selecting which headers and proofs to download (excessive sampling beyond minimum requirements), the system maintains high security confidence while keeping resource consumption low. This partial verification with oversampling mitigates risks from malicious nodes.
Solution Approach 2:
The verification system incorporates feedback mechanisms where full nodes provide verification responses to client queries, and clients can request additional proofs or headers if verification fails. The network provides feedback about chain consistency and node honesty, allowing light clients to adapt their verification strategy. This feedback loop enhances security against malicious nodes while maintaining low resource consumption.
Data Source
AI summary
The method comprises a client device receiving a verification request comprising an interaction identifier. The client device can compare samplings of block headers received from two or more full nodes. The client device can then, based on the comparing, verify at least one block header of the samplings of block headers. The client device can determine that a blockchain maintained by at least one of the two or more full nodes is valid in response to verifying the at least one block header of the samplings of block headers.