WO2020173502A1

WO2020173502A1 - Block chain-based transaction system and transaction method

Info

Publication number: WO2020173502A1
Application number: PCT/CN2020/078673
Authority: WO
Inventors: 白杰; 李冬云; 吴先锋
Original assignee: 白杰
Priority date: 2019-02-26
Filing date: 2020-03-10
Publication date: 2020-09-03
Also published as: CN111614707A; CN111614709B; WO2020173498A1; CN111614709A; WO2020173501A1; JP2022517436A; CN111614708B; CN111614708A; JP7041993B2

Abstract

The present application provides a block chain-based transaction system and transaction method. Some nodes in the system are configured as transaction verification nodes, and some nodes other than the transaction verification nodes are configured as transaction accounting nodes. The transaction verification nodes may obtain a first transaction request from a first preset database and verify the validity of the first transaction request; the transaction accounting nodes may obtain a verified second transaction request from a second preset database, and perform accounting. In this way, the transaction verification nodes are responsible for verification of transactions, and the transaction accounting nodes are responsible for accounting. The two types of nodes have clear division of work. The efficiency of transaction verification is improved, and the time for transaction verification is shortened; the efficiency of transaction accounting is improved, and the time for transaction accounting is shortened; therefore, the situation of long-time waiting and a long transaction queue caused by too many transactions to be verified can be effectively avoided.

Description

A blockchain-based transaction system and transaction method. This application is required to be submitted to the Chinese Patent Office on February 26, 2019. The application number is 201910141898.7. The title of the invention is "Blockchain-based high-concurrency fast transaction and verification method" and The priority of a Chinese patent application filed with the Chinese Patent Office on August 8, 2019, the application number is 201910730034.9, and the invention title is "a blockchain-based transaction system and transaction method", the entire content of which is incorporated herein by reference Applying.

Technical field

This application relates to the field of blockchain technology, in particular to a blockchain-based transaction system and transaction method. Background technique

Blockchain is a chain data structure that combines data blocks in sequence in chronological order, and is a distributed ledger that cannot be tampered with or forged that is guaranteed by cryptography.

For transactions that occur in the blockchain, at least two steps are required to complete a transaction. The first step is used to verify whether the transaction is legal; the second step is used to verify that the transaction is legal. The transactions are accounted for and synchronized across the entire network, and the consensus of the entire network is finally completed. For example, when the Bitcoin network and the Ethereum network process transactions, the above two steps are performed simultaneously, that is, the block is generated while verifying the transaction. Verification and accounting belong to two different processes, and achieving “simultaneous” in a “parallel” manner is conducive to improving efficiency. However, the function of the block is to keep accounts, and the premise of keeping accounts is verification. Therefore, there will inevitably be a contradiction between the timing of "verification and accounting" and the parallelism of "verification and accounting". For example, when there are too many transactions to be verified, this kind of transaction mechanism is likely to cause a longer waiting time and more transaction queues.

Based on this, there is an urgent need for a blockchain-based transaction system to solve the problems that the transaction mechanism in the prior art tends to cause a long wait and more transaction queues when there are too many transactions to be verified.

Summary of the invention

This application provides a blockchain-based transaction system and transaction method, which can be used to solve the technical problems that the transaction mechanism in the prior art tends to cause a long waiting time and more transaction queues when there are too many transactions to be verified.

In the first aspect, an embodiment of the present application provides a blockchain-based transaction system, in which nodes in the system establish a network connection with each other; some nodes in the system are configured as transaction verification nodes, except for the transaction verification node Some other nodes are configured as transaction accounting nodes;

The transaction verification node is further configured to: obtain a first transaction request from a first preset database, and perform legality verification on the first transaction request, if the first transaction request passes the legality verification, Adding the signature of the transaction verification node to the first transaction request, and storing the first transaction request with the added signature in a second preset database;

