Efficient alliance chain method and system based on improved consensus mechanism

Abstract

The invention belongs to the field of alliance chains, and particularly relates to an efficient alliance chain method and system based on an improved consensus mechanism, and the method comprises the following steps: S1, a node is added into a network, the node is added into an alliance chain network, and when the node is added into the alliance chain network, the node passes through an identity verification and node reputation initialization program to ensure that the node meets the security requirement of the network; s2, node reputation evaluation and role allocation: the reputation value of each node in the network is evaluated regularly, different roles are allocated to the nodes based on evaluation, and role allocation is dynamically adjusted according to the reputation of the nodes, the payment and settlement efficiency can be effectively improved, the confirmation delay of large-scale financial transactions is reduced, and the payment and settlement efficiency is improved. And meanwhile, the privacy of sensitive data can be ensured, the leakage of commercial confidentials is avoided, the traceability and compliance of transactions in the supply chain are ensured, and the problems of interoperability and data consistency in cross-chain collaboration in the prior art can be solved.

Description

Technical Field

[0001] The present invention relates to the field of alliance chain technology, and in particular to an efficient alliance chain method and system based on an improved consensus mechanism. Background Art

[0002] As transaction volume increases, existing consensus algorithms (such as PBFT) lose efficiency as node scale expands, making it difficult to meet high throughput and low latency requirements. Furthermore, the multiple participants in a consortium chain have varying requirements for data privacy. Existing mechanisms struggle to balance privacy protection and efficiency while ensuring data consistency. Furthermore, traditional on-chain processing models are inefficient for high-frequency, small-value transactions and real-time data sharing, and exhibit poor interoperability for cross-chain collaboration, failing to meet complex multi-party collaboration and compliance requirements. Therefore, this paper proposes an efficient consortium chain method and system based on an improved consensus mechanism. Summary of the Invention

[0003] The present invention provides an efficient alliance chain method and system based on an improved consensus mechanism, which solves the shortcomings of the existing technology.

[0004] The present invention provides the following technical solutions:

[0005] An efficient alliance chain method based on an improved consensus mechanism includes the following steps:

[0006] S1: Node joins the network. When joining, the node goes through identity authentication and node reputation initialization procedures to ensure that it meets the network's security requirements.

[0007] S2: Node reputation evaluation and role assignment. The reputation value of each node in the network will be evaluated regularly. Based on the evaluation, the node will be assigned different roles. The role assignment is dynamically adjusted according to the node's reputation.

[0008] S3: Transaction Proposal and Verification. When a node (such as a user or contract) initiates a transaction, the transaction information is first broadcast to the nodes in the network. Other nodes will perform preliminary verification on the transaction. Once the transaction passes the verification, the nodes will begin to vote on the transaction to confirm whether it is legal.

[0009] S4: Consensus mechanism selection (dynamic switching). Based on the current network status and potential threats detected, the system will dynamically select the appropriate consensus mechanism.

[0010] S5: Transaction confirmation and off-chain channel processing. After the consensus mechanism is determined, the transaction enters the confirmation stage. At this point, the transaction will be divided into critical transactions and non-critical transactions.

[0011] S6: Privacy protection and data verification, using zero-knowledge proof technology (such as Zero-Knowledge Succinct Non-interractive Argument of Knowledge, zk-SNARK) to verify the legitimacy of transactions;

[0012] S7: Cross-chain data exchange and collaboration, using cross-chain consensus protocols to support data exchange between multiple alliance chains through standardized interfaces and protocols. Transaction data is transmitted through cross-chain bridges and undergoes cross-chain verification and consistency checks to ensure data consistency between different alliance chains.

[0013] S8: The transaction is completed and synchronized with the chain. After passing the consensus and privacy protection steps, the transaction will be recorded on the blockchain. At this point, the system will finally synchronize the transaction information to the main chain and broadcast it to all nodes to ensure that all nodes have the latest ledger data.

[0014] Furthermore, in S1, a node will be assigned an initial reputation value when it first joins, and this value will be dynamically adjusted based on its historical behavior (for example, the node's block generation success rate).

[0015] Furthermore, in S2, the evaluation dimensions include:

[0016] 1) Historical block success rate: The node's past block production records reflect the node's stability;

