A cross-chain dynamic gateway cluster system and management method, device and equipment and medium

Abstract

The application provides a blockchain cross-chain dynamic gateway cluster system and a management method, which covers node registration, cross-chain transaction processing, node dynamic adjustment and exception handling, and ensures efficient and safe operation of the system. The system includes four modules. The gateway monitoring module is responsible for the registration of each blockchain node; the threshold management module sets the threshold value and the key fragment allocation scheme; the cross-chain consensus module synchronizes the transaction status to ensure consistency and tamper resistance; the cluster management module regularly monitors the online status and performance of the gateway nodes. When the system starts, the nodes are registered after verification, and the weight and key fragments are allocated to form the initial gateway cluster. When a user initiates a cross-chain transaction, the gateway monitoring module verifies the request, the threshold management module selects the gateway nodes that meet the conditions, completes asset locking and unlocking, and the cross-chain consensus module synchronizes the transaction status. The system regularly monitors the node performance, automatically adjusts the weight and cluster size, removes low-performance or malicious nodes, and ensures transaction consistency and efficient operation of the system.

Description

Technical Field

[0001] This invention relates to the field of blockchain technology, and in particular to a dynamic gateway cluster system and management method for cross-chain blockchain applications. Background Technology

[0002] Cross-chain technology aims to connect homogeneous or heterogeneous blockchains, enabling interaction between different chains. It serves as an important means to open up information channels between different blockchain systems, achieve information sharing between blockchains, maximize the integration and utilization of blockchain resources, and increase the scalability of blockchain technology. It is also a key technology for further promoting the construction of the blockchain system ecosystem, accelerating the implementation of more applications, and promoting the development of the digital economy.

[0003] However, existing cross-chain technologies, especially those based on cross-chain gateways, still have some shortcomings. First, the traditional single-gateway architecture has a significant single point of failure risk; if the gateway fails or is attacked, the entire cross-chain transaction will be interrupted, severely impacting system stability and transaction security. Second, cross-chain gateways typically rely on fixed gateway nodes when processing cross-chain transactions. This fixed configuration results in poor system scalability, making it difficult to adapt to different business needs or network changes. Furthermore, existing cross-chain gateways rely on relatively simple multi-signature mechanisms for security, which are insufficient to effectively prevent malicious behavior by individual gateway nodes, especially in situations involving concentrated power or malicious node actions, posing potential security vulnerabilities. Therefore, a more flexible, scalable, and secure cross-chain solution is urgently needed to address these issues. The dynamic gateway cluster system proposed in this invention, through clustering and weighting mechanisms, can improve the security, flexibility, and stability of cross-chain transactions, meeting the needs of future cross-chain technology development. Summary of the Invention

[0004] To address the aforementioned issues, the purpose of this invention is to propose a dynamic gateway cluster system and management method, effectively improving the elasticity, scalability, and security of cross-chain gateways. Elasticity refers to the system's ability to flexibly adjust the number and weight of gateway nodes based on network conditions and load requirements, ensuring stable operation even under high load or abnormal conditions. Scalability means that the system can dynamically expand the size of the gateway cluster as the number of participating blockchains and transaction demands increase, guaranteeing cross-chain transaction processing capacity. Security is reflected in the system's use of a weighted threshold mechanism to prevent malicious actions by a single node, ensuring the secure execution of cross-chain transactions. Even if some nodes fail or are attacked, the system can still operate normally and maintain data consistency and integrity.

[0005] To achieve the above objectives, the present invention adopts the following technical solution:

[0006] A dynamic gateway cluster system for cross-chain blockchain is provided, comprising:

[0007] The gateway monitoring module manages the registration and performance monitoring of gateway nodes, tracking their online status and operational conditions in real time. This module is responsible for receiving and validating transaction requests, broadcasting valid requests to the relevant gateway nodes on the target blockchain, and recording cross-chain transaction details in a log file, providing data credentials for threshold management.

