CN109710695B

CN109710695B - Transaction request validity identification and initiation method, device, equipment and medium

Info

Publication number: CN109710695B
Application number: CN201811605439.1A
Authority: CN
Inventors: 肖伟
Original assignee: Baidu Online Network Technology Beijing Co Ltd
Current assignee: Baidu Online Network Technology Beijing Co Ltd
Priority date: 2018-12-26
Filing date: 2018-12-26
Publication date: 2021-10-08
Anticipated expiration: 2038-12-26
Also published as: CN109710695A

Abstract

The embodiment of the invention discloses a method, a device, equipment and a medium for identifying and initiating validity of a transaction request. The transaction request validity identification method is applied to the block chain node and comprises the following steps: acquiring a transaction request and validity check data transmitted in a blockchain network, wherein the validity check data corresponds to a pre-execution numerical value of dependent data in the transaction request execution process; reading a corresponding numerical value of validity verification data from locally stored block chain data, and determining the numerical value change condition of the validity verification data according to the locally read numerical value; and determining the validity of the transaction request according to the value change condition. By adopting the technical scheme of the embodiment of the invention, the transaction request independent of UTXO can be accurately identified in validity, so that the correct execution of the transaction request is ensured, and a new thought is provided for determining the validity of the transaction request.

Description

Transaction request validity identification and initiation method, device, equipment and medium

Technical Field

The embodiment of the invention relates to a block chain data processing technology, in particular to a transaction request validity identification and initiation method, a device, equipment and a medium.

Background

At present, part of the blockchain system realizes Transaction transfer through an Unspent Transaction Output (UTXO), and meanwhile, many blockchain systems process Transaction requests through an intelligent contract or by combining the intelligent contract and the UTXO.

The validity of the transaction request needs to be judged before the transaction request is executed. Validity at least includes whether the transaction request has been executed or not, and if the transaction request has been executed, the transaction request is invalid. For transaction requests that depend on a UTXO, a determination may be made by identifying whether the UTXO that depends on is valid. When the transaction request is executed, the dependent UTXO is spent and is no longer in a valid state and therefore cannot be executed once again.

However, in many cashless blockchain systems, rather than transferring money from the UTXO, other transaction requests are processed, and the validity of the transaction request is difficult to determine. If the validity of the transaction request cannot be effectively determined, it is possible that a legitimate transaction request may be executed multiple times, against the intent of the requestor initiating the transaction, or against the benefit of the requestor.

Disclosure of Invention

Embodiments of the present invention provide a method, an apparatus, a device, and a medium for identifying and initiating validity of a transaction request, so as to implement accurate validity identification of a transaction request that does not depend on a UTXO, and ensure correct execution of the transaction request.

In a first aspect, an embodiment of the present invention provides a method for identifying validity of a transaction request of a block chain, where the method is applied to a block chain node, and the method may include:

acquiring a transaction request and validity check data transmitted in a blockchain network, wherein the validity check data corresponds to a pre-execution numerical value of dependent data in the transaction request execution process;

reading a corresponding numerical value of validity verification data from locally stored block chain data, and determining the numerical value change condition of the validity verification data according to the locally read numerical value;

and determining the validity of the transaction request according to the value change condition. .

In a second aspect, an embodiment of the present invention further provides a method for initiating a transaction request of a blockchain, where the method includes:

generating a transaction request;

generating validity checking data, and binding the validity checking data with the transaction request, wherein the validity checking data is a pre-execution numerical value of dependent data in the transaction request execution process;

initiating the transaction request and the validity check data in a blockchain network;

the validity check data is used for the block chain nodes to read corresponding values of the validity check data from the locally stored block chain data, and the value change condition of the validity check data is determined according to the locally read values; and determining the validity of the transaction request according to the value change condition.

In a third aspect, an embodiment of the present invention further provides a device for identifying validity of a transaction request of a block chain, where the device is configured at a node of the block chain, and the device includes:

an obtaining module, configured to obtain a transaction request and validity check data transmitted in a blockchain network, where the validity check data corresponds to a pre-execution numerical value of dependent data in an execution process of the transaction request;

the value change determining module is used for reading a corresponding value of the validity verification data from the locally stored block chain data and determining the value change condition of the validity verification data according to the locally read value;

and the validity determining module is used for determining the validity of the transaction request according to the value change condition.

In a fourth aspect, an embodiment of the present invention further provides a device for initiating a transaction request of a blockchain, where the device includes:

a request generation module for generating a transaction request;

the data generation and binding module is used for generating validity check data and binding the validity check data with the transaction request, wherein the validity check data is a pre-execution numerical value of the dependent data in the transaction request execution process;

an initiating module for initiating the transaction request and the validity check data in a blockchain network;

In a fifth aspect, an embodiment of the present invention further provides an apparatus, where the apparatus includes:

one or more processors;

storage means for storing one or more programs;

when the one or more programs are executed by the one or more processors, the one or more processors implement the method for identifying validity of a transaction request of a blockchain in the first aspect, or implement the method for initiating a transaction request of a blockchain in the second aspect.

