WO2023279970A1

WO2023279970A1 - Blockchain-based data synchronization method and apparatus

Info

Publication number: WO2023279970A1
Application number: PCT/CN2022/100606
Authority: WO
Inventors: 黄洲荣
Original assignee: 支付宝(杭州)信息技术有限公司; 蚂蚁区块链科技(上海)有限公司
Priority date: 2021-07-07
Filing date: 2022-06-23
Publication date: 2023-01-12
Also published as: CN113596107A

Abstract

A blockchain-based data synchronization method, applied to a data synchronization system, wherein the data synchronization system interfaces with a blockchain node. The method comprises: when a trigger condition for data synchronization is reached, obtaining a first storage attribute of each block on a blockchain from the blockchain node; determining, on the basis of the first storage attribute, whether each block is a non-empty block, and add a service transaction in a block that is determined to be a non-empty block to a synchronization queue, the non-empty block is a block in which a service transaction is stored; and synchronizing the service transaction in the synchronization queue to a service system.

Description

Method and device for data synchronization based on block chain

technical field

This specification relates to the technical field of blockchain, and in particular to a data synchronization method and device based on blockchain.

Background technique

With the continuous development of blockchain technology, blockchain technology has been applied in more and more fields. In related technologies, there is a need to synchronize data on the blockchain to off-chain for related business processing. Based on this, how to improve the speed and efficiency of data synchronization on the blockchain has become the focus of the industry.

Contents of the invention

In view of this, this specification provides a blockchain-based data synchronization method and device.

Specifically, this specification is realized through the following technical solution: a blockchain-based data synchronization method applied to a data synchronization system, the data synchronization system is connected to a blockchain node, including: reaching the trigger condition for data synchronization , the first storage attribute of each block on the blockchain is obtained from the blockchain node; based on the first storage attribute, it is determined whether each block is a non-empty block, and the The business transaction is added to the synchronization queue, and the non-empty block is a block storing the business transaction; the business transaction in the synchronization queue is synchronized to the business system.

A data synchronization device based on blockchain, comprising: an acquisition unit, which acquires the first storage attribute of each block on the blockchain from a blockchain node when a trigger condition for data synchronization is reached; a determination unit, based on the first A storage attribute determines whether each block is a non-empty block, and adds the business transaction in the block determined as a non-empty block to the synchronization queue, and the non-empty block is a block that stores a business transaction; the synchronization unit will synchronize The business transactions in the queue are synchronized to the business system.

A data synchronization device based on blockchain, comprising: a processor; a memory for storing machine-executable instructions; wherein, by reading and executing the machine stored in the memory and corresponding to the logic of data synchronization based on blockchain Executable instructions, the processor is prompted: when the trigger condition of data synchronization is reached, obtain the first storage attribute of each block on the blockchain from the blockchain node; determine whether each block is based on the first storage attribute It is a non-empty block, and the business transaction in the block determined to be a non-empty block is added to the synchronization queue, and the non-empty block is a block storing the business transaction; the business transaction in the synchronization queue is synchronized to the business system.

An embodiment of this specification realizes that the data synchronization system can obtain the first storage attribute of each block on the blockchain from the blockchain node when the trigger condition for data synchronization is reached, and determine each block based on the first storage attribute Whether it is a non-empty block, and add the business transactions in the block determined to be a non-empty block to the synchronization queue, and then synchronize the business transactions in the synchronization queue to the business system.

Using the above method, when synchronizing data on the blockchain, it is possible to determine non-empty blocks containing business transactions, and only perform data synchronization on these non-empty blocks, avoiding data synchronization on empty blocks that do not contain business transactions , compared to the full synchronization of all blocks on the blockchain in related technologies, the efficiency of data synchronization can be greatly improved.

Description of drawings

Fig. 1 is a schematic flow diagram of a blockchain-based data synchronization method shown in an exemplary embodiment of this specification;

Fig. 2 is a schematic diagram of a block chain shown in an exemplary embodiment of this specification;

Fig. 3 is a schematic flow diagram of another blockchain-based data synchronization method shown in an exemplary embodiment of this specification;

FIG. 4 is a hardware structural diagram of an electronic device where a blockchain-based data synchronization device is shown in an exemplary embodiment of this specification;

Fig. 5 is a block diagram of a blockchain-based data synchronization device shown in an exemplary embodiment of this specification.

detailed description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present specification as recited in the appended claims.

The terms used in this specification are for the purpose of describing particular embodiments only, and are not intended to limit the specification. As used in this specification and the appended claims, the singular forms "a", "the", and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It should also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this specification, first information may also be called second information, and similarly, second information may also be called first information. Depending on the context, the word "if" as used herein may be interpreted as "at" or "when" or "in response to a determination."

Blockchain technology, also known as distributed ledger technology, is an emerging technology in which several computing devices jointly participate in "bookkeeping" and jointly maintain a complete distributed database. Due to the characteristics of decentralization, openness and transparency, each computing device can participate in database records, and fast data synchronization between computing devices, blockchain technology has been widely used in many fields. to apply.

In actual application scenarios, there is a need to synchronize data on the blockchain to off-chain for related business processing. For example, the remittance business can be realized based on the blockchain, and a business transaction for remittance can be sent to the blockchain node, and the blockchain node can execute the transaction after receiving the transaction to update the balance of the accounts of the remittance parties. Moreover, based on the characteristics of the block chain, which is not easy to be tampered with and consistent, it can ensure that the remittance transaction is safe and reliable. In this scenario, the remittance transactions on the blockchain can be synchronized through the data synchronization system, and the synchronized data can be provided to the business system for subsequent business processing.

In related technologies, the data on the blockchain is usually synchronized in full, that is, each block on the blockchain is synchronized. However, due to the large amount of data stored on the blockchain, and Not every block stores the data that needs to be synchronized, and the method of full synchronization will lead to inefficiency.

Based on this, this specification provides a blockchain-based data synchronization method, which can determine whether each block is an empty block during the data synchronization process, and only perform data synchronization on non-empty blocks. Synchronization can greatly improve the efficiency of data synchronization.

Please refer to FIG. 1. FIG. 1 is a schematic flow diagram of a blockchain-based data synchronization method shown in an exemplary embodiment of this specification. The method can be applied to a data synchronization system, and the data synchronization system can specifically have a memory , processor server or server cluster.