[0017] 2) Data processing capacity: The node’s ability to process transactions, including its computing resources and bandwidth;

[0018] 3) Behavior transparency: whether the node complies with the protocol specifications and whether there is any malicious behavior.

[0019] Furthermore, the S3 includes:

[0020] 1) Check whether the transaction format is correct;

[0021] 2) Verify that the input and output in the transaction comply with the rules.

[0022] If the transaction passes verification, the node will start voting for the transaction to confirm whether the transaction is legal.

[0023] Furthermore, in said S4:

[0024] 1) Under normal circumstances, the DPoS mechanism is used for consensus to improve efficiency and ensure efficient transaction processing.

[0025] 2) When a malicious node or system anomaly is detected, it automatically switches to the BFT mechanism to ensure system security and tolerate the existence of malicious nodes.

[0026] Furthermore, in said S5:

[0027] 1) Critical transactions, such as fund transfers and large payments, are confirmed on the main chain first.

[0028] 2) Non-critical transactions: such as small payments, real-time data sharing, etc., can be temporarily processed through off-chain channels for consensus, and then synchronized to the main chain when conditions are met.

[0029] Furthermore, S7 involves:

[0030] 1) Data synchronization: Ensure that cross-chain transaction data can be synchronized to the target chain.

[0031] 2) Cross-chain consistency: Confirm the validity and consistency of data through consensus protocols to avoid data conflicts or losses in cross-chain operations.

[0032] The present invention also proposes an efficient alliance chain system based on an improved consensus mechanism, including:

[0033] 1. Node management module:

[0034] 1.1 Node Registration and Authentication: Responsible for registering new nodes, verifying their identities and credibility, and ensuring the legitimacy and credibility of all participating nodes in the network;

[0035] 1.2 Reputation Evaluation and Dynamic Adjustment: Regularly evaluate the reputation of nodes, including their block generation success rate, data processing capabilities, and behavioral transparency, and dynamically adjust their roles and voting weights in the network based on their performance;

[0036] 1.3 Node role allocation: Different node roles (such as consensus nodes, verification nodes, alternative nodes, etc.) are allocated based on reputation values ​​to ensure that nodes with high reputation have priority in participating in consensus.

[0037] 2. Consensus module:

[0038] 2.1 Consensus Mechanism Selection: Select an appropriate consensus mechanism based on the current network status and potential threats. Normally, the DPoS mechanism is used. When malicious nodes or anomalies are detected, the BFT mechanism is automatically switched.

[0039] 2.2 Dynamic Switching and Consensus Execution: The consensus mechanism is dynamically adjusted based on network security to ensure efficient transaction processing and system security. The consensus module coordinates node voting to ensure a balance between security and performance.

[0040] 3. Transaction Verification Module:

[0041] 3.1 Transaction legitimacy verification: After receiving a transaction request, basic legitimacy verification is first performed to check whether the transaction format, signature, input and output, etc. comply with the protocol requirements;

[0042] 3.2 Layered Verification: Different processes are performed based on the priority of transactions (such as critical transactions and non-critical transactions) to ensure that important transactions are given priority.

[0043] 4. Privacy protection module:

[0044] 4.1 Zero-knowledge proof: Using zero-knowledge proof technology, the legitimacy of transactions can be verified without revealing the transaction content, ensuring that transaction privacy is not leaked;

[0045] 4.2 Multi-party computing: In multi-party collaboration scenarios, multi-party computing technology is used to ensure that sensitive data between multiple nodes is not leaked when verifying transactions;

[0046] 4.3 Encryption and Decryption Management: Manage the encryption process of transactions to ensure that transaction data is encrypted and protected during transmission to prevent data leakage.

[0047] 5. Cross-chain collaboration module:

[0048] 5.1 Cross-chain protocol support: Provides a unified protocol interface for data exchange and collaborative operations between different alliance chains to ensure interoperability between different chains;

[0049] 5.2 Cross-chain data consistency: Through the cross-chain consensus mechanism, data consistency between different alliance chains is guaranteed to ensure that cross-chain transactions do not conflict;

[0050] 5.3 Sidechain Collaboration: Use sidechain technology to achieve data synchronization and status confirmation between different chains, and improve the efficiency of cross-chain transactions.