[0008] The threshold management module dynamically adjusts the weights of gateway nodes, recalculating threshold values ​​based on the nodes' historical performance and system status. This module implements a threshold-based secret sharing mechanism, securely allocating critical data such as cross-chain transaction keys to qualified gateway nodes according to their weights, ensuring the secure execution of cross-chain transactions.

[0009] The cross-chain consensus module ensures the state synchronization of cross-chain transactions across different blockchains and confirms the execution results of cross-chain transactions through a distributed consensus algorithm. This module is responsible for coordinating the locking and unlocking operations of transactions to ensure eventual consistency and data integrity.

[0010] The cluster management module is used to dynamically manage the size of the gateway cluster. This module is responsible for adding and removing gateway nodes, reallocating threshold values ​​and key fragments, ensuring the resilience of the gateway cluster and the high availability of the system.

[0011] A method for managing dynamic gateway clusters for cross-chain blockchains is provided, including:

[0012] Upon system startup, nodes in each blockchain network register through the gateway monitoring module, and their performance and historical records are verified and recorded. Successfully registered nodes are assigned initial weights, with threshold values ​​and key fragment allocation schemes set by the threshold management module. The cluster management module configures the initial gateway cluster based on the number and performance of nodes, ensuring cluster security and operational stability. The system also activates the cross-chain consensus module for initial configuration of transaction consensus and state synchronization, completing the overall initialization of the cross-chain environment.

[0013] When a user initiates a cross-chain transaction on a blockchain, the gateway monitoring module receives the request, verifies its legitimacy, and instructs the gateway cluster of this blockchain to broadcast the request to the gateway clusters of other relevant blockchains. During transaction processing, the threshold management module selects gateway nodes whose weights meet the threshold requirements and uses key fragments to lock and unlock assets. The cross-chain consensus module synchronizes the transaction state across blockchains to ensure the consistency and immutability of transaction execution. Successfully executed transaction records are stored in the system log for subsequent querying and traceability.

[0014] During operation, the cluster management module periodically checks the online status and performance of gateway nodes. When a new node requests to join or the performance of an existing node deteriorates, the system automatically adjusts the node's weight and the cluster size. New nodes are verified by the gateway monitoring module; once verified, the threshold management module incorporates them into the existing gateway cluster, assigning them key fragments and weight values. Poorly performing nodes are removed from the cluster when their weight falls below a threshold, thus maintaining system stability and efficient operation.

[0015] If an error occurs during the execution of a cross-chain transaction, the cross-chain consensus module will coordinate with relevant gateway nodes to roll back the transaction and restore the assets to their initial state. The system records detailed information about transaction failures through the gateway monitoring module and notifies relevant nodes to investigate the problem. If the system detects multiple failures or malicious behavior by a node, the threshold management module will reduce its weight and remove the node from the gateway cluster through the cluster management module, reallocating key fragments and adjusting threshold values ​​to ensure the normal operation of subsequent transactions.

[0016] The present invention has the following advantages due to the adoption of the above technical solutions:

[0017] 1. This invention supports cross-chain transactions through a gateway cluster, avoiding the situation where cross-chain transaction requests are only responded to by a single gateway, ensuring efficient response to cross-chain transaction requests, solving the single point of failure problem of cross-chain gateways, and guaranteeing the success rate of cross-chain transactions.

[0018] 2. This invention uses a weighted threshold gateway cluster to process critical data in cross-chain transactions, preventing malicious behavior by any single gateway during the execution of cross-chain transactions and ensuring the security of cross-chain transaction execution; at the same time, the introduction of gateway weights makes cross-chain transaction processing more flexible, without having to completely rely on gateways that meet the threshold requirements, thus providing greater flexibility.

[0019] 3. This invention supports dynamic gateway clusters, providing liquidity to the gateway clusters. Under the premise of meeting the secret analysis threshold, gateway nodes in the network management cluster are allowed to dynamically enter or exit, while still satisfying the security of cross-chain transactions.

[0020] In summary, this invention can be widely applied in the field of blockchain cross-chain technology. Attached Figure Description