The data synchronization method based on the block chain may include the following steps: step 102, when the trigger condition of data synchronization is reached, obtain the first storage attribute of each block on the block chain from the block chain node; step 104, based on the The first storage attribute determines whether each block is a non-empty block, and adds the business transaction in the block that is determined to be a non-empty block to the synchronization queue, and the non-empty block is a block that stores a business transaction; Step 106, Synchronize the business transactions in the synchronization queue to the business system.

The above steps will be described in detail below.

In this embodiment, the data synchronization system can be connected to the blockchain node to obtain data from the blockchain node and synchronize it to the business system. Of course, in other embodiments, the data synchronization system and the business system may be the same system, and there is no special limitation on this.

In this embodiment, a trigger condition for data synchronization may be preset. For example, data synchronization may be performed periodically, and the period may be preset, such as every day, every week, and so on. Then the trigger condition may be when the data synchronization period is reached. For another example, it may also be determined that the trigger condition for data synchronization is met after receiving the data synchronization request. A data synchronization request can be initiated according to a specific business scenario. For example, when the business system needs to obtain data on the blockchain for business processing, it can send a data synchronization request to the data synchronization system. This embodiment does not make special restrictions on this.

In this embodiment, when the trigger condition for data synchronization is reached, the data synchronization system can obtain the first storage attribute of each block on the blockchain from any blockchain node, and determine whether each block is non-empty block. Among them, the first storage attribute can be recorded in the world state of the blockchain, which will be described in detail in the following embodiments.

In this embodiment, a block that does not store a business transaction is determined as an empty block, and a block that stores a business transaction is determined as a non-empty block, wherein the business transaction is data that needs to be synchronized, for example, it can be The remittance transaction can also be other types of transactions, which can be set according to specific application scenarios. Moreover, it is worth noting that there may be various types of transactions stored on the block, including business transactions and non-business transactions. In this embodiment, blocks without business transactions are considered as empty blocks, but it does not mean that There must not be any transactions stored on the empty block, for example, non-business transactions may be stored. For the method of distinguishing business transactions and non-business transactions, reference may be made to related technologies, which is not particularly limited in this embodiment.

In this embodiment, the business transactions in the blocks determined to be non-empty blocks can be added to the synchronization queue, and the synchronization queue can be stored in the data synchronization system. Then the business transactions stored on the non-empty blocks can be synchronized to the business system based on the synchronization queue.

For example, the identification of non-empty blocks can be added to the synchronization queue. When synchronizing business transactions to the business system, the corresponding non-empty blocks can be determined according to these identifications, and then the business transactions stored on the non-empty blocks can be obtained and synchronized to the business system.

For another example, all business transactions stored on non-empty blocks can also be added to the synchronization queue, then when the business transactions are synchronized to the business system, the business transactions can be obtained from the synchronization queue and synchronized to the business system.

In this embodiment, after the data in the synchronization queue is synchronized, the data in the queue can also be cleared.

It can be seen from the above description that in one embodiment of this specification, the data synchronization system can obtain the first storage attribute of each block on the blockchain from the blockchain node when the trigger condition for data synchronization is reached, based on The first storage attribute determines whether each block is a non-empty block, and adds the business transactions in the blocks determined to be non-empty blocks to the synchronization queue, and then synchronizes the business transactions in the synchronization queue to the business system.

The following describes an embodiment of the method for determining whether each block on the block chain is a non-empty block based on the first storage attribute provided by this specification.

1. The first storage attribute indicates whether the block is a non-empty block

In one example, starting from the latest block on the blockchain, according to the order of block height from high to low, it is possible to determine whether each block is a non-empty block based on the first storage attribute of each block, and these Blocks determined to be non-empty blocks are added to the synchronization queue.

A specific example is used below to illustrate. Please refer to Fig. 2, Fig. 2 exemplarily shows a block chain, there may be several blocks in the block chain, respectively block 1, block 2, ..., block n-4, block n-3, block n-2, block n-1, block n. Block n is the latest block, and block 1 is the genesis block. Wherein, if the first storage attribute is "0", it means that the block is an empty block, and if the first storage attribute is "1", it means that the block is a non-empty block. Then block 1 is a non-empty block, block 2 is a non-empty block, block n-4 is a non-empty block, block n-3 is a non-empty block, block n-2 is an empty block, block n- 1 is an empty block, and block n is a non-empty block.

You can first judge from block n (the latest block), and if you find that block n is a non-empty block, you can add block n to the synchronization queue, and then judge whether block n-1 is a non-empty block, and find that block If n-1 is an empty block, it will not be added to the synchronization queue, and then judge whether the block n-2 is a non-empty block, and if the block n-2 is found to be an empty block, it will not be added to the synchronization queue...you can follow the above The method judges each block until the creation block (block 1) is judged, and then it can be determined that the blocks included in the synchronization queue are: block n, block n-3, block n-4 , ..., block 2, block 1.

Of course, although this example describes adding "blocks" to the synchronization queue, in fact, only business transactions stored on non-empty blocks can be added to the synchronization queue, instead of adding the block itself to the synchronization queue. The following embodiments Similar to this.

In another example, when judging whether each block is a non-empty block, it is also possible to directly "skip" the empty block.

Starting from the latest block on the blockchain, it is judged whether the latest block is a non-empty block according to the first storage attribute corresponding to the latest block.

If the latest block is a non-empty block, the latest block can be added to the synchronization queue to continue to judge whether the previous block of the latest block is a non-empty block; if the latest block is an empty block, the latest block will not be added synchronization queue, and can determine the non-empty block closest to the block height of the latest block, add the non-empty block to the synchronization queue, and continue to judge whether the previous block of the non-empty block is a non-empty block.

The above method can be used to determine each non-empty block on the blockchain, and add these non-empty blocks to the synchronization queue, so as to synchronize the business transactions stored on the non-empty block to the business system based on the synchronization queue.

The example shown in FIG. 2 is still used for illustration.

You can first judge whether block n (the latest block) is a non-empty block, and if you find that it is a non-empty block, you can add block n to the synchronization queue, and judge the previous block of block n (block n-1 ) is a non-empty block, if block n-1 is found not to be a non-empty block, block n-1 will not be added to the synchronization queue, and the non-empty block closest to the block height of block n-1 will be determined, is block n-3, block n-3 can be added to the synchronization queue. And judge whether the previous block (block n-4) of block n-3 is a non-empty block, and find that block n-4 is a non-empty block, then it can be added to the synchronization queue. Then it can be judged whether the previous block of block n-4 is a non-empty block, and so on....