[0051] 6. Transaction confirmation and synchronization module:

[0052] 6.1 Transaction Confirmation: Under the consensus mechanism, this module is responsible for ultimately confirming whether the transaction is valid and recording it in the blockchain. This module works with the consensus module to ensure that all participating nodes reach a consensus on the transaction.

[0053] 6.2 Off-chain channel confirmation: For non-critical transactions, temporary consensus processing is carried out through off-chain channels, and then synchronized to the main chain when the conditions are met, thereby reducing transaction confirmation delays;

[0054] 6.3 Data synchronization: Ensure that the data of all nodes remains consistent after the transaction is completed, and synchronize the transaction results to all nodes.

[0055] It should be understood that the foregoing general description and the following detailed description are exemplary only and are not restrictive of the invention.

[0056] In this invention, a consortium chain, a blockchain jointly maintained by multiple institutions, can improve transaction confirmation speed through the hybrid consensus mechanism proposed in this patent, while also ensuring data privacy and meeting regulatory compliance requirements. In particular, the low-latency consensus optimization and node reputation management proposed in this patent can effectively improve payment and settlement efficiency and reduce confirmation delays in large-scale financial transactions.

[0057] This invention can improve transaction efficiency while ensuring system security and adapt to the needs of different nodes. Privacy protection technologies such as zero-knowledge proof and multi-party computing can ensure the privacy of sensitive data, avoid the disclosure of commercial secrets, and ensure the traceability and compliance of transactions in the supply chain.

[0058] In this invention, the multi-party privacy-preserving consensus extension can achieve secure and efficient data exchange between different medical institutions, ensuring the authenticity and privacy of medical records. The rapid confirmation of the off-chain channel mechanism can also ensure the rapid synchronization and processing of medical data between multiple medical institutions;

[0059] In this invention, the cross-chain consensus protocol can effectively improve the data exchange and consensus capabilities between different alliance chains, and solve the interoperability and data consistency problems of existing technologies in cross-chain collaboration;

[0060] This invention combines a consensus mechanism with a dynamic node role adjustment mechanism, enabling trading platforms to quickly confirm transactions and ensure security, while zero-knowledge proof technology ensures user transaction privacy. Low-latency optimization ensures smooth operation of DeFi applications in high-frequency trading scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Figure 1 A schematic diagram of the process structure of an efficient alliance chain method based on an improved consensus mechanism provided by an embodiment of the present invention;

[0062] Figure 2 A schematic diagram of the architecture of an efficient alliance chain system based on an improved consensus mechanism provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0063] The embodiments of the present invention are described below with reference to the accompanying drawings.

[0064] In the description of the embodiments of the present invention, it should be noted that, unless otherwise clearly specified and limited, the terms, "connection", and "installation" should be understood in a broad sense. For example, "connection" can be a detachable connection or a non-detachable connection; it can be a direct connection or an indirect connection through an intermediate medium. In addition, "communication" can be a direct connection or an indirect connection through an intermediate medium. Here, "fixed" means that the two are connected to each other and the relative position relationship after connection remains unchanged. The directional terms mentioned in the embodiments of the present invention, such as "inside", "outside", "top", "bottom", etc., are only reference to the directions of the accompanying drawings. Therefore, the directional terms used are for better and clearer explanation and understanding of the embodiments of the present invention, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the embodiments of the present invention.

[0065] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in one or more embodiments of the present invention. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0066] Reference Figure 1 , an efficient alliance chain method based on an improved consensus mechanism, including the following steps:

[0067] S1: Node joins the network. When joining, the node goes through identity authentication and node reputation initialization procedures to ensure that it meets the security requirements of the network. This step ensures that each joining node is trustworthy and prepares for subsequent reputation management and role allocation.

[0068] S2: Node Reputation Evaluation and Role Assignment. Each node's reputation in the network is regularly evaluated. Based on these evaluations, the node will be assigned different roles, such as consensus participant, validator, and candidate node. Role assignment can be dynamically adjusted based on the node's reputation. Nodes with higher reputations receive more voting rights and priority in consensus participation. This step ensures a fair consensus process within the consortium chain, reduces the impact of malicious nodes, and improves network stability and security based on the node's historical performance.