[0021] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Throughout the drawings, the same reference numerals denote the same parts. In the drawings:

[0022] Figure 1 This is a flowchart illustrating step 1) of the method provided in Embodiment 2 of the present invention;

[0023] Figure 2 This is a flowchart illustrating step 2) of the method provided in Embodiment 2 of the present invention;

[0024] Figure 3 This is a flowchart illustrating step 3) of the method provided in Embodiment 2 of the present invention;

[0025] Figure 4 This is a flowchart of step 4) of the method provided in Embodiment 2 of the present invention. Detailed Implementation

[0026] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the invention and to fully convey the scope of the invention to those skilled in the art.

[0027] It should be understood that the terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “described” as used herein may also include the plural forms. The terms “comprising,” “including,” “containing,” and “having” are inclusive and therefore indicate the presence of the stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not construed as requiring them to be performed in a particular order described or illustrated unless the order of performance is explicitly indicated. It should also be understood that additional or alternative steps may be used.

[0028] The dynamic gateway cluster system and management method for cross-chain blockchain provided in this invention supports cross-chain blockchain transactions through gateway clusters, processes key data in cross-chain transactions through weighted threshold gateway clusters, supports dynamic gateway clusters and provides liquidity for gateway clusters, effectively improving the elasticity, scalability and security of cross-chain gateways.

[0029] Example 1

[0030] This embodiment provides a dynamic gateway cluster system for cross-chain blockchain applications, including:

[0031] The gateway monitoring module manages the registration, health monitoring, and initial transaction processing of blockchain cross-chain gateway nodes, ensuring the overall stability of the system. In node management, the gateway monitoring module is responsible for registering new nodes, verifying their performance, and maintaining node status. Regarding cross-chain transaction processing, the gateway monitoring module receives cross-chain requests, verifies their legitimacy, and distributes them to the gateway nodes of the target blockchain. Furthermore, the gateway monitoring module collaborates with other modules to synchronize the real-time status and performance data of gateway nodes to the system, supporting subsequent threshold management and cluster management operations.

[0032] The threshold management module dynamically adjusts the weights of gateway nodes, manages threshold settings and key allocation for cross-chain transactions, and ensures the system remains secure and reliable even when nodes change dynamically. Regarding weight management, the module dynamically adjusts the weights of gateway nodes based on their historical performance (such as transaction success rate and response time), ensuring that high-performing nodes receive more transaction processing opportunities. For threshold control, the module generates and distributes key fragments using a threshold secret sharing algorithm, allowing only nodes with sufficient weight to participate in transaction signing and asset unlocking operations. This module works in conjunction with the cross-chain consensus module to ensure dynamic updates to weight adjustments and key allocation strategies during transaction execution.

[0033] The cross-chain consensus module is used to achieve consensus and state synchronization for cross-chain transactions across multiple blockchains, ensuring that transactions reach a consistent result on all relevant chains. The cross-chain consensus module coordinates the execution of transactions between multiple blockchains through distributed consensus algorithms (such as PBFT, RAFT, etc.), ensuring consistent confirmation of asset locking and unlocking operations.

[0034] The cluster management module manages the size and topology of the gateway cluster, dynamically adjusts the addition and removal of gateway nodes, and maintains the system's resilience and scalability. Regarding cluster expansion, the module allows high-performance new nodes to join the gateway cluster and reallocates key fragments and threshold values. For cluster contraction, the module removes nodes that have consistently performed poorly or whose weights are below the threshold, based on their weight, response time, and operational status. Simultaneously, the module automatically updates the cluster configuration to ensure stable system operation even with node changes. The cluster management module works closely with the gateway monitoring module and the threshold management module to ensure dynamic adaptability of node management and system operation.

[0035] Example 2

[0036] This embodiment provides a method for managing dynamic gateway clusters for cross-chain blockchains, including the following steps:

[0037] 1) System initialization: Accepting node registrations from the blockchain to become gateway nodes and establishing a cluster, specifically:

[0038] 1.1) Node registration and gateway configuration