The above method can be used to determine each non-empty block in the blockchain, and add the non-empty block to the synchronization queue. For example, the blocks in the synchronization queue in the above example include: block n, block n-3, block n-4, ..., block 2, block 1. Moreover, the above method can determine the nearest non-empty block n-3 according to the block n-1, without the need to judge the block n-2, which is equivalent to "skipping" the empty block and improving the efficiency.

Among them, the non-empty block with the closest block height can be determined by the following method. The following is an example of determining the non-empty block closest to the block height of the latest block.

For example, a second storage attribute (world state) may also be stored on the blockchain node, and the second storage attribute represents the non-empty block closest to the block height of the current block. Then, when determining the non-empty block closest to the block height of the latest block, the second storage attribute corresponding to the latest block may be obtained, and the closest non-empty block is determined according to the attribute.

Wherein, the recording process of the second storage attribute will be described in detail in the following embodiments.

2. The first storage attribute indicates whether the previous block of this block is a non-empty block

In an example, starting from the latest block on the blockchain, it is determined whether the previous block of the latest block is a non-empty block according to the first storage attribute corresponding to the latest block.

If the previous block of the latest block is a non-empty block, the previous block of the latest block can be added to the synchronization queue, and continue to judge whether the previous block of the previous block is a non-empty block; if the latest block If the previous block of the block is an empty block, then the previous block of the latest block will not be added to the synchronization queue, and continue to judge whether the previous block of the previous block is a non-empty block.

Wherein, for the newest block, whether it is a non-empty block can be determined according to the method in the foregoing example, which will not be repeated in this embodiment.

The example shown in FIG. 2 is still used for illustration.

You can start from block n (the latest block), judge whether the previous block (block n-1) is a non-empty block according to the second storage attribute corresponding to block n, and find that it is not a non-empty block, then Do not add block n-1 to the synchronization queue, and judge whether the previous block (block n-2) of block n-1 is a non-empty block, and find that block n-2 is not a non-empty block, then do not Add block n-2 to the synchronization queue, and judge whether the previous block (block n-3) of block n-2 is a non-empty block, and if block n-3 is found to be a non-empty block, then block n-3 joins the synchronization queue, and judges whether the previous block (block n-4) of block n-3 is an empty block, and so on....

The above method can be used to determine each non-empty block in the blockchain, and add the non-empty block to the synchronization queue. For example, the blocks in the synchronization queue in the above example include: block n, block n-3, block n-4, ..., block 2, block 1. Wherein, the method for judging whether the block n is an empty block can refer to the foregoing embodiments.

In another example, similarly, it is also possible to "skip" empty blocks during the judgment process.

It is possible to start from the latest block on the blockchain, and judge whether the previous block of the latest block is a non-empty block according to the first storage attribute corresponding to the latest block.

If the previous block of the latest block is a non-empty block, the previous block of the latest block can be added to the synchronization queue, and continue to judge whether the previous block of the previous block is a non-empty block; if the latest block If the previous block of the latest block is an empty block, the previous block of the latest block will not be added to the synchronization queue, and the non-empty block closest to the block height of the previous block of the latest block can be determined. Add the non-empty block to the synchronization queue, and continue to judge whether the previous block of the non-empty block is a non-empty block.

Wherein, the method for determining the non-empty block closest to the block height of the previous block of the latest block can refer to the foregoing embodiments. Similarly, for the newest block, whether it is a non-empty block can be determined according to the method in the foregoing examples, which will not be repeated in this embodiment.

The example shown in FIG. 2 is still used for illustration.

You can start from block n (the latest block), judge whether the previous block (block n-1) is a non-empty block according to the second storage attribute corresponding to block n, and if it is found to be an empty block, then do not Block n-1 is added to the synchronization queue, and the non-empty block closest to the block height of block n-1 is determined to be block n-3, then block n-3 is added to the synchronization queue, and the block is judged Whether the previous block of n-3 (block n-4) is an empty block, and if block n-4 is found to be not empty, block n-4 will be added to the synchronization queue, and the block n-4 will be judged Whether the previous block (block n-5) is a non-empty block, and so on....

Certainly, the above-mentioned examples are only illustrative descriptions, and are not intended to limit the description.

It can be seen from the above description that in one embodiment of this specification, in the process of data synchronization, if a block is determined to be an empty block, the non-empty block closest to the block height of the block can also be determined , and then directly add the non-empty block (the business transaction stored on it) to the synchronization queue without processing the empty block contained between the two blocks, which is equivalent to directly "skipping" the empty block, Can greatly improve the efficiency of data synchronization.

The following describes another embodiment of a blockchain-based data synchronization method provided in this specification.

In this embodiment, the first storage attribute and the second storage attribute corresponding to each block can be added to the world state of the block chain, so as to determine whether each block is an empty block and the non-empty block with the closest block height based on these attributes. piece. The recording process of these two attributes will be described first below.

1. The first storage attribute

In this embodiment, the first storage attribute corresponding to each block can be set in the world state of the blockchain. The first storage attribute indicates whether the block is an empty block. For example, see Figure 2, when the attribute value is "1" When , it indicates that this block is a non-empty block, and when the attribute value is "0", it indicates that this block is an empty block.

The first attribute can be generated in the following manner.

