Dynamic Blockchain Node Group Removal via Channel Adjustment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain systems face complexity in removing or deleting members from consortium or private blockchain networks, requiring management personnel to replan or recreate the network, which is inefficient and cumbersome.
Innovation Solution
A method and apparatus for dynamically removing a blockchain node group from a channel by instructing the execution node to stop the target node, updating configuration information, and generating channel adjustment information to record the change in the blockchain, allowing for seamless exit of a tenant from the network without disrupting the entire system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If management personnel manually plan or recreate the blockchain network to remove a member, then the blockchain can be maintained with valid participants, but the process becomes complex and time-consuming
Solution Approach 1:
The system enables automatic member removal through the following mechanism: the member to be removed initiates a withdrawal application, the management node automatically generates removal information based on this application, and the system automatically updates channel configuration and blocks without requiring manual replanning or recreation of the blockchain network by management personnel
Solution Approach 2:
The system performs preliminary actions by pre-establishing withdrawal application templates and automatic removal processing mechanisms. When a member wants to leave, the system already has the framework in place to handle the removal automatically, including pre-defined channels for communication and pre-configured removal workflows that eliminate the need for manual network recreation
2Adaptability or versatility
If a blockchain node group is removed from the channel, then the tenant can exit the network, but the removal process disrupts the blockchain maintenance
Solution Approach 1:
The system implements dynamic member removal by allowing the channel configuration to be updated in real-time. When a member withdraws, the management node dynamically generates removal information, updates the channel's member list, and creates new blocks that reflect the changed configuration. This dynamic approach enables tenants to exit flexibly while maintaining blockchain stability through continuous, coordinated updates across all nodes
Solution Approach 2:
The system establishes feedback mechanisms where the management node receives withdrawal applications, processes them, and sends updated configuration information back to all nodes. The removed member's configuration is fed back to other nodes through the consensus mechanism, ensuring all nodes are synchronized with the updated member list before the removal takes effect, thus maintaining stability during the transition
3Productivity
If the target blockchain node group stops running in the channel, then the node group exits the network, but configuration information updates are required across all nodes
Solution Approach 1:
The system merges multiple operations into a single coordinated process: the management node combines the withdrawal application processing, removal information generation, channel configuration update, and block creation into one integrated workflow. This merging eliminates sequential delays and ensures that configuration updates to all nodes happen simultaneously through the consensus mechanism, significantly improving removal efficiency while minimizing total update time
Solution Approach 2:
The management node performs preliminary actions by pre-processing the withdrawal application and generating the complete removal information package before distributing it to nodes. This includes pre-calculating the updated channel configuration, pre-formulating the removal block, and pre-establishing the communication protocol for notifying all nodes, thereby reducing the actual update time when the removal executes
Data Source
AI summary
This application discloses a method used to remove a target blockchain node group of a first tenant from a channel. In the method, an execution node of a second tenant receives configuration information of the target blockchain node group of the first tenant which is sent by a management node, obtains channel configuration information of the channel from a consensus organization, and generates channel adjustment information based on the channel configuration information and the configuration information of the target blockchain node group. The execution node of the second tenant sends the channel adjustment information to the consensus organization, and the consensus organization generates a block including the channel adjustment information. A blockchain node group of the second tenant obtains the block from the consensus organization, and adds the block to a blockchain stored in the second tenant.