In a sixth aspect, an embodiment of the present invention further provides a storage medium, where a computer program is stored, and when executed by a processor, the program implements the method for identifying validity of a transaction request of a blockchain according to any of the first aspects, or implements the method for initiating a transaction request of a blockchain according to any of the second aspects.

According to the method, the device, the equipment and the medium for identifying and initiating the validity of the transaction request of the block chain, before the transaction request is processed, the value change condition of the validity verification data is determined according to the comparison result by comparing the corresponding value of the validity verification data read from the block chain data stored locally with the value before the execution of the validity verification data acquired from the block chain network; and then the validity of the transaction request can be determined according to the value change condition. Compared with the prior art, the embodiment provides a new idea for determining the validity of the transaction request, and realizes that validity identification can be accurately performed on the transaction request independent of the UTXO, so as to ensure correct execution of the transaction request.

Drawings

Fig. 1 is a flowchart of a method for identifying validity of a transaction request of a blockchain according to an embodiment of the present invention;

fig. 2 is a flowchart of a method for identifying validity of a transaction request of a blockchain according to a second embodiment of the present invention;

fig. 3 is a flowchart of a method for initiating a transaction request of a blockchain according to a third embodiment of the present invention;

fig. 4 is a flowchart of a method for initiating a transaction request of a blockchain according to a fourth embodiment of the present invention;

fig. 5 is a flowchart of a method for transaction request initiation and validity identification of a blockchain according to a fifth embodiment of the present invention;

fig. 6 is a schematic structural diagram of an apparatus for identifying validity of a transaction request of a blockchain according to a sixth embodiment of the present invention;

fig. 7 is a schematic structural diagram of a transaction request initiating device of a blockchain provided in a seventh embodiment of the present invention;

fig. 8 is a schematic structural diagram of an apparatus provided in the eighth embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.

Before describing embodiments of the present invention, a description will be given of a memory system that can be used in embodiments of the present invention. The Key Value pair (KV) storage system can be selected as the bottom storage system for the block chain link points, and further, the KV storage system is a multi-version KV storage system,

In a multi-version KV storage system, a key field (key) and a value field (value) are included in the storage unit of each key-value pair. The key domain stores a key identifier and a version identifier, and the key identifier can be an identifier capable of reflecting the actual meaning of data, such as a block identifier or a transaction identifier; the value field of the key-value pair may be used to store the data itself. The version identification is used to identify the version to which the key-value pair was modified during execution of the data processing request.

One version of the data processing request may correspond to one version, or may correspond to a plurality of versions. For example, a block generation process may involve multiple transaction requests, and may also require multiple data processing requests, such as writing data, deleting data, reading data, changing data, and so on. It can be configured that a plurality of data processing requests required to be executed in one tile generation process correspond to one version identification. The next block corresponds to the next version id.

For example, if a transaction request in a block transfers a set amount of money from account a to account B, the key-value pairs of the account balances stored in account a and account B will change as the transaction request is executed. And (3) remaining the old key-value pairs of the account balances of the account A and the account B, generating new key-value pairs of the account balances, and changing the version identifications of the former and later key-value pairs.

Of course, a version id may also correspond to the processing procedure of a transaction request, or the processing procedures of a plurality of blocks, and may be configured specifically according to the situation. In the block chain link point, the corresponding relation between the key identification and each version identification is recorded, and the upper layer software can access the required data through the combination of the key identification and the version identification.

In the embodiment of the invention, the transaction request is a request used for processing various transactions in the blockchain system, and is usually initiated by a certain blockchain node, broadcast in the blockchain network, and executed after being received by other blockchain nodes, and the generated transaction data is added into the block for storage. The technical link involved in this embodiment is to perform validity identification after the block link node receives the transaction request, and then determine whether to process the transaction request.

Example one

Fig. 1 is a flowchart of a method for identifying validity of a transaction request in a blockchain according to an embodiment of the present invention, which is applicable to a case where validity of a transaction request transmitted in a blockchain network is identified before the transaction request is executed by a blockchain node, and is particularly applicable to a scenario where validity of a transaction request that does not depend on a UTXO is identified. The scheme of the embodiment of the invention is applied to the blockchain nodes in the blockchain network, and the method can be executed by a transaction request validity identification device of the blockchain, and the device can be realized in a hardware and/or software mode and can be integrated in computing equipment bearing the blockchain nodes. Referring to fig. 1, the method specifically includes:

s110, acquiring a transaction request and validity check data transmitted in the blockchain network, wherein the validity check data corresponds to a pre-execution numerical value of the dependent data in the transaction request execution process.

In this embodiment, the transaction request may be a transaction request or other requests, such as a request for processing copyright registration information. The transaction request may be a request sent to the blockchain network when a transaction request is locally generated by a blockchain link point or when a trigger mechanism such as a transaction request sent by a third-party device (e.g., a client, a terminal device, or a server) is received; the request may also be a request which is not a blockchain node, such as a terminal device, but can be sent to the blockchain network through a data interaction platform (such as a client interface or a web page) provided by the blockchain node.

