WO2020233086A1

WO2020233086A1 - Block processing method and apparatus, computer device and storage medium

Info

Publication number: WO2020233086A1
Application number: PCT/CN2019/122676
Authority: WO
Inventors: 褚镇飞; 冯世伟; 张培培
Original assignee: 深圳壹账通智能科技有限公司
Priority date: 2019-05-20
Filing date: 2019-12-03
Publication date: 2020-11-26
Also published as: CN110245126A

Abstract

A block processing method, comprising: acquiring a transaction commit instruction; querying the current cached block sequence for a configuration block according to the transaction commit instruction; when the configuration block is found, segmenting, by using the found configuration block as a segmentation reference point, the block sequence into a configuration block and a transaction block sequence; performing transaction commit operations on the configuration block and the transaction blocks in the transaction block sequence in the order of the block sequence; wherein the transaction commit operations performed on the plurality of transaction blocks in the transaction block sequence comprise: performing, in parallel, transaction signature verifications on the plurality of transaction blocks; serially performing multi-version transaction checks on each of the transaction blocks; and concurrently writing the plurality of transaction blocks into a disk.

Description

Block processing method, device, computer equipment and storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on May 20, 2019, the application number is 2019104201125, and the application name is "block processing method, device, computer equipment and storage medium", the entire content of which is by reference Incorporated in this application.

Technical field

This application relates to a block processing method, device, computer equipment and storage medium.

Background technique

Blockchain is usually understood as a distributed ledger, essentially a block-based distributed database. Blockchain includes consortium chains used between institutions. The privacy protection mechanism of consortium chains is usually realized based on signature encryption and verification and decoding in cryptography, so that only members of specific groups and limited third parties can view the area according to their authority. Block transaction. The block transaction submission process of the alliance chain includes three steps: signature verification, multi-version checking and transaction persistence.

At present, for one or more blocks generated and sent by the consensus node, the data node usually executes the transaction commit process for the transactions in each block in sequence according to the block generation order through a single thread. However, the inventor realized that when a data node executes the transaction submission process of a block through a single thread, it can usually only process fewer transactions, which reduces the overall throughput of the blockchain system and wastes the computer resources of the server where the data node is located. . Especially when the block contains only a few transactions, the overall throughput of the blockchain system is further reduced, and the submission efficiency of block transactions is reduced, thereby reducing the efficiency of block processing.

Summary of the invention

According to various embodiments disclosed in the present application, a block processing method, device, computer equipment, and storage medium are provided.

A block processing method includes:

Obtain transaction commit instructions;

Query the configuration block in the currently cached block sequence according to the transaction commit instruction;

When the configuration block is queried, the block sequence is divided into a configuration block and a transaction block sequence using the queried configuration block as a division reference point; and

A transaction commit operation is performed on the configuration block and the transaction block in the transaction block sequence respectively according to the sequence of the block sequence; transaction commit performed on multiple transaction blocks in the transaction block sequence The operations include: performing transaction signature verification on the plurality of transaction blocks in parallel; performing transaction multi-version checking on each of the transaction blocks serially; and simultaneously writing the plurality of transaction blocks to a disk.

A block processing device includes:

Obtaining module for obtaining transaction commit instructions;

The query module is used to query the configuration block in the currently cached block sequence according to the transaction commit instruction;

The segmentation module is used to, when the configuration block is queried, use the queried configuration block as a splitting reference point to split the block sequence into a configuration block and a transaction block sequence; and

The commit module is configured to perform transaction commit operations on the configuration block and the transaction block in the transaction block sequence according to the sequence of the block sequence; for multiple transaction areas in the transaction block sequence The transaction commit operation performed by the block includes: performing transaction signature verification on the multiple transaction blocks in parallel; performing multi-version check on each transaction block serially; writing the multiple transaction blocks simultaneously Into the disk.

A computer device includes a memory and one or more processors. The memory stores computer readable instructions. When the computer readable instructions are executed by the one or more processors, the one or more Each processor implements the steps of the block processing method provided in any embodiment of the present application.

One or more non-volatile computer-readable storage media storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors implement any of the present application The steps of the block processing method provided in an embodiment.

The details of one or more embodiments of the application are set forth in the following drawings and description. Other features and advantages of this application will become apparent from the description, drawings and claims.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed in the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work.

Fig. 1 is an application scenario diagram of a block processing method according to one or more embodiments.

Fig. 2 is a schematic flowchart of a block processing method according to one or more embodiments.

FIG. 3 is a schematic flowchart of a block processing method in another embodiment.

FIG. 4 is a schematic flowchart of a transaction commit operation performed on multiple transaction blocks in a transaction block sequence according to one or more embodiments.

Fig. 5 is a block diagram of a block processing device according to one or more embodiments.

Figure 6 is a block diagram of a computer device according to one or more embodiments.

Detailed ways

In order to make the technical solutions and advantages of the present application clearer, the following further describes the present application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the application, and not used to limit the application.

The block processing method provided in this application can be applied to the application environment shown in FIG. 1. The data node 102 communicates with the consensus node 104 through the network. The data node 102 obtains the transaction commit instruction, and queries the configuration block in the currently cached block sequence according to the obtained transaction commit instruction; when the configuration block is queried, the queried configuration block is used as the dividing reference point, and the current The cached block sequence is divided into a configuration block and a transaction block sequence, and the transaction commit operation is performed on the configuration block and the transaction block in the transaction block sequence respectively according to the sequence of the block sequence. The transaction commit operation performed by the data node 102 for multiple transaction blocks in the transaction block sequence includes: performing transaction signature verification on multiple transaction blocks in parallel; performing transaction multi-version checks on each transaction block serially; Write multiple transaction blocks to disk at the same time. It is understandable that the data node 102 receives the block sent by the consensus node 104 and caches the received block so that the data node 102 can execute the block processing method described above when it obtains the transaction commit instruction. Both the data node 102 and the consensus node 104 correspond to a server, and the server can be implemented by an independent server or a server cluster composed of multiple servers. The data node 102 and the data node 102 both belong to the blockchain network, and the blockchain network includes multiple data nodes 102 and multiple data nodes 102. In one of the embodiments, a data node is a server, and correspondingly, a consensus node is a server.

In one of the embodiments, as shown in FIG. 2, a block processing method is provided. Taking the method applied to the data node in FIG. 1 as an example, the method includes the following steps:

S202: Obtain a transaction commit instruction.

