Permissioned Blockchain Consensus Using Auditing Nodes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing blockchain consensus mechanisms, such as proof of work, are computationally expensive and time-consuming, making them impractical for devices with lower processing power, and require significant computational effort to verify new blocks, which is inefficient and costly.
Innovation Solution
A method and system for a permissioned blockchain using an efficient consensus mechanism involving a processing server that generates a Merkle root and a proposal number, transmitting messages to auditing and consensus nodes for agreement, and utilizing bloom filters for desynchronization recovery, reducing computational requirements and time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If proof of work consensus mechanism is used, then security and decentralization are improved, but processing time and computational cost increase significantly
Solution Approach 1:
The patent segments the blockchain network into different node types (auditing nodes and consensus nodes) with specialized functions. Auditing nodes perform cryptographic verification while consensus nodes handle block proposal and selection, dividing the computational workload to reduce overall verification time while maintaining security through distributed validation
Solution Approach 2:
The patent introduces auditing nodes as intermediary entities that verify the authenticity of blocks before they are added to the blockchain. These auditing nodes act as a intermediary layer between consensus nodes and the blockchain ledger, performing cryptographic verification without requiring all consensus nodes to perform computationally intensive proof of work
2Reliability
If proof of work consensus mechanism is used, then consensus security is improved, but processing power requirements increase prohibitively
Solution Approach 1:
The patent segments the blockchain network into different node types (auditing nodes and consensus nodes) with specialized functions. Auditing nodes perform cryptographic verification while consensus nodes handle block proposal and selection, dividing the computational workload to reduce overall verification time while maintaining security through distributed validation
Solution Approach 2:
The patent uses cryptographic signatures and hash values as lightweight verification objects that can be quickly validated without requiring sustained high computational power. These cryptographic artifacts serve as disposable verification tokens that provide security guarantees without the need for continuous intensive computing resources
3Reliability
If traditional consensus mechanisms are used, then security is maintained, but network traffic and data exchange increase
Solution Approach 1:
The patent extracts the verification logic from every node and concentrates it in specialized auditing nodes. This extraction allows most nodes to participate in consensus with minimal data exchange, while auditing nodes handle the intensive verification processes separately, reducing overall network traffic while maintaining security through centralized cryptographic validation
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method for adding a block to a permissioned blockchain using an efficient consensus mechanism is described. A prepare message is transmitted to a plurality of auditing nodes associated with a blockchain - this prepare message includes at least a confirmation hash value and a proposal number, wherein the proposal number is a numeric value of a digital signature for a proposed block header that includes a previous hash value and a Merkle root generated for a plurality of transaction messages. A prepare response message is received from most of the auditing nodes. Each prepare response message includes at least the confirmation hash value and an accepted proposal number. An agreed proposal number is identified based on the numeric value of the generated proposal number and a numeric value of the accepted proposal number included in each prepare response message, and a predetermined criteria, and an accept message is transmitted to the plurality of auditing nodes - this accept message includes at least the confirmation hash value and the identified agreed proposal number. A confirm message is transmitted to a plurality of consensus nodes associated with the blockchain, wherein the confirm message includes at least the confirmation hash value and the identified agreed proposal number. A query is executed on the memory to add a new block to the blockchain, the new block including at least the transaction value included in each of the plurality of transaction messages and a new block header including at least the previous hash value, the generated Merkle root, and the agreed proposal number.