Systems and methods for hybrid synchronization in virtual distributed ledger networks

1. A system for hybrid synchronization in a virtual distributed ledger technology network, comprising:

at least one hardware processor; and

at least one memory device storing instructions executable by the at least one hardware processor to perform operations comprising:

creating a first virtual machine or container associated with a master ledger, wherein the first virtual machine or container is a master producer node associated with the virtual distributed ledger technology network;

creating one or more additional virtual machines or containers associated with slave ledgers, wherein the one or more additional virtual machines or containers are one or more slave consumer nodes associated with the virtual distributed ledger technology network;

receiving, at the first virtual machine or container, a transaction request comprising transaction information;

updating the master ledger with the transaction information;

determining whether to perform synchronous or asynchronous update of the slave ledgers;

upon determining to perform a synchronous update of the slave ledgers, updating the slave ledgers based on the updated master ledger with the transaction information using a consensus protocol; and

upon determining to perform an asynchronous update of the slave ledgers, communicating, by the first virtual machine or container, with the one or more additional virtual machines or containers, an update of the slave ledgers at one or more times determined based on a delay tolerance associated with each of the one or more additional virtual machines or containers, wherein the one or more times are different and the master producer node communicates the update of the master ledger with each of the one or more slave consumer nodes at a different time so that the one or more slave consumer nodes are asynchronously updated.

2. The system of claim 1 , the at least one memory device further storing instructions executable by the at least one hardware processor to perform operations comprising:

determining a transaction type associated with the transaction request;

wherein determining whether to perform synchronous or asynchronous update of the slave ledgers is based on the transaction type associated with the transaction request.

3. The system of claim 1 , wherein each of the one or more slave consumer nodes stores at least partially replicated ledger.

4. The system of claim 3 , wherein the consensus protocol is one of: Byzantine Fault Tolerance, Practical Byzantine Fault Tolerance, Proof of Work, Proof of Stake, a Delegated Proof of Stake, a majority vote, an all-in-agreement vote, a vote based on percentage/fraction of votes, and a Raft Consensus.

5. The system of claim 1 , wherein the virtual distributed ledger technology network does not seek consensus from the one or more slave consumer nodes for asynchronous updates of the one or more slave consumer nodes.

6. The system of claim 1 , wherein the communicating further comprises:

aggregating a number of transactions; and

transmitting, to the one or more additional virtual machines or containers, a bulk update comprising the number of transactions based on an aggregation delay allowance, the aggregation delay allowance being determined based on the delay tolerance and an inter-node latency determined based on periodic ping measurements of packet delays between a producer node and a consumer node associated with a virtual distributed ledger technology network.

7. A method for hybrid synchronization in a virtual distributed ledger technology network, comprising:

creating, via at least one hardware processor, a first virtual machine or container associated with a master ledger, wherein the first virtual machine or container is a master producer node associated with the virtual distributed ledger technology network;

creating, via the at least one hardware processor, one or more additional virtual machines or containers associated with slave ledgers, wherein the one or more additional virtual machines or containers are one or more slave consumer nodes associated with the virtual distributed ledger technology network;

receiving, via the at least one hardware processor, at the first virtual machine or container, a transaction request comprising transaction information;

updating, via the at least one hardware processor, the master ledger with the transaction information;

determining, via the at least one hardware processor, whether to perform synchronous or asynchronous update of the slave ledgers;

upon determining to perform a synchronous update of the slave ledgers, updating, via the at least one hardware processor, the slave ledgers based on the updated master ledger with the transaction information using a consensus protocol; and

upon determining to perform an asynchronous update of the slave ledgers, communicating, via the at least one hardware processor, by the first virtual machine or container, with the one or more additional virtual machines or containers, an update of the slave ledgers at one or more times determined based on a delay tolerance associated with each of the one or more additional virtual machines or containers, wherein the one or more times are different and the master producer node communicates the update of the master ledger with each of the one or more slave consumer nodes at a different time so that the one or more slave consumer nodes are asynchronously updated.

8. The method of claim 7 , further comprising:

determining, via the at least one hardware processor, a transaction type associated with the transaction request;

wherein determining whether to perform synchronous or asynchronous update of the slave ledgers is based on the transaction type associated with the transaction request.

9. The method of claim 7 , wherein each of the one or more slave consumer nodes stores at least partially replicated ledger.

10. The method of claim 9 , wherein the consensus protocol is one of: Byzantine Fault Tolerance, Practical Byzantine Fault Tolerance, Proof of Work, Proof of Stake, a Delegated Proof of Stake, a majority vote, an all-in-agreement vote, a vote based on percentage/fraction of votes, and a Raft Consensus.

11. The method of claim 7 , wherein the virtual distributed ledger technology network does not seek consensus from the one or more slave consumer nodes for asynchronous updates of the one or more slave consumer nodes.

12. The method of claim 7 , wherein the communicating further comprises:

aggregating, via the at least one hardware processor, a number of transactions; and

transmitting, via the at least one hardware processor, to the one or more additional virtual machines or containers, a bulk update comprising the number of transactions based on an aggregation delay allowance, the aggregation delay allowance being determined based on the delay tolerance and an inter-node latency determined based on periodic ping measurements of packet delays between a producer node and a consumer node associated with a virtual distributed ledger technology network.

13. A non-transitory computer-readable medium storing instructions for hybrid synchronization in a virtual distributed ledger technology network, the instructions executable by a hardware processor to perform operations comprising:

creating, via at least one hardware processor, a first virtual machine or container associated with a master ledger, wherein the first virtual machine or container is a master producer node associated with the virtual distributed ledger technology network;

creating, via the at least one hardware processor, one or more additional virtual machines or containers associated with slave ledgers, wherein the one or more additional virtual machines or containers are one or more slave consumer nodes associated with the virtual distributed ledger technology network;

receiving, via the at least one hardware processor, at the first virtual machine or container, a transaction request comprising transaction information;

updating, via the at least one hardware processor, the master ledger with the transaction information;

determining, via the at least one hardware processor, whether to perform synchronous or asynchronous update of the slave ledgers;

upon determining to perform a synchronous update of the slave ledgers, updating, via the at least one hardware processor, the slave ledgers based on the updated master ledger with the transaction information using a consensus protocol; and

upon determining to perform an asynchronous update of the slave ledgers, communicating, via the at least one hardware processor, by the first virtual machine or container, with the one or more additional virtual machines or containers, an update of the slave ledgers at one or more times determined based on a delay tolerance associated with each of the one or more additional virtual machines or containers, wherein the one or more times are different and the master producer node communicates the update of the master ledger with each of the one or more slave consumer nodes at a different time so that the one or more slave consumer nodes are asynchronously updated.

14. The medium of claim 13 , the at least one memory device further storing instructions executable by the at least one hardware processor to perform operations comprising:

determining, via the at least one hardware processor, a transaction type associated with the transaction request;

wherein determining whether to perform synchronous or asynchronous update of the slave ledgers is based on the transaction type associated with the transaction request.

15. The medium of claim 13 , wherein each of the one or more slave consumer nodes stores at least partially replicated ledger.

16. The medium of claim 15 , wherein the consensus protocol is one of: Byzantine Fault Tolerance, Practical Byzantine Fault Tolerance, Proof of Work, Proof of Stake, a Delegated Proof of Stake, a majority vote, an all-in-agreement vote, a vote based on percentage/fraction of votes, and a Raft Consensus.

17. The medium of claim 15 ,

wherein the virtual distributed ledger technology network does not seek consensus from the one or more slave consumer nodes for asynchronous updates of the one or more slave consumer nodes.

18. The medium of claim 13 , wherein the communicating further comprises:

aggregating, via the at least one hardware processor, a number of transactions; and

transmitting, via the at least one hardware processor, to the one or more additional virtual machines or containers, a bulk update comprising the number of transactions based on an aggregation delay allowance, the aggregation delay allowance being determined based on the delay tolerance and an inter-node latency determined based on periodic ping measurements of packet delays between a producer node and a consumer node associated with a virtual distributed ledger technology network.