In an example, a blockchain node may receive a business transaction, and the business transaction may be initiated by a user or a blockchain platform, and there is no special limitation on this. After the blockchain node receives the business transaction, it can reach a consensus on the business transaction. After the consensus is completed, the business transaction will be stored in the corresponding block, and then the business transaction can be executed. When executing the business transaction, on the one hand, business-related operations (such as changing the balance of the remittance parties' accounts) can be performed, and on the other hand, related operations on the first attribute record can also be performed. Since the business transaction is stored in the block, that is, it is a non-empty block, the first attribute record logic in the smart contract can be called to record the first storage attribute indicating that the block in which the business transaction is located is a non-empty block. For example, still taking the example shown in Figure 2 as an example, assuming that the business transaction is stored in block n, the business transaction can be executed to record the first storage attribute corresponding to block n, and the attribute value is set to "1" .

Among them, there may be some blocks on the block chain that do not store business transactions, so it is impossible to record the first storage attribute corresponding to the blocks by executing business transactions. Then, when determining whether each block is a non-empty block based on the first storage attribute, the block whose corresponding first storage attribute cannot be obtained may be determined as an empty block.

In another example, the blockchain node may also receive the first storage attribute record transaction. Similarly, the first storage attribute record transaction may be initiated by, for example, the blockchain platform or other parties, and there is no special limitation on this. After the blockchain node receives the first storage attribute record transaction, it can reach a consensus on the first storage attribute record transaction. After the consensus is completed, the first storage attribute record transaction can be stored in the corresponding block, and then the transaction can be executed. The first storage attribute records the transaction to call the first storage attribute recording logic in the smart contract to determine whether the block where the first storage attribute generates the transaction stores a business transaction, and if so, determines that the block is a non-empty block; If not, it is determined that the block is an empty block. Then, the first storage attribute corresponding to the block may be recorded according to the judgment result.

Wherein, the first storage attribute record transaction may be sent periodically, and the sending cycle may be the same as the block forming cycle on the blockchain. For example, when the blockchain generates blocks periodically during consensus, for example, one block is generated every second, the sending cycle of the first storage attribute record transaction can also be every second.

In this way, the first storage attribute record transaction can be stored in each block, so as to record the first storage attribute based on the transaction. The above example solves the problem that the business transaction cannot be executed to record the first storage attribute corresponding to the block because there is no business transaction stored in the block.

Moreover, in this specification, the above two methods can also be used at the same time, that is, a business transaction can be executed to record the first storage attribute, and a first storage attribute recording transaction can be executed to record the first storage attribute. Moreover, when the block stores both the business transaction and the first storage attribute record transaction, the result obtained from the later execution of the transaction can be used to overwrite the result of the previous execution of the transaction. Of course, other methods can also be adopted. This embodiment There are no particular restrictions on this.

In other embodiments, the first storage attribute can also represent whether the previous block of this block is an empty block, for example, when the attribute value is "1", it indicates that the previous block of this block is a non-empty block, and the attribute When the value is "0", it indicates that the previous block of this block is an empty block.

In this case, the first storage attribute may be recorded in the following manner.

In one example, a blockchain node may receive a business transaction, and execute the business transaction to call the first storage attribute record logic in the smart contract to determine whether the business transaction is stored in the previous block of the block where the business transaction is located , and record the first storage attribute of the block where the business transaction is located based on the judgment result. For details, reference may be made to the aforementioned embodiments, and details will not be repeated here in this specification.

Similarly, there may be some blocks on the blockchain that do not store business transactions, so it is impossible to record the first storage attribute corresponding to the blocks by executing business transactions. Then, when determining whether each block is a non-empty block based on the first storage attribute, the block preceding the block for which the corresponding first storage attribute cannot be obtained may be determined as an empty block.

In another example, the blockchain node may also receive the first storage attribute record transaction. Similarly, there is no special restriction on the initiator of the first storage attribute record transaction. After the blockchain node receives the first storage attribute record transaction, it can reach a consensus on the first storage attribute record transaction. After the consensus is completed, the first storage attribute record transaction can be stored in the corresponding block, and then the transaction can be executed. The first storage attribute record transaction is used to call the third storage attribute record logic in the smart contract to judge whether the previous block of the block where the first storage attribute record transaction is located has business transactions stored, and if so, determine the previous block The block is a non-empty block; if not, it is determined that the previous block is an empty block. Then, the first storage attribute corresponding to the block may be recorded according to the judgment result.

Similarly, the first storage attribute record transaction can be sent periodically, and the sending cycle can also be the same as the block forming cycle on the blockchain.

Using the above method, since each block in the blockchain is consensused in order, when the first storage attribute record transaction on a block is executed, the previous block should have been consensus completed, then The result of whether the previous block is an empty block obtained by executing the first storage attribute record transaction judgment is accurate, which can avoid the problem of inaccurate judgment results caused by the failure of consensus on the transaction.

Of course, the above examples are only some exemplary examples provided in this specification, and other methods can also be adopted in practical applications to determine whether each block is an empty block, and this specification does not give examples one by one here.

2. The second storage attribute

In this embodiment, the second storage attribute may represent a non-empty block whose block height is closest to the current block.

In an example, a blockchain node may receive a business transaction, and execute the business transaction to call the second storage attribute recording logic in the smart contract to determine the non-block height closest to the block where the business transaction is located. An empty block, and based on the non-empty block, record the second storage attribute corresponding to the block where the business transaction is located. For details, reference may be made to the aforementioned embodiments, and details will not be repeated here in this specification.

In another example, the blockchain node may also receive the second storage attribute record transaction. Similarly, there is no special restriction on the initiator of the second storage attribute record transaction. After the blockchain node receives the second storage attribute record transaction, it can reach a consensus on the second storage attribute record transaction. After the consensus is completed, the second storage attribute record transaction can be stored in the corresponding block, and then the transaction can be executed. The second storage attribute record transaction is used to call the second storage attribute generation logic in the smart contract to determine the non-empty block closest to the block height of the block where the second storage attribute record transaction is located, and record according to the non-empty block The second storage attribute records the second storage attribute corresponding to the block where the transaction is located.

Similarly, the second storage attribute record transaction can be sent periodically, and the sending cycle can also be the same as the block forming cycle on the blockchain.

Certainly, the above-mentioned examples are only some exemplary examples provided in this specification, and other methods may also be adopted in practical applications to determine the non-empty block with the closest block height, and this specification does not give examples one by one here.

After clarifying the above-mentioned method of adding the attributes corresponding to each block in the world state and the method of generating the attributes, the data synchronization method based on the blockchain will be described below.

Please refer to FIG. 3. FIG. 3 is a schematic flowchart of another blockchain-based data synchronization method shown in an exemplary embodiment of this specification. The method may include the following steps:

Step 302, determine whether a trigger condition for data synchronization is met. If yes, execute step 304 .

In this embodiment, the method for determining whether a trigger condition for data synchronization is met may refer to the foregoing embodiments, and details are not repeated here.

Step 304: Obtain the first storage attribute corresponding to the latest block from the blockchain node, and determine whether the latest block is a non-empty block based on the first storage attribute. If not, execute steps 306-308; if yes, execute step 310.

Step 306: Obtain the second storage attribute corresponding to the latest block from the blockchain node, and determine the non-empty block closest to the block height of the latest block based on the second storage attribute.

Step 308, adding the non-empty block to the synchronization queue, and determining whether the previous block is a non-empty block based on the first storage attribute corresponding to the previous block of the non-empty block.

In this embodiment, processing can be started from the latest block on the blockchain node to determine whether the latest block is a non-empty block. For example, the first storage attribute corresponding to the latest block can be obtained from the blockchain node, and the first storage attribute can indicate whether the block is a non-empty block. The non-empty block is determined based on the first storage attribute. Wherein, the method of obtaining the first attribute (world state) from the blockchain can refer to related technologies, and this embodiment will not describe them one by one here.

If the latest block is an empty block, the second storage attribute corresponding to the latest block can be obtained from the blockchain node. The second storage attribute may characterize the closest non-empty block to the block height of the block. A non-empty block may be determined according to the second storage attribute, and the non-empty block is added to the synchronization queue.

Moreover, it can also be judged whether the previous block of the non-empty block is a non-empty block. For example, the first storage attribute corresponding to the previous empty block can be obtained from the blockchain node to determine whether it is a non-empty block, and if it is a non-empty block, add it to the synchronization queue; if it is an empty block Get the non-empty block with the closest block height and add it to the synchronization queue. and so on.

Step 310, adding the latest block into the synchronization queue, and determining whether the previous block of the latest block is a non-empty block based on the first storage attribute corresponding to the previous block of the latest block.

In this embodiment, if the latest block is a non-empty block, the latest empty block can be added to the synchronization queue. And judge whether the previous block of the latest empty block is a non-empty block, for example, the first storage attribute corresponding to the previous empty block can be obtained to determine whether it is a non-empty block, and if it is a non-empty block, upload it The stored business transaction is added to the synchronization queue, and in the case of an empty block, the non-empty block with the closest block height is obtained, and the business transaction stored on the non-empty block is added to the synchronization queue. and so on.

Step 312, after determining each non-empty block in the blockchain, synchronize the data on each block in the synchronization queue.

In this embodiment, each non-empty block in the blockchain can be determined by using the method of the foregoing steps, and the business transactions in these non-empty blocks can be added to the synchronization queue. Then perform data synchronization on the business transactions stored on each block in the synchronization queue. For details, reference may be made to the foregoing embodiments, and details are not repeated here.

In other embodiments, data synchronization on the blockchain can also be performed in batches. For example, a sliding window that can contain a specified number of blocks can be preset. For example, the size of the sliding window is 10 blocks or 5 blocks. synchronization.

Still taking the example shown in Figure 2 as an example, assuming that the size of the sliding window is 4 blocks, the sliding window can be used to determine block n-block n-3, block n-4~block n-7, ... ..., and then perform data synchronization processing for each sliding window.

Taking the sliding window corresponding to block n ~ block n-3 as an example, you can first judge whether block n is an empty block, and if it is not empty, add block n to the synchronization queue, and then continue to judge block n -1 Whether it is an empty block, if it is found to be an empty block, it will not be added to the synchronization queue, and the nearest non-empty block is determined to be block n-3, then block n-3 will be added to the synchronization queue. And block n-3 is the last block in the sliding window, it can be determined that the processing of the sliding window is completed, and data synchronization can be performed on the synchronization queue corresponding to the sliding window.

Similarly, other sliding windows can also be processed by the above method. Moreover, each sliding window can be processed in parallel or serially, which can be set according to actual business scenarios.

It can be seen from the above description that in one embodiment of this specification, several attributes can be added to the world state of the blockchain, based on these attributes to determine whether each block is an empty block, the non-empty block with the closest block height . Therefore, in the process of data synchronization, empty blocks and non-empty blocks are determined to perform data synchronization on non-empty blocks, without the need to process all blocks on the blockchain, which can improve the efficiency of data synchronization.

Corresponding to the aforementioned embodiments of the blockchain-based data synchronization method, this specification also provides embodiments of a blockchain-based data synchronization device.

The embodiment of the blockchain-based data synchronization device in this specification can be applied to electronic equipment. The device embodiments can be implemented by software, or by hardware or a combination of software and hardware. Taking software implementation as an example, as a device in a logical sense, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory for operation by the processor of the electronic device where it is located. From the hardware level, as shown in Figure 4, it is a hardware structure diagram of the electronic device where the blockchain-based data synchronization device in this manual is located, except for the processor, memory, network interface, and non-volatile memory shown in Figure 4 In addition to the volatile memory, the electronic device where the device in the embodiment is located usually may also include other hardware according to the actual function of the electronic device, which will not be repeated here.

Please refer to FIG. 5 , the block chain-based data synchronization device can be applied in the aforementioned electronic device shown in FIG. 4 , including: an acquisition unit 510 , a determination unit 520 and a synchronization unit 530 .

Wherein, the acquisition unit 510, when the trigger condition of data synchronization is reached, acquires the first storage attribute of each block on the blockchain from the blockchain node; the determination unit 520 determines whether each block is non-empty block, and add the business transaction in the block that is determined as the non-empty block to the synchronization queue, and the non-empty block is a block that stores the business transaction; the synchronization unit 530 synchronizes the business transaction in the synchronization queue to the business system.

Optionally, the first storage attribute indicates whether the current block is a non-empty block, and the determining unit 520 determines whether each block is a non-empty block based on the first storage attribute: starting from the latest block, According to the sequence of block heights from high to low, it is sequentially judged whether each block is a non-empty block based on the first storage attribute of each block.

Optionally, the first storage attribute indicates whether the current block is a non-empty block, and the determining unit 520 determines whether each block is a non-empty block based on the first storage attribute: based on the latest block corresponding The first storage attribute judges whether the latest block is a non-empty block; if the latest block is a non-empty block, then judge whether the previous block of the latest block is a non-empty block; if the latest block block is an empty block, then determine the non-empty block closest to the block height of the latest block, and judge whether the previous block of the non-empty block is a non-empty block.

Optionally, the recording process of the first storage attribute includes: after the blockchain node receives the business transaction, executes the business transaction to call the first storage attribute record logic record in the smart contract to represent the business exchange The block is the first storage attribute of a non-empty block.

Optionally, the recording process of the first storage attribute includes: after the blockchain node receives the first storage attribute record transaction sent periodically, executes the first storage attribute record transaction to call the first storage attribute record transaction in the smart contract A storage attribute record logic judges whether a business transaction is stored on the block of the first storage attribute record transaction, and records the first storage attribute corresponding to the block where the first storage attribute record transaction is located based on the judgment result.

Optionally, the second storage attribute corresponding to each block is stored on the block chain node, and the second storage attribute represents the non-empty block closest to the block height of the block, and the determining unit 520 When determining the non-empty block closest to the block height of the latest block: obtaining the second storage attribute corresponding to the latest block from the blockchain node; The block whose block height is closest to the non-empty block.

Optionally, the recording process of the second storage attribute includes: after the blockchain node receives the business transaction, executes the business transaction to call the second storage attribute recording logic in the smart contract to determine the business transaction In the non-empty block closest to the block height of the block, and based on the non-empty block, record the second storage attribute corresponding to the block where the business transaction is located.

Optionally, the recording process of the second storage attribute includes: after the block chain node receives the second storage attribute record transaction sent periodically, execute the second storage attribute record transaction to call the first storage attribute record transaction in the smart contract The second storage attribute recording logic determines the non-empty block closest to the block height of the block where the second storage attribute update transaction is located, and records the block where the second storage attribute update transaction resides based on the non-empty block The corresponding second storage attribute.

Optionally, the first storage attribute indicates whether the previous block of this block is an empty block, and the determining unit 520 determines whether each block is a non-empty block based on the first storage attribute: for all The latest block, based on the first storage attribute to determine whether the previous block of the latest block is a non-empty block; if the previous block is a non-empty block, then based on the previous block corresponding The first storage attribute judges whether the previous block of the previous block is a non-empty block; if the previous block is an empty block, then determine the block height closest to the previous block a non-empty block, and judge whether the previous block of the non-empty block is an empty block based on the first storage attribute corresponding to the non-empty block.

Optionally, the recording process of the first storage attribute includes: after the blockchain node receives the first storage attribute record transaction sent periodically, executes the first storage attribute record transaction to call the first storage attribute record transaction in the smart contract Three storage attribute record logic judges whether the previous block of the first storage attribute record transaction stores business transactions, and generates the first storage attribute record transaction corresponding to the first block based on the judgment result. store attributes.

Optionally, the trigger condition for data synchronization includes: after receiving a data synchronization request; and/or reaching a data synchronization period.

For the implementation process of the functions and effects of each unit in the above device, please refer to the implementation process of the corresponding steps in the above method for details, and will not be repeated here.

As for the device embodiment, since it basically corresponds to the method embodiment, for related parts, please refer to the part description of the method embodiment. The device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in One place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution in this specification. It can be understood and implemented by those skilled in the art without creative effort.

The systems, devices, modules, or units described in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementing device is a computer, which may take the form of a personal computer, laptop computer, cellular phone, camera phone, smart phone, personal digital assistant, media player, navigation device, e-mail device, game control device, etc. desktops, tablets, wearables, or any combination of these.

Corresponding to the aforementioned embodiments of the blockchain-based data synchronization method, this specification also provides a blockchain-based data synchronization device, which includes: a processor and a memory for storing machine-executable instructions. Wherein, the processor and the memory are usually connected to each other by an internal bus. In other possible implementation manners, the device may further include an external interface, so as to be able to communicate with other devices or components.

In this embodiment, by reading and executing the machine-executable instructions stored in the memory and corresponding to the blockchain-based data synchronization logic, the processor is prompted to: a blockchain-based data synchronization method, Applied to a data synchronization system, the data synchronization system is docked with a block chain node, and the method includes: when a trigger condition for data synchronization is reached, obtaining the first storage attribute of each block on the block chain from the block chain node; Determine whether each block is a non-empty block based on the first storage attribute, and add the business transaction in the block that is determined to be a non-empty block to the synchronization queue, and the non-empty block is a block that stores a business transaction; The business transactions in the synchronization queue are synchronized to the business system.

Optionally, the first storage attribute indicates whether the current block is a non-empty block, and when determining whether each block is a non-empty block based on the first storage attribute, the processor is prompted to: start from the latest block At first, according to the order of block height from high to low, it is judged whether each block is a non-empty block based on the first storage attribute of each block.

Optionally, the first storage attribute indicates whether the current block is a non-empty block, and when determining whether each block is a non-empty block based on the first storage attribute, the processor is prompted: based on the latest block The corresponding first storage attribute judges whether the latest block is a non-empty block; if the latest block is a non-empty block, then judges whether the previous block of the latest block is a non-empty block; if the If the latest block is an empty block, determine the non-empty block closest to the block height of the latest block, and determine whether the previous block of the non-empty block is a non-empty block.

Optionally, in the recording process of the first storage attribute, the processor is prompted: after the blockchain node receives the business transaction, execute the business transaction to call the first storage attribute in the smart contract to record the logical record representation The block in which the business transaction is located is the first storage attribute of a non-empty block.

Optionally, in the recording process of the first storage attribute, the processor is prompted: after the blockchain node receives the first storage attribute record transaction sent periodically, executes the first storage attribute record transaction to call The logic of the first storage attribute record in the smart contract judges whether there is a business transaction stored in the block of the first storage attribute record exchange, and records the first storage attribute record transaction corresponding to the block based on the judgment result. A stored attribute.

Optionally, the second storage attribute corresponding to each block is stored on the block chain node, and the second storage attribute represents the non-empty block closest to the block height of this block. When the non-empty block whose block height is the closest, the processor is prompted to: obtain the second storage attribute corresponding to the latest block from the blockchain node; The non-empty block closest to the block height of the latest block.

Optionally, in the recording process of the second storage attribute, the processor is prompted: after the blockchain node receives the business transaction, executes the business transaction to call the second storage attribute recording logic in the smart contract to determine and The non-empty block with the closest block height of the block where the business transaction is located, and record the second storage attribute corresponding to the block where the business transaction is located based on the non-empty block.

Optionally, in the process of recording the second storage attribute, the processor is prompted: after the blockchain node receives the periodically sent second storage attribute record transaction, executes the second storage attribute record transaction to call The second storage attribute recording logic in the smart contract determines the non-empty block closest to the block height of the block where the second storage attribute update transaction is located, and records the second storage attribute update based on the non-empty block The second storage attribute corresponding to the block where the transaction is located.

Optionally, the first storage attribute indicates whether the previous block of the current block is an empty block, and when determining whether each block is a non-empty block based on the first storage attribute, the processor is prompted to: For the latest block, determine whether the previous block of the latest block is a non-empty block based on the first storage attribute; if the previous block is a non-empty block, then based on the previous block The first storage attribute corresponding to the block judges whether the previous block of the previous block is a non-empty block; if the previous block is an empty block, then determine the block height closest to the previous block a non-empty block that is close to it, and judge whether the previous block of the non-empty block is an empty block based on the first storage attribute corresponding to the non-empty block.

Optionally, in the recording process of the first storage attribute, the processor is prompted: after the blockchain node receives the first storage attribute record transaction sent periodically, executes the first storage attribute record transaction to call The third storage attribute record logic in the smart contract judges whether the previous block of the first storage attribute record transaction stores business transactions, and generates the first storage attribute record transaction area based on the judgment result The first storage attribute corresponding to the block.

Corresponding to the aforementioned embodiments of the blockchain-based data synchronization method, this specification also provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the following is achieved: Steps: a blockchain-based data synchronization method applied to a data synchronization system, the data synchronization system is connected to a blockchain node, and the method includes: when a trigger condition for data synchronization is reached, the data is obtained from the blockchain node The first storage attribute of each block on the block chain; determine whether each block is a non-empty block based on the first storage attribute, and add the business transaction in the block determined to be a non-empty block to the synchronization queue, the Non-empty blocks are blocks that store business transactions; synchronize the business transactions in the synchronization queue to the business system.

Optionally, the first storage attribute indicates whether the block is a non-empty block, and determining whether each block is a non-empty block based on the first storage attribute includes: starting from the latest block, according to the block In order of height from high to low, it is determined whether each block is a non-empty block based on the first storage attribute of each block.

Optionally, the first storage attribute indicates whether the current block is a non-empty block, and determining whether each block is a non-empty block based on the first storage attribute includes: based on the first storage corresponding to the latest block attribute to determine whether the latest block is a non-empty block; if the latest block is a non-empty block, then judge whether the previous block of the latest block is a non-empty block; if the latest block is empty block, then determine the non-empty block closest to the block height of the latest block, and judge whether the previous block of the non-empty block is a non-empty block.

Optionally, the second storage attribute corresponding to each block is stored on the block chain node, the second storage attribute represents the non-empty block closest to the block height of the block, and the determination is related to the The non-empty block whose block height is closest to the latest block includes: obtaining the second storage attribute corresponding to the latest block from the blockchain node; determining the relationship between the latest block and the latest block based on the second storage attribute The closest non-empty block to the block height.

Optionally, the first storage attribute indicates whether the previous block of this block is an empty block, and the determining whether each block is a non-empty block based on the first storage attribute includes: for the latest block block, based on the first storage attribute to determine whether the previous block of the latest block is a non-empty block; if the previous block is a non-empty block, based on the first block corresponding to the previous block The storage attribute judges whether the previous block of the previous block is a non-empty block; if the previous block is an empty block, then determine the non-empty block closest to the block height of the previous block , and judge whether the previous block of the non-empty block is an empty block based on the first storage attribute corresponding to the non-empty block.

The foregoing describes specific embodiments of this specification. Other implementations are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. Multitasking and parallel processing are also possible or may be advantageous in certain embodiments.

The above descriptions are only preferred embodiments of this specification, and are not intended to limit this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification shall be included in this specification. within the scope of protection.

Claims

A block chain-based data synchronization method applied to a data synchronization system, the data synchronization system docking with a block chain node, the method comprising:

When the trigger condition of data synchronization is reached, the first storage attribute of each block on the blockchain is obtained from the blockchain node;

Determine whether each block is a non-empty block based on the first storage attribute, and add the business transaction in the block determined to be a non-empty block to the synchronization queue, and the non-empty block is a block storing a business transaction;

Synchronize the business transactions in the synchronization queue to the business system.
According to the method according to claim 1, the first storage attribute indicates whether the block is a non-empty block, and determining whether each block is a non-empty block based on the first storage attribute includes:

Starting from the latest block, according to the sequence of block height from high to low, it is judged whether each block is a non-empty block based on the first storage attribute of each block.
According to the method according to claim 1, the first storage attribute indicates whether the block is a non-empty block, and determining whether each block is a non-empty block based on the first storage attribute includes:

judging whether the latest block is a non-empty block based on the first storage attribute corresponding to the latest block;

If the latest block is a non-empty block, then judging whether the previous block of the latest block is a non-empty block;

If the latest block is an empty block, determine the non-empty block closest to the block height of the latest block, and determine whether the previous block of the non-empty block is a non-empty block.
According to the method according to claim 2 or 3, the recording process of the first storage attribute comprises:

After the blockchain node receives the business transaction, it executes the business transaction to call the first storage attribute record logic in the smart contract to record the first storage attribute that indicates that the block in which the business transaction is located is a non-empty block.
According to the method according to claim 2 or 3, the recording process of the first storage attribute comprises:

After the block chain node receives the first storage attribute record transaction sent periodically, execute the first storage attribute record transaction to call the first storage attribute record logic in the smart contract to determine the location of the first storage attribute record transaction Whether there is a business transaction stored in the block, and based on the judgment result, record the first storage attribute corresponding to the block where the transaction is located.
According to the method according to claim 3, the second storage attribute corresponding to each block is stored on the block chain node, and the second storage attribute represents the non-empty block closest to the block height of this block, and the Determine the non-empty block closest to the block height of the latest block, including:

Obtaining the second storage attribute corresponding to the latest block from the blockchain node;

Determine a non-empty block closest to the block height of the latest block based on the second storage attribute.
According to the method according to claim 6, the recording process of the second storage attribute comprises:

After the blockchain node receives the business transaction, it executes the business transaction to call the second storage attribute recording logic in the smart contract to determine the non-empty block closest to the block height of the block where the business transaction is located, and based on The non-empty block records the second storage attribute corresponding to the block where the business transaction is located.
According to the method according to claim 6, the recording process of the second storage attribute comprises:

After receiving the periodically sent second storage attribute record transaction, the block chain node executes the second storage attribute record transaction to call the second storage attribute record logic in the smart contract to determine the exchange with the second storage attribute update In the non-empty block closest to the block height of the block, and based on the second storage attribute recorded in the non-empty block, the second storage attribute corresponding to the block where the transaction is located is updated.
According to the method according to claim 1, the first storage attribute indicates whether the previous block of the current block is an empty block, and determining whether each block is a non-empty block based on the first storage attribute includes:

For the latest block, determine whether the previous block of the latest block is a non-empty block based on the first storage attribute;

If the previous block is a non-empty block, then judging whether the previous block of the previous block is a non-empty block based on the first storage attribute corresponding to the previous block;

If the previous block is an empty block, determine the non-empty block closest to the block height of the previous block, and judge the non-empty block based on the first storage attribute corresponding to the non-empty block Whether the previous block of is an empty block.
According to the method according to claim 9, the recording process of the first storage attribute comprises:

After receiving the periodically sent first storage attribute record transaction, the blockchain node executes the first storage attribute record transaction to call the third storage attribute record logic in the smart contract to determine the location of the first storage attribute record transaction. Whether the previous block of the block stores business transactions, and based on the judgment result, generate the first storage attribute corresponding to the block where the first storage attribute records the transaction.
According to the method according to claim 1, the triggering conditions for data synchronization include:

After a data synchronization request is received; and/or a data synchronization period is reached.
A data synchronization device based on blockchain, including:

The acquisition unit, when the trigger condition of data synchronization is reached, acquires the first storage attribute of each block on the blockchain from the blockchain node;

The determination unit determines whether each block is a non-empty block based on the first storage attribute, and adds the business transaction in the block determined to be a non-empty block to the synchronization queue, and the non-empty block is an area storing a business transaction piece;

The synchronization unit synchronizes the business transactions in the synchronization queue to the business system.
According to the device according to claim 12, the first storage attribute represents whether the block is a non-empty block, and when the determining unit determines whether each block is a non-empty block based on the first storage attribute:

Starting from the latest block, according to the order of block height from high to low, judge whether each block is a non-empty block based on the first storage attribute of each block.
According to the device according to claim 12, the first storage attribute represents whether the block is a non-empty block, and when the determining unit determines whether each block is a non-empty block based on the first storage attribute:

judging whether the latest block is a non-empty block based on the first storage attribute corresponding to the latest block;

If the latest block is a non-empty block, then judging whether the previous block of the latest block is a non-empty block;

If the latest block is an empty block, determine the non-empty block closest to the block height of the latest block, and determine whether the previous block of the non-empty block is a non-empty block.
According to the device according to claim 13 or 14, the recording process of the first stored attribute comprises:

After the blockchain node receives the business transaction, it executes the business transaction to call the first storage attribute record logic in the smart contract to record the first storage attribute that indicates that the block in which the business transaction is located is a non-empty block.
According to the device according to claim 13 or 14, the recording process of the first stored attribute comprises:

After the block chain node receives the first storage attribute record transaction sent periodically, execute the first storage attribute record transaction to call the first storage attribute record logic in the smart contract to determine the location of the first storage attribute record transaction Whether there is a business transaction stored in the block, and based on the judgment result, record the first storage attribute corresponding to the block where the transaction is located.
According to the device according to claim 14, the second storage attribute corresponding to each block is stored on the block chain node, and the second storage attribute represents the non-empty block closest to the block height of the block, and the When the determination unit determines the non-empty block closest to the block height of the latest block:

Obtaining the second storage attribute corresponding to the latest block from the blockchain node;

Determine a non-empty block closest to the block height of the latest block based on the second storage attribute.
According to the device according to claim 17, the recording process of the second storage attribute comprises:

After the blockchain node receives the business transaction, it executes the business transaction to call the second storage attribute recording logic in the smart contract to determine the non-empty block closest to the block height of the block where the business transaction is located, and based on The non-empty block records the second storage attribute corresponding to the block where the business transaction is located.
According to the device according to claim 17, the recording process of the second storage attribute comprises:

After receiving the periodically sent second storage attribute record transaction, the block chain node executes the second storage attribute record transaction to call the second storage attribute record logic in the smart contract to determine the exchange with the second storage attribute update In the non-empty block closest to the block height of the block, and based on the second storage attribute recorded in the non-empty block, the second storage attribute corresponding to the block where the transaction is located is updated.
According to the device according to claim 12, the first storage attribute indicates whether the previous block of the current block is an empty block, and the determination unit determines whether each block is a non-empty block based on the first storage attribute :

For the latest block, determine whether the previous block of the latest block is a non-empty block based on the first storage attribute;

If the previous block is a non-empty block, then judging whether the previous block of the previous block is a non-empty block based on the first storage attribute corresponding to the previous block;

If the previous block is an empty block, determine the non-empty block closest to the block height of the previous block, and judge the non-empty block based on the first storage attribute corresponding to the non-empty block Whether the previous block of is an empty block.
According to the device according to claim 20, the recording process of the first stored attribute comprises:

After receiving the periodically sent first storage attribute record transaction, the blockchain node executes the first storage attribute record transaction to call the third storage attribute record logic in the smart contract to determine the location of the first storage attribute record transaction. Whether the previous block of the block stores business transactions, and based on the judgment result, generate the first storage attribute corresponding to the block where the first storage attribute records the transaction.
According to the device according to claim 12, the triggering conditions for data synchronization include:

After a data synchronization request is received; and/or a data synchronization period is reached.
A data synchronization device based on blockchain, including:

processor;

memory for storing machine-executable instructions;

Wherein, by reading and executing the machine-executable instructions stored in the memory and corresponding to the blockchain-based data synchronization logic, the processor is caused to:

When the trigger condition of data synchronization is reached, the first storage attribute of each block on the blockchain is obtained from the blockchain node;

Determine whether each block is a non-empty block based on the first storage attribute, and add the business transaction in the block determined to be a non-empty block to the synchronization queue, and the non-empty block is a block storing a business transaction;

Synchronize the business transactions in the synchronization queue to the business system.