[0039] 1.1.1) Each node administrator in the blockchain network accesses the node registration interface of the gateway monitoring module, submits a gateway node registration request, and provides their own performance and identity information, such as node ID, computing power, network bandwidth, node public key, etc.

[0040] 1.1.2) The gateway monitoring module checks the completeness and legality of the node registration request. If the information is incomplete or the format is incorrect, the request is rejected and the node administrator is notified.

[0041] For example, a node in a blockchain network submits a registration request but lacks public key information. The system automatically rejects the request and informs the node that registration has failed.

[0042] 1.1.3) For a valid registration request, the gateway monitoring module generates a unique node identifier and assigns an initial weight to the node. The gateway monitoring module writes the node information into the gateway registration database and returns a successful registration confirmation to the node administrator, including the node's unique identifier and initial weight information.

[0043] 1.2) Cluster establishment and threshold setting

[0044] 1.2.1) The gateway monitoring module transmits the registered node information to the threshold management module, synchronizing the gateway node's identity and initial weight data. The threshold management module automatically sets the threshold value based on the number and weight distribution of currently registered nodes. The threshold management module uses a threshold secret sharing algorithm to shard the core keys required for cross-chain transactions. Different numbers of key shards are allocated according to the node's weight; nodes with higher weights hold more key fragments, improving transaction processing capabilities and security.

[0045] For example, the threshold management module can use the Shamir secret sharing algorithm to shard the key. Assuming the total weight is 10, the threshold value is set to at least 6 weights to pass a transaction. Then, the combination of two nodes with weights of 4 and 3 satisfies the threshold value.

[0046] 1.2.2) The threshold management module securely distributes key fragments to gateway nodes and records the node allocation. The threshold management module saves the threshold value and key fragment allocation results to the state storage of the blockchain network for use in subsequent transaction processing.

[0047] 1.3) Gateway cluster information synchronization

[0048] 1.3.1) After completing the threshold key allocation, the threshold management module needs to synchronize the node registration and key allocation information with the cluster management module, including the list of successfully registered node public keys, the initial weight value of each node, the threshold value setting, and the key sharding information allocated to each node. The cluster management module only stores the sharding identifier; the key itself is encrypted and stored at the node end.

[0049] 1.3.2) The cluster management module completes the remaining cluster organization work, including optimizing the communication paths between nodes, configuring point-to-point encrypted channels to establish a communication topology, and performing a full node status check on the entire network to ensure that the weight distribution and key fragment storage information between nodes are correct, and finally completing the gateway cluster initialization.

[0050] 2) When a user initiates a cross-chain transaction on the blockchain, the gateway monitoring module receives the request, verifies its legitimacy, and requests the gateway cluster of this blockchain to broadcast the request to the gateway clusters of other relevant blockchains, specifically:

[0051] 2.1) User initiates cross-chain request and selects gateway node

[0052] 2.1.1) A user initiates a cross-chain transaction request on the source blockchain, including information such as user address, cross-chain request ID, source chain ID, target chain ID, cross-chain contract address, timestamp, operation type, and operation parameters. The gateway monitoring module receives the request and checks whether its basic information is complete. If the request information is missing or the format is incorrect, the request is marked as failed, and a failure notification is returned to the user.

[0053] 2.1.2) The gateway monitoring module queries the cross-chain management service interface to confirm whether the target blockchain has registered a valid gateway node and supports cross-chain services. If the target blockchain has a valid cross-chain service, the gateway monitoring module forwards the cross-chain request to the gateway node of the source blockchain, initiating the node selection process.

[0054] 2.1.3) The gateway monitoring module broadcasts cross-chain requests to all nodes in the gateway cluster of the source blockchain.

[0055] 2.1.4) After receiving a cross-chain transaction request, the nodes in the gateway cluster submit a participation application to the threshold management module.

