Data storage method and system, device and storage medium

Abstract

The present invention provides a data storage method, system, device and storage medium, the method comprising: locally storing the global index table of the Merkle tree corresponding to each block in each node of the block chain network, and each block Merkle tree of blocks. Among them, the version number of the version is the block height, and the global index table is used for data query according to the block height. The present invention provides the system with data that can directly query the global index table through the block height by configuring the corresponding global index table with the block height as the version number for the Merkle tree, and complete the query through one read operation. The query method greatly improves the data reading performance of the system; and further optimizes the robustness of the system in the event of transaction congestion or node crash.

Description

technical field [0001] The present application relates to the technical field of block chain, in particular to a data storage method, system, equipment and storage medium. Background technique [0002] In the current data reading and writing solutions of the blockchain system, the structure of the Merkle tree is usually adopted. Kerr prefix tree (Merkle Patricia Tree, referred to as MPT) for data reading and writing, and so on. [0003] The shortcomings of the current data storage scheme using the Merkle tree structure are: [0004] The stored data limits the read performance of the system, and querying the data of a transaction requires multiple read operations. For example, for a 20-layer Merkle tree, querying the data of a leaf node requires 20 read operations to complete, resulting in the efficiency of data query is only 1 / 20 of the query efficiency of ordinary databases, which can be completed per second A system with 100,000 read operations can only read data of 5,0...

AI Technical Summary

Problems solved by technology

[0004] The stored data limits the read performance of the system, and querying the data of a transaction requires multiple read operations

For example, for a 20-layer Merkle tree, querying the data of a leaf node requires 20 read operations to complete, resulting in the efficiency of data query is only 1 / 20 of the query efficiency of ordinary databases, which can be completed per second A system with 100,000 read operations can only read data of 5,000 transactions per second

[0005] Furthermore, the existing scheme needs to complete the block consensus after writing the Merkle tree data in the local node database, which leads to transaction congestion when the number of transactions increases sharply

[0006] In addition, if the existing scheme crashes when writing Merkle tree data in the local database of the node, it will result in failure to generate blocks

Images