The transaction accounting node is further configured to: obtain a second transaction request from a second preset database, and according to the signature attached to the second transaction request, if it is determined that the second transaction request is a legal transaction, generate the The first blockchain data corresponding to the second transaction request is stored in the first blockchain data. In a possible implementation manner, the transaction verification node is further configured to: receive a transaction request sent by a transaction initiation node or a neighboring node of the transaction verification node, and store the transaction request in a first preset database .

In a possible implementation, the transaction verification node is further configured to: obtain the historical verification times of the first transaction request from the first preset database, if the historical verification times of the first transaction request are greater than the first Threshold, abandoning the legality verification of the first transaction request, and storing the first transaction request in a second preset database; if the number of historical verifications of the first transaction request is less than or equal to the first threshold , Perform legality verification on the first transaction request.

In a possible implementation manner, the transaction verification node is further configured to: after verifying the validity of the first transaction request, update the number of historical verifications of the first transaction request.

In a possible implementation manner, the transaction verification node is further configured to: if the first transaction request fails the legality verification, ignore the first transaction request, and return to obtain from the first preset database The steps of 0T transaction request.

In a possible implementation manner, the transaction accounting node is further configured to: if the number of additional signatures in the second transaction request is greater than a second threshold, determine that the second transaction request is a legal transaction.

In a possible implementation, the transaction accounting node is further configured to: if the number of additional signatures in the second transaction request is less than or equal to a second threshold, determine that the second transaction request is illegal transaction.

In a possible implementation manner, the transaction accounting node is further configured to: after generating the blockchain data corresponding to the second transaction request, delete the second transaction from a second preset database request.

In a possible implementation manner, nodes other than the transaction verification node and the transaction verification node in the system are configured as transaction participating nodes;

The transaction participating node is further configured to: generate summary information corresponding to the first block chain data, and generate second block chain data according to the summary information, and store the second block chain data.

In the second aspect, an embodiment of the present application provides a blockchain-based transaction method, which is applied to a blockchain-based transaction system, and some nodes in the system are configured as transaction verification nodes, except for the transaction Some nodes other than the verification node are configured as transaction accounting nodes; the method includes:

The transaction verification node obtains the first transaction request from the first preset database, and performs legality verification on the first transaction request. If the first transaction request passes the legality verification, the first transaction request Attaching the signature of the transaction verification node to the transaction verification node, and storing the first transaction request with the additional signature in the second preset database;

The transaction accounting node obtains the second transaction request from the second preset database, and according to the signature attached to the second transaction request, if it is determined that the second transaction request is a legal transaction, generate the corresponding second transaction request The first blockchain data is stored in the first blockchain data.

In a possible implementation manner, the method further includes: The transaction verification node receives a transaction request sent by a transaction initiation node or a neighboring node of the transaction verification node, and stores the transaction request in a first preset database.

In a possible implementation, before the transaction verification node verifies the legality of the first transaction request, the method further includes:

The transaction verification node obtains the number of historical verifications of the first transaction request from the first preset database, and if the number of historical verifications of the first transaction request is greater than a first threshold, the legality of the first transaction request is abandoned Verifying, and storing the first transaction request in a second preset database; if the number of historical verifications of the first transaction request is less than or equal to a first threshold, verify the validity of the first transaction request.

In a possible implementation, after the transaction verification section verifies the legality of the first transaction request, the method further includes:

The transaction verification node updates the historical verification times of the first transaction request.

In a possible implementation manner, the method further includes:

If the first transaction request fails the legality verification, the transaction verification node ignores the first transaction request and returns to the step of obtaining a new transaction request from the first preset database.

In a possible implementation manner, the determination by the transaction accounting node that the second transaction request is a legal transaction includes:

If the number of additional signatures in the second transaction request is greater than the second threshold, the transaction accounting node determines that the second transaction request is a legal transaction.

In a possible implementation manner, the method further includes:

If the number of additional signatures in the second transaction request is less than or equal to the second threshold, the transaction accounting node determines that the second transaction request is an illegal transaction.

In a possible implementation, after the transaction accounting node generates the blockchain data corresponding to the second transaction request, the method further includes:

The transaction accounting node deletes the second transaction request from the second preset database.

The method also includes:

The transaction participating node generates summary information corresponding to the first block chain data, and generates second block chain data according to the summary information, and stores the second block chain data.

In the above block-based transaction system, the transaction verification node can obtain the first transaction request from the first preset database, and verify the legality of the first transaction request. If the first transaction request passes the legality verification, Add the signature of the transaction verification node to the transaction request, and store the first transaction request with the additional signature in the second preset database; the transaction accounting node can obtain the second transaction request from the second preset database, and according to The signature attached to the second transaction request can be generated if it is determined that the second transaction request is a legal transaction The first block chain data corresponding to the second transaction request, and the first block chain data is stored. Using the above transaction system, by configuring the nodes in the system as transaction verification nodes and transaction accounting nodes, different roles are assigned to the nodes in the system. In this way, the transaction verification node is responsible for verifying transactions, and the transaction accounting node is responsible for accounting , The two have a clear division of labor. For the transaction verification node, there is no need to rely on the completion status of the transaction accounting node, which can improve the efficiency of transaction verification and shorten the transaction verification time; for the transaction accounting node, the verified data can be obtained directly from the second preset database. The transaction request, without the need for transaction verification, can use resources for the contention of accounting rights and data synchronization, thereby improving the efficiency of transaction accounting and shortening the time of transaction accounting. In summary, the use of the transaction system provided by this application can effectively avoid the situation of long waiting and more transaction queues when there are too many transactions to be verified.

Description of the drawings

Figure 1 is a schematic structural diagram of a blockchain-based transaction system provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a process of processing transactions in a blockchain-based transaction system provided by an embodiment of the present application; FIG. 3 is a schematic diagram of a process of transactions occurring in a blockchain-based transaction system provided by an embodiment of the present application; FIG. 4 is The process corresponding to the method for a transaction verification node to perform legality verification provided by the embodiment of the application is not intended;

FIG. 5 is a schematic flow diagram corresponding to a method for processing transactions by a transaction accounting node according to an embodiment of the present application;

FIG. 6 is a schematic diagram of the overall flow of processing transactions by a transaction system provided by an embodiment of the present application.

detailed description

In order to make the purpose, technical solutions, and advantages of the present application clearer, the implementation of the present application will be described in further detail below in conjunction with the accompanying drawings.

In the technical solution provided by this application, the blockchain refers to the accounting data generated by transactions in the network system on the one hand, and refers to the network running blockchain technology, that is, the blockchain network. Among them, the blockchain network refers to a peer-to-peer (P2P) network with a decentralized application architecture. The blockchain network can perform distributed storage, public consensus, digital encryption, transaction accounting, and verification. It is a trading platform that covers distributed technology, cryptography, P2P network architecture, and various consensus algorithms that may be applied.

Blockchain or blockchain information is accounting information generated based on transaction data when transactions occur in the blockchain network, that is, multiple specific transactions form a block, and multiple blocks form a blockchain. In the blockchain network, including nodes that establish a peer-to-peer network connection with each other, each node is equipped with a corresponding consensus mechanism, such as a smart contract, and has sufficient computing power to perform transaction verification and accounting procedures. The nodes also have interface specifications that comply with a certain unified standard to realize access to more nodes or other types of blockchain networks through the interface specifications.

The following first introduces a possible system architecture applicable to the embodiment of the present application in conjunction with FIG. 1.

Please refer to FIG. 1, which exemplarily shows a schematic structural diagram of a blockchain-based transaction system provided by an embodiment of the present application. It can be seen from Figure 1 that the nodes in the transaction system provided by this application establish a network connection with each other. among them, Some nodes in the transaction system may be configured as transaction verification nodes, and some nodes other than the transaction verification nodes may be configured as transaction accounting nodes.

