Systems and methods for providing data privacy in a private distributed ledger
Systems and methods for providing data privacy in a private distributed ledger are disclosed. According to another embodiment a distributed ledger network may include a first node comprising a first node computer processor and hosting a central ledger comprising a plurality of entries for public transactions and private transactions, wherein the entries for public transactions comprise transaction payloads for the respective public transaction, and the entries for private transactions comprise a cryptographic hash digest of a transaction payload for the respective private transaction; and a plurality of second nodes each comprising a second node computer processor and hosting a public database comprising the public transactions, and a private database comprising transaction payloads for the private transactions to which the node is a party.
1. A method for providing data privacy in a private distributed ledger, comprising:
receiving, by a node in a distributed ledger network, a block comprising a first transaction and a second transaction;
determining, by a node computer processor, that the first transaction is a private transaction;
communicating, by the node computer processor, a node public key and a transaction hash digest for the first transaction to a transaction key manager for the node;
receiving, by the node computer processor, an encrypted transaction payload for the first transaction;
decrypting, by the node computer processor, the encrypted transaction payload, the transaction payload comprising contract code associated with the first transaction;
executing, by the node computer processor, the contract code associated with the first transaction;
determining, by the node computer processor, that the node is not a party to the second transaction; and
skipping, by the node computer processor, execution of contract code associated with the second transaction;
wherein the node computer processor determines that the first transaction or second transaction is a private transaction based on a flag in a body of the first or second transaction.
2. The method of claim 1 , further comprising:
communicating, by the node computer processor, a node public key and a transaction hash digest for the second transaction to a transaction key manager for the node; and
receiving, by the node computer processor, an indication that the node is not a party to the second transaction in response to the node not being a party to the second transaction.
3. The method of claim 1 , further comprising:
validating, by the node computer processor, the block.
4. The method of claim 3 , wherein the step of validating the block comprises validation of a public state, wherein each node has a different private state.
5. The method of claim 1 , wherein the distributed ledger comprises private transactions and public transactions,
wherein the private transactions and the public transactions are visible and cryptographically immutable.
6. A method for providing data privacy in a private distributed ledger, comprising:
receiving, by a node in a distributed ledger network, a block comprising a first transaction and a second transaction written to the distributed ledger;
determining, by a node computer processor, that the first transaction is a private transaction;
communicating, by the node computer processor, a node public key and a transaction hash digest for the first transaction to a transaction key manager for the node;
receiving, by the node computer processor, an encrypted transaction payload for the first transaction;
decrypting, by the node computer processor, the encrypted transaction payload, the transaction payload comprising contract code associated with the first transaction;
executing, by the node computer processor, the contract code associated with the first transaction;
determining, by the node computer processor, that the node is not a party to the second transaction; and
skipping, by the node computer processor, execution of contract code associated with the second transaction;
wherein the node computer processor determines that the first transaction or second transaction is a private transaction based on a sentinel byte associated with first or second transaction.
7. The method of claim 6 , further comprising:
communicating, by the node computer processor, a node public key and a transaction hash digest for the second transaction to a transaction key manager for the node; and
receiving, by the node computer processor, an indication that the node is not a party to the second transaction in response to the node not being a party to the second transaction.
8. The method of claim 6 , further comprising:
validating, by the node computer processor, the block.
9. The method of claim 8 , wherein the step of validating the block comprises validation of a public state, wherein each node has a different private state.
10. The method of claim 6 , wherein the distributed ledger comprises private transactions and public transactions,
wherein the private transactions and the public transactions are visible and cryptographically immutable.