| CPC G06F 16/1837 (2019.01) [G06F 16/00 (2019.01); G06Q 20/223 (2013.01); G06Q 20/38215 (2013.01); G06Q 20/3825 (2013.01); G06Q 20/3827 (2013.01); G06Q 20/3829 (2013.01); G06Q 20/389 (2013.01); G06Q 20/401 (2013.01); H04L 9/00 (2013.01); H04L 9/0637 (2013.01); H04L 9/0643 (2013.01); H04L 9/0836 (2013.01); H04L 9/30 (2013.01); H04L 9/3247 (2013.01); H04L 9/3255 (2013.01); H04L 9/3265 (2013.01); H04L 9/3297 (2013.01); H04L 67/00 (2013.01); H04L 67/1051 (2013.01); G06F 16/27 (2019.01); G06Q 20/02 (2013.01); G06Q 20/065 (2013.01); G06Q 20/3678 (2013.01); G06Q 20/4016 (2013.01); H04L 9/3239 (2013.01); H04L 9/50 (2022.05); H04L 63/123 (2013.01)] | 20 Claims |

|
1. A network node in a network comprising a committee of validator nodes and at least one client node, the network node comprising at least one processor and at least one memory containing instructions that, when executed by the processor, configure the network node to perform the following steps of a reconfiguration process for reconfiguring the membership of validator nodes in the committee, the steps comprising:
in a first stage of the reconfiguration process:
transmitting to the committee of validator nodes a request to become a new validator node in the committee;
receiving a response from at least one validator node in the committee confirming that the network node has been selected to become a new validator node in the committee; and
in a second stage of the reconfiguration process:
generating a request for data confirming the network node is the new validator node;
receiving the data, wherein the data indicates that at least a threshold number of validator nodes have confirmed that the network node is selected to be the new validator node; and
coordinating with the other validator nodes in the committee to process a transaction received from the client node in the network.
|