[0056] 2.1.5) The threshold management module filters nodes that meet the criteria based on the current gateway node's weight and historical performance, ensuring that the total weight reaches a preset threshold. When multiple gateway combinations meet the weight criteria, the threshold management module will randomly select a group of gateway nodes. The selected gateway nodes will further verify the cross-chain request content to ensure the legitimacy of the identity and request information. If the current gateway cluster cannot meet the weight requirements, or if the gateway's identity information, asset data, or operation parameters are incorrect, the node will reject the request.

[0057] For example, if the threshold requires the total weight to be at least 10, the system can select the first two nodes from the nodes with weights of 6, 5 and 4 respectively, whose total weight is 11, thus meeting the threshold requirement.

[0058] 2.2) Cross-chain transaction execution

[0059] 2.2.1) In step 2.1.5), the gateway node executes the necessary operations in the cross-chain transaction as required based on the received cross-chain request. Each node is responsible for the specific tasks in the cross-chain transaction, such as data processing, transaction confirmation, and state synchronization.

[0060] 2.2.2) The selected node successfully completes the operations required by the cross-chain transaction request and submits the results to the cross-chain consensus module. The cross-chain consensus module verifies the completion of the transaction to ensure that all steps have been executed correctly.

[0061] For example, after node A and node B successfully sign, they submit the result to the cross-chain consensus module, indicating that the transaction has been completed and the state has been synchronized to the target blockchain.

[0062] 2.2.3) The cross-chain consensus module confirms the execution status of transactions between the source and target blockchains. The final state of the transaction is synchronized across all blockchains and recorded in the transaction log. If confirmation fails, the transaction will be rolled back and marked as failed in the gateway monitoring module.

[0063] 2.2.4) The threshold management module adjusts the weights of gateway nodes based on their performance in cross-chain transactions: nodes that successfully complete cross-chain transactions will have their weights increased, ensuring they are selected in more future transactions. Nodes selected in step 2.1.5) but failing to execute cross-chain transactions will have their weights reduced, decreasing their future opportunities to participate.

[0064] For example, the weight values ​​are adjusted according to the number of successful cross-chain transactions. If node A successfully completes a cross-chain transaction, its weight increases from 5 to 6, while if node B fails to execute a cross-chain transaction, its weight decreases from 6 to 5.

[0065] 3) During operation, the cluster management module periodically checks the online status and performance of the gateway nodes. When a new node requests to join or the performance of an existing node deteriorates, the system automatically adjusts the node weights and cluster size, specifically as follows:

[0066] 3.1) Gateway node health check

[0067] 3.1.1) The cluster management module periodically checks the status of the gateway nodes, including indicators such as online status, network connection quality, and response speed. Specifically, the cluster management module confirms whether the gateway nodes are online normally through heartbeat signals at fixed time intervals.

[0068] For example, suppose a gateway node on the blockchain has not sent any heartbeat signals in the past 24 hours. The cluster management module marks the node as "offline" and notifies the relevant modules to take further action.

[0069] 3.1.2) The threshold management module dynamically adjusts the node weight based on the health status of the gateway node and the success rate of cross-chain transactions. Successfully completed transactions increase the node's weight, while failed or inactive nodes decrease their weight.

[0070] Specifically, the system periodically calculates a node's performance in cross-chain transactions, including the number of participations, transaction success rate, and response time. The weight adjustment results are stored in the system log, and changes in node weights are automatically synchronized to all gateway nodes. Nodes that reach the lower weight limit will be marked as "invalid" and will no longer be able to participate in cross-chain transactions.

[0071] 3.1.3) The threshold management module periodically reassigns threshold keys based on changes in node weights to ensure system security and resistance to node failures or malicious behavior. The reassignment period can be determined by developers or administrators during system initialization.

[0072] Specifically, key shares are regenerated using a secret-sharing-based multinomial partitioning algorithm and securely distributed to nodes that meet the weight threshold.

[0073] 3.2) Adding new nodes

[0074] 3.2.1) New nodes submit node information, including node ID, computing power, network bandwidth, and other key information, through the gateway monitoring module. The system verifies the node's blockchain account and digital signature to ensure the authenticity and legitimacy of the registered node.

