Blockchain Consensus Synchronization Across Mixed Fault Tolerance Types
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing blockchain networks face challenges in flexibility due to the use of a single unified consensus algorithm, which fails to meet diverse system service requirements, leading to inefficiencies and service interruptions during algorithm switching.
Innovation Solution
Implementing multiple consensus algorithms of different fault tolerance types in a blockchain network, allowing for flexible switching without service interruption by synchronizing consensus results based on node quantity counts that satisfy specific consensus conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a unified consensus algorithm is used in the blockchain network, then data consistency and reliability are ensured, but flexibility and adaptability to diverse service requirements deteriorate
Solution Approach 1:
The patent segments the consensus algorithm execution by dividing nodes into different consensus groups, where each group can execute different consensus algorithms simultaneously. This allows the system to maintain data consistency within each group while providing flexibility across the entire network to meet diverse service requirements.
Solution Approach 2:
The patent implements dynamic consensus algorithm selection by allowing nodes to switch between different consensus algorithms based on service requirements. The system can dynamically adjust which consensus algorithm is executed by which nodes, enabling adaptability while maintaining reliability through proper consensus result synchronization.
2Adaptability or versatility
If consensus algorithms are switched to meet diverse service requirements, then flexibility is improved, but service interruptions and system stability deteriorate
Solution Approach 1:
The patent performs preliminary actions by pre-establishing multiple consensus groups with different consensus algorithms before service requirements change. When flexibility is needed, the system can switch between pre-configured algorithms without interruption, as the alternative algorithms and groups are already in place and ready to execute.
Solution Approach 2:
The patent ensures continuity of useful action by implementing parallel consensus execution in different groups. While one consensus group is executing a particular algorithm, other groups can simultaneously execute different algorithms, ensuring that consensus services continue without interruption during algorithm transitions or adaptations.
3Adaptability or versatility
If multiple consensus algorithms are executed simultaneously by different nodes, then flexibility and service adaptability are improved, but consensus result consistency and coordination complexity increase
Solution Approach 1:
The patent introduces an intermediary mechanism through designated coordinator nodes within each consensus group. These coordinators manage the execution of specific consensus algorithms, track consensus results, and facilitate synchronization between groups, thereby reducing the overall coordination complexity while allowing multiple algorithms to run simultaneously.
Solution Approach 2:
The patent uses copying by replicating the consensus execution framework across multiple independent consensus groups. Each group maintains its own consensus state and execution environment, allowing different algorithms to run in parallel without interfering with each other, thus simplifying coordination through isolation while maintaining service adaptability.
Data Source
AI summary
A blockchain consensus method includes broadcasting consensus requests to at least two blockchain nodes executing consensus algorithms of different fault tolerance types in a blockchain network. The method further includes obtaining response messages from blockchain nodes in the blockchain network in response to the consensus requests, and counting a node quantity of blockchain nodes transmitting the response messages in a same consensus stage, the node quantity including a quantity of the at least two blockchain nodes executing the consensus algorithms of different fault tolerance types. The method further includes, when the node quantity satisfies a consensus condition of the first consensus algorithm and does not satisfy a consensus condition of the second consensus algorithm, synchronizing a consensus result of the first consensus algorithm with a blockchain node executing the second consensus algorithm such that the blockchain node executing the second consensus algorithm reaches a consensus.