Headers Client Best Chain Determination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain systems face challenges in allowing offline cryptocurrency transactions and efficient data management, particularly in determining the best chain of block headers, which is crucial for transaction verification and network consensus, while maintaining low bandwidth and storage requirements.
Innovation Solution
A headers client system that receives, stores, and analyzes block headers to determine the best chain by validating proof-of-work, providing a lightweight and efficient method for light clients to verify transactions and maintain a shared view of the blockchain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If light clients store and validate complete blockchain data, then transaction verification reliability is improved, but bandwidth and storage requirements increase
Solution Approach 1:
The patent extracts only the essential block header information (hash, timestamp, difficulty target, nonce) from complete blockchain blocks, allowing light clients to verify transactions using minimal data. This extraction principle reduces bandwidth and storage requirements while maintaining verification reliability through cryptographic proofs.
Solution Approach 2:
The patent introduces a headers client as an intermediary service between the blockchain network and light clients. This mediator collects, validates, and distributes block headers to light clients, enabling them to verify transactions without directly accessing the full blockchain data, thus reducing their bandwidth and storage needs while maintaining reliability.
2Adaptability or versatility
If multiple blockchains are supported simultaneously, then system versatility is improved, but computational complexity increases
Solution Approach 1:
The patent designs a universal headers client architecture that can handle multiple blockchain networks through a standardized interface. The system uses a configuration file format (YAML) to define different blockchain parameters, allowing the same core logic to serve multiple chains without requiring separate validation implementations for each.
Solution Approach 2:
The patent manages multi-blockchain support by changing parameters (difficulty targets, hash functions, block intervals) through configuration files rather than hardcoding different validation logic. This allows the system to adapt to different blockchain specifications while maintaining a single computational framework, reducing overall complexity.
3Measurement precision
If block headers are validated in real-time, then consensus accuracy is improved, but processing time increases
Solution Approach 1:
The patent performs preliminary validation of block headers by checking basic properties (difficulty target compliance, timestamp ordering, nonce validity) before full consensus verification. This preliminary action filters out obviously invalid headers early, reducing the computational burden of real-time consensus checking while maintaining accuracy.
Solution Approach 2:
The patent implements partial validation by focusing on critical consensus-determining properties of block headers (cumulative difficulty, chain continuity) rather than verifying every transaction detail. This partial action approach provides sufficient consensus accuracy for light clients while significantly reducing processing time compared to full node validation.
Data Source
AI summary
There is provided mechanisms for managing data in a blockchain network. In one embodiment, there is provided a computer implemented method performed at a headers client and comprising the following steps. Receiving a plurality of block headers from at least one external source, external to the headers client, the block headers each referring to a block in a blockchain. Storing the received plurality of block headers in a storage module. Analysing the plurality of block headers by validating the proof-of work for the plurality of received headers. Determining a best chain of block headers from the analysed plurality of block headers and storing the best chain at the storage module. The best chain can be a chain of blocks from genesis, which is a first block in the blockchain, to a current best block, which is a latest block in the blockchain. The best block may have the highest cumulative proof-of-work.