WO2022160901A1

WO2022160901A1 - Blockchain consensus method, consensus node, and electronic device

Info

Publication number: WO2022160901A1
Application number: PCT/CN2021/132998
Authority: WO
Inventors: 杨达一
Original assignee: 蚂蚁区块链科技(上海)有限公司; 支付宝(杭州)信息技术有限公司
Priority date: 2021-01-28
Filing date: 2021-11-25
Publication date: 2022-08-04
Also published as: CN112465515A; CN112465515B

Abstract

Embodiments of the present description provide a blockchain consensus method, a consensus node, and an electronic device. The consensus method comprises: a target consensus node of a blockchain performs a view switching operation, wherein the target consensus node becomes a consensus backup node after performing the view switching operation; the target consensus node directionally sends transactions in a transaction pool of the present node to a consensus master node of the blockchain; the consensus master node of the blockchain performs validity verification on the received transactions, and stores the transaction that passes the verification into a transaction pool of the present node; and the consensus master node initiates a consensus proposal on the basis of transactions in the transaction pool of the present node.

Description

A consensus method, consensus node and electronic device for blockchain

technical field

This document belongs to the field of blockchain technology, and in particular relates to a consensus method, consensus node and electronic equipment of a blockchain.

Background technique

At present, the consensus nodes of the blockchain synchronize all transactions in the transaction pool of this node to other consensus nodes through broadcasting. This broadcast synchronization method will cause transactions to be sent redundantly, resulting in a large waste of bandwidth resources. For a blockchain system with a large number of consensus nodes and huge transaction data, the waste of bandwidth resources will lead to a decrease in consensus computing power, thus affecting the execution efficiency of blockchain business.

In view of this, there is an urgent need for a technical solution that can improve the waste of bandwidth resources caused by synchronous transactions between consensus nodes.

SUMMARY OF THE INVENTION

The purpose of the embodiments of this specification is to provide a consensus method, consensus node and electronic device for a blockchain, so as to improve the waste of bandwidth resources caused by synchronous transactions between consensus nodes.

In order to achieve the above purpose, the embodiments of this specification are implemented as follows: In a first aspect, a consensus method for a blockchain is provided, including: a target consensus node of the blockchain performs a view switching operation, wherein the target consensus node is in the After performing the view switching operation, it becomes the consensus backup node; the target consensus node sends the transactions in the transaction pool of this node to the consensus master node of the blockchain; the consensus master node of the blockchain responds to the received The transaction is verified for legality, and the verified transaction is stored in the transaction pool of this node; the consensus master node initiates a consensus proposal based on the transaction in the transaction pool of this node.

In a second aspect, a consensus method for a blockchain is provided, including: a target consensus node of the blockchain performs a view switching operation, wherein the target consensus node is a consensus backup node after performing the view switching operation; the target consensus node The node sends the transaction in the transaction pool of this node to the consensus master node of the blockchain, so that the consensus master node of the blockchain verifies the validity of the received transaction, and stores the verified transaction in the The transaction pool of this node, so as to initiate a consensus proposal based on the transactions in the transaction pool of this node.

A third aspect provides a blockchain consensus method, comprising: a target consensus node of the blockchain performs a view switching operation, wherein the target consensus node is a consensus master node after performing the view switching operation; the target consensus node The node receives the transaction sent by the consensus backup node of the blockchain and the blockchain client; the target consensus node verifies the validity of the received transaction, and stores the verified transaction in the transaction pool of the node; The target consensus node initiates a consensus proposal based on transactions in the transaction pool of the node.

In a fourth aspect, a consensus node of a blockchain is provided, including: a view switching module, which executes a view switching operation of the consensus node; a sending module, if the view switching operation makes the consensus node serve as a consensus backup node, it will The transaction in the transaction pool of the consensus node is directed to the consensus master node of the blockchain; the receiving module, if the view switching operation makes the consensus node as the consensus master node, then receives the consensus of the blockchain The transaction sent by the backup node and the blockchain client; the synchronization module, if the view switching operation makes the consensus node act as the consensus master node, the validity of the transaction received by the receiving module is verified, and the verification is passed. The transaction is stored in the transaction pool of the consensus node; the consensus module, if the view switching operation makes the consensus node act as the consensus master node, a consensus proposal is initiated based on the transactions in the transaction pool of the consensus node.