The validity check data is data used for checking whether the transaction request is valid, and specifically is a pre-execution numerical value corresponding to the dependent data in the execution process of the transaction request. The dependency data may include data that needs to be directly or indirectly used in the execution process of a certain transaction request, data that can be adjusted in the execution process or after the execution, and the like; a pre-execution value is a value of data that is relied upon during execution of a transaction request prior to execution of the transaction request. For example, a transaction requests transfer of funds from account a to account B, the dependency data may include account a balance and account B balance, and the like, and the pre-execution values are account a balance value and account B balance value. Optionally, the validity check data corresponds to the transaction requests one to one, that is, one transaction request has uniquely determined validity check data.

In this embodiment, the block link point may perform local transaction request preprocessing in advance before initiating the transaction request, so as to determine validity check data; binding the validity check data with the transaction request; and then sending the validity check data with the binding relation and the transaction request to the blockchain network. Or before the third-party device initiates the transaction request, the third-party device forms the transaction request through a data interaction platform with the block chain node, controls the block chain node to perform local transaction request preprocessing in advance to determine validity check data, and feeds back the validity check data to the transaction request initiator, such as the third-party device used by the user; and after the validity check data and the transaction request are bound by the third-party equipment, the validity check data are packaged through a user signature and then are sent to the block chain network through the block chain nodes.

The local node can acquire the transaction request and the validity check data transmitted in the block chain network, and then can execute the check operation on the validity of the transaction request according to the validity check data.

S120, reading a corresponding numerical value of the validity verification data from the locally stored block chain data, and determining the numerical value change condition of the validity verification data according to the locally read numerical value.

In this embodiment, the corresponding value of the validity verification data is the current value of the dependent data in the block chain data locally stored by the node that receives the transaction request.

Specifically, after the local node acquires the transaction request and the validity check data, the local node may read the current value of the dependent data from the locally stored blockchain data, compare the locally read value with the pre-execution value of the dependent data, and determine the change condition of the pre-execution value of the dependent data according to the comparison result, that is, determine the change condition of the value of the validity check data.

And S130, determining the validity of the transaction request according to the value change condition.

Specifically, if the local read value is the same as the pre-execution value of the dependent data, it is determined that the value has not changed, and it may be determined that the transaction request is valid. If the local read value is different from the value before the execution of the dependent data, determining the value change condition as the change of the value, judging whether the value change quantity is in a set range, and if so, determining that the transaction request is valid; otherwise, the transaction request is determined to be invalid.

For example, determining the validity of the transaction request according to the value change condition may include: and if the numerical value change quantity of the validity verification data is within the set range, determining that the transaction request is valid. In this embodiment, the setting range is a preset controllable range allowed by the error.

It should be noted that, if the local read value is different from the pre-execution value depending on the data, and the number of value changes is within the set range, it may be said that the local read value is not fine-tuned due to the influence of some external factors but the value changes caused by the execution of the transaction request.

Optionally, after determining the validity of the transaction request according to the value change condition, the method may further include: if the transaction is determined to be valid, the transaction request may be executed to obtain transaction data and store the transaction data in the blockchain.

Generally, during the generation of a block, if a transaction request is processed immediately after being received, only a short network delay may exist, and the waiting time for the queuing of the transaction request is short. Therefore, the value of the data relied upon by the transaction request for pre-execution at the initiator node should be identical to the value of the data relied upon by the receiving node before execution. If the data-dependent value has changed, the highest probability is that the transaction request has been executed, so the data-dependent value is overwritten, or the transaction request is delayed until it is sent by the initiator node to the blockchain network, so the data-dependent value has been overwritten by the transaction requests of other blocks. The occurrence of the data-dependent value change caused by any of the above situations indicates that the transaction request is invalid with a high probability. The initiator node may be false, repeatedly sending the user-signed transaction request, or maliciously delaying sending the user-signed transaction request. These situations are not intended by the initiating user and should be considered invalid and not executed.

According to the technical scheme provided by the embodiment of the invention, before the transaction request is processed, the corresponding numerical value of the validity check data read from the locally stored block chain data is compared with the pre-execution numerical value of the validity check data acquired from the block chain network, and the numerical value change condition of the validity check data is determined according to the comparison result; and then the validity of the transaction request can be determined according to the value change condition. Compared with the prior art, the embodiment provides a new idea for determining the validity of the transaction request, and realizes that validity identification can be accurately performed on the transaction request independent of the UTXO, so as to ensure correct execution of the transaction request.

Example two

Fig. 2 is a flowchart of a method for identifying validity of a block chain transaction request according to a second embodiment of the present invention, which is further optimized based on the second embodiment of the present invention, and determines whether a transaction request has been executed and is delayed to be executed, etc. by using a bottom storage system, such as a Key identifier in a Key Value pair (KV) storage system, or a Key identifier and a version identifier, adopted by a block chain system, so as to determine whether the transaction request is valid.

Optionally, in this embodiment, the block chain system uses a key-value pair storage system for storing block chain data; the dependency data comprises a set of dependent key-value pairs that the transaction request needs to read and write during execution, and the set at least comprises key identifications of the dependent key-value pairs. Correspondingly, the pre-execution numerical value is a numerical value associated with the key identifier of the pre-execution dependent key-value pair, and may specifically be data stored in the dependent key-value pair value field, or may also be other data associated with the key identifier, such as a hash signature value of the value field data.

