CN117808476A

CN117808476A - Transaction processing method in block chain system and block chain link point

Info

Publication number: CN117808476A
Application number: CN202311437160.8A
Authority: CN
Inventors: 曹睿学
Original assignee: Ant Blockchain Technology Shanghai Co Ltd
Current assignee: Ant Blockchain Technology Shanghai Co Ltd
Priority date: 2023-10-31
Filing date: 2023-10-31
Publication date: 2024-04-02

Abstract

A transaction processing method and a blockchain node in a blockchain system. For a first transaction received by the blockchain node from the client, including a first amount of resources that allows the first transaction to consume the target resources, and a first account for paying for the first transaction to consume the target resources; the blockchain node can inquire the current resource quantity of the target resource held by the first account from account balance cache information maintained by the blockchain node, and determine whether the first resource quantity is larger than the current resource quantity; the blockchain node may prohibit adding the first transaction to the transaction pool as the transaction to be consensus when the first resource amount is greater than the current resource amount.

Description

Transaction processing method in block chain system and block chain link point

Technical Field

The embodiment of the specification belongs to the technical field of blockchains, and particularly relates to a transaction processing method in a blockchain system and a blockchain node.

Background

Blockchain (Blockchain) is a new application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanisms, encryption algorithms, and the like. In the block chain system, the data blocks are combined into a chain data structure in a sequential connection mode according to the time sequence, and the distributed account book which is not tamperable and counterfeit and is ensured in a cryptographic mode is formed. Because the blockchain has the characteristics of decentralization, non-tamperability of information, autonomy and the like, the blockchain is also receiving more and more attention and application.

Disclosure of Invention

The invention aims to provide a transaction processing method and a blockchain node in a blockchain system.

In a first aspect, a method of transaction processing in a blockchain system is provided, the method performed by a blockchain node in the blockchain system, the blockchain node including account balance cache information independent of status data therein. The method comprises the following steps: receiving a first transaction from a client, including a first amount of resources that allows the first transaction to consume a target resource, and a first account for paying for the first transaction to consume the target resource; inquiring the current resource quantity of the target resource held by the first account from the account balance cache information, and determining whether the first resource quantity is larger than the current resource quantity; and when the first resource quantity is larger than the current resource quantity, prohibiting the first transaction from being added into a transaction pool as a transaction to be consensus.

In a second aspect, there is provided a blockchain node in a blockchain system, the blockchain node including account balance cache information independent of status data therein, the method comprising: a transaction receiving unit configured to receive a first transaction from a client, including a first resource amount allowing the first transaction to consume a target resource, and a first account for paying for the first transaction to consume the target resource; the data processing unit is configured to query the current resource quantity of the target resource held by the first account from the account balance cache information and determine whether the first resource quantity is larger than the current resource quantity; and the transaction scheduling unit is configured to prohibit the first transaction from being added into a transaction pool as a transaction to be consensus when the first resource quantity is larger than the current resource quantity.

In a third aspect, there is provided a computing device comprising a memory having executable code stored therein and a processor which, when executing the executable code, implements the method provided in the first aspect.

In a fourth aspect, there is provided a computer readable storage medium having stored thereon a computer program which, when executed in a computing device, performs the method provided in the first aspect.

In the technical solution provided in the embodiments of the present disclosure, the blockchain link point includes account balance cache information corresponding to status data, and the blockchain node includes, in a first transaction received from the client, a first resource amount of a target resource allowed to be consumed by the blockchain node, and a first account (i.e., a resource payment account) for paying for the target resource consumed by the blockchain node; the blockchain node can inquire the current resource quantity of the target resource held by the first account from the account balance cache information and determine whether the first resource quantity is larger than the current resource quantity; if the first number of resources is greater than the current number of resources, it is indicated that the first account actually holds the target resources, which may not be sufficient to pay for the target resources that are required to be consumed when the block link points successfully execute the first transaction, and thus the first transaction may be prohibited from being added to the transaction pool as a transaction to be consensus. In this way, when a target resource held by a resource payment account designated by a transaction is possibly insufficient to pay for the target resource required to be consumed by the transaction, the transaction is not added to the transaction pool, so that the blockchain node does not need to continue to perform a complex consensus mechanism and execution process on the transaction, an intruder can be prevented from maliciously consuming a large amount of computing resources of the blockchain node to realize the attack blockchain system by initiating a malicious transaction, thereby being beneficial to saving the computing resources of the blockchain node and improving the security of the blockchain system.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings that are needed in the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present disclosure, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is an architecture diagram of a blockchain system as exemplary provided in embodiments of the present description;

FIG. 2 is one of the flowcharts of a transaction processing method in a blockchain system provided in the embodiments of the present disclosure;

FIG. 3 is a schematic diagram of a data structure of a transaction as exemplarily provided in an embodiment of the present disclosure;

FIG. 4 is a schematic diagram of a process for verifying a transaction as exemplarily provided in an embodiment of the present disclosure;