The transaction commit instruction is an instruction used to trigger the transaction commit operation. Specifically, when the previously executed transaction commit operation is completed, the data node detects in real time whether there is a block sequence to be processed currently in the cache. When a block sequence to be processed is detected in the cache, the data node triggers the generation of a transaction commit instruction corresponding to the block sequence.

In one of the embodiments, the transaction commit operation performed last time may be a transaction commit operation performed on multiple transaction blocks in the configuration block, transaction block sequence, or currently cached block sequence. It is understandable that both the transaction block sequence and the block sequence can include a single transaction block.

In one of the embodiments, the data node receives the block (transaction block or configuration block) sent by the consensus node, and caches the received block in the local cache. The data node can cache the received block in the cache queue. When multiple blocks are received at the same time, the data node sequentially caches the blocks in the cache queue according to their block numbers.

S204: Query the configuration block in the currently cached block sequence according to the transaction commit instruction.

A block sequence is a block set composed of multiple blocks arranged according to their respective block numbers. The block can be a transaction block or a configuration block. The transaction block corresponds to the transaction block identifier, and the configuration block corresponds to the configuration block identifier. The transaction data in the transaction block corresponds to the business data. The transaction data in the configuration block corresponds to the configuration data. The configuration data refers to the data on which the data node performs the transaction commit operation on the transaction block or the configuration block, such as verification logic or rule parameters. For example, when the number of digital signatures that have passed the verification reaches the preset number threshold, it is determined that the signature verification result of the corresponding transaction is verified, and the verification logic or rule parameter may be the preset number threshold.

Specifically, when the transaction commit instruction is acquired, the data node queries the currently cached block sequence in the cache or cache queue according to the acquired transaction commit instruction, and according to the pre-configured configuration block sequence identifier, the current cache Query the configuration block in the block sequence to determine whether there is a configuration block in the currently cached block sequence according to the query result.

S206: When the configuration block is queried, the block sequence is divided into a configuration block and a transaction block sequence using the queried configuration block as a dividing reference point.

The transaction block sequence is a block set composed of multiple transaction blocks arranged according to their respective block numbers. The transaction block sequence may specifically be a block set composed of multiple transaction blocks with continuous block numbers arranged according to their respective block numbers.

Specifically, when the configuration block is queried in the currently cached block sequence, the data node uses the queried configuration block as a dividing reference point to divide the block sequence into a configuration block and a transaction block sequence. It is understandable that one or more transaction block sequences can be obtained by dividing the block sequence with the configuration block as the dividing reference point.

In one of the embodiments, when the queried configuration block is located at the critical position (starting position or end position) of the block sequence, the data node divides the block sequence into configuration blocks and a transaction block sequence. When the queried configuration block is located in the middle of the block sequence, the data node divides the block sequence into a configuration block and two transaction block sequences. It is understandable that when multiple configuration blocks are queried in the currently cached block sequence, the data node uses the multiple configuration blocks as the dividing reference point to divide the block sequence into multiple configuration blocks and Sequence of multiple transaction blocks.

For example, suppose the block sequence includes blocks a, b, c, d, e, and f, and d is the configuration block. According to dividing the block sequence into configuration block d, the transaction block sequence X (including transaction Blocks a, b, and c), and transaction block sequence Y (including transaction blocks e and f).

S208: Perform transaction commit operations on the configuration block and transaction blocks in the transaction block sequence respectively in the order of the block sequence; the transaction commit operations performed on multiple transaction blocks in the transaction block sequence include: Transaction signature verification is performed on multiple transaction blocks; multiple transaction versions are checked for each transaction block serially; multiple transaction blocks are simultaneously written to the disk.

Transaction signature verification refers to verifying whether the digital signature corresponding to the transaction in the block meets the preset signature conditions. The preset signature condition, for example, the number of digital signatures that have passed the verification reaches a preset number threshold. Transaction multi-version checking refers to checking whether the target data version number contained in the transaction in the block is consistent with the corresponding latest data version number.

Specifically, when the currently cached block sequence is divided into a configuration block and a transaction block sequence, the data nodes respectively perform the configuration block and transaction block sequence according to the order of the configuration block and transaction block sequence in the block sequence. The transaction block in the block sequence performs the transaction commit operation. The transaction commit operation performed for the configuration block includes: the data node performs transaction signature verification on the transaction in the configuration block; when the transaction signature verification step is completed, the data node performs multiple transactions on the transaction in the configuration block Version check: When the multi-version check step of the transaction is completed, the data node calls the preset write interface to write the configuration block to the disk, that is, write the configuration block to the corresponding blockchain. It is understandable that when the transaction signature verification step is executed, the data node writes the signature verification result into the configuration block, and performs multiple transactions for the transaction whose signature verification result in the configuration block is verified. Version check; when the result of the multi-version check is passed, the data node updates its configuration data according to the transaction data corresponding to the transaction that passed the check, so that the data node can use the updated configuration data for all subsequent configuration blocks. Configure the block or transaction block to perform transaction commit operations. Correspondingly, the data node writes the multi-version check result into the configuration block, and writes the configuration block to the disk,

Further, the transaction commit operation performed on multiple transaction blocks in the transaction block sequence includes: the data node performs transaction signature verification on the multiple transaction blocks in parallel through multiple verification threads; When the transaction signature verification steps performed by the transaction block are all executed, the data node serially performs multi-version check on each transaction block through a single check thread, that is, the data node performs multi-version check on each transaction block according to the multiple transaction blocks. In the sequence of the sequence, the transaction multi-version check is performed on each transaction block in turn; when the transaction multi-version check for each transaction block is sequentially executed, the data node calls the preset write interface to write the multiple transaction blocks Disk. The preset write interface may specifically be a preset batch write interface, and the data node can call the batch write interface to write multiple transaction blocks into the disk at one time.

In one of the embodiments, when the number of transaction blocks in the transaction block sequence is less than or equal to the preset number, the data node determines the number of check threads equal to the number of transaction blocks, and compares the number of check threads in the transaction block sequence Each transaction block is allocated to a corresponding verification thread to perform transaction signature verification on the allocated transaction block in parallel by the verification thread of the number of transaction blocks. When the number of transaction blocks is greater than the preset number, the data node determines the preset number of verification threads, and allocates multiple transaction blocks in the transaction block sequence to the preset number of verification threads to pass the preset number. Suppose a number of verification threads perform transaction signature verification on the allocated transaction blocks in parallel.

