Blockchain Node Block Generation via Local Account Key
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The Proof of Work (POW) consensus mechanism in blockchain networks has become centralized due to the emergence of mining pools, leading to reduced credibility, stability, and security, as large mining pools dominate computing power and can facilitate attacks like double-spending transactions.
Innovation Solution
Introducing a local account key for each node to compete for block generation rights, ensuring that only authorized nodes can participate in block generation, thereby preventing mining pool administrators from allocating computation burdens to other nodes and maintaining account security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If mining pools are used to aggregate computing power for block generation, then block generation efficiency is improved, but decentralization degree deteriorates
Solution Approach 1:
The patent segments the block generation process by introducing multiple candidate block headers with different account keys. Instead of a single centralized mining pool controlling block generation, the system divides the generation process into multiple independent candidates, each associated with different account keys, thereby distributing the generation rights across multiple entities while maintaining efficient block production.
Solution Approach 2:
The patent applies local quality by associating different account keys with different candidate block headers. Each candidate block header has its own local account key, creating distinct authorization zones. This ensures that different parts of the block generation process can be independently verified and secured, preventing centralized control while maintaining overall system efficiency.
2Speed
If mining pools dominate computing power, then block generation speed is improved, but network security deteriorates
Solution Approach 1:
The patent introduces an intermediary verification mechanism where multiple account keys and their corresponding private keys act as intermediaries between the block generation process and network validation. This intermediary layer ensures that even if mining pools control generation speed, each candidate block must pass through independent verification using different account keys, thereby maintaining network security against centralized control.
Solution Approach 2:
The patent changes the security parameter by introducing multiple account keys with different authorization levels. Instead of relying on a single security model, the system uses multiple cryptographic parameters (different account keys and private keys) to verify candidate blocks. This parameter diversification ensures that fast block generation by mining pools does not compromise security, as each candidate must satisfy multiple independent verification criteria.
3Productivity
If mining pool administrators allocate computation burdens to multiple nodes, then computing power utilization is improved, but account security deteriorates
Solution Approach 1:
The patent applies preliminary action by pre-associating account keys with candidate block headers before the actual block generation process. Each candidate block header is prepared with its own account key in advance, and the corresponding private key is securely stored. This preliminary setup ensures that when computing power is distributed across multiple nodes, each node can independently verify its assigned candidate block using its pre-configured account key, preventing unauthorized access and maintaining account security while utilizing distributed computing power.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
The present application discloses a blockchain operation method and apparatus, a device, and a storage medium, which relate to the field of blockchain technologies and may be applied to cloud calculation and cloud service. The specific implementation solution is as follows: performing signature processing on block header data of a block to be broadcast according to a local account key, to obtain a block header signature; and determining a block identifier of the block to be broadcast according to the block header signature, to enable a local node to compete for a block generation right of the block to be broadcast.