Shared blockchain data storage

1. A computer-implemented method for communicating shared blockchain data, the method comprising:

sending, by a consensus node of a blockchain network, current state information associated with a current block of a blockchain to a trusted node with proof of authority outside of the blockchain network, wherein the consensus node stores the current state information and the trusted node stores historic state information associated with every block of the blockchain as a historic state tree, and wherein the historic state tree includes key-value pairs (KVPs) with values of the historic state tree being account states of accounts associated with the blockchain network and keys of the historic state tree being hash values of the corresponding account states;

sending, by the consensus node, a hash value to the trusted node for retrieving an account state stored in the historic state tree;

receiving, by the consensus node, the account state in response to sending the hash value; and

verifying, by the consensus node, that the account state is part of the blockchain based on the hash value.

2. The computer-implemented method of claim 1 , wherein a current state tree includes KVPs with values of the current state tree being account states associated with the current block and keys of the current state tree being node IDs corresponding to nodes of the current state tree.

3. The computer-implemented method of claim 1 , wherein keys of a current state tree further include a block ID corresponding to the current block.

4. The computer-implemented method of claim 1 , wherein the current state information sent by the consensus node includes a digital signature generated based on a private key associated with the consensus node.

5. The computer-implemented method of claim 1 , wherein sending the current state information further comprises sending the current state information and a hash value of the current state information as KVP to the trusted node.

6. The computer-implemented method of claim 1 , wherein verifying that the account state is part of the blockchain is performed based on hashing the account state to generate a hashed account state and comparing the hashed account state to the hash value.

7. The computer-implemented method of claim 1 , wherein the trusted node stores historic state information locally or on a cloud storage.

8. The computer-implemented method of claim 1 , wherein a current state tree and the historic state tree are stored as a fixed depth Merkle tree.

9. A non-transitory, computer-readable storage medium storing one or more instructions executable by a computer system to perform operations for communicating shared blockchain data, the operations comprising:

sending, by a consensus node of a blockchain network, current state information associated with a current block of a blockchain to a trusted node with proof of authority outside of the blockchain network, wherein the consensus node stores the current state information and the trusted node stores historic state information associated with every block of the blockchain as a historic state tree, and wherein the historic state tree includes key-value pairs (KVPs) with values of the historic state tree being account states of accounts associated with the blockchain network and keys of the historic state tree being hash values of the corresponding account states;

sending, by the consensus node, a hash value to the trusted node for retrieving an account state stored in the historic state tree;

receiving, by the consensus node, the account state in response to sending the hash value; and

verifying, by the consensus node, that the account state is part of the blockchain based on the hash value.

10. The non-transitory, computer-readable storage medium of claim 9 , wherein a current state tree includes KVPs with values of the current state tree being account states associated with the current block and keys of the current state tree being node IDs corresponding to nodes of the current state tree.

11. The non-transitory, computer-readable storage medium of claim 9 , wherein keys of a current state tree further include a block ID corresponding to the current block.

12. The non-transitory, computer-readable storage medium of claim 9 , wherein the current state information sent by the consensus node includes a digital signature generated based on a private key associated with the consensus node.

13. The non-transitory, computer-readable storage medium of claim 9 , wherein sending the current state information further comprises sending the current state information and a hash value of the current state information as KVP to the trusted node.

14. The non-transitory, computer-readable storage medium of claim 9 , wherein verifying that the account state is part of the blockchain is performed based on hashing the account state to generate a hashed account state and comparing the hashed account state to the hash value.

15. The non-transitory, computer-readable storage medium of claim 9 , wherein the trusted node stores historic state information locally or on a cloud storage.

16. The non-transitory, computer-readable storage medium of claim 9 , wherein a current state tree and the historic state tree are stored as a fixed depth Merkle tree.

17. A computer-implemented system, comprising:

one or more computers; and

one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations for communicating shared blockchain data, the operations comprising:

sending, by a consensus node of a blockchain network, current state information associated with a current block of a blockchain to a trusted node with proof of authority outside of the blockchain network, wherein the consensus node stores the current state information and the trusted node stores historic state information associated with every block of the blockchain as a historic state tree, and wherein the historic state tree includes key-value pairs (KVPs) with values of the historic state tree being account states of accounts associated with the blockchain network and keys of the historic state tree being hash values of the corresponding account states,

sending, by the consensus node, a hash value to the trusted node for retrieving an account state stored in the historic state tree,

receiving, by the consensus node, the account state in response to sending the hash value, and

verifying, by the consensus node, that the account state is part of the blockchain based on the hash value.

18. The system of claim 17 , wherein a current state tree includes KVPs with values of the current state tree being account states associated with the current block and keys of the current state tree being node IDs corresponding to nodes of the current state tree.

19. The system of claim 17 , wherein keys of a current state tree further include a block ID corresponding to the current block.

20. The system of claim 17 , wherein the current state information sent by the consensus node includes a digital signature generated based on a private key associated with the consensus node.

21. The system of claim 17 , wherein sending the current state information further comprises sending the current state information and a hash value of the current state information as KVP to the trusted node.

22. The system of claim 17 , wherein verifying that the account state is part of the blockchain is performed based on hashing the account state to generate a hashed account state and comparing the hashed account state to the hash value.

23. The system of claim 17 , wherein the trusted node stores historic state information locally or on a cloud storage.

24. The system of claim 17 , wherein a current state tree and the historic state tree are stored as a fixed depth Merkle tree.