Next, the above example will illustrate, when the block sequence is divided into configuration block d and transaction block sequence X (including transaction blocks a, b, and c), and transaction block sequence Y (including transaction blocks e and f) ), the data node first performs transaction commit operations on transaction blocks a, b, and c in the transaction block sequence X according to the sequence of the block sequence; when the transaction commit operation for the transaction block sequence X is completed, the data The node performs transaction commit operation on configuration block d, and updates its own configuration data according to the configuration data in configuration block d; when the transaction commit operation for configuration block d is completed, the data node performs transaction block sequence Y The transaction blocks e and f perform transaction commit operations.

It is understandable that in the process of executing the transaction commit operation on the transaction block in the transaction block sequence X, and/or in the process of executing the transaction commit operation on the configuration block d, the data node may receive the consensus The block sent by the node (transaction block or configuration block), and the received block is cached as a new block. Therefore, the transaction block sequence Y may also include blocks newly added during the transaction commit operation on the transaction block sequence X and the configuration block d. When the transaction commit operation for configuration block d is completed, the data node can use transaction block sequence Y as the currently cached block sequence, and query whether there is a configuration block in the currently cached block sequence according to the above query method, According to the query result, the transaction commit operation is performed on the block sequence according to the method provided in the corresponding embodiment of this application.

In the block processing method described above, when a transaction commit instruction is acquired, the configuration block is queried in the currently cached block sequence according to the acquired transaction commit instruction. When the configuration block is queried, the configuration block is used as a partition As a reference point, the currently cached block sequence is divided into a configuration block and a transaction block sequence, and the transaction commit operation is performed on the configuration block and the transaction block in the transaction block sequence according to the sequence of the block sequence. The transaction commit operation performed in sequence for multiple transaction blocks in the transaction block sequence includes: performing transaction signature verification on multiple transaction blocks in parallel; performing transaction multi-version checks on each transaction block serially; A transaction block is written to the disk at the same time. By performing transaction signature verification on multiple transaction blocks in parallel, the overall efficiency of signature verification is improved, thereby improving the processing efficiency of the block. When the transaction multi-version checks of multiple transaction blocks are all executed, the multiple transaction blocks are written to the disk at the same time, which improves the overall submission efficiency of transactions in the transaction block, thereby further improving the block processing efficiency. Further, writing multiple transaction blocks to the disk at the same time improves the overall throughput of the blockchain system, thereby saving computer resources.

In one of the embodiments, performing transaction signature verification on multiple transaction blocks in parallel includes: determining the number of verification threads according to the number of transaction blocks in the transaction block sequence and the number of CPU cores of the corresponding server; Multiple verification threads are allocated according to the number; multiple verification threads are used to perform transaction signature verification on multiple transaction blocks in parallel.

Specifically, the data node obtains the number of transaction blocks in the transaction block sequence and the number of CPU cores of its corresponding server, determines the number of verification threads according to the number of transaction blocks and the number of CPU cores of the server, and determines the number and the number of cores. Multiple verification threads with the same number of verification threads. The service node allocates multiple transaction blocks in the transaction block sequence to the multiple verification threads, so as to perform transaction signature verification on the multiple transaction blocks in parallel through the multiple verification threads. When the data node is a server, the number of CPU cores of the server corresponding to the data node itself is the number of CPU cores of the data node itself.

In one of the embodiments, the data node determines the threshold of the number of check threads that the server is allowed to carry according to the number of CPU cores of the server, and compares the threshold with the number of transaction blocks. When the number of transaction blocks is less than or equal to the number threshold, the data node determines the number of transaction blocks as the number of verification threads; when the number of transaction blocks is greater than the number threshold, the data node determines the number threshold as the verification thread quantity.

For example, suppose that the number of CPU cores of the server is 2, and the threshold of the number of check threads that the server is allowed to carry is determined according to the number of CPU cores. If the number of transaction blocks in the transaction block sequence is 5, the number of check threads determined according to the number of CPU cores and the number of transaction blocks is 5, and 5 transaction blocks are distributed to the 5 check threads in parallel Perform transaction signature verification; if the number of transaction blocks is 10, the number of verification threads is determined to be 6, and the 10 transaction blocks are distributed to the 6 verification threads to perform transaction signature verification in parallel. For example, 4 verification threads are allocated 2 transaction blocks, and 2 verification threads are allocated 1 transaction block.

In one of the embodiments, the data node may create corresponding multiple verification threads according to the number of verification threads, or obtain multiple idle threads from the thread pool according to the number, as the multiple verification threads allocated.

In the above embodiment, the number of verification threads is determined according to the number of transaction blocks to be processed and the number of CPU cores of the corresponding server, so that the number of verification threads can perform transaction signature verification on multiple transaction blocks in parallel. In the case of considering the carrying capacity of the server, the computer resources are fully utilized, the efficiency of transaction signature verification is improved, and the efficiency of block sorting and processing is improved.

In one of the embodiments, performing transaction signature verification on multiple transaction blocks in parallel through multiple verification threads includes: allocating multiple transaction blocks to multiple verification threads; The allocated transaction block is analyzed to obtain multiple transactions corresponding to the analyzed transaction block; transaction signature verification is performed on each transaction in turn according to the order of the multiple transactions in the transaction block.

Specifically, when multiple verification threads are allocated according to the determined number, the data node allocates multiple transaction blocks in the transaction block sequence to the multiple verification threads. For the transaction block that has been allocated to each verification thread, the data node analyzes its own allocated transaction block in parallel through each verification thread, and obtains multiple transactions corresponding to the analyzed transaction block, and according to the multiple The order of the transaction in the corresponding transaction block, and the transaction signature verification for each transaction in the multiple transactions in turn.

In one of the embodiments, the data node allocates the multiple transaction blocks to the determined multiple verification threads at the same time in accordance with the principle of equal distribution or proportional distribution, and uses each verification thread to allocate the multiple The transaction block performs transaction signature verification serially. Specifically, the data node uses each verification thread to assign multiple transaction blocks to itself, according to the ordering of the multiple transaction blocks in the transaction block sequence (or the block number corresponding to the transaction block), and sequentially Each transaction block in the plurality of transaction blocks performs transaction signature verification. The steps of performing transaction signature verification on each transaction block include: parsing the transaction block to obtain multiple transactions, and sequentially performing transaction signature verification on each transaction according to the order of the transactions in the transaction block.