Taking the schematic diagram shown in Figure 1 as an example, in the current time period, node 1, node 2, node 3, and node 4 can be configured as transaction verification nodes, and node 5, node 6, node 7, and node 8 can be configured as Transaction accounting nodes, node 9, node 10, and node 11 may be configured as transaction participating nodes.

It should be noted that Fig. 1 is only an exemplary illustration, and this application does not limit the respective numbers of transaction verification nodes, transaction accounting nodes, and transaction participating nodes. In addition, Figure 1 shows only the configuration of each node in the trading system in one time period. In another time period, the configuration of each node in the trading system can be changed. For example, it was originally a node in the transaction verification node. 1. In the next time period, it may be configured as a transaction accounting node (or transaction participating node). Similarly, it was originally the node 5 in the transaction accounting node. In the next time period, it may be configured as a transaction verification node (or transaction participating node). Node); or, the configuration of each node in the transaction system may not be changed, which is not specifically limited.

Based on the system architecture shown in FIG. 1, FIG. 2 exemplarily shows a schematic diagram of a transaction processing flow of a blockchain-based transaction system provided by an embodiment of the present application.

As shown in FIG. 2, the transaction verification node (node 1 shown in FIG. 2) may be further configured to: obtain the first transaction request from the first preset database, and then perform legality verification on the first transaction request, If the first transaction request passes the legality verification, the signature of the transaction verification node is added to the first transaction request, and the first transaction request with the added signature is stored in the second preset database.

The transaction verification node may be further configured to: if the first transaction request fails the legality verification, ignore the first transaction request, and return to the step of obtaining a new transaction request from the first preset database (not shown in FIG. 2 ).

The transaction accounting node (node 5 shown in Figure 2) is further configured to: obtain a second transaction request from a second preset database, and according to the signature attached to the second transaction request, if the second transaction request is determined If it is a legal transaction, the first block chain data corresponding to the second transaction request is generated, and the first block chain data is stored.

In the above block-based transaction system, the transaction verification node can obtain the first transaction request from the first preset database, and verify the legality of the first transaction request. If the first transaction request passes the legality verification, Add the signature of the transaction verification node to the transaction request, and store the first transaction request with the additional signature in the second preset database; the transaction accounting node can obtain the second transaction request from the second preset database, and according to For the signature attached to the second transaction request, if it is determined that the second transaction request is a legal transaction, the first blockchain data corresponding to the second transaction request may be generated, and the first blockchain data may be stored. Using the above transaction system, by configuring the nodes in the system as transaction verification nodes and transaction accounting nodes, different roles are assigned to the nodes in the system. In this way, the transaction verification node is responsible for verifying transactions, and the transaction accounting node is responsible for accounting , The two have a clear division of labor. For the transaction verification node, there is no need to rely on the completion status of the transaction accounting node, which can improve the efficiency of transaction verification and shorten the transaction verification time; for the transaction accounting node, the verified data can be obtained directly from the second preset database. The transaction request, without the need for transaction verification, can use resources for the contention of accounting rights and data synchronization, thereby improving the efficiency of transaction accounting and shortening the time of transaction accounting. In summary, the use of the transaction system provided by this application can effectively avoid waiting for a long time when there are too many transactions to be verified When there are too many queues for transactions.

Specifically, the first preset database may be presented in the form of a table, or may also be presented in the form of a queue, which is not specifically limited, and the first preset database may include multiple transactions to be verified. Correspondingly, the second preset database may be presented in the form of a table, or may also be presented in the form of a queue, which is not specifically limited, and the second preset database may include multiple verified transactions.