[0075] 3.2.2) Node performance testing and evaluation: Nodes undergo standardized performance testing, such as transaction response time and data throughput.

[0076] 3.2.3) The threshold management module assigns initial weights and key fragments to new nodes based on performance test results and the current cluster status.

[0077] For example, a node applies to join the gateway cluster. After passing authentication and performance testing, its weight is set to 2, making it a gateway node with full cross-chain transaction processing capabilities.

[0078] 3.3) Node Exit

[0079] 3.3.1) A node submits an exit request, completes authentication through the gateway monitoring module, and exits securely after ensuring there are no incomplete transactions. Alternatively, if the system detects that a node frequently times out, has a high transaction failure rate, or loses connection, it is marked as a failed node.

[0080] 3.3.2) The weight of the failed node is cleared to zero, and the cluster management module removes it from the cluster.

[0081] 4) If an error occurs during the execution of a cross-chain transaction, the cross-chain consensus module will coordinate with the relevant gateway nodes to roll back the transaction and restore the assets to their initial state, specifically as follows:

[0082] 4.1) Cross-chain transaction failure detection and rollback

[0083] 4.1.1) The gateway monitoring module listens for abnormal events during the execution of cross-chain transactions, including transaction locking or unlocking failures, network failures, etc., and records detailed information about transaction failures in real time. When the cross-chain consensus module detects inconsistencies in the cross-chain transaction state, it immediately initiates a transaction rollback request to roll back the transaction to the earliest consistent state, preventing data inconsistencies from spreading to multiple blockchains.

[0084] 4.1.2) The gateway monitoring module notifies all relevant gateway nodes to stop transaction execution, records the reason for failure and rollback information, and marks the transaction status as failed.

[0085] 4.1.3) The gateway monitoring module sends transaction failure information to the threshold management module, which reduces the weight of the failed node, decreasing its chances of participating in the future. When the node's weight drops to zero, the cluster management module removes it from the cluster.

[0086] 4.2) Malicious Node Detection and Isolation

[0087] 4.2.1) The gateway monitoring module analyzes abnormal behaviors through transaction logs, such as multiple unresponsive gateway nodes, frequent signature rejections, and malicious submission of error messages, and generates behavior reports. The threshold management module calculates the weight changes of relevant nodes based on the behavior reports, rapidly reduces the weight of nodes exhibiting malicious behavior, and, if necessary, reduces the weight to zero.

[0088] 4.2.2) The cluster management module blacklists malicious nodes, isolates and removes them from the gateway cluster, and simultaneously restructures the cluster to prevent single points of failure and cross-chain transaction interruptions. It also marks malicious nodes as untrusted, refusing their participation in future cross-chain transactions to ensure the security of cross-chain transaction execution.

[0089] For example, during monitoring, gateway node B refused to sign cross-chain transactions three times in a row, severely impacting the timeliness of cross-chain transactions. The cluster management module blacklisted node B, isolated it, and removed it from the gateway cluster; the threshold management module adjusted node B's weight to zero and marked it as an "untrusted node," ensuring that it would no longer participate in future cross-chain transaction signing and consensus processes, fundamentally eliminating any potential security threats it might pose.

Claims

1. A dynamic gateway cluster system for cross-chain blockchain applications, characterized in that, include: The gateway monitoring module manages the registration and performance monitoring of gateway nodes, tracking their online status and operational conditions in real time. This module is responsible for receiving and validating transaction requests, broadcasting valid requests to the relevant gateway nodes on the target blockchain, and recording cross-chain transaction details in a log file, providing data credentials for threshold management. The threshold management module dynamically adjusts the weights of gateway nodes, recalculating threshold values ​​based on the nodes' historical performance and system status. This module implements a threshold-based secret sharing mechanism, securely allocating critical data such as cross-chain transaction keys to qualified gateway nodes according to their weights, ensuring the secure execution of cross-chain transactions. The cross-chain consensus module ensures the state synchronization of cross-chain transactions across different blockchains and confirms the execution results of cross-chain transactions through a distributed consensus algorithm. This module is responsible for coordinating the locking and unlocking operations of transactions to ensure eventual consistency and data integrity. The cluster management module is used to dynamically manage the size of the gateway cluster. This module is responsible for adding and removing gateway nodes, reallocating threshold values ​​and key fragments, ensuring the resilience of the gateway cluster and the high availability of the system.