In one of the embodiments, the data node extracts a transaction block equal to the number of verification threads from the transaction block sequence in the order of the transaction block sequence, and allocates the extracted transaction block to the corresponding verification thread , To perform transaction signature verification on the extracted multiple transaction blocks in parallel through the multiple verification threads. The data node detects the check thread in the idle state in real time, extracts from the transaction block sequence the transaction block that has not yet been subjected to the transaction commit operation and is sorted first, and allocates it to the check thread in the idle state.

In the above-mentioned embodiment, multiple transaction blocks are allocated to multiple verification threads, so that each verification thread performs transaction signature verification on transactions in the allocated transaction block in parallel, which improves transaction signature verification. Therefore, the processing efficiency of the block is improved.

In one of the embodiments, allocating multiple transaction blocks to multiple verification threads includes: creating a block cache queue corresponding to each verification thread; and allocating multiple transaction blocks to each block according to a preset allocation method The cache queue is used as a transaction block allocated to the corresponding verification thread.

The preset allocation method, for example, allocates multiple transaction blocks to multiple created block cache queues according to the principle of equal allocation or proportional allocation.

Specifically, when multiple verification threads are allocated according to the number of verification threads, the data node creates a block cache queue whose number is equal to the number of verification threads, and the created block cache queue corresponds to the verification thread respectively. The data node allocates multiple transaction blocks in the transaction block sequence to the created block cache queue for caching according to a preset allocation method, so that each verification thread can read from the corresponding block cache queue in parallel Transaction block, and perform transaction signature verification on the read transaction block.

In one of the embodiments, when the number of transaction blocks in the transaction block sequence is greater than the specified number, the data node allocates the specified number of transaction blocks that are ranked higher in the transaction block sequence to the multiple created regions The block cache queue is cached to read transaction blocks from the corresponding block cache queue in parallel through each verification thread and perform transaction signature verification. The specified number is determined by the number of CPU cores of the server and the threshold of the number of transaction blocks allowed by each verification thread. For example, the threshold of the number of verification threads allowed by the server is determined according to the number of CPU cores, and the calculation of the verification thread The product of the number threshold and the number threshold of the transaction block corresponding to the number of each verification thread is the specified number.

In the above embodiment, the transaction block is allocated to the block cache queue corresponding to each verification thread for caching, so that each verification thread reads the transaction block cached in the block cache queue in parallel, and signs the transaction Verification improves the efficiency of transaction block allocation, thereby improving the efficiency of transaction signature verification.

In one of the embodiments, each transaction is parsed in turn according to the ordering of multiple transactions in the transaction block to obtain transaction data and digital signature arrays corresponding to the parsed transactions; the digital signature array is parsed to obtain multiple digital signatures and digital signatures. The public key corresponding to the signature; decrypt the corresponding digital signature according to each public key to obtain the decrypted digital signature; generate the transaction hash value according to the transaction data, and based on the transaction hash value and each decrypted digital signature, respectively Each digital signature is verified; when the number of digital signatures that have passed the verification reaches a preset number threshold, it is determined that the signature verification result corresponding to the parsed transaction is a verification pass.

Transaction data is data corresponding to the transaction in the transaction block. The transaction data includes the business data to be updated (may be called target data) and the updated business data (may be called update data), and the data identifier corresponding to the business data, and may also include the target data version number corresponding to the target data. The data identifier corresponding to the business data can be used as the corresponding transaction data and/or the transaction data identifier corresponding to the transaction. It is understandable that the transaction data identifier corresponds to one or more transaction data (and/or transactions), that is, the corresponding one or more transactions can be queried in the blockchain according to the transaction data identifier, and the corresponding transaction data Transaction data. The preset number threshold is a preset value, such as 2.

The digital signature array includes one or more digital signatures, and may also include a decryption key (public key or private key) corresponding to each digital signature. The decryption key and the encryption key form a key pair. For example, if the encryption key is a private key, the decryption key is the public key corresponding to the private key. A digital signature is a data ciphertext obtained by encrypting transaction data using an encryption algorithm, for example, using a public key and a private key to encrypt transaction data to obtain a digital signature. Encryption algorithms such as symmetric encryption algorithms and asymmetric encryption algorithms. Symmetric encryption algorithm, such as DES (Data Encryption Standard, symmetric algorithm), AES (Advanced Encryption Standard, Advanced Encryption Standard), or IDEA (International Data Encryption Algorithm, International Data Encryption Algorithm), etc. Asymmetric encryption algorithms, such as RSA (Rivest, Shamir, Adleman, encryption algorithm), DSA (Digital Signature Algorithm, digital signature algorithm), or ECC (Elliptic curve cryptography, elliptic curve encryption algorithm), etc.

Specifically, when multiple transactions in the transaction block are obtained by parsing the transaction block allocated by the verification thread, the data node uses the verification thread according to the order of the multiple transactions in the transaction block to order the Each transaction in multiple transactions is analyzed, and transaction data and digital signature array corresponding to the analyzed transaction are obtained. The data node parses the digital signature array through the verification thread to obtain the corresponding multiple digital signatures and the public key corresponding to each digital signature, and decrypts the corresponding digital signature according to each public key to obtain the decrypted digital signature. Correspondingly, the data node uses the verification thread to hash the parsed transaction data based on the hash algorithm to obtain the transaction hash value, and compare the transaction hash value with each decrypted digital signature to compare As a result, the corresponding digital signature is verified. When the transaction hash value is consistent with the decrypted digital signature, it indicates that the verification result of the corresponding digital signature is a verification pass. The data node counts the verification result as the number of digital signatures that have passed the verification through the verification thread. When the counted number is greater than or equal to the preset number threshold, it is determined that the signature verification result of the corresponding transaction is the verification passed. Commonly used hash algorithms, such as MD5 (Message Digest Algorithm, fifth edition of message digest algorithm), SHA1 (Secure Hash Algorithm, secure hash algorithm), and SHA2, are not specifically limited in this embodiment.

In one of the embodiments, the digital signature array includes a single digital signature and corresponding public key, and the preset number threshold is 1. Similar to the above transaction signature verification steps, the data node verifies the digital signature through the verification thread. When the verification result of the digital signature is a verification pass, it is determined that the signature verification result of the corresponding transaction is verification. by.

In one of the embodiments, the data node receives the signature request sent by the blockchain client, obtains the transaction data to be signed according to the signature request, and hashes the transaction data to be signed by the hash algorithm to obtain the transaction hash value (can be Understand as a digest), use its own private key to encrypt the transaction hash value to obtain a digital signature, and feed the digital signature and its own public key to the blockchain client. It is understandable that the blockchain client detects the business data in real time, uses the detected business data as the transaction data to be signed, and sends the transaction data to be signed to multiple data nodes for digital signature according to the signature configuration, and the multiple The digital signatures and public keys fed back by each data node are spliced to obtain a digital signature array. The blockchain client obtains the transaction according to the transaction data and the corresponding digital signature array, and sends the transaction to the consensus node for consensus.

Further, the consensus node performs a consensus on the received transaction based on the consensus mechanism, generates a corresponding block according to the transaction passed by the consensus, and sends the generated block to the data node, so that the data node is based on the information provided in the foregoing embodiments The block processing method writes the block into the block chain. It is understandable that the blockchain client, data node, and consensus node all belong to the blockchain network, and the blockchain network may include multiple blockchain clients, data nodes, and consensus nodes.

In the foregoing embodiment, the transaction signature verification is performed on the transaction based on the digital signature array and the transaction hash value to ensure the authenticity, validity and reliability of the corresponding transaction data.

In one of the embodiments, performing transaction multi-version checking on each transaction block in series includes: according to the sequence of the transaction block sequence, sequentially performing the following transaction multi-version checking steps on multiple transactions in each transaction block : Analyze each transaction in turn according to the order of multiple transactions in the transaction block to obtain the transaction data identifier and target data version number corresponding to the parsed transaction; query the latest data version number corresponding to the transaction data identifier; when the latest data version When the number is consistent with the target data version number, it is determined that the multi-version check result of the parsed transaction is passed.

Specifically, when the transaction signature verification operations performed on multiple transaction blocks in the transaction block sequence are all executed, the data node sequentially performs the multiple transaction blocks according to the order of the multiple transaction blocks in the transaction block sequence. Each transaction block in each transaction block performs transaction multi-version check. The data node performs transaction multi-version check on the transaction block. Specifically, the data node performs transaction multi-version check for multiple transactions in the transaction block, which specifically includes the following steps: the data node parses the transaction block to obtain the corresponding multiple transactions , According to the order of the multiple transactions in the transaction block, analyze each transaction in the multiple transactions in turn to obtain the transaction data identifier and target data version number corresponding to the analyzed transaction. The data node queries the corresponding latest data version number in the blockchain and/or local cache according to the transaction data identifier, and compares the latest data version number found with the target data version number. When the latest data version number is consistent with the target data version number, the data node determines that the multi-version check result of the corresponding transaction is passed.

In one of the embodiments, the data node queries the corresponding latest data version number in the cache according to the parsed transaction data identifier, and performs the above-mentioned transaction multi-version check operation according to the latest data version number found. When the latest data version number corresponding to the transaction data identifier is not queried in the cache, the data node queries the latest data version number from the blockchain that has been written to the disk, and executes the above transaction based on the latest data version number queried. Version check operation.

In one of the embodiments, each transaction block corresponds to a block number, and the block number can be used to characterize the order of the transaction block in the transaction block sequence, block sequence, or corresponding blockchain. Each transaction in the transaction block corresponds to a transaction number, and the transaction number is used to characterize the order of each transaction in the corresponding transaction block. When the multi-version check result of a transaction is passed, the data node generates a corresponding data version number according to the transaction number and block number corresponding to the transaction, which is used as the corresponding transaction data to identify the current corresponding latest data version number. When the multi-version check result of the transaction is that the check fails, the data node will mark the multi-version check result and will not generate the corresponding data version number, that is, the data version number corresponding to the transaction data identifier corresponding to the transaction will not be updated .

In one of the embodiments, when the transaction signature verification operation performed for each transaction in the transaction block is completed, the data node marks the transaction according to the signature verification result corresponding to the transaction. When the transaction multi-version check is performed on the transaction block, the data node performs multi-version check on the transaction whose signature verification result is the verification result according to the signature verification result marked for the transaction, and according to the transaction corresponding The multi-version check result marks the transaction. It is understandable that the data node writes multiple transactions in each transaction block, as well as the signature verification results and multi-version verification results corresponding to each transaction, into the blockchain. The data node may mark a transaction whose signature verification result is that the verification fails and/or the multi-version check result is that the verification fails as an invalid transaction.

For example, suppose that the transaction data corresponding to the transaction to be submitted includes: the target data is A=2, the update data is A=3, and the target data version number is 1. If the current latest data version number is 1, then the transaction is determined The result of multi-version inspection is inspection passed. If the latest data version number corresponding to the transaction data identifier A is found to be 2 in the cache or the blockchain, it is determined that the multi-version check result of the transaction is a failed check.

In one of the embodiments, the data node may specifically perform the above-mentioned transaction multi-version check step on multiple transactions in each transaction block in the order of the transaction block sequence through a single check thread.

In the above-mentioned embodiment, multi-version concurrency control is achieved through multi-version checking operations, so as to avoid the problem of data update errors caused when the same target data is modified by different users or different operations at the same time, and to ensure the accuracy and consistency of transaction data.

In one of the embodiments, after step S204, the block processing method described above further includes: when the configuration block is not found, directly perform the following transaction commit operation on multiple transaction blocks in the block sequence: Transaction signature verification is performed on each transaction block; transaction multi-version check is performed on each transaction block serially; multiple transaction blocks are simultaneously written to the disk.

Specifically, when the configuration block is not queried in the currently cached block sequence, the data node uses the currently cached block sequence as a transaction block sequence and targets multiple transaction areas in the transaction block sequence. The block performs the following transaction commit operations: transaction signature verification is performed on multiple transaction blocks in parallel through multiple verification threads; when the transaction signature verification operations performed for each transaction block are all executed, follow the transaction block The sequence of the sequence is to perform transaction multi-version checks on each transaction block serially; when the transaction multi-version check performed for each transaction block is executed sequentially, the preset write interface is called to write the multiple transaction blocks at the same time Disk.

In one of the embodiments, in the process of sequentially performing transaction multi-version checks for multiple transaction blocks in the transaction block sequence, the data node caches the transaction blocks that have performed transaction multi-version checks locally, so as to facilitate the When the multi-version checks of the transactions that are executed in sequence are all executed, the multiple transaction blocks are directly read from the cache, which improves the reading efficiency and thus the writing efficiency.

It is worth noting that when the configuration block is not queried in the block sequence, the data node determines the block sequence as a transaction block sequence, and is based on the transaction block sequence provided in the foregoing embodiments. The transaction executed by the block is submitted for processing.

In the above embodiment, when the configuration block is not queried in the currently cached block sequence, all transaction blocks in the block sequence are directly processed in batches, which improves the efficiency of transaction signature verification, thereby increasing the area. Block processing efficiency. Writing multiple transaction blocks to the disk at the same time reduces the number of calls to the blockchain network system, reduces program context switching caused by frequent system calls, improves the overall throughput of the system, and saves computer resources.

As shown in Figure 3, in one of the embodiments, a block processing method is provided, which specifically includes the following steps:

S302: Obtain a transaction commit instruction.

S304, query the configuration block in the currently cached block sequence according to the transaction commit instruction.

S306: When the configuration block is queried, the block sequence is divided into a configuration block and a transaction block sequence using the queried configuration block as a dividing reference point.

S308: Perform transaction commit operations on the configuration block and transaction blocks in the transaction block sequence respectively in the order of the block sequence; the transaction commit operations performed on multiple transaction blocks in the transaction block sequence include: Transaction signature verification is performed on multiple transaction blocks; multiple transaction versions are checked for each transaction block serially; multiple transaction blocks are simultaneously written to the disk.

S310: When the configuration block is not queried, directly perform the following transaction commit operations on multiple transaction blocks in the block sequence: perform transaction signature verification on multiple transaction blocks in parallel; and perform transaction signature verification on multiple transaction blocks in series; Block multi-version checking of transactions; write multiple transaction blocks to disk at the same time.

In the above-mentioned embodiment, the corresponding block processing procedures are provided for the two cases of whether the currently cached block sequence contains configuration blocks, and the block sequence and the divided transaction block sequence are processed in batches. , Improve the efficiency of block processing.

As shown in Figure 4, in one of the embodiments, the transaction commit operation performed by the data node for multiple transaction blocks in the transaction block sequence includes the following steps:

S402: Determine the number of verification threads according to the number of transaction blocks in the transaction block sequence and the number of CPU cores of the corresponding server.

S404: Allocate multiple verification threads according to the number.

S406: Create a block buffer queue corresponding to each verification thread.

S408: Allocate multiple transaction blocks to each block cache queue according to a preset allocation method, as transaction blocks allocated to corresponding verification threads.

S410: Analyze the allocated transaction block by each verification thread to obtain multiple transactions corresponding to the analyzed transaction block.

S412: Analyze each transaction in turn according to the order of multiple transactions in the transaction block to obtain transaction data and a digital signature array corresponding to the analyzed transaction.

S414: Parse the digital signature array to obtain multiple digital signatures and public keys corresponding to each digital signature.

S416: Decrypt the corresponding digital signature according to each public key to obtain a decrypted digital signature.

S418: Generate a transaction hash value according to the transaction data, and verify each digital signature based on the transaction hash value and each decrypted digital signature.

S420: When the number of digital signatures that have passed the verification reaches a preset number threshold, it is determined that the signature verification result corresponding to the parsed transaction is a verification pass.

S422: According to the order of the transaction block sequence, sequentially analyze the multiple transactions in each transaction block according to the order of the multiple transactions in the transaction block to obtain the transaction data identifier and the transaction data corresponding to the analyzed transaction. Target data version number.

S424: Query the latest data version number corresponding to the transaction data identifier.

S426: When the latest data version number is consistent with the target data version number, it is determined that the multi-version check result of the parsed transaction is passed.

S428: Write multiple transaction blocks into the disk at the same time.

In the above embodiment, the transaction signature verification is performed on multiple transaction blocks in parallel, which improves the overall efficiency of transaction signature verification. The serial multi-version check ensures the correctness and consistency of transaction data. Transaction blocks are written to the disk at the same time, reducing the number of calls of the blockchain network system, improving the overall throughput of the system, improving the submission efficiency of transaction blocks, and saving computer resources. As a result, the overall block processing efficiency is improved.

In one of the embodiments, the block processing method provided in the above embodiments can be applied to the alliance chain, and can also be applied to the public chain or the private chain.

In one of the embodiments, the consensus node and the data node may be the same blockchain node, and the consensus node and the data node may correspond to the same server or server cluster.

It should be understood that although the various steps in the flowcharts of FIGS. 2-4 are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless specifically stated in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least some of the steps in Figures 2-4 may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. These sub-steps or stages The execution order of is not necessarily performed sequentially, but may be performed alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.

In one of the embodiments, as shown in FIG. 5, a block processing device 500 is provided, which includes: an acquisition module 502, a query module 504, a segmentation module 506, and a submission module 508, wherein:

The obtaining module 502 is used to obtain a transaction commit instruction.

The query module 504 is used to query the configuration block in the currently cached block sequence according to the transaction commit instruction.

The dividing module 506 is used to divide the block sequence into the configuration block and the transaction block sequence when the configuration block is queried, using the queried configuration block as the dividing reference point.

The commit module 508 is used to perform transaction commit operations on the configuration block and transaction blocks in the transaction block sequence according to the sequence of the block sequence; the transaction commit operations performed for multiple transaction blocks in the transaction block sequence include : Perform transaction signature verification on multiple transaction blocks in parallel; perform transaction multi-version check on each transaction block serially; write multiple transaction blocks into the disk at the same time.

In one of the embodiments, the commit module 508 is further configured to determine the number of verification threads according to the number of transaction blocks in the transaction block sequence and the number of CPU cores of its corresponding server; and to allocate multiple verification threads according to the number; Multiple verification threads perform transaction signature verification on multiple transaction blocks in parallel.

In one of the embodiments, the commit module 508 is also used to allocate multiple transaction blocks to multiple verification threads; each verification thread analyzes the allocated transaction blocks by each verification thread to obtain the resolved transaction block correspondence A number of transactions; according to the order of multiple transactions in the transaction block, transaction signature verification is performed on each transaction.

In one of the embodiments, the commit module 508 is also used to parse each transaction in turn according to the ordering of multiple transactions in the transaction block to obtain transaction data and digital signature array corresponding to the parsed transaction; parse the digital signature array to obtain Multiple digital signatures and public keys corresponding to each digital signature; decrypt the corresponding digital signature according to each public key to obtain the decrypted digital signature; generate transaction hash value based on transaction hash value and each decryption After the digital signature, each digital signature is verified separately; when the number of digital signatures that have passed the verification reaches the preset number threshold, it is determined that the signature verification result corresponding to the parsed transaction is the verification passed.

In one of the embodiments, the submission module 508 is also used to create a block cache queue corresponding to each verification thread; to allocate multiple transaction blocks to each block cache queue according to a preset allocation method, as the allocation to the corresponding school The transaction block of the verification thread.

In one of the embodiments, the commit module 508 is also used to perform the following transaction multi-version check steps on multiple transactions in each transaction block in sequence according to the order of the transaction block sequence: The sorting in parses each transaction in turn to obtain the transaction data ID and target data version number corresponding to the parsed transaction; query the latest data version number corresponding to the transaction data ID; when the latest data version number is consistent with the target data version number, It is determined that the result of the multi-version check of the parsed transaction is passed.

In one of the embodiments, the commit module 508 is also used to directly perform the following transaction commit operations on multiple transaction blocks in the block sequence when the configuration block is not queried: perform multiple transaction blocks in parallel Transaction signature verification; serially perform transaction multi-version check on each transaction block; write multiple transaction blocks to the disk at the same time.

For the specific limitation of the block processing device, please refer to the above limitation of the block processing method, which will not be repeated here. Each module in the block processing device described above can be implemented in whole or in part by software, hardware, and a combination thereof. The foregoing modules may be embedded in the form of hardware or independent of the processor in the computer device, or may be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the foregoing modules.

In one of the embodiments, a computer device is provided. The computer device may be a server corresponding to a data node, and its internal structure diagram may be as shown in FIG. 6. The computer equipment includes a processor, a memory, a network interface and a database connected through a system bus. The processor of the computer device is used to provide calculation and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer readable instructions, and a database. The internal memory provides an environment for the operation of the operating system and computer-readable instructions in the non-volatile storage medium. The database of the computer device is used to store a block sequence, and the stored block sequence includes configuration blocks and/or transaction blocks. The network interface of the computer device is used to communicate with an external terminal through a network connection. The computer readable instructions are executed by the processor to realize a block processing method.

Those skilled in the art can understand that the structure shown in FIG. 6 is only a block diagram of part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may Including more or fewer parts than shown in the figure, or combining some parts, or having a different arrangement of parts.

A computer device including a memory and one or more processors. The memory stores computer readable instructions. When the computer readable instructions are executed by one or more processors, the one or more processors can realize any one of the present application. The steps of the block processing method provided in the embodiment.

One or more non-volatile computer-readable storage media storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors implement any one of the embodiments of the present application. Provides the steps of the block processing method. In one of the embodiments in one of the embodiments

A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing relevant hardware through computer-readable instructions, which can be stored in a non-volatile computer. In a readable storage medium, when the computer-readable instructions are executed, they may include the processes of the above-mentioned method embodiments. Any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and/or volatile memory. Non-volatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not a limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Channel (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction between the combinations of these technical features, they should It is considered as the range described in this specification.

The above-mentioned embodiments only express several implementation manners of the present application, and the description is relatively specific and detailed, but it should not be understood as a limitation on the scope of the invention patent. It should be pointed out that for those of ordinary skill in the art, without departing from the concept of this application, several modifications and improvements can be made, and these all fall within the protection scope of this application. Therefore, the scope of protection of the patent of this application shall be subject to the appended claims.

Claims

A block processing method, including:

Obtain transaction commit instructions;

Query the configuration block in the currently cached block sequence according to the transaction commit instruction;

When the configuration block is queried, the block sequence is divided into a configuration block and a transaction block sequence using the queried configuration block as a division reference point; and

A transaction commit operation is performed on the configuration block and the transaction block in the transaction block sequence respectively according to the sequence of the block sequence; transaction commit performed on multiple transaction blocks in the transaction block sequence The operations include: performing transaction signature verification on the plurality of transaction blocks in parallel; performing transaction multi-version checking on each of the transaction blocks serially; and simultaneously writing the plurality of transaction blocks to a disk.
The method according to claim 1, wherein the performing transaction signature verification on the plurality of transaction blocks in parallel comprises:

Determining the number of verification threads according to the number of transaction blocks in the transaction block sequence and the number of CPU cores of the server corresponding to the transaction block;

Allocate multiple verification threads according to the number; and

The transaction signature verification is performed on the plurality of transaction blocks in parallel by the plurality of verification threads.
The method according to claim 2, wherein said performing transaction signature verification on said plurality of transaction blocks in parallel by said plurality of verification threads comprises:

Allocating the multiple transaction blocks to the multiple verification threads;

Analyze the allocated transaction block by each verification thread to obtain multiple transactions corresponding to the analyzed transaction block; and

According to the order of the multiple transactions in the transaction block, transaction signature verification is performed on each transaction in turn.
The method according to claim 3, wherein the step of performing transaction signature verification on each of the transactions according to the order of the multiple transactions in the transaction block comprises:

Analyze each of the transactions in turn according to the order of the multiple transactions in the transaction block to obtain transaction data and digital signature arrays corresponding to the analyzed transactions;

Parsing the digital signature array to obtain multiple digital signatures and public keys corresponding to each of the digital signatures;

Decrypt the corresponding digital signature according to each said public key to obtain the decrypted digital signature;

Generate a transaction hash value according to the transaction data, and verify each of the digital signatures based on the transaction hash value and each of the decrypted digital signatures; and

When the number of the digital signatures that have passed the verification reaches a preset number threshold, it is determined that the signature verification result corresponding to the parsed transaction is a verification pass.
The method according to claim 3, wherein the allocating the plurality of transaction blocks to the plurality of verification threads comprises:

Creating a block buffer queue corresponding to each verification thread; and

The plurality of transaction blocks are allocated to each of the block cache queues according to a preset allocation method as the transaction blocks allocated to the corresponding verification thread.
The method according to claim 1, wherein the serially performing transaction multi-version checking on each of the transaction blocks comprises:

According to the sequence of the transaction block sequence, the following transaction multi-version checking steps are performed sequentially on multiple transactions in each transaction block:

Analyze each of the transactions in turn according to the order of the multiple transactions in the transaction block to obtain the transaction data identifier and target data version number corresponding to the analyzed transaction;

Query the latest data version number corresponding to the transaction data identifier; and

When the latest data version number is consistent with the target data version number, it is determined that the parsed multi-version check result of the transaction is passed.
The method according to any one of claims 1 to 6, characterized in that, after the query configuration block in the currently cached block sequence according to the transaction commit instruction, the method further comprises:

When the configuration block is not found, the following transaction commit operations are directly performed on multiple transaction blocks in the block sequence:

Perform transaction signature verification on the multiple transaction blocks in parallel; perform transaction multi-version checks on each transaction block serially; write the multiple transaction blocks into the disk at the same time.
A block processing device, characterized in that the device includes:

Obtaining module for obtaining transaction commit instructions;

The query module is used to query the configuration block in the currently cached block sequence according to the transaction commit instruction;

A segmentation module, configured to, when the configuration block is queried, use the queried configuration block as a segmentation reference point to split the block sequence into a configuration block and a transaction block sequence;

The commit module is configured to perform transaction commit operations on the configuration block and the transaction block in the transaction block sequence according to the sequence of the block sequence; for multiple transaction areas in the transaction block sequence The transaction commit operation performed by the block includes: performing transaction signature verification on the multiple transaction blocks in parallel; performing multi-version check on each transaction block serially; writing the multiple transaction blocks simultaneously Into the disk.
The device according to claim 8, wherein the commit module is further configured to determine the number of check threads according to the number of transaction blocks in the transaction block sequence and the number of CPU cores of the server corresponding to it; A plurality of verification threads are allocated according to the number; and transaction signature verification is performed on the plurality of transaction blocks in parallel through the plurality of verification threads.
The device according to claim 9, wherein the commit module is further configured to allocate the plurality of transaction blocks to the plurality of verification threads; each verification thread allocates itself to Parse the transaction block to obtain multiple transactions corresponding to the parsed transaction block; and perform transaction signature verification on each transaction in sequence according to the order of the multiple transactions in the transaction block.
The apparatus according to claim 10, wherein the commit module is further configured to parse each of the transactions in sequence according to the order of the multiple transactions in the transaction block to obtain the parsed Transaction data and digital signature array corresponding to the transaction; parsing the digital signature array to obtain multiple digital signatures and public keys corresponding to each of the digital signatures; decrypting the corresponding digital signatures according to each of the public keys to obtain the decrypted Digital signature; generate a transaction hash value based on the transaction data, and verify each of the digital signatures based on the transaction hash value and each of the decrypted digital signatures; and when the verification passes When the number of the digital signatures reaches the preset number threshold, it is determined that the signature verification result corresponding to the analyzed transaction is passed.
The device according to claim 10, wherein the submission module is further configured to create a block cache queue corresponding to each of the verification threads; and assign the plurality of transaction blocks according to a preset allocation method Allocate to each of the block cache queues as transaction blocks allocated to the corresponding verification thread.
8. The device according to claim 8, wherein the commit module is further configured to perform the following transaction multi-version checks on multiple transactions in each transaction block in sequence according to the sequence of the transaction block sequence The steps of: parse each of the transactions in turn according to the order of the multiple transactions in the transaction block to obtain the transaction data identifier and target data version number corresponding to the analyzed transaction; query the transaction data Identify the corresponding latest data version number; and when the latest data version number is consistent with the target data version number, it is determined that the parsed multi-version check result of the transaction is passed.
The device according to any one of claims 8 to 13, wherein the submission module is further configured to directly check multiple transaction areas in the block sequence when the configuration block is not found. The block performs the following transaction commit operations: performs transaction signature verification on the multiple transaction blocks in parallel; performs multi-version check on each transaction block serially; writes the multiple transaction blocks simultaneously Disk.
A computer device includes a memory and one or more processors. The memory stores computer readable instructions. When the computer readable instructions are executed by the one or more processors, the one or more Each processor performs the following steps:

Obtain transaction commit instructions;

Query the configuration block in the currently cached block sequence according to the transaction commit instruction;

When the configuration block is queried, the block sequence is divided into a configuration block and a transaction block sequence using the queried configuration block as a division reference point; and

A transaction commit operation is performed on the configuration block and the transaction block in the transaction block sequence respectively according to the sequence of the block sequence; transaction commit performed on multiple transaction blocks in the transaction block sequence The operations include: performing transaction signature verification on the plurality of transaction blocks in parallel; performing transaction multi-version checking on each of the transaction blocks serially; and simultaneously writing the plurality of transaction blocks to a disk.
The computer device according to claim 15, wherein the processor further executes the following steps when executing the computer-readable instruction:

Determining the number of verification threads according to the number of transaction blocks in the transaction block sequence and the number of CPU cores of the server corresponding to the transaction block;

Allocate multiple verification threads according to the number; and

The transaction signature verification is performed on the plurality of transaction blocks in parallel by the plurality of verification threads.
16. The computer device according to claim 16, wherein the performing transaction signature verification on the multiple transaction blocks in parallel by the multiple verification threads comprises:

Allocating the multiple transaction blocks to the multiple verification threads;

Analyze the allocated transaction block by each verification thread to obtain multiple transactions corresponding to the analyzed transaction block; and

According to the order of the multiple transactions in the transaction block, transaction signature verification is performed on each transaction in turn.
One or more non-volatile computer-readable storage media storing computer-readable instructions, which when executed by one or more processors, cause the one or more processors to perform the following steps:

Obtain transaction commit instructions;

Query the configuration block in the currently cached block sequence according to the transaction commit instruction;

When the configuration block is queried, the block sequence is divided into a configuration block and a transaction block sequence using the queried configuration block as a division reference point; and

A transaction commit operation is performed on the configuration block and the transaction block in the transaction block sequence respectively according to the sequence of the block sequence; transaction commit performed on multiple transaction blocks in the transaction block sequence The operations include: performing transaction signature verification on the plurality of transaction blocks in parallel; performing transaction multi-version checking on each of the transaction blocks serially; and simultaneously writing the plurality of transaction blocks to a disk.
18. The storage medium of claim 18, wherein the following steps are further performed when the computer-readable instructions are executed by the processor:

Determining the number of verification threads according to the number of transaction blocks in the transaction block sequence and the number of CPU cores of the server corresponding to the transaction block;

Allocate multiple verification threads according to the number; and

The transaction signature verification is performed on the plurality of transaction blocks in parallel by the plurality of verification threads.
The storage medium according to claim 19, wherein the following steps are further executed when the computer-readable instructions are executed by the processor:

Allocating the multiple transaction blocks to the multiple verification threads;

Analyze the allocated transaction block by each verification thread to obtain multiple transactions corresponding to the analyzed transaction block; and

According to the order of the multiple transactions in the transaction block, transaction signature verification is performed on each transaction in turn.