Transaction pool data processing method, system and device
Through cache and shard storage technology, the problem of low data processing efficiency in transaction pools in blockchain systems is solved, and efficient transaction verification and blockchain performance improvement are achieved.
Patent Information
- Application Number
- CN202410940369.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-15
- Publication Date
- 2024-11-22
AI Technical Summary
The transaction pool data processing efficiency in the blockchain system is low, resulting in inefficient transaction verification process and affecting the performance of the blockchain system.
By cache the transactions sent by the client and depositing the verified transactions into the shard bucket, the ECDSA elliptic curve digital signature algorithm is used to verify the signature, judge the repetition of random numbers and on-chain verification, reduce data competition, and improve transaction verification efficiency .
It improves the data processing efficiency of the transaction pool and the performance of the blockchain system, ensures that subsequent sign-up verification and client sending new transactions do not conflict, reduces the probability of data competition, and improves the speed of transaction sign-up verification.
Smart Images

Figure CN119006152A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of blockchain, and in particular to a transaction pool data processing method, system and device. Background Art
[0002] In the blockchain system, transactions are stored in the transaction pool before being put on the chain. The transaction pool verifies transactions and rejects illegal transactions on the one hand, and transmits legal transactions to the blockchain system on the other hand. The transaction pool verifies transactions, not only to verify the transaction signature, but also to check whether the transaction is repeated and whether it has been put on the chain, resulting in very low efficiency in providing transactions to the blockchain system. The transaction pool stores legal transactions sent by the client, and at the same time provides legal transactions to the blockchain and deletes transactions that have been put on the chain, resulting in extremely fierce data competition. After the client sends a transaction, a large number of threads are blocked waiting for the transaction to be verified and the transaction hash to be returned, and no more threads can be freed up to send new transactions. It can be said that the transaction pool of the blockchain system is extremely busy, and its performance will directly affect the performance of the blockchain system.
[0003] There is currently no effective solution to the problem of low efficiency in transaction pool data processing in the prior art. Summary of the invention
[0004] To solve the above problems, the present invention provides a transaction pool data processing method, system and device, which improves the data processing performance of the transaction pool by caching transactions sent by clients and storing verified transactions in sharded storage buckets, thereby solving the problem of low transaction pool data processing efficiency in the prior art.
[0005] To achieve the above-mentioned purpose, an embodiment of the present invention provides a transaction pool data processing method, comprising: obtaining a transaction to be verified sent by a client, and adding the transaction to be verified to a cache queue; performing signature verification, repeatability verification and chain verification on the transaction to be verified in the cache queue in turn, and obtaining a transaction to be chained that passes all verifications; dividing the corresponding transaction to be chained into a storage bucket according to the transaction hash; wherein the storage bucket is obtained by sharding the storage space; sending the transaction to be chained to a blockchain node for chaining, and after the chaining is successful, deleting the transaction to be chained from the corresponding storage bucket.
[0006] Further optionally, the transactions to be verified in the cache queue are sequentially subjected to signature verification, repeatability verification and on-chain verification, including: allocating a thread for the transactions to be verified, verifying the signature of the transactions to be verified using the ECDSA elliptic curve digital signature algorithm, and if the signature is valid, the signature verification passes; determining whether the random number of the transaction to be verified is repeated with the random numbers of other transactions to be verified in the cache queue, and if not, the repeatability verification passes; wherein the random number is generated on the client; determining whether the random number of the transaction to be verified exists in the random number list of on-chain transactions, and if not, the on-chain verification passes.
[0007] Further optionally, dividing the corresponding transactions to be put on the chain into storage buckets according to the transaction hash includes: counting the total number of storage buckets and assigning a bucket number to each storage bucket; calculating the division result of the transaction hash and the total number, and determining the corresponding bucket number according to the remainder in the division result; and storing the transactions to be put on the chain in the storage bucket corresponding to the bucket number.
[0008] Further optionally, after adding the transaction to be verified to the cache queue, the method further includes: sending a storage response to the client; and after receiving the storage response, the client sends a new transaction to be verified.
[0009] On the other hand, the present invention also provides a transaction pool data processing system, including: a cache module, used to obtain the transactions to be verified sent by the client, and add the transactions to be verified to the cache queue; a verification module, used to perform signature verification, repeatability verification and chain verification on the transactions to be verified in the cache queue in sequence, and obtain transactions to be chained that pass all verifications; a sharding storage module, used to divide the corresponding transactions to be chained into storage buckets according to the transaction hash; wherein the storage buckets are obtained by sharding the storage space; an on-chain module, used to send the transactions to be chained to the blockchain node for chaining, and after the chaining is successful, delete the transactions to be chained from the corresponding storage buckets.
[0010] Further optionally, the verification module includes: a signature verification submodule, used to assign a thread to the transaction to be verified, and use the ECDSA elliptic curve digital signature algorithm to verify the signature of the transaction to be verified. If the signature is valid, the signature verification is successful; a repeatability verification submodule, used to determine whether the random number of the transaction to be verified is repeated with the random numbers of other transactions to be verified in the cache queue. If not, the repeatability verification is successful; wherein the random number is generated on the client; an on-chain verification submodule, used to determine whether the random number of the transaction to be verified exists in the on-chain transaction random number list. If not, the on-chain verification is successful.
[0011] Further optionally, the shard storage module includes: a statistical submodule, used to count the total number of storage buckets and assign a bucket number to each storage bucket; a calculation submodule, used to calculate the division result of the transaction hash and the total number, and determine the corresponding storage bucket number according to the remainder in the division result; a storage submodule, used to store the transaction to be uploaded to the chain into the storage bucket corresponding to the bucket number.
[0012] Further optionally, the system also includes: a response module, used to send a storage response to the client; and a sending module, used for the client to send a new transaction to be verified after receiving the storage response.
[0013] On the other hand, the present invention also provides a transaction pool data processing device, including the above-mentioned transaction pool data processing system.
[0014] On the other hand, the present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the transaction pool data method as described above.
[0015] The above technical solution has the following beneficial effects: by storing transactions sent by the client in a cache queue and responding directly to the client, it is ensured that subsequent verification and new transactions sent by the client no longer conflict with each other, thereby improving data processing efficiency; by sharding the storage space and storing a large number of transactions to be uploaded to the chain in different storage buckets, the probability of data competition is reduced; transactions are verified in parallel to improve transaction verification efficiency, thereby further improving the data processing speed of the transaction pool and the performance of the blockchain system. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0017] Figure 1 is a flow chart of a transaction pool data processing method provided by an embodiment of the present invention;
[0018] Figure 2 is a flow chart of a transaction legitimacy verification method provided by an embodiment of the present invention;
[0019] Figure 3 is a flow chart of a transaction bucket storage method provided by an embodiment of the present invention;
[0020] Figure 4 is a flowchart of a client response method provided by an embodiment of the present invention;
[0021] Figure 5 is a structural diagram of a transaction pool data processing system provided by an embodiment of the present invention;
[0022] Figure 6 is a schematic diagram of the structure of a verification module provided by an embodiment of the present invention;
[0023] Figure 7 is a schematic diagram of the structure of a shard storage module provided by an embodiment of the present invention;
[0024] Figure 8 It is a schematic diagram of the structure of a module for responding to a client provided in an embodiment of the present invention.
[0025] Figure numerals: 100-cache module; 200-verification module; 2001-signature verification submodule; 2002-repetitiveness verification submodule; 2003-on-chain verification submodule; 300-shard storage module; 3001-statistics submodule; 3002-calculation submodule; 3003-storage submodule; 400-on-chain module; 500-response module; 600-sending module. DETAILED DESCRIPTION
[0026] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0027] In order to solve the problem of low efficiency in data processing in the transaction pool in the prior art, an embodiment of the present invention provides a transaction pool data processing method. Figure 1 is a flow chart of a transaction pool data processing method provided by an embodiment of the present invention. Figure 1 As shown, the method includes:
[0028] S1. Obtain the transaction to be verified sent by the client and add the transaction to be verified to the cache queue;
[0029] A pre-buffer is set in the transaction pool, through which the client can respond directly. The client sends the transaction to be verified to the blockchain node to the pre-buffer and stores it in the cache queue.
[0030] S2. Perform signature verification, repeatability verification and chain verification on the pending transactions in the cache queue in turn, and obtain the pending chain transactions that have passed all verifications;
[0031] Signature verification is performed on the pending transactions in the cache queue to determine whether the transaction is legal. Repeatability verification is performed on the pending transactions to determine whether the transaction already exists in the current transaction pool. After that, the pending transactions are verified on the chain to determine whether the transaction has been successfully on the chain. If the transaction is legal, does not repeat with other transactions in the transaction pool, and has not been on the chain, then the transaction is considered to have passed all verifications and is prepared to be on the chain as a pending transaction. In the above verification process, if one verification fails, the transaction cannot be subsequently on the chain.
[0032] S3. The corresponding transactions to be uploaded to the chain are divided into storage buckets according to the transaction hash; wherein the storage buckets are obtained by sharding the storage space;
[0033] The storage space is pre-sharded to obtain multiple storage buckets, and the storage bucket corresponding to each transaction is calculated based on the transaction hash, and the transaction to be on-chain is stored in the corresponding storage bucket. In this way, a large number of transactions to be on-chain can be evenly distributed into multiple storage buckets to reduce the probability of data competition.
[0034] S4. Send the transaction to be uploaded to the blockchain node for upload. After the upload is successful, delete the transaction to be uploaded from the corresponding storage bucket.
[0035] The blockchain system obtains the transactions to be uploaded from each storage bucket in the storage space. The blockchain node packages the transactions to be uploaded into a new block. After the block reaches a consensus, it marks that the transactions to be uploaded have been successfully uploaded. At this time, the blockchain submits the transaction and the execution result to the blockchain database.
[0036] After the transaction is successfully uploaded to the chain, the storage bucket corresponding to the transaction that has been uploaded to the chain is located according to the transaction hash, and the transaction to be uploaded to the chain is deleted from the storage bucket.
[0037] As an optional implementation, Figure 2 is a flow chart of a transaction legitimacy verification method provided by an embodiment of the present invention, such as Figure 2 As shown, the transactions to be verified in the cache queue are sequentially subjected to signature verification, repeatability verification and chain verification, including:
[0038] S201. Allocate a thread for the transaction to be verified, and use the ECDSA elliptic curve digital signature algorithm to verify the signature of the transaction to be verified. If the signature is valid, the signature verification is successful.
[0039] The transactions to be verified in the cache queue are verified in parallel, that is, multiple transactions to be verified are verified simultaneously through multiple threads.
[0040] The transaction to be verified is signed by the ECDSA elliptic curve digital signature algorithm on the client side. When the transaction to be verified is verified in the transaction pool, the ECDSA elliptic curve digital signature algorithm is used to verify the transaction to be verified. If the signature is valid, the signature verification is successful.
[0041] S202, determining whether the random number of the transaction to be verified is repeated with the random numbers of other transactions to be verified in the cache queue, if not, the repeatability verification is passed; wherein the random number is generated at the client;
[0042] The client generates a random number for each transaction to be verified. When the transaction to be verified passes the signature verification, it is necessary to determine whether the transaction to be verified exists repeatedly in the transaction pool. Specifically, check whether there is a transaction in the cache queue with the same random number as the transaction to be verified. If there is, it proves that the transaction to be verified is a duplicate transaction and cannot pass the repeatability verification; on the contrary, if there is no transaction to be verified, it proves that the transaction to be verified is not a duplicate transaction and passes the repeatability verification.
[0043] S203: Determine whether the random number of the transaction to be verified exists in the random number list of on-chain transactions. If not, the on-chain verification is successful.
[0044] Check whether there is a transaction with the same random number as the transaction to be verified in the random number list of on-chain transactions. If so, it proves that the transaction to be verified has been successfully on-chain and does not need to be on-chain again, and cannot pass the on-chain verification; on the contrary, if it does not exist, it proves that the transaction to be verified is a transaction to be on-chain and has passed the on-chain verification.
[0045] As an optional implementation, the random number list of on-chain transactions includes the random numbers corresponding to the most recent 1000 transactions successfully on-chain. When a new transaction is successfully on-chain, its corresponding random number is saved in the random number list of on-chain transactions.
[0046] As an optional implementation, Figure 3 is a flow chart of a transaction bucket storage method provided by an embodiment of the present invention. Figure 3 As shown, the corresponding transactions to be uploaded to the chain are divided into buckets according to the transaction hash, including:
[0047] S301, counting the total number of storage buckets and assigning a storage bucket sequence number to each storage bucket;
[0048] S302, calculating the division result of the transaction hash and the total quantity, and determining the corresponding storage bucket sequence number according to the remainder in the division result;
[0049] S303: Store the transaction to be uploaded into the storage bucket corresponding to the storage bucket sequence number.
[0050] The storage space is divided into several buckets, each bucket is numbered, and the total number of buckets is counted. The buckets are numbered starting from 0.
[0051] The transaction hash is divided by the total number, and the bucket number is determined based on the remainder after calculation. For example, the transaction hash is converted to an integer and is 1000. The total number of buckets is 256. 1000÷256=3 remainder 232. Then the transaction to be on-chain is stored in the bucket with the serial number 232. For another example, the transaction hash is converted to an integer and is 512. The total number of buckets is 256. 512÷256=2 remainder 0. Then the transaction to be on-chain is stored in the bucket with the serial number 0.
[0052] As an optional implementation, Figure 4 is a flowchart of a client response method provided by an embodiment of the present invention, such as Figure 4 As shown, after adding the transaction to be verified to the cache queue, it includes:
[0053] S5. Send a storage response to the client;
[0054] S6. After receiving the storage response, the client sends a new transaction to be verified.
[0055] Since the client responds directly to the pre-buffer, after the last transaction to be verified is successfully stored in the cache queue, the transaction pool sends a storage response to the client, indicating that the last transaction to be verified has been stored and the client can send the next transaction to be verified. After receiving the storage response, the client can send a new transaction to be verified to the transaction pool. This ensures that the transaction pool can accept new transactions to be verified while verifying, and the client can continue to send new transactions before transaction verification, improving data processing efficiency.
[0056] The present invention also provides a transaction pool data processing system. Figure 5 Schematic diagram of the structure of the transaction pool data processing system provided by the embodiment of the present invention. Figure 5 As shown, the system includes:
[0057] The cache module 100 is used to obtain the transaction to be verified sent by the client and add the transaction to be verified to the cache queue;
[0058] A pre-buffer is set in the transaction pool, through which the client can respond directly. The client sends the transaction to be verified to the blockchain node to the pre-buffer and stores it in the cache queue.
[0059] The verification module 200 is used to perform signature verification, repeatability verification and chain verification on the transactions to be verified in the cache queue in sequence, and obtain the transactions to be chained that have passed all verifications;
[0060] Signature verification is performed on the pending transactions in the cache queue to determine whether the transaction is legal. Repeatability verification is performed on the pending transactions to determine whether the transaction already exists in the current transaction pool. After that, the pending transactions are verified on the chain to determine whether the transaction has been successfully on the chain. If the transaction is legal, does not repeat with other transactions in the transaction pool, and has not been on the chain, then the transaction is considered to have passed all verifications and is prepared to be on the chain as a pending transaction. In the above verification process, if one verification fails, the transaction cannot be subsequently on the chain.
[0061] The shard storage module 300 is used to sort the corresponding transactions to be uploaded into storage buckets according to the transaction hash; wherein the storage buckets are obtained by sharding the storage space;
[0062] The storage space is pre-sharded to obtain multiple storage buckets, and the storage bucket corresponding to each transaction is calculated based on the transaction hash, and the transaction to be on-chain is stored in the corresponding storage bucket. In this way, a large number of transactions to be on-chain can be evenly distributed into multiple storage buckets to reduce the probability of data competition.
[0063] The on-chain module 400 is used to send the transaction to be on-chain to the blockchain node for on-chaining. After the on-chaining is successful, the transaction to be on-chain is deleted from the corresponding storage bucket.
[0064] The blockchain system obtains the transactions to be uploaded from each storage bucket in the storage space. The blockchain node packages the transactions to be uploaded into a new block. After the block reaches a consensus, it marks that the transactions to be uploaded have been successfully uploaded. At this time, the blockchain submits the transaction and the execution result to the blockchain database.
[0065] After the transaction is successfully uploaded to the chain, the storage bucket corresponding to the transaction that has been uploaded to the chain is located according to the transaction hash, and the transaction to be uploaded to the chain is deleted from the storage bucket.
[0066] As an optional implementation, Figure 6 is a schematic diagram of the structure of the verification module provided by the embodiment of the present invention, such as Figure 6 As shown, the verification module 200 includes:
[0067] The signature verification submodule 2001 is used to allocate a thread for the transaction to be verified, and use the ECDSA elliptic curve digital signature algorithm to verify the signature of the transaction to be verified. If the signature is valid, the signature verification is passed;
[0068] The transactions to be verified in the cache queue are verified in parallel, that is, multiple transactions to be verified are verified simultaneously through multiple threads.
[0069] The transaction to be verified is signed by the ECDSA elliptic curve digital signature algorithm on the client side. When the transaction to be verified is verified in the transaction pool, the ECDSA elliptic curve digital signature algorithm is used to verify the transaction to be verified. If the signature is valid, the signature verification is successful.
[0070] The repeatability verification submodule 2002 is used to determine whether the random number of the transaction to be verified is repeated with the random numbers of other transactions to be verified in the cache queue. If not, the repeatability verification is passed; wherein the random number is generated on the client;
[0071] The client generates a random number for each transaction to be verified. When the transaction to be verified passes the signature verification, it is necessary to determine whether the transaction to be verified exists repeatedly in the transaction pool. Specifically, check whether there is a transaction in the cache queue with the same random number as the transaction to be verified. If there is, it proves that the transaction to be verified is a duplicate transaction and cannot pass the repeatability verification; on the contrary, if there is no transaction to be verified, it proves that the transaction to be verified is not a duplicate transaction and passes the repeatability verification.
[0072] The on-chain verification submodule 2003 is used to determine whether the random number of the transaction to be verified exists in the on-chain transaction random number list. If not, the on-chain verification is passed.
[0073] Check whether there is a transaction with the same random number as the transaction to be verified in the random number list of on-chain transactions. If so, it proves that the transaction to be verified has been successfully on-chain and does not need to be on-chain again, and cannot pass the on-chain verification; on the contrary, if it does not exist, it proves that the transaction to be verified is a transaction to be on-chain and has passed the on-chain verification.
[0074] As an optional implementation, the random number list of on-chain transactions includes the random numbers corresponding to the most recent 1000 transactions successfully on-chain. When a new transaction is successfully on-chain, its corresponding random number is saved in the random number list of on-chain transactions.
[0075] As an optional implementation, Figure 7 is a schematic diagram of the structure of a shard storage module provided in an embodiment of the present invention. Figure 7 As shown, the shard storage module 300 includes:
[0076] A counting submodule 3001 is used to count the total number of storage buckets and assign a storage bucket sequence number to each storage bucket;
[0077] A calculation submodule 3002 is used to calculate the division result of the transaction hash and the total quantity, and determine the corresponding storage bucket sequence number according to the remainder in the division result;
[0078] The storage submodule 3003 is used to store the transaction to be uploaded into the storage bucket corresponding to the storage bucket sequence number.
[0079] The storage space is divided into several buckets, each bucket is numbered, and the total number of buckets is counted. The buckets are numbered starting from 0.
[0080] The transaction hash is divided by the total number, and the bucket number is determined based on the remainder after calculation. For example, the transaction hash is converted to an integer and is 1000. The total number of buckets is 256. 1000÷256=3 remainder 232. Then the transaction to be on-chain is stored in the bucket with the serial number 232. For another example, the transaction hash is converted to an integer and is 512. The total number of buckets is 256. 512÷256=2 remainder 0. Then the transaction to be on-chain is stored in the bucket with the serial number 0.
[0081] As an optional implementation, Figure 8 is a schematic diagram of the structure of a module for responding to a client provided in an embodiment of the present invention, such as Figure 8 As shown, the system also includes:
[0082] A response module 500 is used to send a storage response to the client;
[0083] The sending module 600 is used for the client to send a new transaction to be verified after receiving the storage response.
[0084] Since the client responds directly to the pre-buffer, after the last transaction to be verified is successfully stored in the cache queue, the transaction pool sends a storage response to the client, indicating that the last transaction to be verified has been stored and the client can send the next transaction to be verified. After receiving the storage response, the client can send a new transaction to be verified to the transaction pool. This ensures that the transaction pool can accept new transactions to be verified while verifying, and the client can continue to send new transactions before transaction verification, improving data processing efficiency.
[0085] The present invention also provides a transaction pool data processing device, comprising the transaction pool data processing system mentioned above.
[0086] The present invention also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the above-mentioned transaction pool data method is implemented.
[0087] The above storage media include but are not limited to: CDs, floppy disks, hard disks, erasable memory, etc.
[0088] The above technical solution has the following beneficial effects: by storing transactions sent by the client in a cache queue and responding directly to the client, it is ensured that subsequent verification and new transactions sent by the client no longer conflict with each other, thereby improving data processing efficiency; by sharding the storage space and storing a large number of transactions to be uploaded to the chain in different storage buckets, the probability of data competition is reduced; transactions are verified in parallel to improve transaction verification efficiency, thereby further improving the data processing speed of the transaction pool and the performance of the blockchain system.
[0089] The specific implementation methods of the above invention further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above content is only the specific implementation methods of the present invention and is not intended to limit the protection scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.
Claims
1. A transaction pool data processing method, characterized in that: include: Obtain the transaction to be verified sent by the client, and add the transaction to be verified to the cache queue; Perform signature verification, repeatability verification and chain verification on the transactions to be verified in the cache queue in turn, and obtain the transactions to be chained that have passed all verifications; According to the transaction hash, the corresponding transactions to be uploaded to the chain are divided into storage buckets; wherein the storage buckets are obtained by sharding the storage space; The transaction to be on-chain is sent to the blockchain node for on-chain. After the on-chain is successful, the transaction to be on-chain is deleted from the corresponding storage bucket.
2. The transaction pool data processing method according to claim 1, characterized in that: The step of sequentially performing signature verification, repeatability verification and on-chain verification on the transactions to be verified in the cache queue includes: Allocate a thread for the transaction to be verified, and use the ECDSA elliptic curve digital signature algorithm to verify the signature of the transaction to be verified. If the signature is valid, the signature verification is successful; Determine whether the random number of the transaction to be verified is repeated with the random numbers of other transactions to be verified in the cache queue. If not, the repeatability verification is passed; wherein the random number is generated on the client; Determine whether the random number of the transaction to be verified exists in the random number list of on-chain transactions. If not, the on-chain verification is successful.
3. The transaction pool data processing method according to claim 1, characterized in that: The method of dividing the corresponding transactions to be uploaded into storage buckets according to the transaction hash includes: Count the total number of buckets and assign a bucket number to each bucket; Calculate the division result of the transaction hash and the total quantity, and determine the corresponding storage bucket number according to the remainder in the division result; The transaction to be uploaded to the chain is stored in the storage bucket corresponding to the storage bucket sequence number.
4. The transaction pool data processing method according to claim 1, characterized in that: After adding the transaction to be verified into the cache queue, the method further comprises: Sending a storage response to the client; After receiving the storage response, the client sends a new transaction to be verified.
5. A transaction pool data processing system, characterized in that: include: A cache module, used to obtain the transaction to be verified sent by the client, and add the transaction to be verified to a cache queue; A verification module is used to perform signature verification, repeatability verification and chain verification on the transactions to be verified in the cache queue in sequence, and obtain transactions to be chained that have passed all verifications; A shard storage module, used to sort the corresponding transactions to be uploaded into storage buckets according to the transaction hash; wherein the storage buckets are obtained by sharding the storage space; The on-chain module is used to send the transaction to be on-chain to the blockchain node for on-chain. After the on-chain is successful, the transaction to be on-chain is deleted from the corresponding storage bucket.
6. The transaction pool data processing system according to claim 5, characterized in that: The verification module comprises: The signature verification submodule is used to allocate a thread for the transaction to be verified, and use the ECDSA elliptic curve digital signature algorithm to verify the signature of the transaction to be verified. If the signature is valid, the signature verification is passed; A repeatability verification submodule is used to determine whether the random number of the transaction to be verified is repeated with the random numbers of other transactions to be verified in the cache queue. If not, the repeatability verification is passed; wherein the random number is generated on the client; The on-chain verification submodule is used to determine whether the random number of the transaction to be verified exists in the on-chain transaction random number list. If not, the on-chain verification is passed.
7. The transaction pool data processing system according to claim 5, characterized in that: The shard storage module includes: A statistics submodule, used to count the total number of buckets and assign a bucket number to each bucket; A calculation submodule, configured to calculate a division result of the transaction hash and the total quantity, and determine a corresponding storage bucket sequence number according to a remainder in the division result; The storage submodule is used to store the transaction to be uploaded into the storage bucket corresponding to the storage bucket sequence number.
8. The transaction pool data processing system according to claim 5, characterized in that: Also includes: A response module, used for sending a storage response to the client; The sending module is used for the client to send a new transaction to be verified after receiving the storage response.
9. A transaction pool data processing device, characterized in that: A transaction pool data processing system comprising any one of claims 5-8.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the transaction pool data method according to any one of claims 1 to 4 is implemented.