Specifically, after acquiring the transaction request and the validity check data, the local node may read its associated value, such as the data currently stored in the value domain of the dependent key value pair, from the blockchain data according to the key identifier of the dependent key value pair, then compare the locally read data with the pre-execution value, and verify the value change condition of the data according to the validity of the comparison result.

Further, the key domain of the key-value pair in the key-value pair storage system may store a key identifier and a version identifier, the version identifier is used to represent the current version of the key-value pair when the value domain data is written, and the set includes the key identifier of the dependent key-value pair and the version identifier before execution. The pre-execution version identification is pre-execution data and is the version identification of the dependent key-value pair before the transaction request is executed.

Because the number of bytes occupied by the pre-execution numerical value determined according to the key identifier of the dependent key-value pair before execution is relatively large, the version identifier with the relatively small number of bytes can be selected to represent the pre-execution numerical value to determine whether the transaction request is effective.

Based on the above description, the corresponding value of the validity verification data is read from the locally stored blockchain data, and the change of the value of the validity verification data is determined according to the locally read value. Referring to fig. 2, the method may specifically include:

s210, acquiring a transaction request and validity check data transmitted in the blockchain network, wherein the validity check data corresponds to a pre-execution numerical value of the dependent data in the transaction request execution process.

Optionally, in a case that the key domain of the key-value pair in the key-value pair storage system stores the version identifier, if the data or the key-value pair involved in the data processing request generated in the processing process of the same block has the same version identifier, the dependent data may include:

the key identification and version identification in the key domain of the key-value pair that the transaction request directly reads or writes.

Or,

and at least the version identification of the previous block corresponds to the key identification or the version identification in the key domain of all the key value pairs. These key-value pairs are modified during the previous block generation process, but are not necessarily read-write directly for the current transaction request. The data overwritten by the previous block can also be used as the dependent data of the current transaction request.

The two types of dependency data can be used alone or in combination.

For example, if a transfer operation involving an account was performed during the previous block processing, the version identifier in the key field of the key value pair used to store the balance of the account is the version identifier of the previous block. If the transaction request is the transfer operation of the account, the dependency data may include a set of dependency key-value pairs that need to be read and written in the execution process of the transaction request, that is, the key-value pairs of the account balance and the key-value pairs transferred into the account balance; key-value pairs generated during previous block processing that are not directly dependent on the transaction request execution may also be included. Correspondingly, the version identification before execution is the version identification of the previous block.

Optionally, in the case that the key domain of the key-value pair in the key-value pair storage system stores a version identifier, if the data involved in the data processing request generated during the processing of one transaction data has an independent version identifier, the dependent data may include the key-value pair generated during the processing of the previous transaction data, or the key-value pair generated during the processing of the previous transaction data and the set of key-value pairs directly depended on by the transaction request during the execution. The key-value pair generated in the previous transaction data processing process may or may not be the key-value pair on which the transaction request directly depends in the execution process.

S220, reading the version identification corresponding to the key identification of the dependent key value pair from the locally stored blockchain data.

In this embodiment, the version identifier corresponding to the key identifier dependent on the key value pair is the current version identifier corresponding to the key identifier dependent on the key value pair in the locally stored blockchain data.

Specifically, after the transaction request and the validity check data are obtained, the local node may obtain, according to the key identifier of the dependent key-value pair, the version identifier corresponding to the key identifier of the dependent key-value pair. Optionally, the underlying storage system pre-constructs a mapping relationship table between the key identifier and the version identifier, for the upper layer software to query. Therefore, the native node can determine the version identification corresponding to the key identification of the dependent key-value pair through the upper-layer software,

and S230, comparing the locally read version identification with the version identification before execution carried in the validity verification data.

Specifically, the local node may compare the locally read version identifier with the version identifier before execution carried in the validity verification data; if the two are the same, it can be determined that the version identifier read locally is not updated; if the two are different, it can be determined that the version identifier read locally is updated.

S240, if the version identification read locally is determined to be updated, the validity verification data is determined to have a value change.

Specifically, under the condition that the version identifier read locally is determined to be updated, the value change of the validity verification data can be determined; in the event that it is determined that the locally read version identification has not been updated, then it may be determined that the validity verification data has not changed in value.

And S250, determining the validity of the transaction request according to the value change condition.

It should be noted that, the validity of the transaction request is determined by using the version identifier, which not only can determine whether the transaction request is executed, but also can avoid the phenomenon that the block link point is delayed to send, and the false probability exists, thereby ensuring the timeliness of the transaction request. For example, if a transaction request is executed, the version identifier of the key-value pair on which the transaction request depends will be changed, so that the version identifier read locally by the local node will be different from the pre-execution version identifier carried in the valid check data, and it can be determined that the transaction request is invalid. If a certain blockchain node does not send the acquired transaction request to the blockchain network within a specified time, the version identification before execution may be changed due to other transaction requests within the time period. Therefore, even if the transaction request is not executed, the version identifier read locally by the local node is inconsistent with the pre-execution version identifier carried in the validity verification data, and the transaction request is determined to be invalid.

