Facilitating practical byzantine fault tolerance blockchain consensus and node synchronization

1. A computer-implemented method for facilitating a consensus process in a blockchain network based on practical Byzantine fault tolerance (PBFT), comprising:

setting, by a first consensus node, a first timer that initiates a view change upon timeout;

setting, by the first consensus node, a second timer that runs out before the first timer;

in response to the second timer running out, sending, to a second consensus node, a request for one or more missing consensus messages, wherein the one or more missing consensus messages were previously transmitted to the first consensus node, but not received by the first consensus node;

receiving, from the second consensus node, the one or more missing consensus messages each digitally signed by a private key of a corresponding consensus node that generates the one or more missing consensus messages; and

determining that a block of transactions is valid, if a quantity of commit messages included in the one or more missing consensus messages is greater than or equal to 2f+1, where f is a maximum number of faulty nodes that is tolerable by the blockchain network based on PBFT, and wherein n is a total number of consensus nodes in the blockchain network and f is a largest integer less than or equal to (n−1)/3.

2. The computer-implemented method of claim 1 , wherein the request includes a sequence number that indicates a number of a consensus round.

3. The computer-implemented method of claim 1 , wherein the one or more missing consensus messages include one or more of pre-prepare messages, prepare messages, and commit messages missing by the first consensus node.

4. The computer-implemented method of claim 1 , wherein the one or more missing consensus messages are stored in one or more consensus nodes in which they are generated or stored, until a stable checkpoint is reached.

5. The computer-implemented method of claim 1 , further comprising receiving one or more sequence numbers corresponding to the one or more missing consensus messages, wherein each sequence number indicates a number of a consensus round associated with a corresponding consensus message.

6. The computer-implemented method of claim 1 , further comprising submitting the block of transactions to a blockchain and a status database, if the block of transactions is determined valid.

7. The computer-implemented method of claim 1 , further comprising:

sending, to a third consensus node, a request for a second one or more missing consensus messages by the second consensus node in response to the second timer running out and if the block of transactions is determined invalid;

receiving, from the third consensus node, the second one or more missing consensus messages each digitally signed by a private key of a corresponding consensus node that generates the second one or more missing consensus messages; and

determining that the block of transactions is valid, if a quantity of commit messages included in the one or more missing consensus messages and the second one or more missing consensus messages is greater than or equal to 2f+1.

8. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations for for facilitating a consensus process in a blockchain network based on practical Byzantine fault tolerance (PBFT), the operations comprising:

setting, by a first consensus node, a first timer that initiates a view change upon timeout;

setting, by the first consensus node, a second timer that runs out before the first timer;

in response to the second timer running out, sending, to a second consensus node, a request for one or more missing consensus messages, wherein the one or more missing consensus messages were previously transmitted to the first consensus node, but not received by the first consensus node;

receiving, from the second consensus node, the one or more missing consensus messages each digitally signed by a private key of a corresponding consensus node that generates the one or more missing consensus messages; and

determining that a block of transactions is valid, if a quantity of commit messages included in the one or more missing consensus messages is greater than or equal to 2f+1, where f is a maximum number of faulty nodes that is tolerable by the blockchain network based on PBFT, and wherein n is a total number of consensus nodes in the blockchain network and f is a largest integer less than or equal to (n−1)/3.

9. The non-transitory, computer-readable medium of claim 8 , wherein the request includes a sequence number that indicates a number of a consensus round.

10. The non-transitory, computer-readable medium of claim 8 , wherein the one or more missing consensus messages include one or more of pre-prepare messages, prepare messages, and commit messages missing by the first consensus node.

11. The non-transitory, computer-readable medium of claim 8 , wherein the one or more missing consensus messages are stored in one or more consensus nodes in which they are generated or stored, until a stable checkpoint is reached.

12. The non-transitory, computer-readable medium of claim 8 , the operations further comprising receiving one or more sequence numbers corresponding to the one or more missing consensus messages, wherein each sequence number indicates a number of a consensus round associated with a corresponding consensus message.

13. The non-transitory, computer-readable medium of claim 8 , the operations further comprising submitting the block of transactions to a blockchain and a status database, if the block of transactions is determined valid.

14. The non-transitory, computer-readable medium of claim 8 , the operations further comprising:

sending, to a third consensus node, a request for a second one or more missing consensus messages by the second consensus node in response to the second timer running out and if the block of transactions is determined invalid;

receiving, from the third consensus node, the second one or more missing consensus messages each digitally signed by a private key of a corresponding consensus node that generates the second one or more missing consensus messages; and

determining that the block of transactions is valid, if a quantity of commit messages included in the one or more missing consensus messages and the second one or more missing consensus messages is greater than or equal to 2f+1.

15. A system for facilitating a consensus process in a blockchain network based on practical Byzantine fault tolerance (PBFT), comprising:

one or more computers; and

one or more computer-readable memories coupled to the one or more computers and having instructions stored thereon which are executable by the one or more computers to perform operations comprising:

setting, by a first consensus node, a first timer that initiates a view change upon timeout;

setting, by the first consensus node, a second timer that runs out before the first timer;

in response to the second timer running out, sending, to a second consensus node, a request for one or more missing consensus messages, wherein the one or more missing consensus messages were previously transmitted to the first consensus node, but not received by the first consensus node;

receiving, from the second consensus node, the one or more missing consensus messages each digitally signed by a private key of a corresponding consensus node that generates the one or more missing consensus messages; and

determining that a block of transactions is valid, if a quantity of commit messages included in the one or more missing consensus messages is greater than or equal to 2f+1, where f is a maximum number of faulty nodes that is tolerable by the blockchain network based on PBFT, and wherein n is a total number of consensus nodes in the blockchain network and f is a largest integer less than or equal to (n−1)/3.

16. The system of claim 15 , wherein the request includes a sequence number that indicates a number of a consensus round.

17. The system of claim 15 , wherein the one or more missing consensus messages include one or more of pre-prepare messages, prepare messages, and commit messages missing by the first consensus node.

18. The system of claim 15 , wherein the one or more missing consensus messages are stored in one or more consensus nodes in which they are generated or stored, until a stable checkpoint is reached.

19. The system of claim 15 , the operations further comprising receiving one or more sequence numbers corresponding to the one or more missing consensus messages, wherein each sequence number indicates a number of a consensus round associated with a corresponding consensus message.

20. The system of claim 15 , the operations further comprising submitting the block of transactions to a blockchain and a status database, if the block of transactions is determined valid.