Blockchain Block Verification via Segmented Hash and Transaction Rules
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In existing blockchain systems like Bitcoin, the lack of motivation for blockchain management nodes to hold unnecessary transactions leads to a risk of important data loss, as only the block header's hash value is used for verification, making it unnecessary to store detailed transaction information, which can result in data loss when the motivation to hold these transactions is low.
Innovation Solution
A blockchain management apparatus and method that includes a block receiving part to receive blocks with a block header containing a hash value for reference information selected based on a predetermined rule, a block verification part to verify the correctness of the block generation using the reference information, and a consensus formation part to ensure the block is correctly generated and stored in the ledger, thereby incentivizing nodes to hold more transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If only block header hash values are used for verification, then verification efficiency is improved, but data integrity is worsened due to potential loss of detailed transaction information
Solution Approach 1:
The patent segments the verification process into two parts: (1) verification of block header hash values for efficiency, and (2) verification of detailed transaction information through a determination rule for data integrity. This segmentation allows the system to maintain both verification efficiency and data integrity by handling different aspects of verification separately.
Solution Approach 2:
The patent applies preliminary action by storing detailed transaction information in the ledger before verification occurs. The determination rule is established in advance to specify which transaction details must be preserved, ensuring that even if nodes prune old data, the necessary information for verifying block correctness remains available.
2Reliability
If detailed transaction information is stored, then data integrity is improved, but storage capacity requirement is worsened
Solution Approach 1:
The patent applies local quality by selectively storing different types of information with different retention requirements. The determination rule specifies which transaction details (local parts of the data) must be preserved for verification, while allowing other information to be pruned. This ensures data integrity for critical information while reducing overall storage requirements.
Solution Approach 2:
The patent enables discarding of unnecessary old transaction data while recovering or preserving only the specific information needed for verification through the determination rule. Nodes can prune historical data that is no longer needed, but the rule ensures that essential transaction details required for block verification are retained, achieving a balance between storage efficiency and data integrity.
3Stability of the object's composition
If all blockchain nodes store complete transaction data, then data consistency is improved, but processing capability requirement is worsened
Solution Approach 1:
The patent applies universality by creating a determination rule that serves multiple functions: it identifies which transaction details must be stored, defines verification requirements, and enables nodes with varying capabilities to participate in the network. This universal rule ensures data consistency across all nodes while allowing each node to implement the solution according to its processing capacity.
Data Source
AI summary
A blockchain management apparatus includes a block receiving part that receives a block including a block header that includes a hash value for reference information selected from a predetermined range in a ledger based on a predetermined rule established between blockchain management apparatuses; a block verification part that selects the reference information from the predetermined range in the ledger based on the predetermined rule and determines whether or not the hash value for the reference information included in the block has been generated based on the reference information, to verify that the block has been correctly generated; a consensus formation part that, if the block verification part verifies that the block has been correctly generated, forms a consensus with other blockchain management apparatuses to write the block to the ledger; and a ledger storage part that stores the block for which the consensus has been formed.