In a fifth aspect, an electronic device is provided, comprising: a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program being executed by the processor: View switching operation; if the view switching operation makes the consensus node act as a consensus backup node, the transaction in the transaction pool of the consensus node is sent to the consensus master node of the blockchain; if the view switching operation The operation makes the consensus node act as the consensus master node, and then receives the transaction sent by the consensus backup node of the blockchain and the blockchain client; if the view switching operation makes the consensus node serve as the consensus master node, the The validity of the transaction received by the receiving module is verified, and the verified transaction is stored in the transaction pool of the consensus node; if the view switching operation makes the consensus node act as the consensus master node, based on the consensus Transactions in the node's transaction pool initiate consensus proposals.

In a sixth aspect, a computer-readable storage medium is provided, a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the following steps are implemented: performing a view switching operation of a consensus node; If the view switching operation makes the consensus node act as a consensus backup node, then the transactions in the transaction pool of the consensus node are directed to the consensus master node of the blockchain; if the view switching operation makes the consensus node As the consensus master node, it receives the transaction sent by the consensus backup node of the blockchain and the blockchain client; if the view switching operation makes the consensus node as the consensus master node, the receiving module receives Verify the validity of the transaction, and store the verified transaction into the transaction pool of the consensus node; if the view switching operation makes the consensus node act as the consensus master node, the transaction pool based on the consensus node Transactions initiate consensus proposals.

In the consensus mechanism that distinguishes between master and slave of consensus nodes, only the master node of the blockchain can initiate consensus proposals for transactions. Based on the method of the embodiment of this specification, the consensus backup node of the blockchain only directs synchronous transactions to the consensus master node, which can effectively save bandwidth overhead. Subsequently, if the blockchain changes the consensus master node, the consensus backup node will re-synchronize the transaction with the new consensus master node. In addition, the directional synchronization method can also effectively reduce the redundant transmission of transactions, thereby improving the problem of wasting bandwidth resources, and avoiding the problem of the reduction of consensus computing power in the blockchain system due to excessive bandwidth usage.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present specification or the prior art, the following briefly introduces the accompanying drawings required in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some of the embodiments described in the embodiments of this specification. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

FIG. 1 is a schematic flowchart of a first type of consensus method of a blockchain provided by an embodiment of this specification.

FIG. 2 is a schematic flowchart of a second block chain consensus method provided by an embodiment of the present specification.

FIG. 3 is a schematic structural diagram of a consensus node provided by an embodiment of the present specification.

FIG. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present specification.

Detailed ways

In order to make those skilled in the art better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings in the embodiments of this specification. Obviously, the described The embodiments are only some of the embodiments of the present specification, but not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of this specification.

As mentioned above, the current consensus nodes of the blockchain synchronize all transactions in the transaction pool of this node to other consensus nodes through broadcasting. This broadcast synchronization method will cause transactions to be sent redundantly, resulting in a waste of bandwidth resources.

For example, the transaction pool of consensus node A has transactions 1 and 2, the transaction pool of consensus node B has transactions 2 and 3, and the transaction pool of consensus node C has transaction 4. Without considering the addition of new transactions and the removal of old transactions, after the first round of transaction synchronization, consensus node A broadcasts transactions 1 and 2 to consensus nodes B and C, and consensus node B broadcasts transaction 2 to consensus nodes A and C. , 3, consensus node C broadcasts transaction 4 to consensus nodes A and B. It can be seen that the first round of synchronization results in redundant sending of transaction 2.

After the first round of synchronization, the transaction pools of consensus nodes A, B, and C all store transactions 1, 2, 3, and 4. Therefore, during the second round of synchronization, consensus nodes A, B, and C will redundantly send all transactions 1, 2, 3, and 4 in their respective transaction pools.

It can be seen that under the traditional transaction synchronization method, the larger the scale of consensus nodes and the larger the transaction data, the more serious the waste of bandwidth resources will be, which will lead to a significant decrease in the consensus computing power of the blockchain, which will eventually affect the block chain. Execution efficiency of chain business.

To this end, this paper aims to propose a technical solution that can improve the waste of bandwidth resources caused by synchronous transactions between consensus nodes.

FIG. 1 is a flowchart of the consensus method of the blockchain according to the embodiment of this specification. The method shown in FIG. 1 can be performed by the corresponding hardware below, including the following steps: S102 , the target consensus node of the blockchain performs a view switching operation, wherein the target consensus node is a consensus backup node after performing the view switching operation.

