MANAGING PRIVATE TRANSACTIONS ON BLOCKCHAIN NETWORKS BASED ON WORKFLOW

1 . A computer-implemented method for private data transactions through blockchain networks based on a workflow, comprising:

obtaining, by a first consensus node, a policy of a workflow for sending transaction data between at least two client nodes, the policy being digitally signed by each of the at least two client nodes using a corresponding private key, and the policy includes a routing order of the transaction data between the at least two client nodes;

receiving the transaction data submitted by a first of the at least two client nodes, the transaction data being digitally signed by a private key of the first of the at least two client nodes; and

forwarding the transaction data to a second consensus node or a second of the at least two client nodes based on the policy.

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

receiving, from a last client node in the routing order of the at least two client nodes, the transaction data digitally signed by each of the at least two client nodes using the corresponding private key;

determining that the transaction data is valid based on a consensus process of a blockchain; and

recording a hashed value of the transaction data on the blockchain.

3 . The computer-implemented method of claim 1 , wherein the first of the at least two client nodes is a first client node in the routing order.

4 . The computer-implemented method of claim 1 , wherein the second consensus node is trusted by a second client node in the routing order.

5 . The computer-implemented method of claim 1 , wherein the first consensus node is trusted by the first of the at least two client nodes and the second of the at least two client nodes.

6 . The computer-implemented method of claim 1 , wherein the transaction data is digitally signed by the first of the at least two client nodes.

7 . The computer-implemented method of claim 1 , wherein the policy includes an address of each of the at least two client nodes and consensus nodes trusted by the at least two client nodes.

8 . A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:

obtaining, by a first consensus node, a policy of a workflow for sending transaction data between at least two client nodes, the policy being digitally signed by each of the at least two client nodes using a corresponding private key, and the policy includes a routing order of the transaction data between the at least two client nodes;

receiving the transaction data submitted by a first of the at least two client nodes, the transaction data being digitally signed by a private key of the first of the at least two client nodes; and

forwarding the transaction data to a second consensus node or a second of the at least two client nodes based on the policy.

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

receiving, from a last client node in the routing order of the at least two client nodes, the transaction data digitally signed by each of the at least two client nodes using the corresponding private key;

determining that the transaction data is valid based on a consensus process of a blockchain; and

recording a hashed value of the transaction data on the blockchain.

10 . The non-transitory, computer-readable medium of claim 8 , wherein the first of the at least two client nodes is a first client node in the routing order.

11 . The non-transitory, computer-readable medium of claim 8 , wherein the second consensus node is trusted by a second client node in the routing order.

12 . The non-transitory, computer-readable medium of claim 8 , wherein the first consensus node is trusted by the first of the at least two client nodes and the second of the at least two client nodes.

13 . The non-transitory, computer-readable medium of claim 8 , wherein the transaction data is digitally signed by the first of the at least two client nodes.

14 . The non-transitory, computer-readable medium of claim 8 , wherein the policy includes an address of each of the at least two client nodes and consensus nodes trusted by the at least two client nodes.

15 . A system, 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:

obtaining, by a first consensus node, a policy of a workflow for sending transaction data between at least two client nodes, the policy being digitally signed by each of the at least two client nodes using a corresponding private key, and the policy includes a routing order of the transaction data between the at least two client nodes;

receiving the transaction data submitted by a first of the at least two client nodes, the transaction data being digitally signed by a private key of the first of the at least two client nodes; and

forwarding the transaction data to a second consensus node or a second of the at least two client nodes based on the policy.

16 . The system of claim 15 , the operations further comprising:

receiving, from a last client node in the routing order of the at least two client nodes, the transaction data digitally signed by each of the at least two client nodes using the corresponding private key;

determining that the transaction data is valid based on a consensus process of a blockchain; and

recording a hashed value of the transaction data on the blockchain.

17 . The system of claim 15 , wherein the first of the at least two client nodes is a first client node in the routing order.

18 . The system of claim 15 , wherein the second consensus node is trusted by a second client node in the routing order.

19 . The system of claim 15 , wherein the first consensus node is trusted by the first of the at least two client nodes and the second of the at least two client nodes.

20 . The system of claim 15 , wherein the transaction data is digitally signed by the first of the at least two client nodes.