According to the technical scheme provided by the embodiment of the invention, before the transaction request is processed, the version identification corresponding to the key identification of the dependent key value pair read from the locally stored block chain data is compared with the version identification before execution carried in the validity verification data, and the numerical value change condition of the validity verification data is determined according to the comparison result; and then the validity of the transaction request can be determined according to the value change condition. Compared with the prior art, when the validity of the transaction request is determined based on the version identifier stored in the key domain of the key value pair, the transaction request can be prevented from being sent or executed in a delayed manner when the transaction request is not executed, a new idea is provided for determining the validity of the transaction request, validity identification can be accurately performed on the transaction request independent of the UTXO, and therefore correct execution of the transaction request is ensured.

EXAMPLE III

Fig. 3 is a flowchart of a method for initiating a transaction request of a blockchain according to a third embodiment of the present invention, which is applicable to a situation where a blockchain node or a third-party device initiates a transaction request to a blockchain network when the blockchain node or the third-party device generates a transaction request. After the other blockchain nodes obtain the transaction request in the blockchain network, the validity of the transaction request may be identified by using the method provided in the above embodiment. The scheme of the embodiment of the invention can be applied to the block chain nodes in the block chain network, and can also be applied to third-party equipment such as terminal equipment and the like. Referring to fig. 3, the method specifically includes:

s310, a transaction request is generated.

In this embodiment, the transaction request may be a request sent to the blockchain network when a transaction request is locally generated by a blockchain link point, or when a trigger mechanism such as a transaction request sent by a third-party device (e.g., a client, a terminal device, or a server) is received; the request may also be a request that is not a blockchain node such as a terminal device, but may be sent to the blockchain network through a data interaction platform (e.g., a client interface or a web page, etc.) provided by the blockchain node.

And S320, generating validity checking data, and binding the validity checking data with the transaction request, wherein the validity checking data is a pre-execution numerical value depending on data in the transaction request execution process.

In this embodiment, the validity check data is a data set used for checking whether the transaction request is valid, and specifically, is a pre-execution numerical value corresponding to the dependent data in the execution process of the transaction request. The dependency data may include data that needs to be directly or indirectly used in the execution process of a certain transaction request, data that can be adjusted in the execution process or after the execution, and the like; a pre-execution value is a value of data that is relied upon during execution of a transaction request prior to execution of the transaction request.

Illustratively, the blockchain system employs a key-value pair storage system for storing blockchain data; the dependency data comprises a set of dependent key-value pairs that the transaction request needs to read and write during execution, and the set at least comprises key identifications of the dependent key-value pairs. Correspondingly, the pre-execution numerical value is a numerical value associated with the key identifier of the pre-execution dependent key-value pair, and may specifically be data stored in the dependent key-value pair value field, or may also be other data associated with the key identifier, such as a hash signature value of the value field data. In this embodiment, the key identifier is added to the validity check data, so that other subsequent block link points can conveniently obtain the associated numerical value based on the key identifier, and then the validity of the transaction request is determined according to the change situation of the numerical value associated with the key identifier.

Further, the key domain storage of the key-value pair in the key-value pair storage system may have a key identifier and a version identifier, the version identifier is used to represent a current version when the value domain data of the key-value pair is written, and the set includes the key identifier dependent on the key-value pair and the version identifier before execution. The pre-execution version identification is pre-execution data and is the version identification of the dependent key-value pair before the transaction request is executed. In this embodiment, the version identifier is added to the validity check data, so that it is convenient for the subsequent other block link points to determine the validity of the transaction request based on the change condition of the version identifier.

Binding the validity check data with the transaction request refers to establishing an association relationship between the validity check data and the transaction request, and specifically may be adding the validity check data to the transaction request. Illustratively, generating validity check data, binding the validity check data with the transaction request may include: and generating validity check data, and adding the validity check data into a preset field of the transaction request. In this embodiment, the preset field may be any empty field in the transaction request, or a field in a specific location; for ease of reading, the predetermined field is preferably a field at a particular location in the transaction request.

Specifically, the block link points may be pre-processed locally in advance to generate validity check data; binding the validity check data with the transaction request; and then sending the validity check data with the binding relation and the transaction request to the blockchain network. The third-party equipment can also send the transaction request to the block chain node through a data interaction platform with the block chain node to request the block chain node to perform transaction preprocessing locally in advance so as to generate validity check data and feed back the validity check data to the third-party equipment; and the third-party equipment binds the validity check data with the transaction request, namely sends the data to the block chain network after the data is packaged through the user signature.

Illustratively, generating the validity check data may include: carrying out transaction preprocessing on the transaction request locally to determine a pre-execution numerical value of the dependent data in the transaction request execution process; and taking the value of the dependent data before the transaction request is executed as the value of the validity verification data. Specifically, after the block link point generates the transaction request, the transaction request may be subjected to transaction preprocessing locally, so as to determine the pre-execution data of the dependent data required by the transaction request in the execution process, and use the pre-execution value of the dependent data as the value of the message-containing check data.

S330, a transaction request and validity check data are initiated in the blockchain network.