2. A dynamic gateway cluster management method for cross-chain blockchain, characterized in that, include: The system initializes by accepting node registrations from the blockchain to become gateway nodes and establishing a cluster. When a user of the system initiates a cross-chain transaction on the blockchain, the gateway monitoring module receives the request, verifies its legitimacy, and requests the gateway cluster of this blockchain to broadcast the request to the gateway clusters of other related blockchains. During system operation, the cluster management module periodically checks the online status and performance of the gateway nodes. When a new node requests to join or the performance of an existing node deteriorates, the system automatically adjusts the node weights and cluster size. If an error occurs during the execution of a cross-chain transaction in the system, the cross-chain consensus module will coordinate with the relevant gateway nodes to roll back the transaction and restore the assets to their initial state.

3. The method according to claim 2, characterized in that, The system initialization, which accepts node registrations from the blockchain to become gateway nodes and establishes a cluster, includes: The gateway monitoring module accepts gateway node registration requests submitted by node administrators in the blockchain network through the node registration interface. The registration request includes node performance and identity information. The gateway monitoring module checks the completeness and legality of the registration request, rejects requests that do not meet the requirements, and notifies the node administrator. For legal registration requests, the gateway monitoring module generates a unique node identifier, assigns an initial weight, writes the node information into the gateway registration database, and returns registration confirmation information. The gateway monitoring module synchronizes the registered node information to the threshold management module. The threshold management module sets a threshold value based on the number and weight distribution of registered nodes, and uses a threshold secret sharing algorithm to shard the core key. The key shards are then distributed to the gateway nodes according to the node weights, and the threshold value and distribution results are recorded in the state storage of the blockchain network. After the threshold management module completes the key sharding allocation, it synchronizes the node registration status and key allocation status to the cluster management module. The cluster management module stores the sharding identifier and completes the organization of the gateway cluster, including optimizing communication paths, configuring encrypted channels, checking node status and weight distribution, and finally completing the gateway cluster initialization.

4. The method according to claim 2, characterized in that, When a user initiates a cross-chain transaction on the blockchain, the gateway monitoring module receives the request, verifies its legitimacy, and requests the gateway cluster of this blockchain to broadcast the request to the gateway clusters of other related blockchains, including: The gateway monitoring module receives cross-chain transaction requests initiated by users on the source blockchain. The request includes the user address, cross-chain request ID, source chain ID, target chain ID, cross-chain contract address, timestamp, operation type, and operation parameters. The gateway monitoring module checks the completeness of the request information. If the information is missing or the format is incorrect, the request is marked as failed and a failure notification is returned to the user. The gateway monitoring module queries the cross-chain management service interface to confirm the status of the gateway nodes and cross-chain service support of the target blockchain. If the target blockchain supports cross-chain services, the gateway monitoring module forwards the cross-chain request to the gateway cluster of the source blockchain and broadcasts the request to all gateway nodes within the cluster. After receiving the request, the gateway node submits a participation application to the threshold management module. The threshold management module selects a combination of nodes that meet preset weight conditions based on the weight and historical performance of the gateway nodes. If the total weight of the nodes in the gateway cluster reaches the threshold value, a group of gateway nodes is randomly selected, and the identity information and request content of the cross-chain request are verified. Requests that fail verification are rejected. The selected gateway node performs data processing, transaction confirmation, and state synchronization operations according to the operation requirements of the cross-chain request, and submits the execution results to the cross-chain consensus module. The cross-chain consensus module verifies the execution of the transaction, ensures that each step is completed correctly, and synchronizes the transaction state between the source blockchain and the target blockchain. If the transaction confirmation fails, the cross-chain consensus module triggers a rollback operation and marks the request as failed in the gateway monitoring module. The threshold management module adjusts the weight value of the gateway node based on its performance in cross-chain transactions; the weight of the node that successfully completes the transaction is increased, and the weight of the node that fails to complete the transaction is decreased. The weight change information is recorded in the gateway management database as the basis for subsequent transaction node selection.

