Transaction Processing Method, Device, Medium and Electronic Device

Through the availability detection and data channel transmission of the blockchain network, the problems of transaction abnormalities or failures are solved, the continuity and stability of transaction business are ensured, and the disaster recovery capabilities are provided.

CN115511486BActive Publication Date: 2025-08-05TENCENT TECHNOLOGY (SHENZHEN) CO LTD

Patent Information

Application Number
CN202110654338.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-06-07
Publication Date
2025-08-05
Estimated Expiration
2041-06-07

AI Technical Summary

Technical Problem

In online and offline transactions, transaction abnormalities or failures caused by equipment failures lead to poor business continuity and stability and reliability.

Method used

The availability of each blockchain node is detected through the transaction data recorded in the blockchain network, normal nodes and abnormal nodes are determined, and when a transaction request is generated on the abnormal node, the request is transmitted to the normal node for joint processing, and a data channel is established for data transmission and processing.

Benefits of technology

It realizes the resolution of transaction abnormalities or failures, avoids transaction interruptions, improves the continuity and stability of trading business, and provides independent regulation and disaster recovery capabilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115511486B_ABST
    Figure CN115511486B_ABST
Patent Text Reader

Abstract

This application belongs to the field of blockchain technology, and specifically relates to a transaction processing method, a transaction processing device, a computer-readable medium, and an electronic device. The transaction processing method includes: performing an availability detection on each blockchain node according to the transaction data recorded in the blockchain network to determine whether each of the blockchain nodes is a normal node or an abnormal node; when a transaction request is generated on the abnormal node, transmitting the transaction request to the normal node so as to jointly process the transaction request by the abnormal node and the normal node. The embodiments of this application can improve the continuity, stability, and reliability of transaction services.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application belongs to the technical field of blockchain, and specifically relates to a transaction processing method, a transaction processing device, a computer-readable medium, and an electronic device. Background Art

[0002] In a large number of online and offline transaction services, problems such as transaction anomalies or transaction failures inevitably occur due to equipment failures or other reasons. How to quickly and accurately eliminate faults is the key to ensuring the business continuity and stable reliability of transaction services. Summary of the Invention

[0003] The purpose of this application is to provide a transaction processing method, a transaction processing device, a computer-readable medium, and an electronic device, which can at least overcome the technical problems such as low fault processing efficiency, poor business continuity, and poor stable reliability existing in the related technologies.

[0004] Other features and advantages of this application will become obvious through the following detailed description, or will be learned partially through the practice of this application.

[0005] According to one aspect of the embodiments of this application, a transaction processing method is provided. The method includes: performing an availability detection on each blockchain node according to the transaction data recorded in the blockchain network to determine whether each blockchain node is a normal node or an abnormal node; when a transaction request is generated on the abnormal node, transmitting the transaction request to the normal node to jointly process the transaction request through the abnormal node and the normal node.

[0006] According to one aspect of the embodiments of this application, a transaction processing device is provided. The device includes: a detection module configured to perform an availability detection on each blockchain node according to the transaction data recorded in the blockchain network to determine whether each blockchain node is a normal node or an abnormal node; a processing module configured to transmit the transaction request to the normal node when a transaction request is generated on the abnormal node to jointly process the transaction request through the abnormal node and the normal node.

[0007] In some embodiments of this application, based on the above technical solution, the detection module includes: a cache module configured to save the transaction data generated on the blockchain network to a transaction cache pool; a packaging module configured to perform a packaging process on the transaction data saved in the transaction cache pool to generate a current block to be chained when the preset block chaining condition is met; a current block detection module configured to perform an availability detection on each blockchain node according to the transaction data recorded in the current block.

[0008] In some embodiments of the present application, based on the above technical solutions, the current block detection module includes: a statistics module configured to count the number of transaction failures and the transaction failure rate of each blockchain node according to the transaction data recorded in the current block; an abnormality determination module configured to determine that the blockchain node is an abnormal node with an availability failure if both the number of transaction failures and the transaction failure rate of the blockchain node reach the corresponding parameter thresholds; a normal determination module configured to determine that the blockchain node is a normal node with availability if either the number of transaction failures or the transaction failure rate of the blockchain node does not reach the corresponding parameter threshold.

[0009] In some embodiments of the present application, based on the above technical solutions, the statistics module includes: a failure count statistics module configured to count the number of transaction failures of each blockchain node according to the transaction data recorded in the current block; a failure rate statistics module configured to count the transaction failure rate of the blockchain node if the number of transaction failures reaches a preset number threshold.

[0010] In some embodiments of the present application, based on the above technical solutions, the statistics module is further configured to: perform integrity verification on the transaction data recorded in the current block to determine whether the transaction data has a complete transaction process; if the transaction process of the transaction data is incomplete, determine that the transaction data is failed transaction data; obtain the node identifier of the blockchain node that processes the transaction data recorded in the transaction data; count the failed transaction data according to the node identifier to obtain the number of transaction failures of each blockchain node.

[0011] In some embodiments of the present application, based on the above technical solutions, the statistics module is further configured to: perform data screening on the transaction data recorded in the current block according to the transaction process to obtain the transaction start data generated when initiating a transaction; obtain a process identifier indicating the transaction process where the transaction start data is located; according to the process identifier, perform matching detection on the transaction start data and other transaction data recorded in the current block to determine whether there is transaction end data with the same process identifier as the transaction start data in the current block, where the transaction end data is data generated when ending a transaction; if there is transaction end data with the same process identifier as the transaction start data in the current block, determine that the transaction data has a complete transaction process; if there is no transaction end data with the same process identifier as the transaction start data in the current block, determine that the transaction process of the transaction data is incomplete.

[0012] In some embodiments of the present application, based on the above technical solutions, the detection module further includes: a historical block acquisition module configured to acquire one or more historical blocks that were most recently linked to the blockchain; a historical block detection module configured to perform availability detection on each blockchain node according to the transaction data recorded in the historical blocks.