FIG. 5 is a block chain node in a block chain system according to one embodiment of the present disclosure;

FIG. 6 is a second flowchart of a transaction processing method in a blockchain system provided in the embodiments of the present disclosure;

FIG. 7 is a second block chain node diagram of a block chain system according to one embodiment of the present disclosure.

Detailed Description

In order to make the technical solution in the present specification better understood by those skilled in the art, the technical solution in the embodiments of the present specification will be clearly and completely described in the following with reference to the accompanying drawings, and it is apparent that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.

Fig. 1 is a block chain system architecture diagram exemplarily provided in an embodiment of the present specification. The blockchain system may include N blockchain nodes, with 8 blockchain nodes, node 1-node 8, being shown in fig. 1 by way of example. The connection between nodes schematically represents a node-to-node connection, which may be, for example, a transmission control protocol (transmission control trotocol, TCP) connection, which is used to support the transmission of data between different nodes.

System data in a blockchain system that requires persistent storage may be divided into two parts, blockdata and state data.

The block data includes one or more blocks incremented by a block height (or referred to as a block number), and a single block may include a block header and a block body. The block header may include a block Hash previous_hash (or referred to as a parent Hash), a Timestamp, a block number BlockNum, a State Root Hash state_root, a Transaction Root Hash transaction_root, a Receipt Root Hash Receipt_root, and the like. The zone block may include a transaction set and a receipt set therein.

Transactions in a blockchain system refer to task units that execute in the blockchain system and are recorded in the blockchain system. A single transaction typically includes a send field (From), a receive field (To), and a Data field (Data), where the From field includes an account From which the transaction originated (i.e., the sender account), and the To field may include another account To which the transaction relates/points.

For any kth block, a plurality of transactions arranged in sequence included in a transaction set belonging to the kth block may be executed according to state data of a block height (or referred to as a block number) of k-1, and execution results of the plurality of transactions are obtained. And updating the state data with the block height of k-1 according to the execution results of the transactions to obtain the state data with the block height of k.

The consensus mechanism in the blockchain system is a mechanism that the blockchain node achieves the same consensus of the whole network about the blockinformation, and can ensure that the latest obtained block is accurately stored. The consensus mechanisms of the current mainstream include: proof of Work (POW), proof of equity (POS), proof of commission (Delegated Proof ofStake, DPOS), practical bayer fault tolerance (Practical Byzantine Fault Tolerance, PBFT) algorithms, and the like. Wherein in various consensus algorithms, it is generally determined that the data to be consensus is consensus after a preset number of consensus nodes reach the same data to be consensus. For example, in the PBFT algorithm, it is assumed that when there are at most f node failures, if there are at least 3f+1 nodes in total, it is guaranteed that security and activity are provided in the entire blockchain system.

The blockchain node may verify the transaction after receiving the transaction from the client or other blockchain point to which it is connected. The validated transaction is added as a to-be-agreed transaction to the corresponding transaction pool/transaction cache pool. The blockchain node may also select a plurality of transactions from the transaction pool to generate a consensus proposal corresponding to any kth block, and consensus the consensus proposal by the plurality of blockchain nodes according to the various consensus mechanisms described above; after consensus is reached for the consensus proposal, the blockchain node can execute the plurality of transactions, and after completing executing the plurality of transactions, the plurality of transactions are deleted from the transaction pool.

Execution of a transaction requires consumption of computing resources of the blockchain node, particularly for transactions that request deployment of a smart contract and requests invocation of a smart contract, the blockchain node may need to execute a large number of instructions in executing the transaction. An intruder may consume computing resources of a blockchain node by submitting a large number of malicious transactions to implement a malicious attack on the blockchain system.

The blockchain system may define a target resource that is consumed by executing a transaction, such as a Token or other digital resource of some form. The minimum value of the required consumption target resource when a single transaction is successfully executed can also be defined in part of the technical scenes, for example, the minimum value of the required consumption target resource is respectively defined for different types of transactions.

In the process of executing the transaction, the blockchain system can count the consumption quantity of the resources of the target resources consumed in the process of executing the transaction as far as possible in real time based on the instruction consumed by the transaction or the data quantity processed by executing the transaction, and further deduct the target resources held by the target resources from the designated resource payment account of the transaction according to the consumption quantity of the resources; if the target resource held by the resource payment account specified by the transaction is insufficient to pay for the target resource consumed by the transaction, i.e., the current resource quantity of the target resource held by the resource payment account is less than the corresponding resource consumption quantity of the transaction, the blockchain node may terminate execution of the transaction, the transaction execution fails and the target resource held by the resource payment account is cleared.