It should be understood that each consensus node of the blockchain corresponds to a view number. The blockchain generally switches views periodically based on certain rules (such as polling), and the corresponding consensus node is to perform the view switching operation. For the target consensus node, if the blockchain switches to the view corresponding to the view number of this node, it will be the consensus master node, otherwise it will be the consensus backup node. Based on this view switching mechanism, each consensus node of the blockchain can have a certain chance to become the consensus master node to initiate consensus proposals (consensus backup nodes cannot initiate consensus proposals), thereby achieving a certain degree of decentralization.

S104, the target consensus node sends the transactions in the transaction pool of the node to the consensus master node of the blockchain.

It should be understood that, in the solution of the embodiment of this specification, the target consensus node sends the transactions in the transaction pool of this node to the consensus master node of the blockchain in a direction, which can mean that the consensus backup node only synchronizes transactions with the consensus master node, that is, any consensus The backup node will not add new transactions to the transaction pool of this node through other consensus backup nodes.

Here, when the target consensus node acts as a consensus backup node, it can obtain new transactions initiated by the blockchain client and add the new transactions to the transaction pool of this node. On this basis, in order to achieve a smaller bandwidth overhead, as a possible but not necessary solution, when the target consensus node acts as a consensus backup node, it will only add transactions initiated by the blockchain client to the transaction pool of this node. , that is, only using bandwidth resources to receive transactions sent directly from the blockchain client. Of course, the target consensus node may also not reject transactions received by other means, but not process them.

S106, the consensus master node of the blockchain verifies the validity of the received transaction, and stores the verified transaction into the transaction pool of this node.

Wherein, the legality verification in this step may refer to the verification that an existing blockchain consensus node needs to perform before adding a transaction to the transaction pool. Since the embodiments of this specification do not involve improvements in this aspect, detailed descriptions are therefore omitted.

S108, the consensus master node initiates a consensus proposal based on the transactions in the transaction pool of this node.

In this step, the consensus master node will select at least a part of the transactions from the transaction pool of this node to initiate a consensus proposal, and the transactions selected to initiate consensus here may include transactions provided by the target node. Among them, the consensus transaction will be generated by each consensus node to save the block, so as to realize the on-chain transaction data.

It should be understood that in the consensus mechanism of the distinction between the master and the standby of the consensus nodes, only the consensus master node of the blockchain can initiate a consensus proposal for a transaction. Based on the method of the embodiment of this specification, the consensus backup node of the blockchain only directs synchronous transactions to the consensus master node, which can effectively save bandwidth overhead. Subsequently, if the blockchain changes the consensus master node, the consensus backup node will re-synchronize the transaction with the new consensus master node. In addition, the directional synchronization method can also effectively reduce the redundant transmission of transactions, thereby improving the problem of wasting bandwidth resources, and avoiding the problem of the reduction of consensus computing power in the blockchain system due to excessive bandwidth usage.

Specifically, in this illustrative embodiment, when the target consensus node is a consensus backup node, the transaction that has been sent to the consensus master node of the blockchain in the transaction pool of the node can be marked. Correspondingly, in the above S104, the target consensus node sends the unmarked transactions in the transaction pool of the node to the consensus master node of the blockchain. That is, if the blockchain does not switch views to replace the consensus master node, the target consensus node (consensus backup node) will not synchronize duplicate transactions with the consensus master node.

In addition, on the basis of the above, after the target consensus node performs the view switching operation, it can also clear the transaction mark in the transaction pool of this node. It should be understood that the new consensus master node will be replaced after the blockchain view is switched. When the target consensus node clears the mark and then executes the above S104, the new consensus master node can send the original message to the old consensus master node but not to the new consensus master node. transaction sent.

The consensus method in the embodiments of the present specification will be described in detail below.

In the consensus method of the embodiment of this specification, the transactions in the target consensus node transaction pool are mainly divided into two categories. One is the transaction of the target consensus node's own node, which is the transaction initiated by the blockchain client directly to the target consensus node after entering the target consensus node; the other is the transaction of other consensus nodes, which is connected by other blockchain clients. Transactions initiated after entering other consensus nodes need to be synchronized through other consensus nodes (consensus backup nodes) after the target node acts as the consensus master node.

Among them, taking the target consensus node initially as the consensus backup node as an example, the process of executing the consensus method is shown in Figure 2, including: the target consensus node sends its own transactions in the transaction pool of this node to the current consensus master of the blockchain node. Here, the target consensus node ignores transactions belonging to other consensus nodes in the node's transaction pool.