[0013] In some embodiments of the present application, based on the above technical solutions, the processing module includes: a target selection module configured to select a target node that is currently in an idle state from the normal nodes of the blockchain network; a channel establishment module configured to establish a data channel for data communication between the abnormal node and the target node; a request transmission module configured to transmit the transaction request from the abnormal node to the target node based on the data channel.

[0014] In some embodiments of the present application, based on the above technical solutions, the target selection module includes: a miner node selection module configured to select the blockchain node with the highest degree of idleness in the blockchain network as the miner node for packaging the current block; a target node selection module configured to select a target node that is currently in an idle state from the normal nodes of the blockchain network through the miner node.

[0015] In some embodiments of the present application, based on the above technical solutions, the miner node selection module is configured to: count the transaction quantities of each blockchain node in the blockchain network according to a preset time period; screen the transaction quantities of each blockchain node according to the transaction data recorded in a preset number of most recently chained blocks to obtain the recent transaction quantities of each blockchain node; select the blockchain node with the smallest recent transaction quantity as the blockchain node with the highest degree of idleness.

[0016] In some embodiments of the present application, based on the above technical solutions, the processing module further includes: a behavior data stream transmission module configured to acquire a behavior data stream associated with the transaction request through the abnormal node and transmit the behavior data stream to the normal node, where the behavior data stream includes interaction behavior data collected through the interaction interface of the abnormal node; a result data stream transmission module configured to process the behavior data stream through a background processing thread on the normal node to obtain a result data stream that is the response data of the behavior data stream and transmit the result data stream to the abnormal node; a result data stream display module configured to display the result data stream on the interaction interface of the abnormal node.

[0017] In some embodiments of the present application, based on the above technical solutions, the transaction processing device further includes: a front-end processing module configured to, if a new transaction request is generated on the normal node, process the new transaction request through a front-end processing thread on the normal node to obtain a transaction processing result of the new transaction request, where the front-end processing thread is a thread that runs concurrently with the back-end processing thread; and a front-end display module configured to display the transaction processing result of the new transaction request on an interaction interface of the normal node.

[0018] According to one aspect of the embodiments of the present application, there is provided a computer-readable medium having a computer program stored thereon, and when the computer program is executed by a processor, it implements the transaction processing method in the above technical solutions.

[0019] According to one aspect of the embodiments of the present application, there is provided an electronic device, which includes: a processor; and a memory for storing executable instructions of the processor; wherein, the processor is configured to execute the transaction processing method in the above technical solutions by executing the executable instructions.

[0020] According to one aspect of the embodiments of the present application, there is provided a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the transaction processing method in the above technical solutions.

[0021] In the technical solutions provided in the embodiments of the present application, by performing data transmission between an abnormal node and a normal node, a solution in which the normal node and the abnormal node jointly perform transaction processing can be implemented. This not only solves the problem of transaction anomalies or transaction failures, but also avoids the problem of transaction interruption, improves the continuity and stable reliability of transaction services, and can provide a stable and reliable self-regulating disaster recovery ability for the business system in the long term.

[0022] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The accompanying drawings here are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application. Obviously, the accompanying drawings in the following description are only some embodiments of the present application, and those of ordinary skill in the art can obtain other drawings without creative efforts based on these drawings.

[0024] Figure 1 Shows a schematic diagram of the composition of a blockchain system.

[0025] Figure 2 Shows the composition structure of a blockchain maintained on a blockchain network.

[0026] Figure 3 Shows a schematic diagram of the generation process of a new block.

[0027] Figure 4 Schematically shows the flowchart of the steps of the transaction processing method in an embodiment of the present application.

[0028] Figure 5 Shows the business process flowchart of generating transaction data in an embodiment of the present application.

[0029] Figure 6 Schematically shows the business process flowchart of performing fault detection in an embodiment of the present application.

[0030] Figure 7 Schematically shows the business process flowchart of performing fault recovery in an embodiment of the present application.

[0031] Figure 8 Schematically shows the flowchart of the steps of performing availability detection on a blockchain node in an embodiment of the present application.

[0032] Figure 9 Schematically shows the flowchart of the steps of counting the number of transaction failures in an embodiment of the present application.

[0033] Figure 10 Schematically shows the flowchart of the steps of performing transaction request transmission in an embodiment of the present application.

[0034] Figure 11 Schematically shows the flowchart of the steps of an abnormal node and a normal node jointly processing a transaction request in an embodiment of the present application.

[0035] Figure 12 Schematically shows the structural block diagram of the transaction processing device provided in an embodiment of the present application.

[0036] Figure 13 Schematically shows the computer system structural block diagram of an electronic device suitable for implementing the embodiments of the present application. Detailed implementation manners

[0037] Now, example embodiments will be described more fully with reference to the accompanying drawings. However, the example embodiments can be implemented in various forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete, and will fully convey the concept of the example embodiments to those skilled in the art.

[0038] In addition, the described features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. In the following description, numerous specific details are provided to give a thorough understanding of the embodiments of the present application. However, those skilled in the art will realize that the technical solutions of the present application may be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other cases, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the present application.

[0039] The block diagrams shown in the drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0040] The flowcharts shown in the drawings are merely illustrative and do not necessarily include all the content and operations / steps, nor do they necessarily have to be executed in the described order. For example, some operations / steps may be decomposed, while some operations / steps may be combined or partially combined, so the actual execution order may change according to the actual situation.

[0041] The technical solutions provided by the embodiments of the present application mainly relate to transaction business scenarios such as online payment and transfer based on blockchain technology. The business processing status and capabilities of offline devices can be regulated by means of the smart contracts and block content detection of blockchain technology, so as to ensure that the business system has strong business continuity and stable reliability.