[0069] S3: Transaction Proposal and Verification. When a node (such as a user or contract) initiates a transaction, the transaction information is first broadcast to all nodes in the network. Other nodes will then perform preliminary verification on the transaction. Once the transaction passes verification, the nodes will begin voting to confirm whether the transaction is legal. This step ensures that all transactions comply with basic rules before entering the consensus process, preventing invalid transactions from polluting the network.

[0070] S4: Consensus mechanism selection (dynamic switching). Based on the current network status and detected potential threats, the system will dynamically select the appropriate consensus mechanism. This process is automated and the system will make judgments based on the current network conditions to ensure that the consensus process is both efficient and secure. By dynamically switching the consensus mechanism, it is possible to optimize performance while ensuring system security, allowing the system to flexibly respond to different network conditions.

[0071] S5: Transaction confirmation and off-chain channel processing. After the consensus mechanism is established, the transaction enters the confirmation phase. At this point, transactions are divided into critical and non-critical transactions. For non-critical transactions, the use of off-chain channels can significantly reduce transaction confirmation time and improve the overall throughput of the system. Through layered consensus and off-chain channel processing, the system can optimize transaction confirmation time, especially in high-concurrency scenarios, reducing latency and improving throughput.

[0072] S6: Privacy protection and data verification: Zero-knowledge proof technology (such as Zero-Knowledge Succinct Non-interactive Argument of Knowledge, zk-SNARK) is used to verify the legitimacy of transactions without exposing sensitive transaction information. At the same time, MPC technology is used to ensure that private data is not leaked in collaborations involving multiple parties.

[0073] Each participant verifies the validity of transaction data through zero-knowledge proof without having to directly view the transaction content, ensuring the privacy of sensitive data is protected;

[0074] This step ensures the privacy and transparency of transactions during the verification process, balancing privacy protection and consensus verification, and avoiding the risk of data leakage in traditional methods.

[0075] S7: Cross-chain data exchange and collaboration. This uses a cross-chain consensus protocol to support data exchange between multiple consortium chains through standardized interfaces and protocols. Transaction data is transmitted through a cross-chain bridge and undergoes cross-chain verification and consistency checks to ensure data consistency between different consortium chains. This step improves interoperability between consortium chains and supports collaborative operations within a multi-consortium chain ecosystem.

[0076] S8: Transaction completion and on-chain synchronization. After passing consensus and privacy protection steps, the transaction is recorded on the blockchain. At this point, the system will finally synchronize the transaction information to the main chain and broadcast it to all nodes, ensuring that all nodes consistently hold the latest ledger data, completing transaction confirmation and ensuring data consistency across all nodes to prevent data tampering and rollback.

[0077] In the present invention, in S1, a node is assigned an initial reputation value when it first joins, and this value is dynamically adjusted based on its historical behavior (e.g., the node's block generation success rate).

[0078] In particular, in S2, the dimensions of evaluation include:

[0079] 1) Historical block success rate: The node's past block production records reflect the node's stability;

[0080] 2) Data processing capacity: The node’s ability to process transactions, including its computing resources and bandwidth;

[0081] 3) Behavior transparency: whether the node complies with the protocol specifications and whether there is any malicious behavior.

[0082] It should be noted that S3 includes:

[0083] 1) Check whether the transaction format is correct;

[0084] 2) Verify that the input and output in the transaction comply with the rules.

[0085] If the transaction passes verification, the node will start voting for the transaction to confirm whether the transaction is legal.

[0086] In the present invention, in S4:

[0087] 1) Under normal circumstances, the DPoS mechanism is used for consensus to improve efficiency and ensure efficient transaction processing.

[0088] 2) When a malicious node or system anomaly is detected, it automatically switches to the BFT mechanism to ensure system security and tolerate the existence of malicious nodes.

[0089] In particular, in S5:

[0090] 1) Critical transactions, such as fund transfers and large payments, are confirmed on the main chain first.

[0091] 2) Non-critical transactions: such as small payments, real-time data sharing, etc., can be temporarily processed through off-chain channels for consensus, and then synchronized to the main chain when conditions are met.

[0092] It should be noted that S7 involves:

[0093] 1) Data synchronization: Ensure that cross-chain transaction data can be synchronized to the target chain.