At the same time, the target consensus node also receives the new transaction initiated by the blockchain client, and verifies the validity of the new transaction initiated by the blockchain client. If the verification passes, it will be added to the transaction pool of the target consensus node. Here, the target consensus node adds a new transaction initiated by the blockchain client, which is a completely independent process, and is not restricted by other steps and the distinction between master and backup.

After that, the blockchain switch view initiates a master change, and the target consensus node performs the view switch operation.

If the target consensus node is still the consensus backup node after performing the view switching operation, it will send all its own transactions in the transaction pool of this node to the new consensus master node of the blockchain, and the sent transactions include: the previous round of consensus master nodes. The node sends transactions, and, in addition, new transactions are added to the node's transaction pool via the blockchain client.

If the target consensus node is the consensus master node after performing the view switching operation, it will receive the transaction sent by the consensus backup node and the blockchain client, verify the validity of the received transaction, and store the verified transaction in this The node's transaction pool.

After that, if the consensus execution condition is triggered, the target consensus node initiates a consensus proposal based on the transactions in the transaction pool of this node. Here, the transaction initiated by the consensus proposal is not limited to the source, but can be the transaction of the target consensus node and other consensus nodes.

Obviously, based on the directional synchronization method of the embodiment of this specification, the consensus backup node selects whether to send the existing transaction to the new consensus master node according to whether the consensus master node switches, which not only reduces the use of network bandwidth, but also ensures that the transaction is packaged successfully. Rate. A linear increase in the throughput of the blockchain is achieved.

The above is an exemplary introduction to the method of the embodiment of the present invention. Appropriate changes may also be made without departing from the above-mentioned principles herein, and these changes should also be regarded as the protection scope of the embodiments of the present invention.

In addition, it should also be understood that, in the method of the embodiment of this specification, if the target consensus node is a consensus backup node after the view switching operation is performed, the following steps are performed: send the transaction in the transaction pool of this node to the The consensus master node of the blockchain enables the consensus master node of the blockchain to verify the validity of the received transactions, and store the verified transactions into the transaction pool of this node, so as to be based on the transactions in the transaction pool of this node. Initiate a consensus proposal.

Correspondingly, if the target consensus node is the consensus master node after the view switching operation is performed, the following steps are performed: receiving the transaction sent by the consensus backup node of the blockchain and the blockchain client; validating the received transaction. Validation is performed, and the verified transactions are stored in the transaction pool of this node; consensus proposals are initiated based on transactions in the transaction pool of this node.

In addition, corresponding to the consensus method shown in FIG. 1 , an embodiment of the present invention further provides a consensus node of a blockchain. FIG. 3 is a schematic structural diagram of a consensus node 300 according to an embodiment of the present invention, including: a view switching module 310, which performs a view switching operation of the consensus node.

The sending module 320 sends the transactions in the transaction pool of the consensus node to the consensus master node of the blockchain, if the view switching operation makes the consensus node act as a consensus backup node.

The receiving module 330, if the view switching operation makes the consensus node act as the consensus master node, receives the transaction sent by the consensus backup node of the blockchain and the blockchain client.

The synchronization module 340 , if the view switching operation makes the consensus node act as the consensus master node, verify the validity of the transaction received by the receiving module, and store the verified transaction into the transaction pool of the consensus node .

The consensus module 350, if the view switching operation makes the consensus node act as the consensus master node, initiates a consensus proposal based on transactions in the transaction pool of the consensus node.

In the consensus mechanism that distinguishes between master and slave of consensus nodes, only the master node of the blockchain can initiate consensus proposals for transactions. After the consensus node in the embodiment of this specification performs the view switching operation, if it is a consensus backup node, it will only direct synchronous transactions to the consensus master node, thereby effectively saving bandwidth overhead. Subsequently, if the blockchain changes the consensus master node, it will re-synchronize the transaction to the new consensus master node. In addition, the directional synchronization method can also effectively reduce the redundant transmission of transactions, thereby improving the problem of wasting bandwidth resources, and avoiding the problem of the reduction of consensus computing power in the blockchain system due to excessive bandwidth usage.

Optionally, the sending module 320 only sends the transactions directly obtained from the blockchain client in the transaction pool of the consensus node to the consensus master node of the blockchain.

Optionally, when the consensus node acts as a consensus backup node, the sending module 320 marks the transactions that have been sent to the consensus master node of the blockchain in the transaction pool of the consensus node, and sends the transaction of the node to the transaction pool. Unmarked transactions in the pool are directed to the consensus master node of the blockchain.