[0042] Blockchain is a digital ledger with a chained-block data structure that is anti-counterfeiting, anti-tampering, and traceable, constructed through transparent and trusted rules in a peer-to-peer network environment. The chained-block data structure stores the transaction processing that occurs within a period of time in units of blocks, and connects the blocks in chronological order with cryptographic algorithms to form a chain. The ledger is distributed to all member nodes in the network, and in the sequential chain of blocks linked by hash cryptographic algorithms, the historical records of asset transactions that occur between peer nodes in the network are permanently recorded. All confirmed and proven transactions are linked from the beginning of the chain to the latest block, hence the name blockchain. Blockchain can serve as a single source of truth, and members in the blockchain network can only view the transactions related to them.

[0043] Figure 1The figure shows a schematic composition of a blockchain system. The blockchain system 100 may include at least one client 110 and a blockchain network 120, and the blockchain network 120 includes at least one blockchain node 121. The client 110 may be various electronic devices such as a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart wearable device, a smart vehicle-mounted device, a smart payment terminal, a face recognition terminal, etc. By installing the corresponding client application program, blockchain data services can be provided to users. The blockchain node 121 may be a terminal device or a server. For example, the blockchain node 121 may be an independent physical server, or may be a server cluster composed of multiple physical servers, or may also be a cloud server providing cloud computing services.

[0044] In the blockchain network 120, each blockchain node 121 can receive input information during normal operation and maintain the shared data in the blockchain network based on the received input information. To ensure information interconnection, there may be information connections between each blockchain node 121, and each blockchain node 121 can transmit information through the information connection. For example, when any blockchain node 121 in the blockchain network 120 receives input information and broadcasts the input information in the blockchain network 120, other node devices in the blockchain network 120 can obtain the input information according to the consensus algorithm and store the input information as shared data.

[0045] For each blockchain node 121 in the blockchain network 120, it has a corresponding node identifier, and each blockchain node 121 in the blockchain network 120 can store the node identifiers of other blockchain nodes in the same blockchain network, so as to broadcast the generated block to other nodes in the blockchain network 120 according to the node identifiers of other blockchain nodes later. A node identifier list as shown in Table 1 can be maintained in the blockchain node 121, and the node name and the node identifier are correspondingly stored in the node identifier list. Among them, the node identifier may be an IP (Internet Protocol) address and any other information that can be used to identify the node. Table 1 is a node identifier list taking the IP address as an example.

[0046] Table 1

[0047] Node Name Node Identifier Node 1 117.114.151.174 Node 2 117.116.189.145 … … Node N 119.123.789.258

[0048] Figure 2 The figure shows the composition structure of the blockchain maintained on the blockchain network. As Figure 2As shown in the figure, the blockchain consists of multiple sequentially connected blocks. Whenever new data needs to be written into the blockchain, this data will be aggregated into a newly generated block, and the newly generated block will be linked to the end of the blockchain. Through the consensus algorithm, it can be ensured that the newly added blocks on each node device 121 are exactly the same. In the block body of each block, the data of the current block is recorded, and at the same time, the hash value (Hash) of the previous block connected to it is stored in its block header. If the transaction data in the previous block changes, then the hash value of the current block will also change accordingly. Therefore, the data uploaded to the blockchain network is difficult to be tampered with, which can improve the reliability of shared data.

[0049] Figure 3 FIG. shows a schematic diagram of the generation process of a new block. As Figure 3 shown, when generating each block in the blockchain, first, the blockchain node verifies the received input information. After the verification is completed, the input information is stored in the memory pool, and its hash tree for recording the input information is updated; then, the update timestamp is updated to the time when the input information is received, and different random numbers are tried, and the eigenvalue calculation is performed multiple times so that the calculated eigenvalue can satisfy the following formula:

[0050] SHA256(SHA256(version+prev_hash+merkle_root+ntime+nbits+x))<TARGET

[0051] where, SHA256 is the eigenvalue algorithm used to calculate the eigenvalue; version (version number) is the version information of the relevant block protocol in the blockchain; prev_hash is the block header eigenvalue of the parent block of the current block; merkle_root is the eigenvalue of the input information; ntime is the update time of the update timestamp; nbits is the current difficulty, which is a fixed value within a period of time and is determined again after exceeding the fixed time period; x is a random number; TARGET is the eigenvalue threshold, and this eigenvalue threshold can be determined according to nbits.

[0052] In this way, when a random number that satisfies the above formula is calculated, the information can be correspondingly stored, the block header and the block body are generated, and the current block is obtained. Subsequently, the node where the blockchain is located sends the newly generated block to other nodes in the data sharing system where it is located according to the node identifiers of other nodes in the data sharing system. The other nodes verify the newly generated block and add the newly generated block to the blockchain stored by them after the verification is completed.

[0053] The following makes a detailed description of the technical solutions such as the transaction processing method, transaction processing device, computer-readable medium, and electronic device provided by the present application in combination with specific embodiments.

[0054] Figure 4 Schematically shows a step flowchart of a transaction processing method in an embodiment of the present application. This transaction processing method can be executed by Figure 1 the terminal device serving as the client shown, or can be executed by a blockchain node in the blockchain network. The embodiment of the present application takes the transaction processing method executed by the blockchain node as an example for illustration. As Figure 4 shown, this transaction processing method may include the following steps S410 to step S420.

[0055] Step S410: Perform availability detection on each blockchain node according to the transaction data recorded in the blockchain network to determine whether each blockchain node is a normal node or an abnormal node.

[0056] In an embodiment of the present application, a blockchain network is established based on all offline Internet of Things (IOT) devices. Each block can be regarded as an encrypted file containing device transaction details + timestamp + block hash. In the embodiment of the present application, the size of the block is specified as 20M, and the complete record of a single transaction is about 1k.