[0094] 2) Cross-chain consistency: Confirm the validity and consistency of data through consensus protocols to avoid data conflicts or losses in cross-chain operations.

[0095] Reference Figure 2 The present invention also proposes an efficient alliance chain system based on an improved consensus mechanism, including:

[0096] 1. Node management module:

[0097] 1.1 Node Registration and Authentication: Responsible for registering new nodes, verifying their identities and credibility, and ensuring the legitimacy and credibility of all participating nodes in the network;

[0098] 1.2 Reputation Evaluation and Dynamic Adjustment: Regularly evaluate the reputation of nodes, including their block generation success rate, data processing capabilities, and behavioral transparency, and dynamically adjust their roles and voting weights in the network based on their performance;

[0099] 1.3 Node role allocation: Different node roles (such as consensus nodes, verification nodes, alternative nodes, etc.) are allocated based on reputation values ​​to ensure that nodes with high reputations have priority in participating in consensus;

[0100] The node management module ensures the security and stability of the consortium chain, ensuring that each node's participation meets the network's requirements and dynamically adjusting its participation priority based on its performance. Node reputation assessment and dynamic adjustment mechanisms are key to preventing malicious nodes from affecting system operations and ensuring the long-term effectiveness of the system.

[0101] 2. Consensus module:

[0102] 2.1 Consensus Mechanism Selection: Select an appropriate consensus mechanism based on the current network status and potential threats. Normally, the DPoS mechanism is used. When malicious nodes or anomalies are detected, the BFT mechanism is automatically switched.

[0103] 2.2 Dynamic Switching and Consensus Execution: The consensus mechanism is dynamically adjusted based on network security to ensure efficient transaction processing and system security. The consensus module coordinates node voting to ensure a balance between security and performance.

[0104] Through the consensus module, the system can flexibly select consensus mechanisms based on actual conditions, thereby finding the optimal balance between efficiency and security, ensuring rapid transaction confirmation and secure system operation, ensuring that all participants in the consortium chain reach consensus, and balancing performance and security with high throughput and low latency requirements. The design of dynamically switching consensus mechanisms (such as combining DPoS with BFT) enables the system to optimize performance based on network conditions.

[0105] 3. Transaction Verification Module:

[0106] 3.1 Transaction legitimacy verification: After receiving a transaction request, basic legitimacy verification is first performed to check whether the transaction format, signature, input and output, etc. comply with the protocol requirements;

[0107] 3.2 Tiered Verification: Differentiate the processing based on transaction priority (e.g., critical transactions vs. non-critical transactions) to ensure that important transactions are prioritized.

[0108] This module ensures that only legitimate transactions enter the subsequent consensus process, preventing invalid or malicious transactions from contaminating the network. It also provides support for off-chain channel processing. Before each transaction is submitted to the consortium chain, the transaction verification module is responsible for checking the legitimacy of the transaction, including verifying the transaction format, the authority of the transaction initiator, and the validity of the signature. This step is crucial to ensuring the validity of transactions and the security of the system.

[0109] 4. Privacy protection module:

[0110] 4.1 Zero-knowledge proof: Using zero-knowledge proof technology, the legitimacy of transactions can be verified without revealing the transaction content, ensuring that transaction privacy is not leaked;

[0111] 4.2 Multi-party computing: In multi-party collaboration scenarios, multi-party computing technology is used to ensure that sensitive data between multiple nodes is not leaked when verifying transactions;

[0112] 4.3 Encryption and Decryption Management: Manage the encryption process of transactions to ensure that transaction data is encrypted and protected during transmission to prevent data leakage;

[0113] The privacy protection module protects users' private data through zero-knowledge proof and multi-party computing technology, ensuring that sensitive information will not be exposed even in the case of multi-person collaboration. At the same time, it can verify the legitimacy of transactions and ensure that the security and privacy needs of the alliance chain among multiple participants are met.

[0114] 5. Cross-chain collaboration module:

[0115] 5.1 Cross-chain protocol support: Provides a unified protocol interface for data exchange and collaborative operations between different alliance chains to ensure interoperability between different chains;

[0116] 5.2 Cross-chain data consistency: Through the cross-chain consensus mechanism, data consistency between different alliance chains is guaranteed to ensure that cross-chain transactions do not conflict;