In the foregoing solution, when the target resource held by the resource payment account is insufficient to support successful execution of the corresponding transaction, the execution of the corresponding transaction is terminated, so that an intruder can be prevented from attacking the blockchain system to a certain extent by submitting a large number of malicious transactions to the blockchain system. However, even with the foregoing solutions, it is still possible for an intruder to attack the blockchain system with a distributed denial of service (Distributed Denial of Service, DDOS) attack or the like. For example, an intruder may use a large number of accounts holding only a small number of target resources, for example, the number of target resources held by a single account is equal to or approaching a minimum value of required consumption digital resources defined by a blockchain system when a single transaction is successfully executed, and a large number of malicious transactions are constructed in a relatively short time, and all the malicious transactions are verified to be added into a transaction pool as transactions to be agreed, and block chain links will execute an consensus mechanism and subsequent execution flow and failure; causing the blockchain point to expend significant computing resources to handle these malicious transactions, making it difficult to service normal transactions, even directly paralyzing the entire blockchain system.

The embodiment of the specification at least provides a transaction processing method and a blockchain node in a blockchain system. The blockchain node includes account balance cache information corresponding to the status data, a first resource amount of the target resource that the blockchain node is permitted to consume is included in a first transaction received from the client, and a first account (i.e., a resource payment account) for paying for the target resource that the blockchain node consumes; the blockchain node can inquire the current resource quantity of the target resource held by the first account from the account balance cache information and determine whether the first resource quantity is larger than the current resource quantity; if the first number of resources is greater than the current number of resources, it is indicated that the first account actually holds the target resources, which may not be sufficient to pay for the target resources that are required to be consumed when the block link points successfully execute the first transaction, and thus the first transaction may be prohibited from being added to the transaction pool as a transaction to be consensus.

In this way, when a transaction specifies a target resource held by a resource payment account, the transaction is not added to a transaction pool, so that the blockchain node does not need to continue to perform a complex consensus mechanism and execution process on the transaction, thereby avoiding an intruder from maliciously consuming a large amount of computing resources of the blockchain node to realize attacking the blockchain system by initiating a large amount of malicious transactions, further being beneficial to saving the computing resources of the blockchain node and improving the security of the blockchain system.

Fig. 2 is a flowchart of a transaction processing method in a blockchain system according to an embodiment of the present disclosure. The method is performed by a blockchain link point in a blockchain system that includes account balance cache information corresponding to status data. When the blockchain node is initialized, the resource quantity of the target resources respectively held by each account registered in the blockchain system can be read from the state data of the blockchain node, and the resource quantity is cached as account balance caching information independent of the state data.

The method illustrates a process in which a blockchain node processes a transaction Tx1 from a client.

Referring to fig. 2, the method may include, but is not limited to, the following steps S201 to S213.

First, in step S201, a transaction Tx1 is received from a client, which includes a resource amount S1 that allows the transaction Tx1 to consume a target resource, and a first account for paying for the target resource consumed by the transaction Tx 1.

The aforementioned first account is the resource payment account specified in transaction Tx 1. In the event that no other account is designated in transaction Tx1 as its resource payment account, the sender account of transaction Tx1 may be the resource payment account thereof.

In the case where an account other than its sender account is designated as a resource payment account in the transaction Tx 1: transaction Tx1 includes a transactionAn ontology including a sender account, a first account that is a resource payment account, and a number of resources S1 that allow the transaction Tx1 to consume a target resource; the transaction Tx1 also includes a first signature of the transaction body by the sender account (denoted as signature S _c1 ) And a second signature of the transaction body by the first account (noted as signature S _c3 )。

For example, see fig. 3. The user U1 holding the account C1 may first construct a transaction body of the transaction Tx1 in the client A1, wherein the From field of the transaction body includes the sender account C1, the To field includes the receiver account C2, and the Data field includes the resource payment account C3 declared by a specific subfield such as target, the number of resources S1 declared by a specific subfield such as gas limit; the transaction body may then be signed with the private key of account C1 to obtain signature S _c1 And provides the transaction body and signature S to the client A3 corresponding to the user U3 holding the account C3 _c1 . Further, in case the user U3 agrees to pay the target resource for the transaction Tx1 through the account C3 held by the user U3, the transaction body may be signed with the private key of the account C3 to obtain the signature S _c1 . Finally, transaction body, signature S _c1 Signature S _c3 The composition transaction Tx1 is sent by either client A1 or client A3 to a certain blockchain node in the blockchain system. The structure of the transaction Tx1 exemplarily provided in fig. 3 is merely exemplary, and for example, the resource payment account C3 designated by the transaction Tx1 and the resource amount S1 of the target resource allowed to be consumed by the transaction Tx1 may be separately declared through other specific fields juxtaposed with the Data field in the transaction body.

The number of resources S1 that allow transaction Tx1 to consume the target resource may be user-defined.

Next, in step S203, the transaction Tx1 is verified.

The process of verifying transaction Tx1 may include one or more of the following a 1-a 4.

a1, transaction flow control checking. I.e. determining whether the number of transactions comprised by the transaction pool reaches its corresponding capacity threshold, if so, determining that the transaction Tx1 is not validated, otherwise the transaction Tx1 passes the transaction flow control check. When the transaction pool includes a plurality of transaction pool fragments, it may be determined whether the number of transactions included in the target transaction pool fragment to which the transaction Tx1 belongs reaches its corresponding capacity threshold, if so, it is determined that the transaction Tx1 is not verified, otherwise, the transaction Tx1 passes the transaction flow control check.