It should be noted that: (1) The first preset database and the second preset database may be two independent databases, or may also be the same database; when the first preset database and the second preset database are the same In the case of a database, the transaction verification node can directly add the signature of the transaction verification node to the first transaction request, and the transaction accounting node can directly obtain the second transaction request with the additional oil signature. (2) Both the first preset database and the second preset database can process transaction requests in the database on a first-in first-out principle.

In the specific implementation process, as shown in FIG. 3, a schematic diagram of a transaction process in a blockchain-based transaction system is provided for this embodiment of the application.

The transaction verification node (node 1 shown in FIG. 3) is further configured to: receive a transaction request, and store the transaction request in a first preset database.

It can be seen from Figure 3 that the transaction request received by the transaction verification node (ie node 1) comes from node 0. Node 0 can be the transaction initiating node or the neighboring node of the transaction verification node (ie, node 1). In other words, the transaction verification node (node 1 as shown in Figure 3) can be further configured to: receive the transaction request sent by the transaction initiating node or the neighboring node of the transaction verification node.

Depending on the actual application environment, the transaction form between the transaction initiation point and the transaction verification node is also different. There may be two situations in which the transaction verification node receives the transaction request sent by the transaction initiation node.

In one situation, if the transaction initiation node can conduct a transaction or information interaction with the direct transaction verification node, it can directly send a transaction request to the transaction verification node through the transaction initiation node. This method is most suitable for transactions where the transaction initiating node and the transaction verification node are in the same blockchain network, that is, the transaction initiating node is also a node in the transaction system.

Another situation is that if the transaction initiating node cannot directly conduct a transaction or information interaction with the transaction verification node, the transaction request can be broadcast through the transaction initiating node. Specifically, it can first broadcast the transaction request to the neighboring nodes, and then the neighboring nodes combine their own roles to determine whether to complete the transaction or continue broadcasting until the transaction verification node receives the transaction request.

The situation corresponding to the transaction verification node receiving the transaction data sent by its neighboring nodes may be that the transaction initiating node does not know the location information of the transaction verification node, and sends the transaction request in the blockchain through broadcast. In this way, as the information spreads, the transaction The verification node can receive the transaction request through its neighboring nodes.

It should be noted that the above two situations are only illustrative. In other possible examples, if the transaction initiating node is a neighboring node of the transaction verification node, then the transaction verification node can also be regarded as directly receiving the transaction initiation node The transaction request sent.

In the embodiment of the present application, there may be multiple nodes that are also transaction verification nodes. Then, when a transaction occurs, there may be a situation in which multiple transaction verification nodes all receive the transaction request. At this time, in order to avoid multiple transactions The verification node stores the same transaction request in the first preset database, so that if the transaction accounting node records multiple times, a consensus can be reached between the transaction verification nodes. For example, for the same transaction request, it is agreed to be stored as early as the first The transaction request in the preset database is valid; for another example, a decentralized method is adopted to determine whether to perform accounting according to the storage times of the transaction request.

In the specific implementation process, a possible implementation manner is that after receiving the transaction request, the transaction verification node can query whether there are the same transaction requests in the first preset database. If there is no same transaction request in the first preset database, The transaction request is stored in the first preset database; if there is the same transaction request in the first preset database, the transaction request is ignored.

Another possible implementation manner is that, after the transaction verification node stores the received transaction request in the first preset database, it may also broadcast it in the transaction system, so as to notify other transaction verification nodes that it is not necessary to store the transaction request.

Another possible implementation manner is that after multiple transaction verification nodes all receive the transaction request, the multiple transaction verification nodes all verify the transaction request, and store the transaction request in the first preset database in a sequential order; further, the transaction record The accounting node can determine whether the accounting operation can be performed according to the number of times the transaction request is stored (that is, the number of verifications). Further, after the transaction accounting node completes the accounting operation, the transaction verification node can synchronize the data block To confirm that the transaction has been booked, and then delete the transaction request of the first preset database.