[0117] 5.3 Sidechain Collaboration: Use sidechain technology to achieve data synchronization and status confirmation between different chains, improving the efficiency of cross-chain transactions;

[0118] The cross-chain collaboration module ensures data sharing and collaborative operations between different alliance chains, solves the problem of interoperability between different chains, and improves the flexibility and scalability of the system.

[0119] 6. Transaction confirmation and synchronization module:

[0120] 6.1 Transaction Confirmation: Under the consensus mechanism, this module is responsible for ultimately confirming whether the transaction is valid and recording it in the blockchain. This module works with the consensus module to ensure that all participating nodes reach a consensus on the transaction.

[0121] 6.2 Off-chain channel confirmation: For non-critical transactions, temporary consensus processing is carried out through off-chain channels, and then synchronized to the main chain when the conditions are met, thereby reducing transaction confirmation delays;

[0122] 6.3 Data synchronization: Ensure that the data of all nodes is consistent after the transaction is completed, and synchronize the transaction results to all nodes;

[0123] This module ensures that all transactions are correctly confirmed and reduces latency through off-chain channels, while also ensuring data consistency and blockchain state synchronization across different nodes. The transaction confirmation module ensures that, under the consensus mechanism, the final transaction results are verified and agreed upon by multiple parties. The transaction synchronization module ensures that every confirmed transaction is synchronized to the blockchain in a timely and consistent manner, ensuring consistency of transaction data across all nodes.

[0124] The above are only specific embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. The embodiments of the present invention and the features therein can be combined with each other unless there is a conflict. Therefore, the scope of protection of the present invention shall be based on the scope of protection of the claims.

Claims

1. An efficient alliance chain method based on an improved consensus mechanism, characterized by: The following steps are involved: S1: Node joins the network. When joining, the node goes through identity authentication and node reputation initialization procedures to ensure that it meets the network's security requirements. S2: Node reputation evaluation and role assignment. The reputation value of each node in the network will be evaluated regularly. Based on the evaluation, the node will be assigned different roles. The role assignment is dynamically adjusted according to the node's reputation. S3: Transaction Proposal and Verification. When a node initiates a transaction, the transaction information is first broadcast to all nodes in the network. Other nodes then conduct preliminary verification of the transaction. Once the transaction passes verification, the nodes will begin voting to confirm whether the transaction is legal. S4: Consensus mechanism selection (dynamic switching). Based on the current network status and potential threats detected, the system will dynamically select the appropriate consensus mechanism. S5: Transaction confirmation and off-chain channel processing. After the consensus mechanism is determined, the transaction enters the confirmation stage. At this point, the transaction will be divided into critical transactions and non-critical transactions. S6: Privacy protection and data verification, using zero-knowledge proof technology to verify the legitimacy of transactions; S7: Cross-chain data exchange and collaboration, using cross-chain consensus protocols to support data exchange between multiple alliance chains through standardized interfaces and protocols. Transaction data is transmitted through cross-chain bridges and undergoes cross-chain verification and consistency checks to ensure data consistency between different alliance chains. S8: The transaction is completed and synchronized with the chain. After passing the consensus and privacy protection steps, the transaction will be recorded on the blockchain. At this point, the system will finally synchronize the transaction information to the main chain and broadcast it to all nodes to ensure that all nodes have the latest ledger data.

2. The efficient alliance chain method based on the improved consensus mechanism according to claim 1 is characterized in that: In S1, a node is assigned an initial reputation value when it first joins, and this value is dynamically adjusted based on its historical behavior.

3. The efficient alliance chain method based on the improved consensus mechanism according to claim 1 is characterized in that: In S2, the evaluation dimensions include: 1) Historical block success rate: The node's past block production records reflect the node's stability; 2) Data processing capacity: The node’s ability to process transactions, including its computing resources and bandwidth; 3) Behavior transparency: whether the node complies with the protocol specifications and whether there is any malicious behavior.

4. The efficient alliance chain method based on the improved consensus mechanism according to claim 1 is characterized in that: Said S3 includes: 1) Check whether the transaction format is correct; 2) Verify that the input and output in the transaction comply with the rules. If the transaction passes verification, the node will start voting for the transaction to confirm whether the transaction is legal.

