Deterministic concurrency control for private blockchains

A system comprising:

• one or more processors;
• and
• a computer-readable medium comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
• receiving a set of transactions from one or more blocks in a blockchain at a node;
• performing a simulation step by:
• generating a dependency graph comprising the set of transactions and a set of dependencies between the set of transactions, the set of dependencies including one or more read-write dependencies and one or more write-write dependencies;
• and
• identifying in the dependency graph one or more occurrences of a dangerous structure, the dangerous structure including a first read-write dependency from a second transaction to a first transaction, and a second read-write dependency from a third transaction to the second transaction, wherein a transaction ID of the first transaction is less than a transaction ID of the second transaction, and the transaction ID of the first transaction is less than or equal to a transaction ID of the third transaction;
• and
• performing a commit step by:
• in response to identifying the one or more occurrences of the dangerous structure, aborting one transaction from the first transaction, the second transaction, and the third transaction for each of the one or more occurrences of of the dangerous structure in the dependency graph;
• for a subset of the set of transactions having a write-write dependency within the dependency graph, determining a commit order for the subset of transactions based on an ascending order of a minimal outgoing transaction ID associated with each transaction in the subset, wherein the minimal outgoing transaction ID is based on one or more read-write dependencies from other transactions to each transaction in the subset;
• and
• committing each non-aborted transaction of the set of transactions, wherein committing the subset of the set of transactions having the write-write dependency is performed according to the determined commit order to resolve the write-write dependency without an abort.

A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:

• receiving a set of transactions from one or more blocks in a blockchain at a node;
• performing a simulation step by:
• generating a dependency graph comprising the set of transactions and a set of dependencies between the set of transactions, the set of dependencies including one or more read-write dependencies and one or more write-write dependencies;
• and
• identifying in the dependency graph one or more occurrences of a dangerous structure, the dangerous structure including a first read-write dependency from a second transaction to a first transaction, and a second read-write dependency from a third transaction to the second transaction, wherein a transaction ID of the first transaction is less than a transaction ID of the second transaction, and the transaction ID of the first transaction is less than or equal to a transaction ID of the third transaction;
• and
• performing a commit step by:
• in response to identifying the one or more occurrences of the dangerous structure, aborting one transaction from the first transaction, the second transaction, and the third transaction for each of the one or more occurrences of of the dangerous structure in the dependency graph;
• for a subset of the set of transactions having a write-write dependency within the dependency graph, determining a commit order for the subset of transactions based on an ascending order of a minimal outgoing transaction ID associated with each transaction in the subset, wherein the minimal outgoing transaction ID is based on one or more read-write dependencies from other transactions to each transaction in the subset;
• and
• committing each non-aborted transaction of the set of transactions, wherein committing the subset of the set of transactions having the write-write dependency is performed according to the determined commit order to resolve the write-write dependency without an abort.