Specifically, after binding the transaction request with the validity check data, the block chain node may initiate the transaction request and the validity check data to the block chain network. The third-party device may also initiate the transaction request and the validity check data to the blockchain network through a data interaction platform provided by the blockchain node after binding the transaction request and the validity check data. After receiving the transaction request and the validity check data, other nodes in the blockchain network can read the corresponding numerical value of the validity check data from the locally stored blockchain data, compare the locally read numerical value with the obtained numerical value of the validity check data, and determine the numerical value change condition of the validity check data according to the comparison result; the validity of the transaction request is then determined based on the value change.

According to the technical scheme provided by the embodiment of the invention, after a transaction request is generated, validity check data of the transaction request is correspondingly generated, the transaction request and the validity check data are bound, and then the transaction request and the validity check data are sent to the block chain network, so that other nodes in the block chain network read corresponding values of the validity check data from the locally stored block chain data before processing the transaction request, the values are compared with the pre-execution values of the validity check data acquired from the block chain network, the value change condition of the validity check data is determined according to the comparison result, and the validity of the transaction request is further determined according to the value change condition. Compared with the prior art, the embodiment provides a new idea for determining the validity of the transaction request, and realizes that validity identification can be accurately performed on the transaction request independent of the UTXO, so as to ensure correct execution of the transaction request.

Example four

Fig. 4 is a flowchart of a method for initiating a transaction request of a blockchain according to a fourth embodiment of the present invention, which is further optimized based on the foregoing embodiments. Referring to fig. 4, the method specifically includes:

s410, generating a transaction request.

And S420, determining validity check data for the transaction request through an intelligent contract deployed by the block chain nodes, and binding the validity check data with the transaction request.

In this embodiment, the intelligent contract may be a code segment for implementing a certain function, specifically, a code segment corresponding to validity check data for determining the transaction request; the block chain can be pre-appointed during the creation and stored in the created block; or dynamically added in the creation process of the block chain and stored in a certain block; or may be stored locally at a block link point independently of the block chain.

Specifically, the block link point may obtain an intelligent contract used for determining validity check data of the transaction request from an intelligent contract locally deployed by the block link point, then execute the intelligent contract, determine validity check data for the transaction request, and bind the validity check data with the transaction request. The third-party equipment can also send a validity check data determination request comprising a transaction request to the block chain node, so that the block chain node determines validity check data for the transaction request through a locally deployed intelligent contract and feeds back the validity check data; after the third-party device receives the validity check data, the validity check data may be bound to the transaction request.

S430, the transaction request signed by the transaction request initiator is obtained.

In this embodiment, the transaction request initiator may be a block link point, or may be a third-party device. The signature is a means for indicating the identity of the initiator, and may be a signature of the initiator by using a private key, a signature algorithm such as a hash algorithm, or a signature rule agreed by a block chain network.

Specifically, if the transaction request is a request sent to the blockchain network when the transaction request is locally generated by the blockchain node or the transaction request sent by the third-party device is received, the blockchain node may obtain the transaction request and the validity check data signed by the private key of the blockchain node, or may obtain the transaction request and the validity check data signed by the third-party device by the private key and the like.

If the transaction request is a request sent by the third-party device to the blockchain network through a data interaction platform (such as a client interface or a webpage) provided by the blockchain node, the third-party device may obtain the transaction request signed by its own private key and the validity check data.

S440, initiate a transaction request and validity check data in the blockchain network.

The technical scheme provided by the embodiment of the invention provides a scheme for determining validity check data based on only contracts in block link point deployment. The intelligent contract for determining the validity check data is deployed at the block link point, so that the reasonability and the accuracy of the determined validity check data are ensured.

EXAMPLE five

Fig. 5 is a flowchart of a transaction request initiation and validity identification method for a blockchain according to a fifth embodiment of the present invention. Referring to fig. 5, the method specifically includes:

s510, the block chain node generates a transaction request.

S520, generating validity checking data by the block chain nodes, and binding the validity checking data with the transaction request, wherein the validity checking data is a pre-execution numerical value depending on data in the transaction request execution process;

s530, the block chain node initiates a transaction request and validity check data in the block chain network.

S540, other blockchain nodes acquire the transaction request and the validity check data transmitted in the blockchain network.

And S550, other blockchain nodes read the corresponding numerical values of the validity verification data from the locally stored blockchain data, and determine the numerical value change condition of the validity verification data according to the locally read numerical values.

And S560, determining the validity of the transaction request by other block chain nodes according to the value change condition.

According to the technical scheme provided by the embodiment of the invention, after a transaction request is generated, the block chain nodes correspondingly generate validity check data of the transaction request, bind the transaction request and the validity check data and then send the bound transaction request and the bound validity check data to the block chain network, so that other nodes in the block chain network read corresponding values of the validity check data from the locally stored block chain data before processing the transaction request, compare the corresponding values with the pre-execution values of the validity check data acquired from the block chain network, determine the value change condition of the validity check data according to the comparison result, and further determine the validity of the transaction request according to the value change condition. Compared with the prior art, the embodiment provides a new idea for determining the validity of the transaction request, and realizes that validity identification can be accurately performed on the transaction request independent of the UTXO, so as to ensure correct execution of the transaction request.

EXAMPLE six

Fig. 6 is a schematic structural diagram of an apparatus for identifying validity of a transaction request of a block chain according to a sixth embodiment of the present invention, where the apparatus may be configured in a block chain node, and the apparatus may execute the method for identifying validity of a transaction request of a block chain according to the first and second embodiments of the present invention, and has corresponding functional modules and beneficial effects of the execution method. As shown in fig. 6, the apparatus includes:

an obtaining module 610, configured to obtain a transaction request and validity check data transmitted in a blockchain network, where the validity check data corresponds to a pre-execution numerical value of dependent data in a transaction request execution process;

a value change determining module 620, configured to read a corresponding value of the validity verification data from the locally stored blockchain data, and determine a value change condition of the validity verification data according to the locally read value;

and a validity determining module 630, configured to determine validity of the transaction request according to the value change condition.

Illustratively, the blockchain system employs a key-value pair storage system for storing blockchain data; the dependency data comprises a set of dependent key-value pairs that the transaction request needs to read and write during execution, and the set at least comprises key identifications of the dependent key-value pairs.

Illustratively, a key domain of a key-value pair in the key-value pair storage system stores a key identifier and a version identifier, the version identifier is used for representing a current version when value domain data of the key-value pair is written, and the set comprises a key identifier dependent on the key-value pair and a version identifier before execution;

accordingly, the value change determination module 620 may be specifically configured to:

reading a version identification corresponding to the key identification of the dependent key value pair from the locally stored blockchain data;

comparing the locally read version identification with the version identification before execution carried in the validity verification data;

and if the locally read version identification is determined to be updated, determining that the value of the validity verification data is changed.

Illustratively, the validity determination module 630 may be specifically configured to:

and if the numerical value change quantity of the validity verification data is within the set range, determining that the transaction request is valid.

EXAMPLE seven

Fig. 7 is a schematic structural diagram of a device for initiating a transaction request of a block chain according to a seventh embodiment of the present invention, which can execute the method for initiating a transaction request of a block chain according to the third and fourth embodiments of the present invention, and has functional modules and beneficial effects corresponding to the execution method. As shown in fig. 7, the apparatus includes:

a request generation module 710 for generating a transaction request;

the data generating and binding module 720 is configured to generate validity check data, and bind the validity check data with the transaction request, where the validity check data is a pre-execution numerical value of the dependent data in the execution process of the transaction request;

an initiating module 730, configured to initiate a transaction request and validity check data in a blockchain network;

Illustratively, the data generation binding module 720, in generating the validity check data, may be configured to:

carrying out transaction preprocessing on the transaction request locally to determine a pre-execution numerical value of the dependent data in the transaction request execution process;

and taking the value of the dependent data before the transaction request is executed as the value of the validity verification data.

Illustratively, the key domain of a key-value pair in the key-value pair storage system stores a key identifier and a version identifier, the version identifier is used for representing the current version of the key-value pair when the value domain data is written, and the set comprises the key identifier of a dependent key-value pair and the version identifier before execution.

Illustratively, the data generation binding module 720 may be specifically configured to:

and generating validity check data, and adding the validity check data into a preset field of the transaction request.

Illustratively, the data generation binding module 720 may be further specifically configured to:

determining validity check data for the transaction request through an intelligent contract deployed by a block link point, and binding the validity check data with the transaction request;

a transaction request signed by a transaction request initiator is obtained.

Example eight

Fig. 8 is a schematic structural diagram of an apparatus according to an eighth embodiment of the present invention. FIG. 8 illustrates a block diagram of an exemplary device 12 suitable for use in implementing embodiments of the present invention. The device 12 shown in fig. 8 is only an example and should not bring any limitation to the function and scope of use of the embodiments of the present invention. Device 12 may typically be a computing device that assumes the functionality of a blockchain network node.

As shown in FIG. 8, device 12 is in the form of a general purpose computing device. The components of device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16.

Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, micro-channel architecture (MAC) bus, enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

Device 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by device 12 and includes both volatile and nonvolatile media, removable and non-removable media.

The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)30 and/or cache memory 32. Device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 8, and commonly referred to as a "hard drive"). Although not shown in FIG. 8, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. System memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.

Device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), with one or more devices that enable a user to interact with device 12, and/or with any devices (e.g., network card, modem, etc.) that enable device 12 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 22. Also, the device 12 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet) via the network adapter 20. As shown, the network adapter 20 communicates with the other modules of the device 12 via the bus 18. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

The processing unit 16 executes programs stored in the system memory 28 to execute various functional applications and data processing, such as a transaction request validity identification method for the blockchain and/or a transaction request initiation method for the blockchain provided by the embodiment of the present invention.

Example nine

The ninth embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, can implement the method for identifying validity of a transaction request of a blockchain and/or the method for initiating a transaction request of a blockchain described in the foregoing embodiments. The computer readable storage medium may be configured on a blockchain node.

Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A transaction request validity identification method of a blockchain is applied to a scene of identifying the validity of a transaction request before the transaction request transmitted in a blockchain network is executed by blockchain nodes, and is characterized in that the method is applied to the blockchain nodes, and the method comprises the following steps:

acquiring a transaction request and validity check data transmitted in a block chain network, wherein the validity check data correspond to a pre-execution numerical value of dependent data in the transaction request execution process, the validity check data correspond to the transaction request one by one, and the dependent data comprise data adjusted in the transaction request execution process or after execution;

reading a corresponding numerical value of validity verification data from locally stored blockchain data, and determining a numerical value change condition of the validity verification data according to the locally read numerical value, wherein the corresponding numerical value of the validity verification data is a current numerical value of data-dependent data in the blockchain data locally stored by a node receiving the transaction request;

and determining the validity of the transaction request according to the value change condition.

2. The method of claim 1, wherein the blockchain system employs a key-value pair storage system for storing blockchain data; the dependency data comprises a set of dependent key-value pairs which the transaction request needs to read and write during execution, and the set at least comprises key identifications of the dependent key-value pairs.

3. The method of claim 2, wherein the key domain of a key-value pair in the key-value pair storage system stores a key identifier and a version identifier, the version identifier being used to represent the current version of the value domain data of the key-value pair when written, and the set comprising the key identifier of the dependent key-value pair and the version identifier before execution;

correspondingly, reading a corresponding numerical value of the validity verification data from the locally stored blockchain data, and determining a numerical value change condition of the validity verification data according to the locally read numerical value includes:

4. The method according to any of claims 1-3, wherein determining the validity of the transaction request based on the value change comprises:

and if the numerical value change quantity of the validity verification data is within a set range, determining that the transaction request is valid.

5. A method for initiating a transaction request of a blockchain is applied to a scene of identifying validity of the transaction request before the transaction request transmitted in a blockchain network is executed by a blockchain node, and is characterized by comprising the following steps:

generating a transaction request;

generating validity checking data, and binding the validity checking data with the transaction request, wherein the validity checking data is a pre-execution numerical value of dependent data in the transaction request execution process, and the dependent data comprises data adjusted in the transaction request execution process or after the execution;

the validity check data is used for the block chain nodes to read corresponding values of the validity check data from the locally stored block chain data, and the value change condition of the validity check data is determined according to the locally read values; and determining the validity of the transaction request according to the value change condition, wherein the corresponding value of the validity verification data is the current value of the dependent data in the block chain data locally stored by the node receiving the transaction request.

6. The method of claim 5, wherein generating validity check data comprises:

performing transaction preprocessing on the transaction request locally to determine a pre-execution numerical value of the dependent data in the transaction request execution process;

and taking the value of the dependent data before the execution of the transaction request as the value of the validity verification data.

7. The method of claim 5 or 6, wherein the blockchain system employs a key-value pair storage system for storing blockchain data; the dependency data comprises a set of dependent key-value pairs which the transaction request needs to read and write during execution, and the set at least comprises key identifications of the dependent key-value pairs.

8. The method of claim 7, wherein the key domain of a key-value pair in the key-value pair storage system stores a key identifier and a version identifier, the version identifier being used to represent the current version of the value domain data of the key-value pair when written, and the set comprises the key identifier of the dependent key-value pair and the version identifier before execution.

9. The method of claim 5 or 6, wherein generating validity check data, binding the validity check data with the transaction request, comprises:

and generating validity check data, and adding the validity check data to a preset field of the transaction request.

10. The method of claim 5 or 6, wherein generating validity check data, binding the validity check data with the transaction request, comprises:

a transaction request signed by a transaction request initiator is obtained.

11. A blockchain transaction request validity identification apparatus, applied to a scenario in which validity of a transaction request transmitted in a blockchain network is identified before the transaction request is executed by a blockchain node, is configured at the blockchain node, and includes:

an obtaining module, configured to obtain a transaction request and validity check data transmitted in a blockchain network, where the validity check data corresponds to a pre-execution numerical value of dependent data in an execution process of the transaction request, the validity check data corresponds to the transaction request in a one-to-one manner, and the dependent data includes data that is adjusted in the execution process or after the execution of the transaction request;

the value change determining module is used for reading a corresponding value of validity verification data from the locally stored blockchain data and determining the value change condition of the validity verification data according to the locally read value, wherein the corresponding value of the validity verification data is a current value of dependent data in the blockchain data locally stored by the node receiving the transaction request;

12. A blockchain transaction request initiator for use in a scenario in which validity of a transaction request transmitted in a blockchain network is identified before the transaction request is executed by a blockchain node, the blockchain transaction request initiator comprising:

a request generation module for generating a transaction request;

the data generation and binding module is used for generating validity check data and binding the validity check data with the transaction request, wherein the validity check data is a pre-execution numerical value of dependent data in the transaction request execution process, and the dependent data comprises data which is adjusted in the transaction request execution process or after the execution;

13. An apparatus, characterized in that the apparatus comprises:

one or more processors;

storage means for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement the method for identifying validity of a transaction request of a blockchain according to any one of claims 1 to 4 or the method for initiating a transaction request of a blockchain according to any one of claims 5 to 10.

14. A storage medium on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out a method for identifying validity of a transaction request of a blockchain according to one of claims 1 to 4 or a method for initiating a transaction request of a blockchain according to one of claims 5 to 10.