5. The efficient alliance chain method based on the improved consensus mechanism according to claim 1 is characterized in that: In said S4: 1) Under normal circumstances, the DPoS mechanism is used for consensus to improve efficiency and ensure efficient transaction processing. 2) When a malicious node or system anomaly is detected, it automatically switches to the BFT mechanism to ensure system security and tolerate the existence of malicious nodes.

6. The efficient alliance chain method based on the improved consensus mechanism according to claim 1, characterized in that in S5: 1) Critical transactions: Fund transfers or large payments are confirmed on the main chain first. 2) Non-critical transactions: Small payments or real-time data sharing can be processed through temporary consensus through off-chain channels and then synchronized to the main chain when conditions are met.

7. The efficient alliance chain method based on the improved consensus mechanism according to claim 1, characterized in that S7 involves: 1) Data synchronization: Ensure that cross-chain transaction data can be synchronized to the target chain. 2) Cross-chain consistency: Confirm the validity and consistency of data through consensus protocols to avoid data conflicts or losses in cross-chain operations.

8. An efficient consortium chain system based on an improved consensus mechanism, characterized in that the system serves the efficient consortium chain method based on an improved consensus mechanism described in claims 1-7, comprising:

1. Node management module: 1.1 Node Registration and Authentication: Responsible for registering new nodes, verifying their identities and credibility, and ensuring the legitimacy and credibility of all participating nodes in the network; 1.2 Reputation Evaluation and Dynamic Adjustment: Regularly evaluate the reputation of nodes and dynamically adjust their roles and voting weights in the network based on their performance; 1.3 Node role allocation: Different node roles are allocated based on reputation value to ensure that nodes with high reputation have priority in participating in consensus.

2. Consensus module: 2.1 Consensus Mechanism Selection: Select an appropriate consensus mechanism based on the current network status and potential threats. Normally, the DPoS mechanism is used. When malicious nodes or anomalies are detected, the BFT mechanism is automatically switched. 2.2 Dynamic Switching and Consensus Execution: The consensus mechanism is dynamically adjusted according to the network security status to ensure efficient transaction processing and system security. The consensus module coordinates node voting to ensure a balance between security and performance.

3. Transaction Verification Module: 3.1 Transaction legitimacy verification: After receiving a transaction request, basic legitimacy verification is first performed to check whether the transaction format, signature, input and output, etc. comply with the protocol requirements; 3.2 Layered Verification: Different processing is performed based on the priority of the transaction to ensure that important transactions are given priority.

4. Privacy protection module: 4.1 Zero-knowledge proof: Using zero-knowledge proof technology, the legitimacy of transactions can be verified without revealing the transaction content, ensuring that transaction privacy is not leaked; 4.2 Multi-party computing: In multi-party collaboration scenarios, multi-party computing technology is used to ensure that sensitive data between multiple nodes is not leaked when verifying transactions; 4.3 Encryption and Decryption Management: Manage the encryption process of transactions to ensure that transaction data is encrypted and protected during transmission to prevent data leakage.

5. Cross-chain collaboration module: 5.1 Cross-chain protocol support: Provides a unified protocol interface for data exchange and collaborative operations between different alliance chains to ensure interoperability between different chains; 5.2 Cross-chain data consistency: Through the cross-chain consensus mechanism, data consistency between different alliance chains is guaranteed to ensure that cross-chain transactions do not conflict; 5.3 Sidechain Collaboration: Use sidechain technology to achieve data synchronization and status confirmation between different chains, and improve the efficiency of cross-chain transactions.

6. Transaction confirmation and synchronization module: 6.1 Transaction Confirmation: Under the consensus mechanism, this module is responsible for ultimately confirming whether the transaction is valid and recording it in the blockchain. This module works with the consensus module to ensure that all participating nodes reach a consensus on the transaction. 6.2 Off-chain channel confirmation: For non-critical transactions, temporary consensus processing is carried out through off-chain channels, and then synchronized to the main chain when the conditions are met, thereby reducing transaction confirmation delays; 6.3 Data synchronization: Ensure that the data of all nodes remains consistent after the transaction is completed, and synchronize the transaction results to all nodes.

Images