a2, checking the validity of the transaction. I.e. determining if the data structure of transaction Tx1 is a data structure allowed by the blockchain system, if so, transaction Tx1 passes the transaction validity check, otherwise, determining that transaction Tx1 is not validated.

a3, transaction replay checking, namely determining whether the transaction Tx1 is a replay transaction, if so, determining that the transaction Tx1 is not verified, otherwise, determining that the transaction Tx1 passes the transaction replay checking.

a4, transaction integrity checking, i.e. verifying the signature in transaction Tx1 with the relevant public key. When other accounts are not designated as resource payment accounts in the transaction Tx1, the transaction Tx1 comprises a transaction body and a first signature corresponding to a sender account of the transaction body, the first signature is verified by using a public key of the sender account, the transaction Tx1 passes the integrity check if the first signature passes the verification, and otherwise, the transaction Tx1 is determined to not pass the verification. When other first accounts different from the sender account are designated as resource payment accounts of the transaction Tx1 in the transaction Tx1, the transaction Tx1 includes a transaction body, a first signature corresponding to the sender account and a second signature corresponding to the first account, the first signature needs to be verified by using a public key of the sender account, and in addition, the second signature needs to be verified by using a public key of the first account; in the event that both the first signature and the second signature are verified, the transaction Tx1 passes the transaction integrity check, otherwise it is determined that the transaction Tx1 is not verified.

In the case of defining minima of the required consumption digital resources in the blockchain system when a single transaction is successfully executed, the validation of transaction Tx1 may further include: determining a minimum value S of the digital resources required to be consumed by the transaction Tx1, and if the number S1 of the resources of the target resources which are permitted to be consumed by the transaction Tx1 is smaller than the minimum value S, determining that the transaction Tx1 is not verified.

After the transaction Tx1 is verified, the blockchain node may then perform step S205 to query the account balance cache information for the current resource number S0 of the target resource held by the first account, and determine whether the resource number S1 is greater than the current resource number S0.

The account balance cache information is independent of and corresponds to state data of the blockchain node. When the transaction pool is empty, the number of resources of the target resources held by any account recorded in the account balance cache information is the same as the number of resources of the target resources held by any account recorded in the state data of the blockchain node.

When the number of resources S1 is greater than the current number of resources S0, the target resources held by the first account may not be sufficient to pay for the target resources that the blockchain system needs to consume when it successfully performs the transaction Tx 1; the blockchain node may perform step S207 as follows, prohibiting the transaction Tx1 from being added to the transaction pool as a pending consensus transaction. Such as discarding or other processing of transaction Tx 1.

When the number of resources S1 is not greater than the current number of resources S0, the blockchain node may execute step S209 to subtract the target resources of the number of resources S1 from the first account in the account balance cache information, and add the transaction Tx1 to the transaction pool.

In the case where the transaction pool is divided into a plurality of transaction pool fragments, a target transaction pool fragment to which the transaction Tx1 belongs among the plurality of transaction pool fragments may be determined according to the sender account of the transaction Tx1, and the transaction Tx1 may be added to the target transaction pool fragment. The target transaction pool fragment to which the transaction Tx1 belongs may be determined, for example, from a hash value of the sender account or a corresponding binary string.

By fragmenting the transaction pools, the throughput and performance of transactions in each transaction pool fragment can be ensured according to the sender account of the transaction as the basis for determining the target transaction pool fragment to which the transaction belongs, so that the blockchain system can support super-large-scale accounts and extremely high CTPS, and extremely high transaction processing performance is realized.

In the case where the transaction pool is divided into a plurality of transaction pool slices, as shown in fig. 4, the plurality of transaction pool slices may correspond to a plurality of different account cache slices and to different playback prevention meta-information slices, i.e., one transaction pool slice may bind one account cache slice and one playback prevention meta-information slice.

The account cache shards may be used to cache account status of sender accounts for transactions in their corresponding transaction pool shards. The account status may include, for example, a sender account, a public key corresponding to the sender account, and a current resource number of the target resource held by the sender account recorded in the foregoing account balance cache information; in other words, the account balance cache information may be partitioned into a plurality of portions corresponding to the plurality of transaction pool slices according to the sender accounts to which the plurality of transaction pools correspond.

The anti-replay meta-information fragment may be used to buffer transaction information for transactions that were sent by the sender of the transaction in its corresponding transaction pool fragment (e.g., sent within a near set period of time) and that passed verification. The duration of the set period of time may be, for example, 5 minutes or 10 minutes, and may be set according to actual requirements, which is not specifically limited herein. The transaction information may be referred to as transaction meta-information or anti-replay meta-information, which may include any of the following: the hash value of the corresponding transaction, one or more of the items of information included in the corresponding transaction, for example, include the sender account and nonce value in the corresponding transaction. The nonce value may represent the number of transactions issued from the sender account. Further, the plurality of information may also include a time stamp.