On the basis of the above, the sending module 320 may also clear the transaction flag in the transaction pool of the consensus node after the view switching module 310 completes the view switching operation.

Optionally, when the consensus node acts as a consensus backup node, the synchronization module 340 only adds transactions initiated by the blockchain client to the transaction pool of the node.

Obviously, the consensus node in the embodiment of this specification can be used as the execution body of the consensus method shown in FIG. 1 above, and thus can realize the functions implemented by the consensus method in FIG. 1 and FIG. 2 . Since the principle is the same, this article will not repeat them.

FIG. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present specification. Referring to FIG. 4 , at the hardware level, the electronic device includes a processor, and optionally an internal bus, a network interface, and a memory. The memory may include memory, such as high-speed random-access memory (Random-Access Memory, RAM), or may also include non-volatile memory (non-volatile memory), such as at least one disk memory. Of course, the electronic equipment may also include hardware required for other services.

The processor, network interface and memory can be connected to each other through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus or an EISA (Extended Component Interconnect) bus. Industry Standard Architecture, extended industry standard structure) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one bidirectional arrow is used in FIG. 4, but it does not mean that there is only one bus or one type of bus.

memory for storing programs. Specifically, the program may include program code, and the program code includes computer operation instructions. The memory may include memory and non-volatile memory and provide instructions and data to the processor.

The processor reads the corresponding computer program from the non-volatile memory into the memory and runs it, forming a consensus device at the logical level, and the consensus device can be a consensus node or a component in a consensus node. The processor executes the program stored in the memory, and is specifically configured to perform the following operations: perform the view switching operation of the consensus node.

If the view switching operation makes the consensus node serve as a consensus backup node, the transactions in the transaction pool of the consensus node are directed to the consensus master node of the blockchain.

If the view switching operation makes the consensus node act as the consensus master node, then receive the transaction sent by the consensus backup node of the blockchain and the blockchain client.

If the view switching operation makes the consensus node act as the consensus master node, the validity of the transaction received by the receiving module is verified, and the verified transaction is stored in the transaction pool of the consensus node.

If the view switching operation makes the consensus node act as the consensus master node, a consensus proposal is initiated based on transactions in the transaction pool of the consensus node.

In the consensus mechanism that distinguishes between master and slave of consensus nodes, only the master node of the blockchain can initiate consensus proposals for transactions. Based on the electronic device of the embodiment of this specification, the consensus backup node of the blockchain only directs synchronous transactions to the consensus master node, which can effectively save bandwidth overhead. Subsequently, if the blockchain changes the consensus master node, the consensus backup node will re-synchronize the transaction with the new consensus master node. In addition, the directional synchronization method can also effectively reduce the redundant transmission of transactions, thereby improving the problem of wasting bandwidth resources, and avoiding the problem of the reduction of consensus computing power in the blockchain system due to excessive bandwidth usage.