5. The method according to claim 2, characterized in that, During system operation, the cluster management module periodically checks the online status and performance of the gateway nodes. When a new node requests to join or the performance of an existing node deteriorates, the system automatically adjusts the node weights and cluster size, including: The cluster management module periodically checks the online status and performance indicators of the gateway nodes, including online status, network connection quality, and response speed. The cluster management module confirms the status of the gateway nodes through heartbeat signals at fixed time intervals. If a node is detected to be offline, it is marked as "offline" and the relevant modules are notified to take further action. The threshold management module dynamically adjusts the weights of nodes based on their online status and the performance of cross-chain transactions. Nodes that successfully complete cross-chain transactions have their weights increased, while those that do not respond have their weights decreased. If a node's weight falls below a preset lower limit, the threshold management module marks it as an "invalid" node, which will no longer participate in cross-chain transactions. The threshold management module periodically reassigns threshold keys based on changes in node weights, generating new key fragments using a secret-sharing-based multinomial segmentation algorithm. These key fragments are then securely distributed to nodes that meet the weight thresholds to ensure system security and fault tolerance for invalid or malicious nodes. The new node submits a registration application through the gateway monitoring module. The application information includes performance indicators such as node ID, computing power, and network bandwidth. The gateway monitoring module verifies the node's blockchain account and digital signature to confirm the node's authenticity and legitimacy. Based on the new node's performance test results and the current status of the gateway cluster, the threshold management module assigns an initial weight and threshold key fragment to the new node. After completing registration, the new node has the ability to participate in cross-chain transactions. When a node exits, it can proactively submit an exit request. The gateway monitoring module verifies its identity and confirms that it has no outstanding transactions before allowing its exit. If the system detects frequent timeouts, high transaction failure rates, or loss of network connectivity, the cluster management module marks the node as a "failed" node and resets its weight to zero. The cluster management module removes the failed node from the gateway cluster, and the threshold management module synchronously updates the node list and threshold key allocation scheme to ensure system security and the normal execution of cross-chain transactions.

6. The method according to claim 2, characterized in that, If an error occurs during the execution of a cross-chain transaction in the system, the cross-chain consensus module will coordinate with the relevant gateway nodes to roll back the transaction and restore the assets to their initial state. When the cross-chain consensus module detects inconsistencies in the cross-chain transaction state, it initiates a transaction rollback request to restore the transaction to its initial consistent state, preventing data inconsistencies from spreading to multiple blockchains. The gateway monitoring module listens for abnormal events in cross-chain transactions in real time, including transaction locking or unlocking failures, network failures, etc., records detailed failure information, and notifies all relevant gateway nodes to stop transaction execution. The gateway nodes restore locked assets according to the rollback instruction, record the reason for the failure and rollback information, and mark the transaction as failed. The gateway monitoring module sends transaction failure information to the threshold management module. The threshold management module reduces the weight of the relevant nodes based on the failure information, reducing their chances of participating in cross-chain transactions in the future. Nodes whose weight drops below a certain threshold will no longer participate in cross-chain transactions. The gateway monitoring module analyzes abnormal behavior through transaction logs and generates a behavior report. The threshold management module calculates and adjusts the weight of malicious nodes based on the report, quickly reducing their weight, and if necessary, reducing their weight to zero. The cluster management module blacklists malicious nodes and isolates and removes them from the gateway cluster. The cluster management module readjusts the cluster structure to prevent single points of failure or cross-chain transaction interruptions. At the same time, it marks malicious nodes as untrusted and refuses their participation in future cross-chain transactions to ensure the security of cross-chain transactions.

Images