In the case of performing a transaction playback check on a transaction, for example, transaction Tx1, for example, the corresponding playback meta information may be searched for from the corresponding playback meta information fragment, and the transaction playback check may be performed based on the searched playback meta information.

When the integrity check is performed on a transaction, for example, the transaction Tx1, for example, the public key corresponding to the account of the sender may be queried from the corresponding account cache in a sliced manner, and the integrity check may be performed based on the queried public key.

It should be noted that, when the current resource number S0 of the target resource held by the first account is queried from the account balance cache information, for example, the corresponding account cache partition may be determined according to the first account, and the current resource number S0 of the target resource held by the first account may be queried from the account cache partition.

It should be noted that, the account cache fragment and the playback prevention meta-information fragment may be located on the same device as the corresponding transaction pool fragment. It can be appreciated that account cache shards may share or exclusively share resources of the corresponding cache service; the playback-preventing meta-information fragments may also share or exclusively share resources of the corresponding cache service.

As described above, the blockchain node may select a plurality of transactions corresponding to a target block from the transaction pool according to a certain rule, generate a consensus proposal corresponding to the target block based on the plurality of transactions, and perform the plurality of transactions after completing consensus on the consensus proposal based on the various consensus mechanisms.

Referring to FIG. 5, a blockchain node includes, for example, a caching service for managing a pool of transactions, a consensus service for performing a consensus mechanism, a computing service for performing transactions, and a blockmanagement service for implementing scheduling and other blockmanagement transactions for transactions. The consensus service may select a plurality of transactions corresponding to a target block from a pool of transactions by invoking a caching service, generate a consensus proposal corresponding to the target block based on the plurality of transactions, and consensus the consensus proposal with remaining blockchain nodes in the blockchain system. After consensus is achieved on the consensus proposal, the computing service can execute the plurality of transactions and submit the execution results of the plurality of transactions to the block management service; the block management service may submit the target block and its corresponding status data based on the execution results of the transactions. In addition, the block management service may delete the plurality of transactions from the transaction pool by invoking the caching service after obtaining the execution result of the plurality of transactions.

It will be appreciated that the blockchain node may be configured to execute a single transaction to obtain an execution result that includes the resource payment account specified in the transaction and the number of resources that actually consume the target resource for the transaction.

In the process of executing the transaction Tx1 by the block chain node, the amount of resources consumed by the transaction Tx1 is accumulated relatively synchronously according to the amount of instructions consumed by the transaction Tx1 or the amount of data processed by executing the transaction Tx 1. Accordingly, after the block link point completes executing the transaction Tx1, there may be two cases where the resource amount S2 of the target resource is actually consumed.

In the first case, the blockchain node directly terminates the execution of the transaction Tx1, and the transaction Tx1 fails to execute, when the amount of resources consumed by the transaction Tx1 has reached the amount of resources S1 allowed to be consumed by the transaction Tx1 without ending the execution of the transaction Tx 1. The blockchain node deducts the amount of the target resource held by the first account according to the amount of the resource S1 allowed to be consumed by the transaction Tx1 in the state data thereof, that is, the amount of the resource S2 actually consumed by the transaction Tx1 is the same as the amount of the resource S1.

In the second case, the blockchain node may not exceed the amount of resources allowed for the transaction Tx1 to consume by the amount of resources S2 actually consumed by the transaction Tx1 if the execution of the transaction Tx1 has been completed. The blockchain node deducts the number of target resources held by the first account from the number of resources S2 actually consumed by the transaction Tx1 in its status data.

Since the amount of resources S1 allowed to be consumed by Tx1 may be different from the amount of resources S2 actually consumed by the transaction Tx1, the following steps S211 and S213 may be further performed after the block link point completes the execution of the transaction Tx1.

In step S211, the number S2 of the target resources consumed by the transaction Tx1 is obtained from the execution result of the transaction Tx1.

After the block chain link point completes execution of the transaction Tx1, the transaction Tx1 is deleted from the transaction pool. Accordingly, the blockchain node may obtain the number of resources S2 of the target resources consumed by the transaction Tx1 from the execution result of the transaction Tx1 in response to the operation of deleting the transaction Tx1 from the transaction pool.

In step S213, the target resource of the resource number S3 is added to the first account in the account balance cache information, and the resource number S3 is the difference between the resource number S1 and the resource number S2.

For a transaction Tx1 that a blockchain node receives from a client, after it completes validation of the transaction Tx1, the blockchain node may also need to send the transaction Tx1 to other blockchain nodes in the blockchain system so that the other blockchain nodes can perform corresponding consensus mechanisms and/or subsequent executions on the transaction Tx1. Accordingly, for a blockchain node performing the method of fig. 2 described above, it may also receive transactions such as transaction Tx2 from other blockchain nodes in the blockchain system; while other blockchain nodes may have deducted their holding target resources from the resource payment account specified by transaction Tx2 and the amount of resources allowed to be consumed by transaction Tx 2S 4 in their account balance cache information.

To ensure consistency of transaction processing by multiple blockchain nodes in the blockchain system, the blockchain points may process transactions Tx2 that it receives from other blockchain points by a different method than shown in fig. 2.

FIG. 6 is a second flowchart of a transaction processing method in a blockchain system provided in the embodiments of the present disclosure. The method is performed by a blockchain link point in a blockchain system that includes account balance cache information corresponding to status data. The method illustrates a process in which a blockchain node processes transaction Tx2 from other blockchain nodes.

First, at step S601, a transaction Tx2 is received from other block chain link points in the blockchain system, including a resource amount S4 that allows the transaction Tx2 to consume target resources, and a second account for paying for target resources consumed by the transaction Tx2.

The data structure of the transaction Tx2 can be referred to the data structure of the transaction Tx1 described above, and will not be described again.

The second account may be the same or different from the first account described previously.

Next, in step S603, the transaction Tx2 is verified.

The process of verifying transaction Tx2 is similar to that of verifying transaction Tx1, and will not be repeated.

When the transaction Tx2 passes the verification, step S605 may be followed, in which the target resource of the resource quantity S4 is deducted for the second account in the account balance cache information, and the transaction Tx2 is added to the transaction pool as a transaction to be consensus.

The process of adding transaction Tx2 pride to the transaction pool is similar to the process of adding transaction Tx1 to the transaction pool as described above, and will not be described again.

In step S607, after the blockchain node completes executing the transaction Tx2, the number of resources S5 of the target resources consumed by the transaction Tx2 is obtained from the execution result of the transaction Tx 2.

In step S609, the target resource of the resource number S6 is added to the second account in the account balance buffer information, where the resource number S6 is the difference between the resource number S4 and the resource number S5.

In the embodiment of the present disclosure, account balance cache information independent of status data is maintained in a blockchain node, and based on the account balance cache information, it is determined whether a transaction cannot be successfully executed due to insufficient payment of a target resource allowed for consumption of the transaction caused by payment of the target resource held by an account by a resource designated by the transaction, without frequent access to the status data.

For any account, although the account balance cache information and the number of resources of target resources held by the any account recorded in the status data may not be guaranteed to be equal at any moment, the account balance cache information and the number of resources of target resources held by the any account recorded in the status data may be guaranteed to be equal when no transaction exists in the transaction pool, so that it is guaranteed that whether a transaction may not be successfully executed due to insufficient target resources held by a designated resource payment account can be always determined based on the account balance cache information in the block link point operation process.

Based on the same conception as the foregoing method embodiments, a blockchain node 700 in a blockchain system is also provided in the embodiments of the present specification, where the blockchain node 700 includes account balance cache information corresponding to status data. Referring to fig. 7, the blockchain node 700 includes: a transaction receiving unit 701 configured to receive a first transaction from a client, including a first resource amount allowing the first transaction to consume a target resource, and a first account for paying for the first transaction to consume the target resource; a data processing unit 703 configured to query the account balance cache information for a current number of resources of the target resource held by the first account, and determine whether the first number of resources is greater than the current number of resources; the transaction scheduling unit 705 is configured to prohibit the first transaction from being added to the transaction pool as a transaction to be consensus, in case the first resource amount is larger than the current resource amount.

In one possible implementation, when there is no transaction in the transaction pool, the number of resources of the target resource held by any account recorded in the account balance cache information is the same as the number of resources of the target resource held by any account recorded in the state data of the blockchain node.

In a possible implementation manner, the data processing unit 703 is further configured to deduct, in the account balance cache information, the target resource of the first resource amount from the first account, if the first resource amount is not greater than the current resource amount; the transaction scheduling unit 705 is further configured to add the first transaction to the transaction pool if the first resource amount is not greater than the current resource amount; the data processing unit 703 is further configured to obtain, from an execution result of the first transaction, a second resource amount of the target resource consumed by the first transaction after the block link point completes execution of the first transaction; and adding a third resource amount of a target resource to the first account in the account balance cache information, wherein the third resource amount is a difference value between the first resource amount and the second resource amount.

In one possible embodiment, the transaction pool includes a plurality of transaction pool tiles; wherein the transaction scheduling unit 705 is specifically configured to determine, according to the account of the sender of the first transaction, a target transaction pool fragment to which the first transaction belongs in the plurality of transaction pool fragments; and adding the first transaction to the target transaction pool fragment.

In a possible implementation manner, the transaction scheduling unit 705 is specifically configured to obtain, in response to an operation of deleting the first transaction from the transaction pool, a second resource amount of the target resource consumed by the first transaction from an execution result of the first transaction.

In a possible implementation, the transaction receiving unit 701 is further configured to receive a second transaction from other blockchain points in the blockchain system, including a fourth resource amount that allows the second transaction to consume a target resource, and a second account for paying for the second transaction to consume the target resource; the data processing unit 703 is further configured to deduct the target resource of the fourth resource amount from the second account in the account balance cache information; the transaction scheduling unit 705 is further configured to add the second transaction as a transaction to be consensus to a transaction pool; the data processing unit 703 is further configured to obtain a fifth resource amount of the target resource consumed by the second transaction from an execution result of the second transaction after the execution of the second transaction is completed by the block link point; and adding a sixth resource amount of target resources to the second account in the account balance cache information, wherein the sixth resource amount is a difference value between the fourth resource amount and the fifth resource amount.

In one possible implementation, the blockchain node further includes: a transaction verification unit 707 configured to verify the first transaction before the querying the current resource amount of the target resource held by the first account from the account balance cache information.

In one possible implementation, the first transaction includes a transaction body, where the transaction body includes a sender account of the first transaction, the first account, and the first resource amount; the first transaction further comprises a first signature of the sender account on the transaction body and a second signature of the first account on the transaction body; wherein the transaction verification unit 707 is specifically configured to verify the first signature and the second signature.

There is also provided in embodiments of the present specification a computer readable storage medium having stored thereon a computer program/instructions which, when executed in a computer, cause the computer to perform the method steps of the various embodiments described above that are performed by a computing device or a data storage system.

Embodiments of the present disclosure also provide a computing device including a memory and a processor, where the memory stores a computer program/instruction that, when executed, implements the method steps performed by the computing device or data storage system in the foregoing embodiments.

In the 90 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable Gate Array, FPGA)) is an integrated circuit whose logic function is determined by the programming of the device by a user. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented by using "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before the compiling is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but not just one of the hdds, but a plurality of kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), lava, lola, myHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers, and embedded microcontrollers, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation device is a server system. Of course, the present application does not exclude that as future computer technology evolves, the computer implementing the functions of the above-described embodiments may be, for example, a personal computer, a laptop computer, a car-mounted human-computer interaction device, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

Although one or more embodiments of the present description provide method operational steps as described in the embodiments or flowcharts, more or fewer operational steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one way of performing the order of steps and does not represent a unique order of execution. When implemented in an actual device or end product, the instructions may be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment, or even in a distributed data processing environment) as illustrated by the embodiments or by the figures. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, it is not excluded that additional identical or equivalent elements may be present in a process, method, article, or apparatus that comprises a described element. For example, if first, second, etc. words are used to indicate a name, but not any particular order.

For convenience of description, the above devices are described as being functionally divided into various modules, respectively. Of course, when one or more of the present description is implemented, the functions of each module may be implemented in the same piece or pieces of software and/or hardware, or a module that implements the same function may be implemented by a plurality of sub-modules or a combination of sub-units, or the like. The above-described apparatus embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, read only compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage, graphene storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be used by the computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

One skilled in the relevant art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Moreover, one or more embodiments of the present description can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

One or more embodiments of the present specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the present description may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments. In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present specification. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the various embodiments or examples described in this specification and the features of the various embodiments or examples may be combined and combined by those skilled in the art without contradiction.

The foregoing is merely an example of one or more embodiments of the present specification and is not intended to limit the one or more embodiments of the present specification. Various modifications and alterations to one or more embodiments of this description will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, or the like, which is within the spirit and principles of the present specification, should be included in the scope of the claims.

Claims

1. A transaction processing method in a blockchain system, the method performed by a blockchain node in the blockchain system, the blockchain node including account balance cache information therein corresponding to status data, the method comprising:

receiving a first transaction from a client, including a first amount of resources that allows the first transaction to consume a target resource, and a first account for paying for the first transaction to consume the target resource;

inquiring the current resource quantity of the target resource held by the first account from the account balance cache information, and determining whether the first resource quantity is larger than the current resource quantity;

and when the first resource quantity is larger than the current resource quantity, prohibiting the first transaction from being added into a transaction pool as a transaction to be consensus.

2. The method of claim 1, wherein the number of resources of the target resource held by any account recorded in the account balance cache information is the same as the number of resources of the target resource held by any account recorded in the state data of the blockchain node when no transaction already exists in the transaction pool.

3. The method of claim 1, the method further comprising:

when the first resource quantity is not larger than the current resource quantity, deducting target resources of the first resource quantity from the first account in the account balance cache information, and adding the first transaction into the transaction pool;

after the block link point finishes executing the first transaction, acquiring a second resource quantity of the consumed target resource of the first transaction from an execution result of the first transaction;

and adding a target resource of a third resource quantity to the first account in the account balance cache information, wherein the third resource quantity is a difference value between the first resource quantity and the second resource quantity.

4. A method according to claim 3, the transaction pool comprising a plurality of pool slices; wherein the adding the first transaction as the transaction pool to be consensus transaction comprises:

Determining a target transaction pool fragment to which the first transaction belongs in the transaction pool fragments according to a sender account of the first transaction;

and adding the first transaction into the target transaction pool fragment.

5. The method of claim 3, after the block link point completes executing the first transaction, obtaining a second resource amount of the first transaction consumed target resource from an execution result of the first transaction, comprising: and responding to the operation of deleting the first transaction from the transaction pool, and acquiring a second resource quantity of the consumed target resource of the first transaction from an execution result of the first transaction.

6. The method of claim 1, the method further comprising:

receiving a second transaction from other blockchain points in the blockchain system, including a fourth amount of resources that allows the second transaction to consume target resources, and a second account for paying for the second transaction to consume target resources;

the target resources of the fourth resource quantity are deducted from the second account in the account balance cache information, and the second transaction is added into a transaction pool as a transaction to be consensus;

After the block chain link point finishes executing the second transaction, acquiring a fifth resource quantity of the consumed target resource of the second transaction from an execution result of the second transaction;

and adding a sixth resource amount of target resources to the second account in the account balance cache information, wherein the sixth resource amount is a difference value between the fourth resource amount and the fifth resource amount.

7. The method of any one of claims 1-6, the method further comprising: and verifying the first transaction before inquiring the current resource quantity of the target resource held by the first account from the account balance cache information.

8. The method of claim 7, the first transaction comprising a transaction body comprising a sender account of the first transaction, the first account, and the first resource amount; the first transaction further comprises a first signature of the sender account on the transaction body and a second signature of the first account on the transaction body;

wherein said verifying said first transaction comprises: verifying the first signature and the second signature.

9. A blockchain node in a blockchain system, the blockchain node including account balance cache information therein corresponding to status data, the method comprising:

a transaction receiving unit configured to receive a first transaction from a client, including a first resource amount allowing the first transaction to consume a target resource, and a first account for paying for the first transaction to consume the target resource;

the data processing unit is configured to query the current resource quantity of the target resource held by the first account from the account balance cache information and determine whether the first resource quantity is larger than the current resource quantity;

and the transaction scheduling unit is configured to prohibit the first transaction from being added into a transaction pool as a transaction to be consensus when the first resource quantity is larger than the current resource quantity.

10. The blockchain node of claim 9, wherein the number of resources of the target resource held by any account recorded in the account balance cache information is the same as the number of resources of the target resource held by any account recorded in the state data of the blockchain node when no transaction already exists in the transaction pool.

11. The blockchain node of claim 9, wherein:

the data processing unit is further configured to deduct a target resource of the first resource amount from the first account in the account balance cache information when the first resource amount is not greater than the current resource amount;

the transaction scheduling unit is further configured to add the first transaction to the transaction pool when the first resource amount is not greater than the current resource amount;

the data processing unit is further configured to acquire a second resource quantity of the consumed target resource of the first transaction from an execution result of the first transaction after the block link point completes execution of the first transaction; and adding a target resource of a third resource quantity to the first account in the account balance cache information, wherein the third resource quantity is a difference value between the first resource quantity and the second resource quantity.

12. The blockchain node of claim 11, the transaction pool comprising a plurality of transaction pool slices; the transaction scheduling unit is specifically configured to determine a target transaction pool fragment to which the first transaction belongs in the transaction pool fragments according to a sender account of the first transaction; and adding the first transaction to the target transaction pool fragment.

13. The blockchain node of claim 11, the transaction scheduling unit being specifically configured to obtain the second resource amount of the first transaction consumed target resource from an execution result of the first transaction in response to an operation of deleting the first transaction from the transaction pool.

14. The blockchain node of claim 9, wherein:

the transaction receiving unit is further configured to receive a second transaction from other blockchain points in the blockchain system, including a fourth resource amount that allows the second transaction to consume a target resource, and a second account for paying for the second transaction to consume the target resource;

the data processing unit is further configured to withhold the target resources of the fourth resource amount for the second account in the account balance cache information;

the transaction scheduling unit is further configured to add the second transaction as a transaction to be consensus to a transaction pool;

the data processing unit is further configured to obtain a fifth resource quantity of the target resources consumed by the second transaction from an execution result of the second transaction after the block link point completes execution of the second transaction; and adding a sixth resource amount of target resources to the second account in the account balance cache information, wherein the sixth resource amount is a difference value between the fourth resource amount and the fifth resource amount.

15. The blockchain node of any of claims 9-14, further comprising: and the transaction verification unit is configured to verify the first transaction before inquiring the current resource quantity of the target resource held by the first account from the account balance cache information.

16. The blockchain node of claim 15, the first transaction including a transaction ontology including a sender account of the first transaction, the first account, and the first resource amount therein; the first transaction further comprises a first signature of the sender account on the transaction body and a second signature of the first account on the transaction body; wherein the transaction verification unit is specifically configured to verify the first signature and the second signature.

17. A computing device comprising a memory having executable code stored therein and a processor, which when executing the executable code, implements the method of any of claims 1-8.

18. A computer readable storage medium having stored thereon a computer program which, when executed in a computing device, implements the method of any of claims 1-8.