The above consensus method disclosed in the embodiment shown in FIG. 1 of this specification may be applied to a processor, or implemented by a processor. A processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above-mentioned method can be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The above-mentioned processor can be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; it can also be a digital signal processor (Digital Signal Processor, DSP), dedicated integrated Circuit (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. Various methods, steps and logic block diagrams disclosed in the embodiments of this specification can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the methods disclosed in conjunction with the embodiments of this specification may be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.

It should be understood that the electronic device in the embodiments of the present specification can implement the functions of the above consensus method in the embodiments shown in FIG. 1 and FIG. 2 . Since the principle is the same, this article will not repeat them.

Of course, in addition to software implementations, the electronic devices in this specification do not exclude other implementations, such as logic devices or the combination of software and hardware, etc. That is to say, the execution subjects of the following processing procedures are not limited to each logic unit. It can also be a hardware or logic device.

In addition, the embodiments of this specification also provide a computer-readable storage medium, where the computer-readable storage medium stores one or more programs, and the one or more programs include instructions, and the instructions, when stored in a portable computer including multiple application programs When executed by the electronic device, the portable electronic device can be made to execute the method of the embodiment shown in FIG. 1 , and is specifically configured to execute the following steps: execute the view switching operation of the consensus node.

As will be appreciated by one skilled in the art, the embodiments of the present specification may be provided as a method, a system or a computer program product. Accordingly, this description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The foregoing describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that in the embodiments and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The above are merely examples of the present specification, and are not intended to limit the present specification. Various modifications and variations of this specification are possible for those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification shall be included within the scope of the claims of this specification. In addition, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of this document.

Claims

A consensus method for blockchain, including:

The target consensus node of the blockchain performs a view switching operation, wherein the target consensus node is a consensus backup node after performing the view switching operation;

The target consensus node sends the transactions in the transaction pool of this node to the consensus master node of the blockchain;

The consensus master node of the blockchain verifies the validity of the received transaction, and stores the verified transaction into the transaction pool of this node;

The consensus master node initiates a consensus proposal based on the transactions in the transaction pool of this node.
The method of claim 1,

The target consensus node sends the transactions in the transaction pool of this node to the consensus master node of the blockchain, including:

The target consensus node only sends the transactions directly obtained from the blockchain client in the transaction pool of this node to the consensus master node of the blockchain.
The method of claim 1, further comprising:

When the target consensus node is a consensus backup node, mark the transaction that has been sent to the consensus master node of the blockchain in the transaction pool of the node;

The target consensus node sends the transactions in the transaction pool of this node to the consensus master node of the blockchain, including:

The target consensus node sends the unmarked transactions in the transaction pool of the node to the consensus master node of the blockchain.
The method of claim 3, further comprising:

After the target consensus node performs the view switching operation, it clears the transaction mark in the transaction pool of the node.
The method of claim 1, further comprising:

When the target consensus node acts as a consensus backup node, only the transactions initiated by the blockchain client are added to the transaction pool of this node.
A consensus method for blockchain, including:

The target consensus node of the blockchain performs a view switching operation, wherein the target consensus node is a consensus backup node after performing the view switching operation;

The target consensus node sends the transaction in the transaction pool of the node to the consensus master node of the blockchain, so that the consensus master node of the blockchain verifies the validity of the received transaction and passes the verification The transactions of this node are stored in the transaction pool of this node, so as to initiate a consensus proposal based on the transactions in the transaction pool of this node.
A consensus method for blockchain, including:

The target consensus node of the blockchain performs a view switching operation, wherein the target consensus node is the consensus master node after performing the view switching operation;

The target consensus node receives the transaction sent by the consensus backup node of the blockchain and the blockchain client;

The target consensus node verifies the validity of the received transaction, and stores the verified transaction into the transaction pool of the node;

The target consensus node initiates a consensus proposal based on transactions in the transaction pool of the node.
A consensus node of a blockchain, including:

The view switching module, which performs the view switching operation of the consensus node;

A sending module, if the view switching operation makes the consensus node serve as a consensus backup node, then directionally sends the transactions in the transaction pool of the consensus node to the consensus master node of the blockchain;

The receiving module, if the view switching operation makes the consensus node act as the consensus master node, then receives the transaction sent by the consensus backup node of the blockchain and the blockchain client;

The synchronization module, if the view switching operation makes the consensus node act as the consensus master node, verify the validity of the transaction received by the receiving module, and store the verified transaction in the transaction pool of the consensus node;

The consensus module, if the view switching operation makes the consensus node act as the consensus master node, initiates a consensus proposal based on transactions in the transaction pool of the consensus node.
An electronic device includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program being executed by the processor:

Perform the view switching operation of the consensus node;

If the view switching operation enables the consensus node to serve as a consensus backup node, the transactions in the transaction pool of the consensus node are directed to the consensus master node of the blockchain;

If the view switching operation makes the consensus node act as the consensus master node, receiving the transaction sent by the consensus backup node of the blockchain and the blockchain client;

If the view switching operation makes the consensus node act as the consensus master node, verify the validity of the transaction received by the receiving module, and store the verified transaction in the transaction pool of the consensus node;

If the view switching operation makes the consensus node act as the consensus master node, a consensus proposal is initiated based on transactions in the transaction pool of the consensus node.
A computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the following steps are implemented:

Perform the view switching operation of the consensus node;

If the view switching operation enables the consensus node to serve as a consensus backup node, the transactions in the transaction pool of the consensus node are directed to the consensus master node of the blockchain;

If the view switching operation makes the consensus node act as the consensus master node, receiving the transaction sent by the consensus backup node of the blockchain and the blockchain client;

If the view switching operation makes the consensus node act as the consensus master node, verify the validity of the transaction received by the receiving module, and store the verified transaction in the transaction pool of the consensus node;

If the view switching operation makes the consensus node act as a consensus master node, a consensus proposal is initiated based on transactions in the consensus node's transaction pool.