In the embodiment of this application, when the transaction verification node verifies the legality of the first transaction request, in an example, after the transaction verification node determines that the first transaction request passes the legality verification, the transaction verification may be added to the first transaction request. The signature of the node and the first transaction request with the additional signature are stored in the second preset database.

In another example, considering that the transaction verification node may have verification errors, if only one transaction verification node verifies the first transaction request, the verification result may be incorrect. Therefore, this application embodiment also provides another method for the transaction verification node to perform legality verification.

As shown in FIG. 4, it is a schematic diagram of a flow corresponding to a method for a transaction verification node to perform legality verification provided by an embodiment of this application.

The transaction verification node (node 1 as shown in Figure 4) may be further configured to: obtain the historical verification times of the first transaction request from the first preset database, if the historical verification times of the first transaction request are greater than the first Threshold, abandon the legality verification of the first transaction request, and store the first transaction request in the second preset database; if the number of historical verifications of the first transaction request is less than or equal to the first threshold, the first transaction request Perform legality verification.

That is, in the method shown in Figure 4, multiple transaction verification nodes can verify the same transaction request multiple times. Only when the number of historical verifications of the transaction request is greater than the first threshold, indicating that the transaction request is recognized by multiple transaction verification nodes (the number of historical verifications is greater than or equal to the number of transaction verification nodes), then the transaction verification node will have The signed transaction request is stored in the second preset database.

It should be noted that the first threshold may be determined by those skilled in the art based on experience and actual conditions, and is not specifically limited.

Further, if the first transaction request is legal, the signature of the transaction verification node is added to the first transaction request. Name; if the first transaction request is illegal, the first transaction request is ignored.

Furthermore, after the transaction verification node completes the legality verification of the first transaction request, it may update the historical verification times of the first transaction request, and store the updated historical verification times in the first preset database.

Using the above method, the number of verifications for the transaction request in the first preset database can be limited. In this way, the verification efficiency of the transaction verification node can be further improved, and the verification waiting time of other transaction requests can be shortened.

In the embodiment of the present application, when the transaction verification node verifies the legality of the transaction request, only after determining that the transaction request passes the legality verification, the transaction verification node's signature is appended to the transaction request. In other words, for a transaction request that fails the legality verification, the transaction request will not be accompanied by the signature of the transaction verification node.

Based on this, the transaction accounting node determines whether the second transaction request is a legal transaction, which can be determined according to the signature attached to the second transaction request.

Specifically, as shown in FIG. 5, it is a schematic flow diagram corresponding to a method for processing transactions by a transaction accounting node provided in an embodiment of this application. The transaction accounting node (node 5 shown in Figure 5) may be further configured to: if the number of additional signatures in the second transaction request is greater than the second threshold, determine that the second transaction request is a legal transaction; If the number of additional signatures in the transaction request is less than or equal to the second threshold, it is determined that the second transaction request is an illegal transaction.

It should be noted that the second threshold may be determined by those skilled in the art based on experience and actual conditions, and is not specifically limited.

Further, if it is determined that the second transaction request is a legal transaction, the first block chain data corresponding to the second transaction request is generated, and the first block chain data is stored; if the second transaction request is an illegal transaction, then The second preset database deletes the second transaction request.

Furthermore, as shown in FIG. 5, the transaction accounting node (node 5 shown in FIG. 5) may be further configured to: after generating the blockchain data corresponding to the second transaction request, from the second The second transaction request is deleted from the preset database.

In order to more clearly describe a blockchain-based transaction system provided by an embodiment of the present application, the overall flow of the transaction system in the present application for processing transactions will be described below with reference to FIG. 6.

As shown in Figure 6, when sending a transaction, the transaction verification node (node 1 shown in Figure 6) can receive the transaction from the transaction initiating node or the neighboring node of the transaction verification node (node 0 shown in Figure 6). The transaction request, and the transaction request is stored in the second preset database.