[0057] Figure 5 Shows a business flowchart for generating transaction data in an embodiment of the present application. As Figure 5 shown, a blockchain is maintained on the blockchain network composed of a node cluster. Each node stores the transaction system and smart contract of the blockchain network, as well as multiple blocks generated locally at the blockchain node. For example, node 1 stores blocks 1 to 3, node 2 stores blocks 4 to 6, and node 3 stores blocks 7 to 9. Each block can be regarded as an encrypted file including multiple transaction records. This encrypted file is encrypted and decrypted using the symmetric key method. Each IOT device has a unique decryption key burned into the device system layer Rom and cannot be forcibly obtained through technical means. Through the private key, each IOT device can obtain the data information in the encrypted block. When a transaction occurs on the blockchain node, a miner node can be selected to write the transaction record into the block, and then the block is linked to the blockchain through the on-chain operation.

[0058] Figure 6 Schematically shows a business flowchart for performing fault detection in an embodiment of the present application. As Figure 6As shown, miner nodes can obtain transaction records broadcast by blockchain nodes in the blockchain network. Using the smart contract configured on the miner nodes, they can perform availability checks on each blockchain node that generates the transaction records. Based on the test results, they can obtain a result receipt indicating the node type. For example, they can determine which blockchain nodes are abnormal and which are normal. The transaction system running on the abnormal node is marked as a faulty system, while the transaction system running on the normal node is compared as an available system.

[0059] Step S420: When a transaction request is generated on the abnormal node, the transaction request is transmitted to the normal node, so that the transaction request is processed jointly by the abnormal node and the normal node.

[0060] Figure 7 The following schematically shows a business process diagram for fault recovery in one embodiment of the present application. Figure 7 As shown in the figure, when a miner node determines that a blockchain node has an abnormality, it will obtain a device with normal transactions and idle time from the transaction ledger as a normal node, and notify the network to establish a data communication channel (long connection) between the abnormal node and the normal node.

[0061] Abnormal nodes will receive data information from miner nodes, which includes the unique identification and IP information of normal nodes. The faulty nodes will establish connections with normal nodes based on this information. When transactions occur on abnormal nodes, the conditions for the interaction between the device and the outside world can be converted into data information (such as click events, face recognition events, etc.), and this information can be transmitted to available nodes through the connection.

[0062] When a normal node receives a data stream from an abnormal node, it leverages its own system availability to help the abnormal node process the data stream and returns the processed results to the abnormal node. This process is not displayed on the normal node's interface. If the normal node is used to execute its own transaction (currently processing the abnormal node's transaction), a new thread will be started to execute the process concurrently, but the execution of its own transaction will be returned to the interface for interactive display.

[0063] After the normal node processes the transaction data of the abnormal node, it will return the transaction result to the abnormal node, and the abnormal node will display the result (whether the payment is successful, how much money was deducted from the user, how much money was exempted, etc.).

[0064] At this point, the abnormal node completes disaster recovery by forwarding data streams with the help of the available systems of normal nodes.

[0065] In the transaction processing method provided by the embodiments of the present application, by performing data transmission between abnormal nodes and normal nodes, a solution can be implemented in which normal nodes and abnormal nodes jointly process transactions. This not only solves the problems of transaction anomalies or transaction failures, but also avoids the problem of transaction interruption, improves the continuity, stability, and reliability of transaction services, and can provide the business system with a stable and reliable self-regulating disaster recovery ability in the long term.

[0066] Figure 8 Schematically shows a flowchart of steps for performing availability detection on blockchain nodes in an embodiment of the present application. As Figure 8 shown, based on the above embodiments, the availability detection of each blockchain node according to the transaction data recorded in the blockchain network in step S410 may include the following steps S810 to step S830.

[0067] Step S810: Save the transaction data generated on the blockchain network to the transaction cache pool.

[0068] Each blockchain node can maintain its own transaction cache pool. When transaction data is generated on the blockchain network, it can be temporarily stored in the transaction cache pool and wait to be processed for being added to the blockchain.

[0069] Step S820: When the preset blockchain addition condition is met, perform a packaging process on the transaction data saved in the transaction cache pool to generate the current block to be added to the blockchain.

[0070] The blockchain addition condition may include, for example, a time condition or a capacity condition. The time condition is that the link time from the previous block in the blockchain network has reached a specified time threshold, and the capacity condition is that the number of transactions in the transaction cache pool reaches a specified quantity threshold or storage capacity threshold.

[0071] The operation of packaging and adding to the blockchain is generally performed by miner nodes. After generating the current block to be added to the blockchain, the miner nodes can broadcast the current block to the blockchain network, and the consensus nodes in the blockchain network perform consensus authentication on it, and link the current block to the blockchain after the authentication passes. Then, new transaction data can continue to be accumulated in the emptied transaction cache pool.

[0072] Step S830: Perform availability detection on each blockchain node according to the transaction data recorded in the current block.

[0073] In an embodiment of the present application, a method for detecting the availability of each blockchain node according to the transaction data recorded in the current block includes: counting the number of transaction failures and the transaction failure rate of each blockchain node according to the transaction data recorded in the current block; if both the number of transaction failures and the transaction failure rate of the blockchain node reach the corresponding parameter thresholds, determining that the blockchain node is an abnormal node with an availability fault; if either the number of transaction failures or the transaction failure rate of the blockchain node does not reach the corresponding parameter threshold, determining that the blockchain node is a normal node with availability.

[0074] In an embodiment of the present application, the number of transaction failures and the transaction failure rate of each blockchain node can be counted simultaneously. If both the number of transaction failures and the transaction failure rate of a blockchain node are large, it indicates that the blockchain node is very likely to be an abnormal node.

[0075] In an embodiment of the present application, a method for counting the number of transaction failures and the transaction failure rate of each blockchain node according to the transaction data recorded in the current block may include: counting the number of transaction failures of each blockchain node according to the transaction data recorded in the current block; if the number of transaction failures reaches a preset number threshold, counting the transaction failure rate of the blockchain node.

[0076] In an embodiment of the present application, first, the number of transaction failures of each blockchain node is counted. For the blockchain nodes whose number of transaction failures reaches the number threshold, their transaction failure rate is further counted. For the blockchain nodes whose number of transaction failures is lower than the number threshold, they can be directly determined as normal nodes without counting their transaction failure rate.

[0077] For example, if the number of transaction failures of a certain blockchain node in the current block reaches more than 5 times, its transaction failure rate is started to be counted for fault judgment. If the transaction failure rate of the blockchain node is greater than 80%, it can be determined that the blockchain node has an availability fault and is an abnormal node. For this abnormal node, disaster recovery needs to be performed on it to avoid problems such as continued transaction anomalies or transaction failures on this abnormal node.

[0078] Figure 9 Schematically shows the step flowchart of counting the number of transaction failures in an embodiment of the present application. As Figure 9 shown, based on the above embodiment, a method for counting the number of transaction failures of each blockchain node according to the transaction data recorded in the current block may include the following steps S910 to step S940.

[0079] Step S910: Perform integrity verification on the transaction data recorded in the current block to determine whether the transaction data has a complete transaction process.

[0080] Step S920: If the transaction process of the transaction data is incomplete, determine that the transaction data is failed transaction data.

[0081] Step S930: Obtain the node identifier of the blockchain node that processes the transaction data recorded in the transaction data.

[0082] Step S940: Statistically analyze the failed transaction data according to the node identifier to obtain the number of failed transactions of each blockchain node.

[0083] The block content is mainly composed of transaction data. The transaction data is divided into two parts, one is the starting point of the transaction, and the other is the ending point of the transaction. These two pieces of data can be associated through a single process identifier session, so that the corresponding transaction ending point data can be found through the unique transaction starting point data. At the same time, the transaction status of each block is adjusted based on the smart contract. Since each node (face recognition IOT device) writes the transaction information (starting point and ending point) of a single process into a specified block during the transaction, the smart contract can know the transaction situation of any block and thus judge the availability of the node. The embodiment of the present application can perform head-tail matching on all transaction records recorded in a block. For a transaction record that only has a head but no tail, we determine it as a failed transaction record. When the entire block record ends, the smart contract coordinates the total number of failed transactions that occurred in the corresponding block and performs grouped statistics according to the node identifier to establish the number of failed transactions of each node.

[0084] Based on the above method of recording the transaction process, in an embodiment of the present application, the method for performing integrity verification on the transaction data recorded in the current block may include: screening the transaction data recorded in the current block according to the transaction process to obtain the transaction starting point data generated when the transaction is initiated; obtaining the process identifier indicating the transaction process where the transaction starting point data is located; according to the process identifier, performing matching detection on the transaction starting point data and other transaction data recorded in the current block to determine whether there is transaction ending point data with the same process identifier as the transaction starting point data in the current block, and the transaction ending point data is the data generated when the transaction ends; if there is transaction ending point data with the same process identifier as the transaction starting point data in the current block, determine that the transaction data has a complete transaction process; if there is no transaction ending point data with the same process identifier as the transaction starting point data in the current block, determine that the transaction process of the transaction data is incomplete.

[0085] In an embodiment of the present application, in addition to performing availability detection according to the current block to be uploaded to the blockchain, one or more historical blocks that were recently linked to the blockchain may also be obtained, and availability detection may be performed on each blockchain node according to the transaction data recorded in the historical blocks.

[0086] In one embodiment of the present application, one or more historical blocks may also be merged with the current block to be chained for transaction data, so as to detect the availability of each blockchain node in the merged transaction data.

[0087] Figure 10 Schematically shows a flowchart of steps for transmitting a transaction request in one embodiment of the present application. As Figure 10 shown, based on the above embodiments, transmitting the transaction request to a normal node in step S420 may include the following steps S1010 to step S1030.

[0088] Step S1010: Select a target node that is currently idle from the normal nodes in the blockchain network.

[0089] By monitoring the working status of each normal node, it can be determined whether each normal node is processing transaction services. If a certain normal node is not currently processing services, it can be determined that the normal node is idle and can be used as a candidate node. When there are multiple candidate nodes in an idle state, an embodiment of the present application can randomly select one node as the target node.

[0090] In one embodiment of the present application, multiple target nodes can also be selected simultaneously in this step, so that the multiple target nodes form a relationship of a primary node and a standby node with each other, thereby improving the processing reliability and processing efficiency of transaction services.

[0091] Step S1020: Establish a data channel for data communication between the abnormal node and the target node.

[0092] An embodiment of the present application can send the network access address of the target node to the abnormal node, so that the abnormal node can initiate the establishment of a data channel with the target node. Among them, the network access address may include an Internet Protocol IP address and a port number PORT. The data channel established between the abnormal node and the target node may be, for example, a long connection channel based on the TCP communication protocol.

[0093] Step S1030: Based on the data channel, transmit the transaction request from the abnormal node to the target node.

[0094] After the data channel is established, point-to-point data transmission can be performed between the abnormal node and the target node, thereby implementing a solution for jointly processing transactions by the abnormal node and the normal node.

[0095] In an embodiment of the present application, selecting a target node that is currently in an idle state from the normal nodes of the blockchain network in step S1010 may include: selecting the blockchain node with the highest degree of idleness from the blockchain network as the miner node for packaging the current block; and selecting the target node that is currently in an idle state from the normal nodes of the blockchain network through the miner node.

[0096] In an embodiment of the present application, the method of selecting the blockchain node with the highest degree of idleness from the blockchain network may include: counting the transaction quantities of each blockchain node in the blockchain network according to a preset time period; screening the transaction quantities of each blockchain node based on the transaction data recorded in a preset number of recently chained blocks to obtain the recent transaction quantities of each blockchain node; and selecting the blockchain node with the smallest recent transaction quantity as the blockchain node with the highest degree of idleness.

[0097] For example, an embodiment of the present application may stipulate that each blockchain node reports the transaction situation processed on the node every 12 hours. Each generated transaction is recorded as an increase in the transaction quantity by 1, and if no transaction is generated, the transaction quantity is recorded as 0. An embodiment of the present application may take the transaction data recorded in three consecutive blocks, screen the transaction quantities counted for each blockchain node to obtain the recent transaction quantities, then arrange them in ascending order of the recent transaction quantities to form a node list, select the node ranked first in the node list as the blockchain node with the highest degree of idleness, and then use this node as the miner node for block packaging and chaining.

[0098] Figure 11 Schematically shows the step flow chart of an abnormal node and a normal node jointly processing a transaction request in an embodiment of the present application. As Figure 11 shown, based on the above embodiment, jointly processing the transaction request by the abnormal node and the normal node in step S420 may include the following steps S1110 to step S1150.

[0099] Step S1110: Obtain the behavior data stream associated with the transaction request through the abnormal node and transmit the behavior data stream to the normal node. The behavior data stream includes the interaction behavior data collected through the interaction interface of the abnormal node.

[0100] Step S1120: Process the behavior data stream through the background processing thread on the normal node to obtain the result data stream as the response data of the behavior data stream, and transmit the result data stream to the abnormal node.

[0101] Step S1130: Display the result data stream on the interaction interface of the abnormal node.

[0102] Step S1140: If a new transaction request is generated on a normal node, the new transaction request is processed by the foreground processing thread on the normal node to obtain the transaction processing result of the new transaction request. The foreground processing thread is a thread that runs concurrently with the background processing thread.

[0103] Step S1150: Display the transaction processing result of the new transaction request on the interaction interface of the normal node.

[0104] In the embodiment of the present application, the normal node can process the transaction requests generated on the abnormal node through the background processing thread, and still visually display the processing results on the abnormal node, making the user completely unaware of node failure detection and failure repair. When a new transaction request is generated on the normal node itself, the concurrently running foreground processing thread can be used for transaction processing, without any impact on the transaction processing process for abnormal nodes running in the background.

[0105] It should be noted that although the steps of the method in the present application are described in a specific order in the drawings, this does not require or imply that these steps must be executed in that specific order, or that all the steps shown must be executed to achieve the desired result. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step for execution, and / or one step may be decomposed into multiple steps for execution, etc.

[0106] The following introduces the device embodiments of the present application, which can be used to execute the transaction processing method in the above embodiments of the present application.

[0107] Figure 12 Schematically shows the structural block diagram of the transaction processing device provided by the embodiment of the present application. As Figure 12 shown, the transaction processing device 1200 mainly may include: a detection module 1210, configured to perform availability detection on each blockchain node according to the transaction data recorded in the blockchain network to determine each of the blockchain nodes as a normal node or an abnormal node; a processing module 1220, configured to when a transaction request is generated on the abnormal node, transmit the transaction request to the normal node to jointly process the transaction request by the abnormal node and the normal node.

[0108] In some embodiments of the present application, based on the above embodiments, the detection module 1210 includes: a cache module, configured to save the transaction data generated on the blockchain network to the transaction cache pool; a packaging module, configured to perform packaging processing on the transaction data saved in the transaction cache pool when the preset block chain-up condition is met to generate the current block to be chained up; a current block detection module, configured to perform availability detection on each blockchain node according to the transaction data recorded in the current block.

[0109] In some embodiments of the present application, based on the above embodiments, the current block detection module includes: a statistics module configured to count the number of transaction failures and the transaction failure rate of each blockchain node according to the transaction data recorded in the current block; an abnormality determination module configured to determine that the blockchain node is an abnormal node with an availability failure if both the number of transaction failures and the transaction failure rate of the blockchain node reach the corresponding parameter thresholds; and a normal determination module configured to determine that the blockchain node is a normal node with availability if any one of the number of transaction failures and the transaction failure rate of the blockchain node does not reach the corresponding parameter threshold.

[0110] In some embodiments of the present application, based on the above embodiments, the statistics module includes: a failure count statistics module configured to count the number of transaction failures of each blockchain node according to the transaction data recorded in the current block; and a failure rate statistics module configured to count the transaction failure rate of the blockchain node if the number of transaction failures reaches a preset number threshold.

[0111] In some embodiments of the present application, based on the above embodiments, the statistics module is further configured to: perform integrity verification on the transaction data recorded in the current block to determine whether the transaction data has a complete transaction process; if the transaction process of the transaction data is incomplete, determine that the transaction data is transaction failure data; obtain the node identifier of the blockchain node that processes the transaction data recorded in the transaction data; and count the transaction failure data according to the node identifier to obtain the number of transaction failures of each blockchain node.

[0112] In some embodiments of the present application, based on the above embodiments, the statistics module is further configured to: perform data screening on the transaction data recorded in the current block according to the transaction process to obtain the transaction start point data generated when initiating a transaction; obtain a process identifier representing the transaction process where the transaction start point data is located; and perform matching detection on the transaction start point data and other transaction data recorded in the current block according to the process identifier to determine whether there is transaction end point data with the same process identifier as the transaction start point data in the current block, where the transaction end point data is data generated when ending a transaction; if there is transaction end point data with the same process identifier as the transaction start point data in the current block, determine that the transaction data has a complete transaction process; and if there is no transaction end point data with the same process identifier as the transaction start point data in the current block, determine that the transaction process of the transaction data is incomplete.

[0113] In some embodiments of the present application, based on the above embodiments, the detection module 1210 further includes: a historical block acquisition module configured to acquire one or more historical blocks that were most recently linked to the blockchain; a historical block detection module configured to perform an availability detection on each blockchain node according to the transaction data recorded in the historical blocks.

[0114] In some embodiments of the present application, based on the above embodiments, the processing module 1220 includes: a target selection module configured to select a target node that is currently in an idle state from the normal nodes of the blockchain network; a channel establishment module configured to establish a data channel for data communication between the abnormal node and the target node; a request transmission module configured to transmit the transaction request from the abnormal node to the target node based on the data channel.

[0115] In some embodiments of the present application, based on the above embodiments, the target selection module includes: a miner node selection module configured to select the blockchain node with the highest degree of idleness from the blockchain network as the miner node for packaging the current block; a target node selection module configured to select a target node that is currently in an idle state from the normal nodes of the blockchain network through the miner node.

[0116] In some embodiments of the present application, based on the above embodiments, the miner node selection module is configured to: count the transaction amounts of each blockchain node in the blockchain network according to a preset time period; screen the transaction amounts of each blockchain node according to the transaction data recorded in a preset number of blocks that were most recently added to the chain, to obtain the recent transaction amounts of each blockchain node; select the blockchain node with the smallest recent transaction amount as the blockchain node with the highest degree of idleness.

[0117] In some embodiments of the present application, based on the above embodiments, the processing module 1220 further includes: a behavior data stream transmission module configured to acquire a behavior data stream associated with the transaction request through the abnormal node and transmit the behavior data stream to the normal node, where the behavior data stream includes interaction behavior data collected through the interaction interface of the abnormal node; a result data stream transmission module configured to process the behavior data stream through a background processing thread on the normal node to obtain a result data stream that is the response data of the behavior data stream, and transmit the result data stream to the abnormal node; a result data stream display module configured to display the result data stream on the interaction interface of the abnormal node.

[0118] In some embodiments of the present application, based on the above embodiments, the transaction processing device 1200 further includes: a front-end processing module configured to, if a new transaction request is generated on the normal node, process the new transaction request through a front-end processing thread on the normal node to obtain a transaction processing result of the new transaction request, where the front-end processing thread is a thread that runs concurrently with the back-end processing thread; and a front-end display module configured to display the transaction processing result of the new transaction request on an interaction interface of the normal node.

[0119] The specific details of the transaction processing device provided in each embodiment of the present application have been described in detail in the corresponding method embodiments, and will not be elaborated here.

[0120] Figure 13 Schematically shows a block diagram of a computer system of an electronic device for implementing embodiments of the present application.

[0121] It should be noted that Figure 13 The computer system 1300 of the shown electronic device is only an example and should not impose any limitation on the functions and usage scope of the embodiments of the present application.

[0122] As Figure 13 shown, the computer system 1300 includes a central processing unit 1301 (Central Processing Unit, CPU), which can perform various appropriate actions and processes according to a program stored in a read-only memory 1302 (Read-Only Memory, ROM) or a program loaded from a storage section 1308 into a random access memory 1303 (Random Access Memory, RAM). In the random access memory 1303, various programs and data required for system operation are also stored. The central processing unit 1301, the read-only memory 1302, and the random access memory 1303 are connected to each other through a bus 1304. An input / output interface 1305 (Input / Output interface, i.e., I / O interface) is also connected to the bus 1304.

[0123] The following components are connected to the input / output interface 1305: an input section 1306 including a keyboard, a mouse, etc.; an output section 1307 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1308 including a hard disk, etc.; and a communication section 1309 including a network interface card such as a local area network card, a modem, etc. The communication section 1309 performs communication processing via a network such as the Internet. A drive 1310 is also connected to the input / output interface 1305 as required. A removable medium 1311, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1310 as required so that a computer program read therefrom is installed into the storage section 1308 as required.

[0124] Specifically, according to an embodiment of the present application, the processes described in each method flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product including a computer program carried on a computer-readable medium, the computer program including program codes for performing the methods shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 1309, and / or installed from the removable medium 1311. When the computer program is executed by the central processing unit 1301, various functions defined in the system of the present application are executed.

[0125] It should be noted that the computer-readable medium shown in the embodiments of the present application can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, the computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, apparatus, or device. In the present application, the computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, and this computer-readable medium can send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0126] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagram can represent a module, a program segment, or a part of code, and the above module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, as well as the combination of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0127] It should be noted that although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of the two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0128] Through the description of the above embodiments, those skilled in the art can easily understand that the exemplary embodiments described herein can be implemented by software or by a combination of software and necessary hardware. Therefore, the technical solutions according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (such as a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the embodiments of the present application.

[0129] After considering the specification and practicing the invention disclosed herein, those skilled in the art will readily conceive of other embodiments of the present application. The present application aims to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include well-known knowledge or conventional technical means in the technical field not disclosed in the present application.

[0130] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. A transaction processing method, characterized in that: include: Performing availability checks on each blockchain node based on transaction data recorded in the blockchain network to determine whether each blockchain node is a normal node or an abnormal node; wherein the transaction system installed on the abnormal node is marked as a faulty system, and the transaction system installed on the normal node is marked as an available system; the abnormal node is a node whose number of transaction failures and transaction failure rate both reach corresponding parameter thresholds; When a transaction request is generated on the abnormal node, the transaction request is transmitted to the normal node; Acquire a behavior data stream associated with the transaction request through the abnormal node, and transmit the behavior data stream to the normal node, wherein the behavior data stream includes interaction behavior data collected through the interaction interface of the abnormal node; Processing the behavior data stream by a background processing thread on the normal node to obtain a result data stream as response data of the behavior data stream, and transmitting the result data stream to the abnormal node; The result data stream is displayed on the interactive interface of the abnormal node.

2. The transaction processing method according to claim 1, characterized in that: Perform availability checks on each blockchain node based on transaction data recorded in the blockchain network, including: Save transaction data generated on the blockchain network to the transaction cache pool; When the preset block chain conditions are met, the transaction data stored in the transaction buffer pool is packaged and processed to generate the current block to be chained; The availability of each blockchain node is checked based on the transaction data recorded in the current block.

3. The transaction processing method according to claim 2, characterized in that: Performing availability checks on each blockchain node based on the transaction data recorded in the current block, including: Counting the number of transaction failures and the transaction failure rate of each blockchain node based on the transaction data recorded in the current block; If both the number of transaction failures and the transaction failure rate of the blockchain node reach corresponding parameter thresholds, the blockchain node is determined to be an abnormal node with availability failure; If any one of the number of transaction failures and the transaction failure rate of the blockchain node does not reach the corresponding parameter threshold, the blockchain node is determined to be a normal node with availability.

4. The transaction processing method according to claim 3, characterized in that: The number of transaction failures and transaction failure rates of each blockchain node are counted based on the transaction data recorded in the current block, including: Counting the number of transaction failures of each blockchain node based on the transaction data recorded in the current block; If the number of transaction failures reaches a preset threshold, the transaction failure rate of the blockchain node is counted.

5. The transaction processing method according to claim 3, characterized in that: The number of transaction failures of each blockchain node is counted based on the transaction data recorded in the current block, including: Performing an integrity check on the transaction data recorded in the current block to determine whether the transaction data has a complete transaction process; If the transaction process of the transaction data is incomplete, determining that the transaction data is transaction failed data; Obtaining a node identifier of a blockchain node that processes the transaction data, recorded in the transaction data; The data of the transaction failures are counted according to the node identifier to obtain the number of transaction failures for each blockchain node.

6. The transaction processing method according to claim 5, characterized in that: Perform integrity check on the transaction data recorded in the current block, including: Filter the transaction data recorded in the current block according to the transaction process to obtain the transaction starting point data generated when the transaction was initiated; Obtaining a process identifier for indicating the transaction process in which the transaction starting point data resides; According to the process identifier, the transaction starting point data is matched with other transaction data recorded in the current block to determine whether there is transaction ending point data with the same process identifier as the transaction starting point data in the current block, the transaction ending point data being data generated when a transaction ends; If transaction end point data having the same process identifier as the transaction start point data exists in the current block, it is determined that the transaction data has a complete transaction process; If the transaction end point data having the same process identifier as the transaction start point data does not exist in the current block, it is determined that the transaction process of the transaction data is incomplete.

7. The transaction processing method according to claim 2, characterized in that: The availability test of each blockchain node is performed based on the transaction data recorded in the blockchain network, including: Obtain one or more historical blocks most recently linked to the blockchain; The availability of each blockchain node is checked based on the transaction data recorded in the historical block.

8. The transaction processing method according to claim 1, wherein: Transmitting the transaction request to the normal node includes: Select a target node that is currently idle from the normal nodes of the blockchain network; Establishing a data channel for data communication between the abnormal node and the target node; Based on the data channel, the transaction request is transmitted from the abnormal node to the target node.

9. The transaction processing method according to claim 8, characterized in that: Selecting a target node that is currently in an idle state from the normal nodes of the blockchain network includes: Selecting the blockchain node with the highest idleness from the blockchain network as the miner node for packaging the current block; The miner node selects a target node that is currently in an idle state from the normal nodes of the blockchain network.

10. The transaction processing method according to claim 9, characterized in that: Selecting the blockchain node with the highest idleness from the blockchain network, including: Counting the number of transactions on each blockchain node in the blockchain network according to a preset time period; Filtering the transaction counts of each blockchain node based on the transaction data recorded in a preset number of blocks that have been recently uploaded to the blockchain to obtain the recent transaction counts of each blockchain node; The blockchain node with the smallest number of recent transactions is selected as the blockchain node with the highest idleness.

11. The transaction processing method according to claim 1, wherein: When processing the behavior data stream by the background processing thread on the normal node, the method further includes: If a new transaction request is generated on the normal node, the new transaction request is processed by the foreground processing thread on the normal node to obtain a transaction processing result of the new transaction request. The foreground processing thread is a thread running concurrently with the background processing thread. The transaction processing result of the new transaction request is displayed on the interactive interface of the normal node.

12. A transaction processing device, characterized in that: include: a detection module configured to perform availability detection on each blockchain node based on transaction data recorded in the blockchain network to determine whether each blockchain node is a normal node or an abnormal node; wherein the transaction system installed on the abnormal node is marked as a faulty system, and the transaction system installed on the normal node is marked as an available system; the abnormal node is a node whose number of transaction failures and transaction failure rate both reach corresponding parameter thresholds; The processing module is configured to, when a transaction request is generated on the abnormal node, transmit the transaction request to the normal node, obtain a behavior data stream associated with the transaction request through the abnormal node, and transmit the behavior data stream to the normal node, wherein the behavior data stream includes interactive behavior data collected through the interactive interface of the abnormal node; process the behavior data stream through a background processing thread on the normal node to obtain a result data stream as response data of the behavior data stream, and transmit the result data stream to the abnormal node; and display the result data stream on the interactive interface of the abnormal node.

13. A computer-readable medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the transaction processing method according to any one of claims 1 to 11 is implemented.

14. An electronic device, characterized in that: include: processor; as well as a memory for storing executable instructions of the processor; The processor is configured to execute the transaction processing method according to any one of claims 1 to 11 by executing the executable instructions.

15. A computer program product, characterized in that The computer program product or computer program comprises computer instructions stored in a computer-readable storage medium; The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the transaction processing method described in any one of claims 1 to 11.

Citation Information

Patent Citations

  • Node processing method and device based on block chains

    CN111104282A

Cited By

  • Transaction processing method and apparatus, medium and electronic device

    WO2022257656A1