In addition, the transaction verification node (node 1 shown in FIG. 6) can also obtain the first transaction request from the first preset database, and then verify the legality of the first transaction request. If the first transaction request passes the legality Verification, the signature of the transaction verification node is added to the first transaction request, and the first transaction request with the additional signature is stored in the second preset database; if the first transaction request fails the legality verification, the first transaction is ignored Request, and return to the step of obtaining a new transaction request from the first preset database.

The transaction accounting node (node 5 as shown in Figure 6) can obtain the second transaction from the second preset database Request, and according to the signature attached to the second transaction request, if it is determined that the second transaction request is a legal transaction, the first blockchain data corresponding to the second transaction request is generated, the first blockchain data is stored, and the second preset The database deletes the second transaction request.

The transaction accounting node (node 5 shown in Figure 6) deletes the second transaction request from the second preset database if it determines that the second transaction request is an illegal transaction according to the signature attached to the second transaction request.

Transaction participating nodes (node 9 as shown in Figure 6) can generate summary information corresponding to the first blockchain data, and generate second blockchain data according to the summary information, and store the second blockchain data.

It should be noted that the transaction participating node is essentially a user of the network, and it completes its own business and transaction by querying the second preset database of the transaction verification node and synchronizing the first blockchain data with the transaction accounting node The closed loop. In this process, for scenarios with low real-time requirements, the final confirmation can be made through the first blockchain data, and for those with high real-time requirements, the relevant confirmation can be quickly completed by querying the second preset database.

In this way, the transaction verification node can obtain the first transaction request from the first preset database and verify the legality of the first transaction request. If the first transaction request passes the legality verification, the transaction verification is appended to the first transaction request. The signature of the node, and the first transaction request with the additional signature stored in the second preset database; the transaction accounting node can obtain the second transaction request from the second preset database, and according to the additional signature in the second transaction request Sign, if it is determined that the second transaction request is a legal transaction, the first blockchain data corresponding to the second transaction request can be generated, and the first blockchain data can be stored. The transaction participating node can generate summary information corresponding to the first block chain data, and generate second block chain data according to the summary information, and store the second block chain data. Using the above transaction system, by configuring the nodes in the system as transaction verification nodes and transaction accounting nodes, different roles are assigned to the nodes in the system. In this way, the transaction verification node is responsible for verifying transactions, and the transaction accounting node is responsible for accounting , The two have a clear division of labor. For the transaction verification node, there is no need to rely on the completion status of the transaction accounting node, which can improve the efficiency of transaction verification and shorten the transaction verification time; for the transaction accounting node, the verified data can be obtained directly from the second preset database. The transaction request, without the need for transaction verification, can use resources for the contention of accounting rights and data synchronization, thereby improving the efficiency of transaction accounting and shortening the time of transaction accounting. In summary, the use of the transaction system provided by this application can effectively avoid the situation where there are too many transactions to be verified, which will cause longer waiting times and more transaction queues.

Based on the same inventive concept, the embodiments of the present application also provide a blockchain-based transaction method, which is applied to a blockchain-based transaction system, and some nodes in the system are configured as transaction verification nodes, except Some nodes other than the transaction verification node are configured as transaction accounting nodes; the method includes:

The transaction accounting node obtains the second transaction request from the second preset database, and according to the signature attached to the second transaction request, if it is determined that the second transaction request is a legal transaction, generate the corresponding second transaction request The first blockchain data is stored in the first blockchain data. In a possible implementation manner, the method further includes:

The transaction verification node receives a transaction request sent by a transaction initiation node or a neighboring node of the transaction verification node, and stores the transaction request in a first preset database.

In a possible implementation manner, the method further includes:

The method also includes:

Using the above transaction method, the transaction verification node is responsible for verifying the transaction, and the transaction accounting node is responsible for bookkeeping, and the division of labor is clear. For the transaction verification node, there is no need to rely on the completion status of the transaction accounting node, which can improve the efficiency of transaction verification and shorten the transaction verification time; for the transaction accounting node, the verified data can be obtained directly from the second preset database. Transaction request without the need to verify the transaction. All resources can be used The competition for accounting rights and the synchronization of data can improve the efficiency of transaction accounting and shorten the time for transaction accounting. In summary, the use of the transaction system provided by this application can effectively avoid the situation of long waiting and more transaction queues when there are too many transactions to be verified.

In an exemplary embodiment, a computer-readable storage medium is also provided, in which a computer program or smart contract is stored, and the computer program or smart contract is loaded and executed by a node to implement the above-mentioned embodiments. Transaction processing method. Optionally, the aforementioned computer-readable storage medium may be a read-only storage memory

(Read-Only Memory, ROM), Random Access Memory (RAM),

CD-ROM, magnetic tape, floppy disk and optical data storage device etc.

Those skilled in the art can clearly understand that the technology in the embodiments of the present application can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solutions in the embodiments of the present application can be embodied in the form of software products, which can be stored in a storage medium, such as ROM/RAM. , Magnetic disks, optical disks, etc., include a number of instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in each embodiment or some parts of the embodiment of the present application.

Those skilled in the art will easily think of other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptive changes of the present disclosure, and these variations, uses, or adaptive changes follow the general principles of the present disclosure and include common knowledge or conventional technical means in the technical field that are not disclosed in the present disclosure. . The description and embodiments are only regarded as exemplary, and the true scope and spirit of the present disclosure are pointed out by the following claims.

It should be understood that the present disclosure is not limited to the precise structure that has been described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present disclosure is only limited by the appended claims.

Claims

1. A blockchain-based transaction system, in which nodes in the system establish a network connection with each other; characterized in that, some nodes in the system are configured as transaction verification nodes, except for the transaction verification nodes The node is configured as a transaction accounting node;

The transaction accounting node is further configured to: obtain a second transaction request from a second preset database, and according to the signature attached to the second transaction request, if it is determined that the second transaction request is a legal transaction, generate the The first blockchain data corresponding to the second transaction request is stored in the first blockchain data.

2. The system according to claim 1, wherein the transaction verification node is further configured to: receive a transaction request sent by a transaction initiating node or a neighboring node of the transaction verification node, and store the transaction request in The first preset database.

3. The system according to claim 1, wherein the transaction verification node is further configured to: obtain the historical verification times of the first transaction request from the first preset database, if the If the number of historical verification times is greater than the first threshold, the legality verification of the first transaction request is abandoned, and the first transaction request is stored in a second preset database; if the historical verification times of the first transaction request If it is less than or equal to the first threshold, verify the validity of the first transaction request.

4. The system according to claim 3, wherein the transaction verification node is further configured to: after verifying the validity of the first transaction request, update the number of historical verifications of the first transaction request .

5. The system according to claim 1, wherein the transaction verification node is further configured to: if the first transaction request fails the legality verification, ignore the first transaction request, and return the slave A step of obtaining a new transaction request in a preset database.

6. The system according to claim 1, wherein the transaction accounting node is further configured to: if the number of additional signatures in the second transaction request is greater than a second threshold, determine the second transaction The request is a legitimate transaction.

7. The system according to claim 6, wherein the transaction accounting node is further configured to: if the number of additional signatures in the second transaction request is less than or equal to a second threshold, determine the first 2. The transaction request is an illegal transaction.

8. The system according to claim 1, wherein the transaction accounting node is further configured to: after generating the blockchain data corresponding to the second transaction request, from a second preset database Delete the second transaction request.

9. The system according to claim 1, wherein nodes other than the transaction verification node and the transaction verification node in the system are configured as transaction participating nodes;

10. A blockchain-based transaction method, characterized in that the method is applied to a blockchain-based transaction system, and some nodes in the system are configured as transaction verification nodes, except for the transaction verification nodes Some nodes of are configured as transaction accounting nodes; the method includes: