Transaction processing method, related method and device, storage medium and equipment

Abstract

The embodiment of the invention discloses a transaction processing method, a related method, a related device, a storage medium and equipment. A transaction request sent by a client is received, and generated verification information is returned according to a communication address corresponding to the transaction request; receiving a transaction data structure generated by the client according to the verification information, wherein the transaction data structure comprises a transaction signature, encrypted verification information and an object signature; performing first verification of digital signature on the transaction data structure according to the object signature and the transaction signature, and performing second verification of verification information on the transaction data structure according to the encrypted verification information to obtain a target verification result; when the target verification result indicates that the transaction data structure passes, broadcasting the transaction data structure to other nodes of the same block chain for broadcast verification to obtain a broadcast verification result; and when the broadcast verification result indicates passing, executing the corresponding transaction in the transaction data structure. Therefore, the security of transaction processing is improved through a dual verification mechanism of digital signature verification and verification information.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and specifically to a transaction processing method and related methods, devices, storage media and equipment. Background Art

[0002] With the development of blockchain technology, many transaction processing systems based on blockchain technology have emerged. Objects can realize virtual resource transfer, resource exchange and other operations based on the transaction processing system.

[0003] In related technologies, when an object needs to process a transaction through a transaction processing system, it is necessary to input the private key corresponding to the account and use the private key to authorize the transaction to be processed. For example, when transferring virtual resources, the object needs to input the private key for authorization before the virtual resource transfer can be realized in the blockchain.

[0004] However, in the related art, once the private key of the object is leaked or stolen, the thief can transfer the virtual resources of the object according to the account and private key of the object, causing the loss of the virtual resources of the object. Therefore, there is an unsafe problem in the transaction processing process in the related art. Summary of the invention

[0005] The embodiments of the present application provide a transaction processing method and related methods, devices, storage media and equipment, which can improve the security of the transaction processing process.

[0006] In a first aspect, an embodiment of the present application provides a transaction processing method, including:

[0007] Receive the transaction request sent by the client, and return the generated verification information according to the communication address corresponding to the transaction request;

[0008] Receive a transaction data structure generated by the client according to the verification information, the transaction data structure including a transaction signature generated by encryption according to the transaction-related data, encrypted verification information generated by encryption according to the verification information, and an object signature generated by encryption according to the transaction-related data, the transaction signature, and the encrypted verification information;

[0009] Performing a first verification of the digital signature of the transaction data structure according to the object signature and the transaction signature, and performing a second verification of the verification information of the transaction data structure according to the encrypted verification information, to obtain a target verification result;

[0010] When the target verification result indicates passing, the transaction data structure is broadcast to other nodes in the same blockchain for broadcast verification to obtain the broadcast verification result;

[0011] When the broadcast verification result indicates pass, the corresponding transaction in the transaction data structure is executed.

[0012] Second aspect, embodiments of the present application provide a transaction request method, including:

[0013] Generating a transaction request according to a transaction input by an object, and sending the transaction request to a target node, where the transaction request includes a target account address of the object;

[0014] Receiving verification information generated by the target node according to the transaction request and returned through a communication address associated with the target account address, and encrypting the verification information according to the node public key of the target node to generate encrypted verification information;

[0015] Generating transaction-associated data based on the target account address and the transaction, and encrypting the transaction-associated data with the object private key of the object to generate a transaction signature;

[0016] Encrypting the transaction-associated data, the transaction signature, and the encrypted verification information with the object private key to generate an object signature;

[0017] Generating a transaction data structure according to the transaction-associated data, the transaction signature, the encrypted verification information, and the object signature, and sending the transaction data structure to the target node.

[0018] Third aspect, embodiments of the present application provide a transaction processing device, including:

[0019] A first receiving module, configured to receive a transaction request sent by a client, and return generated verification information according to a communication address corresponding to the transaction request;

[0020] A second receiving module, configured to receive a transaction data structure generated by the client according to the verification information, where the transaction data structure includes a transaction signature encrypted according to transaction-associated data, encrypted verification information encrypted according to the verification information, and an object signature encrypted according to the transaction-associated data, the transaction signature, and the encrypted verification information;

[0021] A verification module, configured to perform a first verification of the digital signature of the transaction data structure according to the object signature and the transaction signature, and perform a second verification of the verification information of the transaction data structure according to the encrypted verification information, to obtain a target verification result;

[0022] A broadcast module, configured to, when the target verification result indicates passing, broadcast the transaction data structure to other nodes of the same blockchain for broadcast verification, to obtain a broadcast verification result;

[0023] An execution module, configured to execute the corresponding transaction in the transaction data structure when the broadcast verification result indicates passing.

[0024] In some embodiments, the transaction data structure consists of a sub-transaction data structure and an object signature, and the sub-transaction data structure includes transaction-associated data, a transaction signature, and encrypted verification information; the verification module includes:

[0025] The first determination sub-module is used to determine the object public key corresponding to the transaction data structure;

[0026] The first verification sub-module is used to verify the object signature according to the object public key to obtain the first target verification result, and the first target verification result is used to verify the integrity of the sub-transaction data structure;

[0027] The second verification sub-module is used to verify the transaction signature according to the object public key to obtain the second target verification result, and the second target verification result is used to verify the integrity of the transaction associated data;

[0028] The first decryption sub-module is used to decrypt the encrypted verification information to obtain the decrypted verification information when both the first target verification result and the second target verification result indicate passing;

[0029] The third verification sub-module is used to verify the decrypted verification information according to the verification information to obtain the target verification result.

[0030] In some embodiments, the first decryption sub-module is further used for:

[0031] When both the first target verification result and the second target verification result indicate passing, determine the node private key corresponding to the current node;

[0032] Decrypt the encrypted verification information according to the node private key to obtain the decrypted verification information, wherein the encrypted verification information is generated by the client according to the node public key of the current node.

[0033] In some embodiments, the broadcast module includes:

[0034] The first signature sub-module is used to encrypt the sub-transaction data structure according to the node private key of the current node to generate a node signature;

[0035] The first generation sub-module is used to replace the object signature in the transaction data structure with the node signature to obtain the target transaction data structure;

[0036] The first broadcast sub-module is used to broadcast the target transaction data structure to other nodes of the same blockchain for broadcast verification to obtain the broadcast verification result.

[0037] In some embodiments, the first broadcast sub-module is further used for:

[0038] Broadcast the target transaction data structure to other nodes of the same blockchain, so that other nodes can determine the node signature, transaction signature, object public key, and node public key corresponding to the target transaction data structure, verify the node signature based on the node public key to obtain a third target verification result, and verify the transaction signature based on the object public key to obtain a fourth target verification result, and obtain a broadcast verification result based on the third target verification result and the fourth target verification result;

[0039] Among them, the third target verification result is used to verify the authenticity of the node corresponding to the target transaction data structure, and the fourth target verification result is used to verify the integrity of the transaction-related data.

[0040] In some embodiments, before broadcasting the transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result, the broadcast module is further configured to:

[0041] Obtain the elapsed duration since the verification information was generated;

[0042] When the elapsed duration does not exceed a preset elapsed duration, broadcast the transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result.

[0043] In some embodiments, the first receiving module is further configured to:

[0044] Generate verification information according to the transaction request and determine the target account address carried in the transaction request;

[0045] Query the communication address associated with the target account address in the ledger of the blockchain and return the verification information through the communication address.

[0046] In some embodiments, the transaction processing device further includes a third receiving module, a first verification module, a second verification module, and a registration module, where:

[0047] The third receiving module is configured to receive the registration data structure sent by the client before receiving the transaction request sent by the client and returning the generated verification information according to the communication address corresponding to the transaction request. The registration data structure includes a registration transaction signature encrypted according to the registration-related data, an encrypted communication address encrypted according to the communication address, and a registration object signature encrypted according to the registration-related data, the registration transaction signature, and the encrypted communication address;

[0048] The first verification module is configured to verify the digital signature of the registration data structure according to the registration object signature and the registration transaction signature, and verify the communication address of the registration data structure according to the encrypted communication address to obtain a registration verification result;

[0049] A second verification module, configured to broadcast the registration data structure to other nodes for registration verification when the registration verification result indicates passing, so as to obtain a target registration verification result;

[0050] A registration module, configured to perform registration of the corresponding target account address and communication address in the registration data structure when the target registration verification result indicates passing.

[0051] In some embodiments, the first verification module is further configured to:

[0052] Before verifying the digital signature of the registration data structure according to the registration object signature and the registration transaction signature, and verifying the communication address of the registration data structure according to the encrypted communication address to obtain a registration verification result, determine the target fields in the registration associated data, where the target fields at least include the fields corresponding to the transfer account address;

[0053] Determine whether the target fields are empty. When the target fields are empty, verify the digital signature of the registration data structure according to the registration object signature and the registration transaction signature, and verify the communication address of the registration data structure according to the encrypted communication address to obtain a registration verification result.

[0054] In some embodiments, the registration data structure consists of a sub-registration data structure and a registration object signature, and the sub-registration data structure includes registration associated data, a registration transaction signature, and an encrypted communication address; the first verification module further includes:

[0055] A second determination sub-module, configured to determine the object public key corresponding to the registration data structure;

[0056] A first registration verification sub-module, configured to verify the registration object signature according to the object public key to obtain a first registration verification result, where the first registration verification result is used to verify the integrity of the sub-registration data structure;

[0057] A second registration verification sub-module, configured to verify the registration transaction signature according to the object public key to obtain a second registration verification result, where the second registration verification result is used to verify the integrity of the registration associated data;

[0058] A second decryption sub-module, configured to decrypt the encrypted communication address with the node private key of the current node to obtain a decrypted communication address when both the first registration verification result and the second registration verification result indicate passing;

[0059] A third registration verification sub-module, configured to verify the authenticity of the decrypted communication address to obtain a registration verification result.

[0060] In some embodiments, the second verification module further includes:

[0061] A second signature sub-module, configured to encrypt and generate a registration node signature for the sub-registration data structure according to the node private key of the current node;

[0062] A second generation sub-module, configured to replace the registration object signature in the registration data structure with the registration node signature to obtain a target registration data structure;

[0063] A second broadcast sub-module, configured to broadcast the target registration data structure to other nodes for registration verification to obtain a target registration verification result.

[0064] In some embodiments, the registration module is further configured to:

[0065] Concatenate the strings corresponding to the object public key, the encrypted communication address, and the node public key of the current node in sequence to obtain an associated address corresponding to the target account address;

[0066] Write the associated address into the ledger corresponding to the blockchain.

[0067] In a fourth aspect, an embodiment of the present application provides a transaction request device, including:

[0068] A sending module, configured to generate a transaction request according to a transaction input by an object and send the transaction request to a target node, where the transaction request includes the target account address of the object;

[0069] An encryption module, configured to receive verification information generated by the target node according to the transaction request and returned through a communication address associated with the target account address, and encrypt the verification information according to the node public key of the target node to generate encrypted verification information;

[0070] A first signature module, configured to generate transaction-associated data based on the target account address and the transaction, and encrypt the transaction-associated data with the object private key of the object to generate a transaction signature;

[0071] A second signature module, configured to encrypt the transaction-associated data, the transaction signature, and the encrypted verification information with the object private key to generate an object signature;

[0072] A generation module, configured to generate a transaction data structure according to the transaction-associated data, the transaction signature, the encrypted verification information, and the object signature, and send the transaction data structure to the target node.

[0073] In some embodiments, the transaction request device further includes:

[0074] A registration request module, configured to generate registration-associated data before generating a transaction request according to a transaction input by an object and sending the transaction request to a target node, and encrypt the registration-associated data with the object private key of the object to generate a registration transaction signature;

[0075] A communication encryption module for encrypting the communication address of an object according to the node public key of a target node to obtain an encrypted communication address;

[0076] A registration object signature module for generating a registration object signature by encrypting registration association data, a registration transaction signature, and an encrypted communication address according to an object private key;

[0077] A registration data generation module for generating a registration data structure according to registration association data, a registration transaction signature, an encrypted communication address, and a registration object signature;

[0078] A registration data sending module for sending the registration data structure to the target node to request registration of the corresponding target account address and communication address in the registration data structure.

[0079] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium storing multiple instructions adapted to be loaded by a processor to execute the transaction processing method or the transaction request method provided by an embodiment of the present application.

[0080] In a sixth aspect, an embodiment of the present application provides a computer device including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the transaction processing method or the transaction request method provided by an embodiment of the present application is implemented.

[0081] In a seventh aspect, an embodiment of the present application provides a computer program product including a computer program or instruction. When the computer program or instruction is executed by a processor, the transaction processing method or the transaction request method provided by an embodiment of the present application is implemented.

[0082] In the embodiments of the present application, a transaction request sent by a client is received, and verification information generated is returned according to the communication address corresponding to the transaction request; a transaction data structure generated by the client according to the verification information is received, and the transaction data structure includes a transaction signature encrypted according to transaction-related data, an encrypted verification information encrypted according to the verification information, and an object signature encrypted according to the transaction-related data, the transaction signature, and the encrypted verification information; a first verification of digital signature of the transaction data structure is performed according to the object signature and the transaction signature, and a second verification of the verification information of the transaction data structure is performed according to the encrypted verification information to obtain a target verification result; when the target verification result indicates passing, the transaction data structure is broadcast to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result; when the broadcast verification result indicates passing, the corresponding transaction in the transaction data structure is executed. In the embodiments of the present application, the current node can return the generated verification information according to the communication address corresponding to the transaction request, and then receive the transaction data structure returned by the client according to the verification information. The digital signature of the transaction data structure is verified through the object signature and the transaction signature in the transaction data structure. After the digital signature verification passes, the verification information in the transaction data structure is also verified. When the verification information passes, it is confirmed that the transaction data structure is generated by the object's own operation. Finally, the transaction corresponding to the transaction data structure is executed. In this way, through the dual verification of digital signature verification and verification information verification, it can be ensured that the transaction data structure is legally authorized by the object and is complete, thereby ensuring the security in the transaction processing process.

[0083] Other features and advantages of the present application will be described in the subsequent description, and, in part, will be obvious from the description, or will be understood by implementing the present application. The objectives and other advantages of the present application can be realized and obtained through the structures specifically pointed out in the description, the claims, and the drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0084] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative efforts.

[0085] Figure 1A is a schematic diagram of the data sharing system provided by the embodiments of the present application;

[0086] Figure 1B is a schematic diagram of the composition structure of the blockchain provided by the embodiments of the present application;

[0087] Figure 1CIt is a schematic diagram of the process of generating a new block in the blockchain provided by an embodiment of the present application;

[0088] Figure 2 It is a schematic diagram of the scenario of transaction processing in the blockchain provided by an embodiment of the present application;

[0089] Figure 3 It is a schematic diagram of the overall process of the transaction processing method provided by an embodiment of the present application;

[0090] Figure 4 It is a schematic diagram of the transaction data structure provided by an embodiment of the present application;

[0091] Figure 5 It is a schematic diagram of the process of determining the target verification result provided by an embodiment of the present application;

[0092] Figure 6 It is a schematic diagram of the process of determining the broadcast verification result provided by an embodiment of the present application;

[0093] Figure 7 It is a schematic diagram of the target transaction data structure provided by an embodiment of the present application;

[0094] Figure 8 It is a schematic diagram of the process of verifying the target transaction data structure provided by an embodiment of the present application;

[0095] Figure 9 It is a schematic diagram of the process of transaction processing provided by an embodiment of the present application;

[0096] Figure 10 It is a schematic diagram of the interaction of transaction processing provided by an embodiment of the present application;

[0097] Figure 11 It is a flowchart of the registration process in the transaction processing provided by an embodiment of the present application;

[0098] Figure 12 It is a schematic diagram of the registration data structure provided by an embodiment of the present application;

[0099] Figure 13 It is a schematic diagram of the process of verifying the registration data structure provided by an embodiment of the present application;

[0100] Figure 14 It is a schematic diagram of the target registration data structure provided by an embodiment of the present application;

[0101] Figure 15 It is a schematic diagram of the process of the registration process provided by an embodiment of the present application;

[0102] Figure 16 It is a schematic diagram of the interaction of the registration process provided by an embodiment of the present application;

[0103] Figure 17It is another process schematic diagram of the transaction processing method provided by the embodiments of the present application;

[0104] Figure 18 It is the overall process schematic diagram of the transaction request method provided by the embodiments of the present application;

[0105] Figure 19 It is another process schematic diagram of the transaction request method provided by the embodiments of the present application;

[0106] Figure 20 It is the structural schematic diagram of the transaction processing device provided by the embodiments of the present application;

[0107] Figure 21 It is the structural schematic diagram of the transaction request device provided by the embodiments of the present application;

[0108] Figure 22 It is the structural schematic diagram of the server provided by the embodiments of the present application;

[0109] Figure 23 It is the structural schematic diagram of the computer device provided by the embodiments of the present application. Detailed implementation manners

[0110] In order to enable those skilled in the art to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative efforts belong to the scope protected by the present application.

[0111] It can be understood that in the specific implementation manners of the present application, when it comes to data related to the account address, communication address, etc. of an object, when the above embodiments of the present application are applied to specific products or technologies, user permission or consent needs to be obtained, and the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards.

[0112] In addition, when the embodiments of the present application need to obtain data related to the account address, communication address, etc., a separate permission or separate consent for the data related to the account address, communication address, etc. will be obtained through pop-up windows or by jumping to a confirmation page. After clearly obtaining the separate permission or separate consent for the data related to the account address, communication address, etc., the necessary data related to the account address, communication address, etc. for the normal operation of the embodiments of the present application will be obtained.

[0113] It should be noted that in some processes described in the specification, claims, and the above-mentioned drawings, there are multiple steps that appear in a specific order. However, it should be clearly understood that these steps can be executed not in the order in which they appear herein or in parallel. The step numbers are only used to distinguish different steps, and the numbers themselves do not represent any execution order. In addition, descriptions such as "first", "second", or "target" in this article are used to distinguish similar objects and do not necessarily describe a specific order or sequence.

[0114] Before further elaborating on the embodiments of the present application, the nouns and terms involved in the embodiments of the present application are described. The nouns and terms involved in the embodiments of the present application are applicable to the following explanations:

[0115] Two-factor authentication (2FA, 2Factor Authentication): Two-factor authentication is a secure password verification method. Different from traditional password verification, since traditional password verification consists of a set of static information, such as characters, images, gestures, etc., it is easily obtained and relatively insecure. Two-factor authentication is based on natural variables such as time, historical length, physical objects (credit cards, SMS mobile phones, tokens, fingerprints), etc., combined with a certain encryption algorithm to combine a set of dynamic passwords, which are generally refreshed every 60 seconds. It is not easily obtained and cracked and is relatively secure.

[0116] One-time password (OTP, One-time-Password): Also known as a dynamic password or a single-use password, it refers to a password that can only be used once on a calculator system or other digital device, and its validity period is only for one login session or transaction.

[0117] Data structure: A data structure is a way for a computer to store and organize data. A data structure refers to a collection of data elements that have one or more specific relationships with each other.

[0118] Blockchain: It is a chain composed of one block after another. Each block stores certain information, and they are connected into a chain in the order of their respective generation times.

[0119] Block: A block has a main structure, including a block header and a block body. The data in the block header and block body is block data. The block header stores the hash value of the previous block, the hash value of the current block, a nonce, a timestamp, and a Merkle root. The block body contains a set of transactions or other data records, and these records are encoded and placed together, and are also calculated in the hash value of the entire block. The size of the block body can vary according to needs and is usually limited by a certain size.

[0120] Node: refers to each participant or network node in the blockchain network.

[0121] Nonce: A one-time random number automatically generated by the system, used to solve difficult mathematical problems. A new random number is generated each time a problem is solved.

[0122] Ledger: refers to the data structure of the blockchain, a record state of all transaction information, similar to bookkeeping, so it is called "ledger".

[0123] Peer-to-Peer (P2P): refers to a single node that can interact directly with other nodes without the need for intermediate nodes or intermediaries.

[0124] Remote Procedure Call (RPC): allows calling remote services just like calling local services. During the whole process, RPC hides the specific communication details. RPC is a communication method that can be implemented through HTTP or through a set of protocols implemented by sockets.

[0125] Digital Signature: Also known as a public key digital signature, it is a digital string that can only be generated by the sender of the data and cannot be forged by others. This digital string is also a valid proof of the authenticity of the information sent by the sender of the data.

[0126] Asymmetric encryption: also known as public key encryption, refers to an encryption method consisting of a corresponding pair of unique keys (i.e., a public key and a private key).

[0127] With the development of blockchain technology, many transaction processing systems based on blockchain technology have emerged. Objects can realize virtual resource transfer, resource exchange and other operations based on the transaction processing system.

[0128] In the related technology, when an object needs to process a transaction through a transaction system, it is necessary to enter the object's account and the private key corresponding to the account, and use the private key to authorize the transaction to be processed. For example, when transferring virtual resources, the object needs to enter its account and private key for authorization before the virtual resource transfer can be performed.

[0129] However, in the related art, once the private key of the object is leaked or stolen, the thief can transfer the virtual resources of the object according to the account and private key of the object, causing the loss of the virtual resources of the object. Therefore, there is an unsafe problem in the transaction processing process in the related art.

[0130] In order to solve the above problems, embodiments of the present application propose a solution for implementing blockchain transaction processing based on two-factor authentication. The transactions to be processed are double-authenticated through the object private key and dynamic authentication information, which is different from the solution in the related art that only uses the private key to authenticate the transactions to be processed. The authentication method in the present application can greatly improve the security of blockchain transaction processing.

[0131] The following will describe in detail the transaction processing method and related methods, devices, storage media, and devices provided by the embodiments of the present application.

[0132] Before describing the transaction processing method provided by the embodiments of the present application, please refer to Figures 1A to 1C , Figures 1A to 1C which describes the entire data sharing system. The transaction processing method provided by the embodiments of the present application can be executed based on the data sharing system.

[0133] Refer to Figure 1A , which is a schematic diagram of the data sharing system provided by the embodiments of the present application. The data sharing system 100 refers to a system for data sharing between nodes. The data sharing system may include multiple nodes 101, and the multiple nodes 101 may refer to each client in the data sharing system. Each node 101 can receive input information during normal operation and maintain the shared data in the data sharing system based on the received input information. To ensure information interconnection within the data sharing system, there may be information connections between each node in the data sharing system, and information can be transmitted between nodes through the above information connections. For example, when any node in the data sharing system receives input information, other nodes in the data sharing system obtain the input information according to the consensus algorithm and store the input information as data in the shared data, so that the data stored on all nodes in the data sharing system is consistent.

[0134] For each node in the data sharing system, it has a corresponding node identifier, and each node in the data sharing system can store the node identifiers of other nodes in the data sharing system, so as to broadcast the generated block to other nodes in the data sharing system according to the node identifiers of other nodes later. Each node can maintain a node identifier list as shown in the following table, and store the node name and node identifier in the node identifier list correspondingly. Among them, the node identifier can be an IP (Internet Protocol) address and any other information that can be used to identify the node. Only the IP address is used as an example in Table 1 for illustration.

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

[0136] Each node in the data sharing system stores an identical blockchain. The blockchain consists of multiple blocks.

[0137] See Figure 1B , Figure 1B which is a schematic diagram of the composition structure of the blockchain provided by an embodiment of the present application. The blockchain consists of multiple blocks. The genesis block includes a block header and a block body. The block header stores an input information feature value, a version number, a timestamp, and a difficulty value. The block body stores the input information. The next block of the genesis block uses the genesis block as the parent block. The next block also includes a block header and a block body. The block header stores the input information feature value of the current block, the block header feature value of the parent block, the version number, the timestamp, and the difficulty value, and so on. This ensures that the block data stored in each block in the blockchain is associated with the block data stored in the parent block, guaranteeing the security of the input information in the block.

[0138] See Figure 1C , Figure 1C which is a schematic diagram of the process of generating a new block in the blockchain provided by an embodiment of the present application. When generating each block in the blockchain, the node where the blockchain is located, upon receiving the input information, verifies the 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. The eigenvalue calculation is performed multiple times so that the calculated eigenvalue can satisfy the following formula:

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

[0140] 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 feature value 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 certain period of time and is determined again after exceeding the fixed time period; x is a random number; TARGET is the eigenvalue threshold, which can be determined based on nbits.

[0141] In this way, when a random number that satisfies the above formula is calculated, the information can be stored correspondingly to generate a block header and a block body, thus obtaining the current block. Subsequently, the node where the blockchain is located sends the newly generated block to other nodes in the data sharing system it belongs to according to the node identifiers of other nodes in the data sharing system. Other nodes verify the newly generated block and add the newly generated block to the blockchain they store after the verification is completed.

[0142] Please continue to refer to Figure 2 , Figure 2 which is a schematic diagram of the scenario of transaction processing in the blockchain provided by the embodiments of the present application.

[0143] As Figure 2 shown, when an object needs to process some transactions, for example, when the object needs to transfer virtual resources, it can communicate with the current node through the client, so as to realize the processing of the corresponding transaction. For example, the object can input the corresponding transaction on the client. The client generates a transaction request according to the transaction and sends the transaction request to the corresponding node. This node is a node in the blockchain, and this node can be the server corresponding to the client. In the following text, in order to distinguish this node in the blockchain from other nodes in the blockchain, this node is called the current node.

[0144] After receiving the transaction request, the current node generates verification information according to the transaction request, determines the target account address of the object, then queries the communication address corresponding to the target account address in the ledger of the stored blockchain according to the target account address, and then sends the verification information to the object through the communication address.

[0145] After receiving the verification information, the object inputs the verification information into the client. The client encrypts the verification information to generate encrypted verification information, and at the same time generates a transaction data structure according to the transaction input by the object and the encrypted verification information. The transaction data structure includes transaction-related data, transaction signatures, encrypted verification information, and object signatures. Then the client sends the transaction data structure to the current node through the way of remote procedure call communication. Among them, the transaction corresponding to the transaction data structure can be the transfer of virtual resources.

[0146] The current node can verify the transaction data structure. For example, it can verify the object signature through the object public key, and can also verify the transaction signature through the object public key. When the object signature and the transaction signature pass the verification, it is also necessary to decrypt and verify the encrypted verification information. When the verification passes, the current node can set the node signature of the current node for the transaction data structure. For example, replace the object signature in the transaction data structure with the node signature to obtain the target transaction data structure. Finally, the target transaction data structure is sent to other nodes in the same blockchain, for example, the target transaction is broadcast to other nodes through the peer-to-peer method. AsFigure 2 As shown, other nodes include nodes such as Node 1, Node 2, Node 3, Node 4, etc. The current node in the blockchain can perform peer-to-peer communication with any other node.

[0147] After receiving the target transaction data structure, other nodes can verify the node signature of the target transaction data structure through the node public key of the current node, and verify the transaction signature of the target transaction data structure through the object public key of the object. When both the node signature and the transaction signature are verified, other nodes reach a consensus on the transaction corresponding to the target transaction data structure.

[0148] After other nodes reach a consensus on the transaction, the current node can execute the transaction corresponding to the transaction data structure, such as implementing virtual resource transfer. The current node can write the transaction data structure into the corresponding target block, such as writing it into a block that is not full of storage, or writing it into a newly created block, thereby obtaining an updated block, and finally sending the updated block to other nodes. Other nodes verify the updated block. When other nodes pass the verification of the updated block, the current node can receive the message that the verification of the updated block sent by other nodes has passed.

[0149] The current node adds the updated block to the blockchain it stores, and then the transaction is completed. Each node in the blockchain will write the execution result corresponding to the transaction into the ledger corresponding to the blockchain.

[0150] As can be seen from the above, in the embodiment of the present application, during the transaction processing, the current node in the blockchain will use a two-factor verification method to verify the transaction to be processed, that is, the current node uses digital signature verification and verification information verification, thereby ensuring the security during the transaction processing.

[0151] To understand the transaction processing method provided by the embodiment of the present application in more detail, please refer to Figure 3 , Figure 3 is the overall flowchart of the transaction processing method provided by the embodiment of the present application. This transaction processing method can improve the security during the transaction processing.

[0152] The execution subject of this transaction processing method can be a server or a terminal. The terminal includes but is not limited to mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle-mounted terminals, aircraft, etc. The server can be a high-performance computer in a network platform, a cluster of multiple high-performance computers, a part (such as a virtual machine) allocated from a high-performance computer, a combination of parts (such as virtual machines) allocated from multiple high-performance computers, etc. The embodiment of the present application can be applied to various scenarios, including but not limited to virtual resource transfer, resource exchange, etc.

[0153] It can be understood that in the following description of the transaction processing method, it can be described from the perspective of a certain node in the blockchain, and this node is referred to as the current node.

[0154] As Figure 3 shown, the transaction processing method may include the following steps:

[0155] Step 210: Receive a transaction request sent by a client, and return the generated verification information according to the communication address corresponding to the transaction request;

[0156] Step 220: Receive the transaction data structure generated by the client according to the verification information. The transaction data structure includes a transaction signature encrypted according to transaction-related data, an encrypted verification information encrypted according to the verification information, and an object signature encrypted according to the transaction-related data, the transaction signature, and the encrypted verification information;

[0157] Step 230: Perform a first verification of the digital signature on the transaction data structure according to the object signature and the transaction signature, and perform a second verification of the verification information on the transaction data structure according to the encrypted verification information to obtain a target verification result;

[0158] Step 240: When the target verification result indicates passing, broadcast the transaction data structure to other nodes in the same blockchain for broadcast verification to obtain a broadcast verification result;

[0159] Step 250: When the broadcast verification result indicates passing, execute the transaction corresponding to the transaction data structure.

[0160] The following will describe steps 210 to 250 in detail.

[0161] In step 210, receive a transaction request sent by a client, and return the generated verification information according to the communication address corresponding to the transaction request.

[0162] It can be understood that when an object needs to perform transaction processing, a corresponding transaction can be input on the client. The client generates a transaction request according to this transaction, and then sends this transaction request to the current node. For example, when an object needs to perform virtual resource transfer, the transaction will be input on the client, and then the client generates a transaction request according to this transaction, and then sends this transaction request to the current node.

[0163] The current node can generate verification information according to a transaction request and return the verification information according to the communication address of the object. The verification information is used to verify whether the transaction request is created by the object himself / herself. The communication address includes, but is not limited to, a terminal number, an email address, and a software account address. The verification information can be a string, such as a string of pure numbers, a string of pure English, or a string composed of a mixture of numbers and English. The verification information is randomly generated, that is, each time a transaction request is received, a random verification information needs to be generated.

[0164] In some embodiments, returning the generated verification information according to the communication address corresponding to the transaction request may include the following steps:

[0165] (1.1) Generate verification information according to the transaction request and determine the target account address carried in the transaction request;

[0166] (1.2) Query the communication address associated with the target account address in the ledger of the blockchain and return the verification information through the communication address.

[0167] After the current node receives a transaction request, the current node can generate verification information according to the transaction request. The verification information can be a verification code or a one-time password.

[0168] The transaction request contains the target account address of the object. The current node only needs to read the transaction request to determine the target account address therein. Then, through the target account address, find the associated address of the target account address in the stored ledger of the blockchain, and then find the encrypted communication address corresponding to the target account address from the associated address. Decrypt the encrypted communication address with the node private key to obtain the communication address corresponding to the target account address.

[0169] It should be noted that the object has an object private key and an object public key. The object private key is privately kept by the object, while the object public key can be broadcast to any node of the blockchain. The current node has a node private key and a node public key. The node private key is only separately kept by the current node, while the node public key can be sent to the client and other nodes of the same blockchain. That is to say, in the following text of this application, when the object public key and the node public key are used, it can be understood that the object public key and the node public key have been obtained in advance, or the object public key and the node public key can be read from the interactive data. Among them, the above object private key and object public key are generated by an asymmetric encryption algorithm, and the node private key and node public key are generated by an asymmetric encryption algorithm.

[0170] The current node sends the verification information to the client through the communication address. At the same time, the current node also caches the verification information for use in subsequent verification processes. The verification information is random and is generated in a random manner, which can prevent the verification information from being cracked by following a single rule. The verification information has a certain character length. For example, the character length is composed of 10 characters. When the character length reaches a certain length, the probability of the verification information being cracked is lower. The verification information has a time limit. For example, the time limit is 60 seconds. When the verification information starts to be timed from generation and the duration reaches the preset duration, the verification information is recognized as an invalid verification information and cannot be used for verification.

[0171] It can be understood that the verification information can only be sent to the communication address specified by the target account address to ensure the security of the verification information transmission, thereby ensuring the security in the subsequent transaction processing process.

[0172] In some embodiments, after the current node generates and returns the verification information, the current node can determine whether the client continues to request to obtain the verification information. When the client continues to request to obtain the verification information, it detects the acquisition frequency of the client's request to obtain the verification information within the preset duration. If the acquisition frequency is higher than the preset acquisition frequency, the current node can stop sending the verification information to the client. This can prevent the current node from being subject to external malicious requests and protect the security of the current node.

[0173] As can be seen from the above, by generating verification information through a transaction request and then verifying the transaction through the verification information, the security in the transaction processing process can be improved.

[0174] In step 220, receive the transaction data structure generated by the client according to the verification information. The transaction data structure includes a transaction signature encrypted according to the transaction-related data, an encrypted verification information encrypted according to the verification information, and an object signature encrypted according to the transaction-related data, the transaction signature, and the encrypted verification information.

[0175] It can be understood that after the object views the verification information, it can input the verification information into the client, and the client can generate a transaction data structure according to the transaction, the verification information, etc. The transaction data structure contains various different types of data.

[0176] To better illustrate the embodiments of the present application, please refer to Figure 4 , Figure 4 which is a schematic diagram of the transaction data structure provided by the embodiments of the present application.

[0177] As Figure 4As shown, the transaction data structure includes various types of data. The transaction data structure consists of a sub - transaction data structure and an object signature. The sub - transaction data structure contains transaction - related data, a transaction signature, and encryption verification information.

[0178] Among them, the transaction - related data consists of fields corresponding to the target account address, the transfer - in account address, the amount, the random number, and the object public key respectively. The target account address can also be understood as the transfer - out account address, and virtual resources can be transferred out from the target account address. Virtual resources can be transferred in through the transfer - in account address. The amount is the amount of virtual resources to be transferred. The random number is a randomly generated number, which can be used to prevent replay attacks and enhance the security of transaction - related data. The object public key is the public key opened by the object to the current node, and the object also has an object private key that it alone holds.

[0179] The transaction signature is generated by the client encrypting the transaction - related data with the object private key, that is, using an asymmetric encryption algorithm to calculate the hash value of the transaction - related data, and then using the object private key to encrypt the hash value to generate the transaction signature. The transaction signature is used by the current node to verify the integrity of the transaction - related data.

[0180] In some embodiments, the object public key may not be included in the transaction - related data. For example, the client can set the object public key in the transaction signature. When the current node reads the transaction signature, the object public key can be obtained from the transaction signature.

[0181] The encryption verification information is generated by the client encrypting the verification information based on the node public key of the current node. By encrypting the verification information with the node public key of the current node, the obtained encryption verification information can only be read after being decrypted by the current node using the node private key, thus avoiding the risk of verification information leakage.

[0182] The object signature is generated by the client encrypting the sub - transaction data structure with the object private key. The object signature can be used to verify the integrity of the sub - transaction data structure, thereby realizing the verification of the integrity of the encryption verification information.

[0183] In some embodiments, the current node can read the transaction data structure to read different types of data therein.

[0184] In step 230, a first verification of the digital signature of the transaction data structure is performed according to the object signature and the transaction signature, and a second verification of the verification information of the transaction data structure is performed according to the encryption verification information to obtain a target verification result.

[0185] Among them, during the process of transaction processing, the first verification of the digital signature of the transaction data structure can be performed first according to the object signature and the transaction signature. For example, through the object signature verification, the integrity of the sub-transaction data structure in the transaction data structure can be verified. Through the transaction signature, the integrity of the transaction association data in the sub-transaction data structure can be verified, so as to ensure that the transaction data structure is complete and not tampered with. After the verification passes, the second verification of the verification information is performed on the transaction data structure according to the encrypted verification information. Verifying the transaction data structure through the verification information can ensure that the transaction data structure is generated by the operation of the object itself. Thus, the dual-factor verification of the transaction data structure is realized to improve the security during the transaction processing process.

[0186] Please refer to Figure 5 , Figure 5 which is a schematic flowchart of the process for determining the target verification result provided by an embodiment of the present application. In some embodiments, the first verification of the digital signature of the transaction data structure according to the object signature and the transaction signature, and the second verification of the verification information of the transaction data structure according to the encrypted verification information to obtain the target verification result may include the following steps:

[0187] Step 310: Determine the object public key corresponding to the transaction data structure;

[0188] Step 320: Verify the object signature according to the object public key to obtain a first target verification result, where the first target verification result is used to verify the integrity of the sub-transaction data structure;

[0189] Step 330: Verify the transaction signature according to the object public key to obtain a second target verification result, where the second target verification result is used to verify the integrity of the transaction association data;

[0190] Step 340: When both the first target verification result and the second target verification result indicate passing, decrypt the encrypted verification information to obtain the decrypted verification information;

[0191] Step 350: Verify the decrypted verification information according to the verification information to obtain the target verification result.

[0192] The following will describe steps 310 to 350 in detail.

[0193] In step 310, the object public key corresponding to the transaction data structure is determined.

[0194] In some embodiments, before using the object public key to verify the transaction signature and the object signature, the client has sent the object public key to the current node, and the current node can directly obtain the object public key locally.

[0195] In some embodiments, the object public key is included in the transaction associated data corresponding to the transaction data structure. The current node can read the transaction associated data to obtain the object public key in the transaction associated data.

[0196] In step 320, the object signature is verified according to the object public key to obtain a first target verification result, and the first target verification result is used to verify the integrity of the sub-transaction data structure.

[0197] In some embodiments, if the object signature is generated by encrypting the sub-transaction data structure with the RSA encryption algorithm and the object private key, the current node can decrypt the object signature through the RSA encryption algorithm and the object public key to obtain the corresponding hash value A1. The current node can also calculate the hash value A2 of the sub-transaction data structure through a hash function. By comparing the hash value A1 and the hash value A2, the first target verification result can be obtained. The hash value is also the hash value. When the first target verification result is verification passed, it indicates that the sub-transaction data structure is complete.

[0198] If the hash value A1 is equal to the hash value A2, it indicates that the object signature verification is passed. If the hash value A1 is not equal to the hash value A2, it indicates that the object signature verification fails. By verifying the object signature, the integrity of the sub-transaction data structure can be verified, and thus the integrity of the encrypted verification information in the sub-transaction data structure can be indirectly verified.

[0199] It should be noted that if the object signature is generated by other encryption algorithms, the current node also needs to use the corresponding encryption algorithm for decryption when verifying the object signature. For example, the ECDSA (Elliptic Curve DSA) algorithm can be used, that is, the Elliptic Curve Digital Signature Algorithm (DSA, Digital Signature Algorithm). It is a variant of the digital signature algorithm that applies the elliptic curve encryption algorithm. The principle of the elliptic curve algorithm is very complex, but it has good public key algorithm characteristics, and the private key cannot be obtained reversely through the public key. Another example is that the SM2 algorithm can be used. The full name of the SM2 algorithm is the SM2 elliptic curve public key cryptography algorithm (SM is the pinyin abbreviation of commercial cryptography), which is a kind of cryptography ECC (Elliptic Curve Cryptography) based on "elliptic curve". SM2 is an asymmetric encryption. Since this algorithm is based on ECC, its signature speed and key generation speed are faster than RSA. The security strength of ECC 256 bits (SM2 uses one of ECC 256 bits) is higher than that of RSA2048 bits, but the operation speed is faster than RSA.

[0200] It can be understood that in the embodiments of the present application, the object public key and the object private key are obtained through an asymmetric encryption algorithm, which can ensure the security during information transmission. That is, the current node cannot obtain the object private key through the object public key, and the current node can use the object public key to verify whether the transaction data structure sent by the client is complete.

[0201] In step 330, verify the transaction signature according to the object public key to obtain a second target verification result, and the second target verification result is used to verify the integrity of the transaction associated data.

[0202] In some embodiments, if the transaction signature is generated by encrypting the transaction signature through the RSA encryption algorithm and the object private key, the current node can decrypt the transaction signature through the RSA encryption algorithm and the object public key to obtain the corresponding hash value B1. The current node can also calculate the hash value B2 of the transaction associated data through a hash function. By comparing the hash value B1 and the hash value B2, the second target verification result is obtained. When the second target verification result indicates verification passed, it means that the transaction associated data is complete.

[0203] If the hash value B1 is equal to the hash value B2, it means that the transaction signature verification passes. If the hash value B1 is not equal to the hash value B2, it means that the transaction signature verification fails. By verifying the transaction signature, the integrity of the transaction associated data can be verified.

[0204] Similarly, if the transaction signature is encrypted and generated by the client using other encryption algorithms, the current node can use the corresponding encryption algorithm for decryption.

[0205] In step 340, when both the first target verification result and the second target verification result indicate passing, decrypt the encrypted verification information to obtain the decrypted verification information.

[0206] It can be understood that when both the first target verification result and the second target verification result indicate passing, it means that both the transaction associated data and the sub-transaction data structure are complete, and the encrypted verification information is also complete. This also indirectly indicates that the transaction data structure is sent by the object himself / herself.

[0207] This process uses two digital signature verifications, namely object signature verification and transaction signature verification, thus improving the security verification level of the transaction data structure. Compared with the single digital signature verification in the related art, the security of the two digital signature verifications is significantly higher.

[0208] In addition, when both the first target verification result and the second target verification result indicate passing, it is also necessary to decrypt the encrypted verification information to obtain the decrypted verification information. Thereby further verifying the transaction data structure to determine whether it is generated by the object himself / herself.

[0209] In some embodiments, step 340 of decrypting the encrypted verification information to obtain the decrypted verification information may include the following steps:

[0210] (1.1) Determine the node private key corresponding to the current node;

[0211] (1.2) Decrypt the encrypted verification information according to the node private key to obtain the decrypted verification information, where the encrypted verification information is generated by the client encrypting according to the node public key of the current node.

[0212] It can be understood that the client and the current node hold each other's public keys. The client can encrypt the verification information through the node public key of the current node to generate the encrypted verification information.

[0213] When the current node decrypts the encrypted verification information, it can use the node private key to decrypt the encrypted verification information to obtain the decrypted verification information. Among them, the algorithm used in the process of the current node decrypting the encrypted verification information is the same as the algorithm used when generating the encrypted verification information.

[0214] In step 350, verify the decrypted verification information according to the verification information to obtain the target verification result.

[0215] It can be understood that the current node can compare the decrypted verification information with the verification information to obtain the target verification result. When the decrypted verification information is consistent with the verification information, the target verification result is verification passed. When the decrypted verification information is inconsistent with the verification information, the target verification result is verification failed.

[0216] For example, if the verification information is a string of verification codes, and the decrypted verification information also corresponds to a string of verification codes, the two verification codes can be directly compared to obtain the target verification result. When the two verification codes are consistent, the target verification result is verification passed. When the two verification codes are inconsistent, the target verification result is verification failed.

[0217] By using the verification information to verify the transaction data structure again, it is possible to further determine whether the transaction data is generated by the operation of the object itself, thereby further ensuring the security in the transaction processing process.

[0218] It can be seen from step 310 to step 350 that in the process of verifying the transaction data structure, digital signature verification and verification information verification are adopted in the embodiments of the present application. Digital signature verification can verify the integrity of the transaction data structure, and verification information verification can verify whether the transaction data structure is generated by the operation of the object itself. Through the two verification methods, the security in the transaction processing process can be improved.

[0219] In step 240, when the target verification result indicates passing, the transaction data structure is broadcast to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result.

[0220] When the target verification result indicates passing, it means that the transaction data structure is generated by the operation of the object itself. The current node can broadcast the transaction data structure to other nodes of the same blockchain for broadcast verification, so as to obtain a broadcast verification result.

[0221] Please refer to Figure 6 , Figure 6 is a schematic flowchart of the process for determining a broadcast verification result provided by an embodiment of the present application. In some embodiments, broadcasting the transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result includes:

[0222] Step 410: Encrypt the sub-transaction data structure with the node private key of the current node to generate a node signature;

[0223] Step 420: Replace the object signature in the transaction data structure with the node signature to obtain a target transaction data structure;

[0224] Step 430: Broadcast the target transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result.

[0225] The following will describe steps 410 to 430 in detail.

[0226] In step 410, the sub-transaction data structure is encrypted with the node private key of the current node to generate a node signature.

[0227] The current node can perform node authentication processing for the transaction corresponding to the transaction data structure, such as setting the node signature of the current node for the transaction data structure, so as to obtain a target transaction data structure.

[0228] Among them, the current node can encrypt the sub-transaction data structure with its node private key to generate a node signature. For example, the current node first calculates the digest value of the sub-transaction data structure, and this digest value can be a hash value. Then, the digest value is encrypted with the node private key to generate a node signature, and this node signature also corresponds to a value.

[0229] In step 420, the node signature is used to replace the object signature in the transaction data structure to obtain a target transaction data structure.

[0230] Please refer to Figure 7 , Figure 7It is a schematic diagram of the target transaction data structure provided by an embodiment of the present application. Among them, the transaction association data and the sub-transaction data structure have not changed. Only the current node replaces the object signature in the transaction data structure with the node signature, thereby generating the target transaction data structure.

[0231] By setting the node signature, it is beneficial for other subsequent nodes to authenticate the target transaction data structure through the node signature, thereby realizing the authentication of the transaction corresponding to the target transaction data.

[0232] In step 430, the target transaction data structure is broadcast to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result.

[0233] It can be understood that during the execution of a transaction, other nodes of the same blockchain corresponding to the current node need to reach a consensus on the transaction before the transaction can be executed. For example, other nodes can verify the target transaction data structure. When most nodes in the blockchain verify the target transaction data structure and pass, for example, when more than 80% of the nodes verify the target transaction data structure and pass, can a consensus on the transaction corresponding to the target transaction data be achieved, and the current node can execute the transaction.

[0234] Therefore, it is necessary to broadcast the target transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result.

[0235] In some embodiments, broadcasting the target transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result includes:

[0236] Broadcasting the target transaction data structure to other nodes of the same blockchain so that other nodes determine the node signature, transaction signature, object public key, and node public key corresponding to the target transaction data structure, and verify the node signature according to the node public key to obtain a third target verification result, and verify the transaction signature according to the object public key to obtain a fourth target verification result, and obtain a broadcast verification result based on the third target verification result and the fourth target verification result; wherein, the third target verification result is used to verify the authenticity of the node corresponding to the target transaction data structure, and the fourth target verification result is used to verify the integrity of the transaction association data.

[0237] That is to say, other nodes can authenticate the transaction through the object signature and the node signature.

[0238] For details, please refer to Figure 8 , Figure 8 It is a schematic diagram of the process for verifying the target transaction data structure provided by an embodiment of the present application. Combining Figure 8, the following will be described from the perspective of other nodes. Other nodes can verify the target transaction data structure in the following ways:

[0239] Step 410: Determine the node signature, transaction signature, object public key, and node public key corresponding to the target transaction data structure;

[0240] Step 420: Verify the node signature according to the node public key to obtain a third target verification result, which is used to verify the authenticity of the node corresponding to the target transaction data structure;

[0241] Step 430: Verify the transaction signature according to the object public key to obtain a fourth target verification result, which is used to verify the integrity of the transaction-related data;

[0242] Step 440: Based on the third target verification result and the fourth target verification result, obtain a broadcast verification result.

[0243] The following will describe steps 410 to 440 in detail.

[0244] In step 410, determine the node signature, transaction signature, object public key, and node public key corresponding to the target transaction data structure.

[0245] It can be understood that when other nodes receive the target transaction data structure broadcast by the current node, they can also receive the node public key broadcast by the current node at the same time.

[0246] Other nodes can read the object public key, transaction signature, and node signature from the target transaction data structure.

[0247] In step 420, verify the node signature according to the node public key to obtain a third target verification result, which is used to verify the authenticity of the node corresponding to the target transaction data structure.

[0248] In some embodiments, after other nodes receive the target transaction data structure, if the node signature is generated by encrypting the sub-transaction data structure with an asymmetric encryption algorithm and the node private key, other nodes can verify the node signature with the corresponding asymmetric encryption algorithm and the node public key to obtain a third target verification result. Through the third target verification result, the integrity of the sub-transaction data structure can be verified. When the third target verification result is verification passed, it indicates that the sub-transaction data structure is complete.

[0249] For example, other nodes can decrypt the node signature through the corresponding asymmetric encryption algorithm and the node public key to obtain the corresponding hash value C1, then obtain the hash value C2 of the sub-transaction data structure, and compare the hash value C1 and the hash value C2 to obtain the third target verification result. If the hash value C1 is equal to the hash value C2, it indicates that the node signature verification passes. If the hash value C1 is not equal to the hash value C2, it indicates that the node signature verification fails.

[0250] In step 430, the transaction signature is verified according to the object public key to obtain a fourth target verification result, and the fourth target verification result is used to verify the integrity of the transaction associated data.

[0251] In some embodiments, after receiving the target transaction data structure, if the transaction signature is generated by encrypting the transaction associated data using an asymmetric encryption algorithm and the object private key, other nodes can verify the transaction signature through the corresponding asymmetric encryption algorithm and the object public key to obtain a fourth target verification result. Through the fourth target verification result, the integrity of the transaction associated data can be verified. When the fourth target verification result indicates verification passed, it means that the transaction associated data is complete.

[0252] For example, other nodes can decrypt the transaction signature through the corresponding asymmetric encryption algorithm and the object public key to obtain the corresponding hash value D1, then obtain the hash value D2 of the transaction associated data, and compare the hash value D1 and the hash value D2 to obtain a fourth target verification result. If the hash value D1 is equal to the hash value D2, it indicates that the transaction signature verification passes. If the hash value D1 is not equal to the hash value D2, it indicates that the transaction signature verification fails.

[0253] In step 440, based on the third target verification result and the fourth target verification result, a broadcast verification result is obtained.

[0254] It can be understood that when both the third target verification result and the fourth target verification result indicate passing, the obtained broadcast verification result indicates that the target transaction data structure verification passes. Other nodes reach a consensus on the transaction corresponding to the target transaction data structure.

[0255] If any one of the third target verification result and the fourth target verification result fails to pass the verification, the obtained broadcast verification result indicates that the target transaction data structure verification fails.

[0256] Other nodes can send the broadcast verification result to the current node.

[0257] As can be seen from Steps 410 to 440, during the execution of a transaction, the target transaction data structure corresponding to the transaction also requires other nodes to perform verification. Only after the verification passes can the current node execute the transaction, thereby enhancing the security during the transaction processing.

[0258] In some embodiments, before broadcasting the transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result, the duration of the verification information from its generation can also be obtained. For example, when the current node generates verification information, it will determine the generation time and then start timing from the generation time to calculate the duration of the verification information.

[0259] When the target verification result indicates passing and the duration does not exceed the preset duration, the transaction data structure is broadcast to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result. Among them, the duration not exceeding the preset duration indicates that the verification information is still valid. By setting the preset valid duration of the verification information, the security during the transaction processing can be further ensured. When the duration exceeds the preset duration, it indicates that the duration of the verification information from its generation has been a long time, and there may be a risk of verification information leakage during this process. At this time, the current node chooses not to broadcast the transaction data structure to other nodes of the same blockchain for broadcast verification to ensure the security during the transaction processing.

[0260] In Step 250, when the broadcast verification result indicates passing, the transaction corresponding to the transaction data structure is executed.

[0261] In some embodiments, when the broadcast verification result indicates passing, it means that other nodes in the blockchain reach a consensus on the transaction. At this time, the current node can execute the transaction corresponding to the transaction data structure.

[0262] Specifically, executing the transaction corresponding to the transaction data structure includes:

[0263] (1.1) Writing the transaction data structure into the target block to obtain an updated block;

[0264] (1.2) Sending the updated block to other nodes. After receiving the verification passed message of the updated block from other nodes, writing the updated block into the blockchain and writing the execution result corresponding to the transaction into the ledger corresponding to the blockchain.

[0265] For example, the current node can determine the block that is not full locally as the target block, or create a new block and determine it as the template block. Then write the transaction data structure into the target block to obtain an updated block.

[0266] The current node sends the updated block to other nodes, enabling other nodes to verify the updated block. Other nodes can verify the node signature corresponding to the updated block. After successful verification, consensus is reached on the updated block. After receiving the message indicating successful verification of the updated block from other nodes, the current node can write the updated block into the blockchain and write the execution result of the transaction into the corresponding ledger of the blockchain.

[0267] For example, if the transaction is a virtual resource transfer, the transferred account address, target account address, amount, etc. can be written into the ledger of the blockchain.

[0268] As can be seen from steps 210 to 250, in the embodiment of the present application, double verification of the transaction data structure is achieved through digital signature verification and verification information verification, and then the transaction corresponding to the transaction data structure is executed, thus ensuring the security during the transaction processing.

[0269] In the embodiment of the present application, a transaction request sent by a client is received, and verification information generated is returned according to the communication address corresponding to the transaction request; a transaction data structure generated by the client according to the verification information is received. The transaction data structure includes a transaction signature encrypted according to transaction associated data, an encrypted verification information encrypted according to the verification information, and an object signature encrypted according to the transaction associated data, transaction signature, and encrypted verification information; a first verification of the digital signature of the transaction data structure is performed according to the object signature and transaction signature, and a second verification of the verification information of the transaction data structure is performed according to the encrypted verification information to obtain a target verification result; when the target verification result indicates passing, the transaction data structure is broadcast to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result; when the broadcast verification result indicates passing, the transaction corresponding to the transaction data structure is executed. In the embodiment of the present application, the current node can return the generated verification information according to the communication address corresponding to the transaction request, and then receive the transaction data structure returned by the client according to the verification information. The digital signature of the transaction data structure is verified through the object signature and transaction signature in the transaction data structure. After the digital signature verification passes, the encrypted verification information in the transaction data structure is also verified for verification information. When the verification information passes, it is confirmed that the transaction data structure is generated by the operation of the object itself. Finally, the transaction corresponding to the transaction data structure is executed. In this way, through the double verification of digital signature verification and verification information verification, it can be ensured that the transaction data structure is legally authorized by the object and is complete, thus ensuring the security during the transaction processing.

[0270] Please refer to Figure 9 , Figure 9 , which is a schematic flowchart of transaction processing provided by the embodiment of the present application. Here, the description is from the perspective of the current node.

[0271] As Figure 9 shown, after the current node receives the transaction data structure sent by the client, it is necessary to use cryptographic techniques to verify the object signature and transaction signature in the transaction data structure. Among them, the transaction data structure includes a sub-transaction data structure and an object signature, and the sub-transaction data structure includes transaction-related data, a transaction signature, and an encrypted verification information encrypted and generated by the client according to the verification information sent by the current node.

[0272] After the object signature and transaction signature are verified, the encrypted verification information is decrypted using the node private key of the current node to obtain the decrypted verification information, and then it is determined whether the decrypted verification information is the same as the verification information saved by the current node. If they are the same, the transaction data structure is verified.

[0273] The current node needs to send the transaction data structure to other nodes in the same blockchain for verification. At this time, the node private key can be used to encrypt the sub-transaction data structure to generate a node signature, and the node signature replaces the object signature to generate a target transaction data structure. Then the target transaction data structure is broadcast to other nodes. After other nodes verify the target transaction data structure, other nodes reach a consensus on the transaction corresponding to the target transaction data structure.

[0274] After the current node receives the message that other nodes have verified the target transaction data structure, it executes the transaction corresponding to the transaction data structure and writes the execution result of the transaction into the ledger of the blockchain, thus completing the transaction processing.

[0275] As can be seen from the above, double verification of the transaction data structure is achieved through digital signature verification and verification information verification, improving the security of the transaction processing process.

[0276] For the specific implementation of each of the above steps, reference can be made to the previous embodiments and will not be elaborated here.

[0277] Please refer to Figure 10 , Figure 10 which is an interaction schematic diagram of transaction processing provided by an embodiment of the present application. It involves a client, a current node, and other nodes.

[0278] When an object wants to execute a transaction, the transaction is input into the client, and the client sends a transaction request to the current node. The current node can return corresponding verification information to the client according to the transaction request. The client can generate a transaction data structure according to the verification information and the transaction, and send the transaction data structure to the current node. The current node verifies the transaction data structure, specifically verifying the object signature, transaction signature, and encrypted verification information in the transaction data structure, that is, realizing double-factor verification of digital signature verification and verification information verification.

[0279] After the current node successfully validates the target transaction data structure, it sets a node signature for the sub - transaction data structure within the transaction data structure and replaces the object signature in the transaction data structure with the node signature, thereby generating the target transaction data structure. Then, the target transaction data structure is broadcast to other nodes.

[0280] Other nodes verify the target transaction data structure and return the broadcast verification result to the current node. When the broadcast verification result indicates passing, the current node executes the transaction corresponding to the transaction data structure, writes the transaction data structure into the target block, obtains the updated block, and then broadcasts the updated block to other nodes.

[0281] After other nodes verify the updated block and reach a consensus, they return the block verification result to the current node. When the block verification result indicates passing, the current node writes the updated block into the blockchain and writes the execution result of the transaction into the ledger of the block. The current node sends a transaction processing result to the client, thereby informing that the transaction processing of the object is successful.

[0282] For the specific implementation of each of the above steps, reference can be made to the previous embodiments, which will not be elaborated here.

[0283] Please refer to Figure 11 , Figure 11 which is the registration flow chart in the transaction processing provided by the embodiments of this application.

[0284] In some embodiments, before receiving the transaction request sent by the client and returning the generated verification information according to the communication address corresponding to the transaction request, it also involves the registration of the target account address and communication address of the object. Only when the target account address and communication address of the object are registered can the transaction processing be requested.

[0285] Specifically, as Figure 11 shown, before receiving the transaction request sent by the client and returning the generated verification information according to the communication address corresponding to the transaction request, it further includes:

[0286] Step 610: Receive the registration data structure sent by the client. The registration data structure includes a registration transaction signature encrypted according to the registration association data, an encrypted communication address encrypted according to the communication address, and a registration object signature encrypted according to the registration association data, registration transaction signature, and encrypted communication address;

[0287] Step 620: Verify the digital signature of the registration data structure based on the registration object signature and registration transaction signature, and verify the communication address of the registration data structure based on the encrypted communication address to obtain the registration verification result;

[0288] Step 630: When the registration verification result indicates passing, broadcast the registration data structure to other nodes for registration verification to obtain a target registration verification result;

[0289] Step 640: When the target registration verification result indicates passing, implement the registration of the corresponding target account address and communication address in the registration data structure.

[0290] Steps 610 to 640 will be described in detail below.

[0291] In step 610, receive the registration data structure sent by the client. The registration data structure includes a registration transaction signature encrypted based on registration association data, an encrypted communication address encrypted based on the communication address, and a registration object signature encrypted based on the registration association data, the registration transaction signature, and the encrypted communication address.

[0292] It can be understood that when an object needs to register its target account address and communication address, the client will generate a registration data structure. For example, the client can generate a registration data structure based on the target account address that the object needs to register and the communication address of the object. Among them, the registration data structure consists of a sub-registration data structure and a registration object signature, and the sub-registration data structure includes registration association data, a registration transaction signature, and an encrypted communication address.

[0293] It should be noted that the object has an object private key and an object public key. The object private key is privately held by the object, while the object public key can be broadcast to any node of the blockchain. The current node has a node private key and a node public key. The node private key is only held by the current node alone, while the node public key can be sent to the client and other nodes of the same blockchain. That is to say, in the following text of this application, when the object public key and the node public key are used, it can be understood that the object public key and the node public key have been obtained in advance, or the object public key and the node public key can be read from the interactive data. Among them, the above object private key and object public key are generated by an asymmetric encryption algorithm, and the node private key and node public key are generated by an asymmetric encryption algorithm.

[0294] Please refer to Figure 12 , Figure 12 which is a schematic diagram of the registration data structure provided by the embodiment of this application.

[0295] As Figure 12 shown, the registration data structure includes various types of data. The registration data structure consists of a sub-registration data structure and a registration object signature. The sub-registration data structure contains registration association data, a registration transaction signature, and an encrypted communication address.

[0296] Among them, the registered associated data consists of fields corresponding to the target account address, transfer-in account address, amount, random number, and object public key respectively. Since the registered associated data is actually used for registration, the fields corresponding to the transfer-in account address and the amount in it can both be empty. Therefore, what actually exists in the registered associated data are the target account address, random number, and object public key.

[0297] The target account address is the account address to be registered. The random number can be used to prevent replay attacks and enhance the security of the registered associated data. The object public key is the public key opened by the object to the current node, and the object also has an object private key that it alone holds.

[0298] The registration transaction signature is generated by the client encrypting the registered associated data with the object private key. The registration transaction signature is used for the current node to verify the integrity of the registered associated data.

[0299] In some embodiments, the object public key may not be included in the registered associated data either. For example, the client can set the object public key in the registration transaction signature, and when the current node reads the registration transaction signature, it can obtain the object public key from the registration transaction signature.

[0300] The encrypted communication address is generated by the client encrypting the object's communication address based on the node public key of the current node.

[0301] The registration object signature is generated by the client encrypting the sub-registration data structure with the object private key. The registration object signature can be used to verify the integrity of the sub-registration data structure, thereby realizing the verification of the integrity of the encrypted communication address.

[0302] The current node can read the registration data structure to read different types of data in it.

[0303] In some embodiments, before verifying the registration data structure, the target fields in the registered associated data can also be determined. The target fields at least include the fields corresponding to the transfer-in account address, and the target fields can also include other fields. For example, the target fields also include the fields corresponding to the amount. If the target fields are empty, the registration data structure is verified.

[0304] It can be understood that when the target fields are empty, the current node can determine that the registration transaction data structure is used for registering the target account.

[0305] In step 620, the digital signature of the registration data structure is verified according to the registration object signature and the registration transaction signature, and the communication address of the registration data structure is verified according to the encrypted communication address to obtain the registration verification result.

[0306] In some embodiments, the current node may verify the digital signature of the registration data structure through the registration object signature and the registration transaction signature. After the verification passes, it decrypts the encrypted communication address to obtain the decrypted communication address, and then verifies the authenticity of the decrypted communication address to obtain the registration verification result.

[0307] Please refer to Figure 13 , Figure 13 which is a schematic flowchart of the verification of the registration data structure provided by the embodiments of the present application.

[0308] In some embodiments, verifying the digital signature of the registration data structure according to the registration object signature and the registration transaction signature, and verifying the communication address of the registration data structure according to the encrypted communication address to obtain the registration verification result may include the following steps:

[0309] Step 710: Determine the object public key corresponding to the registration data structure;

[0310] Step 720: Verify the registration object signature according to the object public key to obtain the first registration verification result, and the first registration verification result is used to verify the integrity of the sub-registration data structure;

[0311] Step 730: Verify the registration transaction signature according to the object public key to obtain the second registration verification result, and the second registration verification result is used to verify the integrity of the registration associated data;

[0312] Step 740: When both the first registration verification result and the second registration verification result indicate passing, decrypt the encrypted communication address through the node private key of the current node to obtain the decrypted communication address;

[0313] Step 750: Verify the authenticity of the decrypted communication address to obtain the registration verification result.

[0314] Steps 710 to 750 will be described in detail below.

[0315] In step 710, determine the object public key corresponding to the registration data structure.

[0316] The current node may read the registration associated data in the registration data structure, and then read the object public key of the object in the registration associated data.

[0317] In step 720, verify the registration object signature according to the object public key to obtain the first registration verification result, and the first registration verification result is used to verify the integrity of the sub-registration data structure.

[0318] In some embodiments, if the registration object signature is generated by encrypting the sub-registration data structure using an asymmetric encryption algorithm and the object private key, the current node can decrypt the registration object signature using the asymmetric encryption algorithm and the object public key to obtain the corresponding hash value E1. The current node can also calculate the hash value E2 of the sub-registration data structure using a hash function. By comparing the hash value E1 and the hash value E2, the first registration verification result is obtained. The hash value is also known as the hash value. When the first registration verification result indicates verification passed, it means that the sub-registration data structure is complete.

[0319] If the hash value E1 is equal to the hash value E2, it means that the registration object signature verification has passed. If the hash value A1 is not equal to the hash value A2, it means that the registration object signature verification has failed. By verifying the registration object signature, the integrity of the sub-registration data structure can be verified, thereby indirectly verifying the integrity of the encrypted communication information in the sub-registration data structure.

[0320] In step 730, the registration transaction signature is verified according to the object public key to obtain the second registration verification result, and the second registration verification result is used to verify the integrity of the registration associated data.

[0321] In some embodiments, if the registration transaction signature is generated by encrypting the registration transaction signature using an asymmetric encryption algorithm and the object private key, the current node can decrypt the registration transaction signature using the asymmetric encryption algorithm and the object public key to obtain the corresponding hash value F1. The current node can also calculate the hash value F2 of the registration associated data using a hash function. By comparing the hash value F1 and the hash value F2, the second registration verification result is obtained. When the second registration verification result indicates verification passed, it means that the registration associated data is complete.

[0322] If the hash value F1 is equal to the hash value F2, it means that the registration transaction signature verification has passed. If the hash value F1 is not equal to the hash value F2, it means that the registration transaction signature verification has failed. By verifying the registration transaction signature, the integrity of the registration associated data can be verified.

[0323] In step 740, when both the first registration verification result and the second registration verification result indicate passing, the encrypted communication address is decrypted using the node private key of the current node to obtain the decrypted communication address.

[0324] It can be understood that when both the first registration verification result and the second registration verification result indicate passing, it means that both the registration associated data and the sub-registration data structure are complete, and the encrypted communication address is also complete, thereby verifying the security of the registration data structure.

[0325] This process adopts two digital signature verifications, namely the registration object signature verification and the registration transaction signature verification, thus improving the security verification level of the registration data structure. Compared with the single digital signature verification in the related technology, the security of the two digital signature verifications is significantly higher.

[0326] In addition, when both the first registration verification result and the second registration verification result indicate passing, it is also necessary to decrypt the encrypted communication address to obtain the decrypted communication address. This decrypted communication address is actually the communication address provided by the object. Because in the above verification of the registration object signature, the integrity of the sub-registration data structure has been proven, that is, the integrity of the encrypted communication address in the sub-transaction data structure has been proven, indicating that the encrypted communication address has not changed.

[0327] Specifically, for example, the current node can use the node private key to decrypt the encrypted communication address to obtain the decrypted communication address. Among them, the encrypted communication address is generated by the client encrypting the object's communication address according to the node public key of the current node.

[0328] In step 750, the authenticity of the decrypted communication address is verified to obtain the registration verification result.

[0329] After obtaining the communication address, the current node also needs to verify the authenticity of the communication address. For example, verify whether the communication address is a real and available communication address. The current node can send a communication address authenticity inquiry request to the operator. If the operator replies that the communication address is a real and available address, it is determined that the decrypted communication address can be used for registration, thereby obtaining the registration verification result. At this time, the registration verification result indicates that the decrypted communication address verification passes. On the contrary, if the decrypted communication address is not a real and available communication address, the registration verification result indicates that the decrypted communication address verification fails.

[0330] It should be noted that for the authenticity verification of the decrypted communication address, it can also be verified by other methods.

[0331] It can be seen from step 710 to step 750 that through the digital signature verification of the registration object signature and the registration transaction signature, the security of the registration data structure can be determined. Then, through the communication address verification of the encrypted communication address, the authenticity of the encrypted communication address can be determined. Thus, the security in the registration process is achieved through the verification of two aspects.

[0332] In step 630, when the registration verification result indicates passing, the registration data structure is broadcast to other nodes for registration verification to obtain the target registration verification result.

[0333] When the registration verification result indicates passing, it means that the registration data structure is safe and can be registered. The current node can set a registration node signature for the sub-registration data structure in the registration data structure. For example, the sub-registration data structure is encrypted with the node private key to generate a registration node signature, and then the registration node signature replaces the registration object signature in the registration data structure, thereby obtaining the target registration data structure. Then, the target registration data structure is broadcast to other nodes for registration verification.

[0334] Please refer to Figure 14 , Figure 14 which is a schematic diagram of the target registration data structure provided by the embodiments of the present application. The target registration data structure consists of a sub-registration data structure and a registration node signature. The sub-registration data structure includes registration associated data, a registration transaction signature, and an encrypted communication address. That is to say, compared with the registration data structure, the target registration data structure only replaces the registration object signature.

[0335] In some embodiments, after other nodes receive the target registration data structure, other nodes can determine the object public key, node public key, registration node signature, and registration transaction signature corresponding to the target registration data structure. Other nodes can verify the registration node signature through the node public key to obtain a third registration verification result, which is used to verify the authenticity of the node corresponding to the target registration data structure. Other nodes can verify the registration transaction signature through the object public key to obtain a fourth registration verification result, which is used to verify the integrity of the registration associated data in the target registration data structure. Other nodes obtain the target registration verification result based on the third registration verification result and the fourth registration verification result. When both the third registration verification result and the fourth registration verification result indicate passing the verification, the target registration verification result indicates that the target registration data structure passes the verification. When any one of the third registration verification result and the fourth registration verification result does not indicate passing the verification, the target registration verification result indicates that the target registration data structure fails the verification.

[0336] The current node can receive the target registration verification result sent by other verification nodes.

[0337] In step 640, when the target registration verification result indicates passing, the registration of the corresponding target account address and communication address in the registration data structure is realized.

[0338] It can be understood that when the target registration verification result indicates passing, the current node can perform the registration of the target account address and communication address. For example, write the registration association data into a block to obtain a registration block, and then send the registration block to other nodes. After other nodes verify the registration block and reach a consensus, the current node can write the registration block into the blockchain, thereby realizing the registration of the target account address and communication address.

[0339] The current node can also write the target account address and encrypted communication address of the object into the ledger of the blockchain.

[0340] In some embodiments, implementing the registration of the corresponding target account address and communication address in the registration data structure includes:

[0341] (1.1) Concatenate the strings corresponding to the object public key, encrypted communication address, and the node public key of the current node in sequence to obtain the associated address corresponding to the target account address;

[0342] (1.2) Write the associated address into the corresponding ledger of the blockchain.

[0343] Among them, the current node can obtain the strings corresponding to the object public key, encrypted communication address, and node public key respectively, and then concatenate the strings corresponding to the object public key, encrypted communication address, and the node public key of the current node in sequence to obtain the associated address corresponding to the target account address. This associated address can be stored in the ledger of the blockchain in the form of key - value. In this way, when the object needs to execute a transaction later, the current node can directly query the encrypted communication address of the object in the ledger of the blockchain, and then decrypt the encrypted communication address to obtain the communication address of the object.

[0344] In steps 610 to 640, when the object wants to register its target account address and communication address, by performing digital signature verification on the registration object signature and registration transaction signature of the registration data structure, and at the same time performing communication address verification on the encrypted communication address, the security during the registration process is ensured in two aspects.

[0345] Please refer to Figure 15 , Figure 15 which is the flow diagram of the registration process provided by the embodiments of this application.

[0346] When the current node receives the registration data structure, it can read the registration data structure. When the target field in the registration data structure is empty, it starts to execute the registration process. Then extract the target account address from the registration data structure. If there is no registration information of the target account address in the current node, the subsequent registration of the target registration address can be performed.

[0347] The current node uses cryptographic techniques to verify the registration transaction signature and the registration object signature in the registration data structure. When both the registration transaction signature and the registration object signature are verified successfully, it is also necessary to decrypt the encrypted communication address to obtain the decrypted communication address, and then verify the authenticity of the decrypted communication address to obtain the registration verification result.

[0348] If the registration verification result indicates passing, the current node uses the node private key to encrypt the sub-registration data structure in the registration data structure to generate a registration node signature. Then, the registration node signature replaces the registration object signature in the registration data structure to obtain the target registration data structure, and the target registration data structure is broadcast to other nodes. Other nodes can verify the target registration data structure, generate a target registration verification result, and send the target registration verification result to the current node. When the target verification result indicates passing, other nodes reach a consensus on the registration request, and the current node can register the target account address and communication address and write the target account address and communication address into the blockchain ledger.

[0349] As can be seen from the above, through digital signature verification and communication address verification of the registration data structure, double verification is achieved, thereby determining the security of the registration data structure and ensuring the security during the registration process.

[0350] For the specific implementation of each of the above steps, reference can be made to the previous embodiments, which will not be elaborated here.

[0351] Please refer to Figure 16 , Figure 16 which is an interaction schematic diagram of the registration process provided by the embodiments of the present application. It includes a client, a current node, and other nodes.

[0352] When an object needs to register an account, the target account address and communication address to be registered can be input on the client. The client generates a registration data structure based on the target account address and communication address, and then sends the registration data structure to the current node.

[0353] The current node will verify the registration data structure, such as performing digital verification on the registration object signature and the registration transaction signature in the registration data structure. When the verification passes, it performs communication address verification on the encrypted communication address in the registration data structure to obtain the registration verification result.

[0354] When the registration verification result indicates passing, the current node uses the node private key to encrypt the sub-registration data structure in the registration data structure to generate a registration node signature. Then, the registration node signature replaces the registration object signature in the registration data structure to obtain the target registration data structure, and the target registration data structure is broadcast to other nodes.

[0355] Other nodes can verify the target registration data structure, generate a target registration verification result, and send the target registration verification result to the current node. When the target registration verification result indicates passing, the current node then executes the verification of the target account address and communication address, and sends the registration result to the client.

[0356] For the specific implementation of each of the above steps, reference can be made to the previous embodiments, which will not be elaborated here.

[0357] The detailed process of the transaction processing method provided by the embodiments of this application.

[0358] Please refer to Figure 17 , Figure 17 , which is another schematic flowchart of the transaction processing method provided by the embodiments of this application. The transaction processing method may further include the following steps:

[0359] Step 801: Receive the registration data structure sent by the client. The registration data structure includes a registration transaction signature encrypted according to registration association data, an encrypted communication address encrypted according to the communication address, and a registration object signature encrypted according to the registration association data, the registration transaction signature, and the encrypted communication address;

[0360] Step 802: Determine the object public key corresponding to the registration data structure, verify the registration object signature according to the object public key, and obtain a first registration verification result. The first registration verification result is used to verify the integrity of the sub-registration data structure;

[0361] Step 803: Verify the registration transaction signature according to the object public key, and obtain a second registration verification result. The second registration verification result is used to verify the integrity of the registration association data;

[0362] Step 804: When both the first registration verification result and the second registration verification result indicate passing, decrypt the encrypted communication address with the node private key of the current node to obtain the decrypted communication address, and verify the authenticity of the decrypted communication address to obtain a registration verification result;

[0363] Step 805: When the registration verification result indicates passing, broadcast the registration data structure to other nodes for registration verification to obtain a target registration verification result;

[0364] Step 806: When the target registration verification result indicates passing, implement the registration of the target account address and communication address corresponding to the registration data structure;

[0365] Step 807: Receive the transaction request sent by the client, and return the generated verification information according to the communication address corresponding to the transaction request;

[0366] Step 808: Receive the transaction data structure generated by the client based on the verification information. The transaction data structure includes a transaction signature encrypted based on the transaction associated data, an encrypted verification information encrypted based on the verification information, and an object signature encrypted based on the transaction associated data, the transaction signature, and the encrypted verification information.

[0367] Step 809: Determine the object public key corresponding to the transaction data structure, verify the object signature based on the object public key, and obtain a first target verification result, which is used to verify the integrity of the sub-transaction data structure.

[0368] Step 810: Verify the transaction signature based on the object public key to obtain a second target verification result, which is used to verify the integrity of the transaction associated data.

[0369] Step 811: When both the first target verification result and the second target verification result indicate passing, decrypt the encrypted verification information to obtain the decrypted verification information, and verify the decrypted verification information based on the verification information to obtain a target verification result.

[0370] Step 812: When the target verification result indicates passing, broadcast the transaction data structure to other nodes in the same blockchain for broadcast verification to obtain a broadcast verification result.

[0371] Step 813: When the broadcast verification result indicates passing, execute the transaction corresponding to the transaction data structure.

[0372] This embodiment describes the entire process from registration to transaction execution. The related aspects of the above steps have been described in detail in the previous embodiments and will not be elaborated here.

[0373] The execution process from the perspective of the client in the embodiments of this application.

[0374] In some embodiments, the process of transaction processing can also be described from the perspective of the client. Please continue to refer to Figure 18 , Figure 18 which is the overall flow diagram of the transaction request method provided by the embodiments of this application. The transaction request method may include the following steps:

[0375] Step 910: Generate a transaction request based on the transaction input by the object and send the transaction request to the target node. The transaction request includes the target account address of the object.

[0376] Step 920: Receive the verification information generated by the target node based on the transaction request and returned through the communication address associated with the target account address, and encrypt the verification information based on the node public key of the target node to generate encrypted verification information.

[0377] Step 930: Generate transaction - related data based on the target account address and the transaction, and encrypt the transaction - related data with the object's private key to generate a transaction signature.

[0378] Step 940: Encrypt the transaction - related data, the transaction signature, and the encryption verification information with the object's private key to generate an object signature.

[0379] Step 950: Generate a transaction data structure based on the transaction - related data, the transaction signature, the encryption verification information, and the object signature, and send the transaction data structure to the target node.

[0380] The following will describe steps 910 to 950 in detail.

[0381] In step 910, generate a transaction request according to the transaction input by the object, and send the transaction request to the target node. The transaction request includes the target account address of the object.

[0382] When the object needs to execute a transaction, it can input the corresponding transaction on the client. The client generates a transaction request according to the input transaction and then sends the transaction request to the target node. The transaction request also includes the target account address of the object. It can also include the amount, the transfer account address, etc.

[0383] It should be noted that the target node is the current node in the corresponding embodiment of the transaction processing method described above.

[0384] In step 920, receive the verification information returned by the target node according to the transaction request and through the communication address associated with the target account address, and encrypt the verification information with the public key of the target node to generate encrypted verification information.

[0385] After receiving the transaction request, the target node generates verification information and returns the verification information through the communication address associated with the target account address. What is also returned can also include the public key of the target node.

[0386] The client can encrypt the verification information with the public key of the target node to generate encrypted verification information. This enables the encrypted verification information to be decrypted only with the private key of the target node, thus preventing the verification information from being stolen and ensuring the security of the verification information.

[0387] In step 930, generate transaction - related data based on the target account address and the transaction, and encrypt the transaction - related data with the object's private key to generate a transaction signature.

[0388] The client can generate transaction - related data based on the target account address and the transaction. For example, the transaction - related data includes the target account address, the transfer - in account address, the amount, the random number, the object public key, etc. The client can encrypt the transaction - related data with the object's private key to generate a transaction signature. For example, first calculate the hash value corresponding to the transaction - related data, and then encrypt the hash value with the object's private key to generate the object signature.

[0389] The transaction signature is used to verify the integrity of the transaction - related data.

[0390] In step 940, an object signature is generated by encrypting the transaction - related data, the transaction signature, and the encryption verification information with the object's private key.

[0391] Then the client can generate an object signature by encrypting the transaction - related data, the transaction signature, and the encryption verification information with the object's private key. For example, first calculate the hash value corresponding to the transaction - related data, the transaction signature, and the encryption verification information, and then encrypt the hash value with the object's private key to generate the object signature.

[0392] The object signature is used to verify the integrity of the transaction - related data, the transaction signature, and the encryption verification information.

[0393] In step 950, a transaction data structure is generated based on the transaction - related data, the transaction signature, the encryption verification information, and the object signature, and the transaction data structure is sent to the target node.

[0394] That is to say, the transaction data structure contains the transaction - related data, the transaction signature, the encryption verification information, and the object signature, and then the transaction data structure is sent to the target node. Subsequently, the target node can verify the transaction data structure.

[0395] In some embodiments, after the target node verifies the transaction data structure, the transaction corresponding to the transaction data structure can be executed, and then the execution result is returned to the client.

[0396] It can be seen from step 910 to step 950 that by setting the transaction signature, the object signature for the transaction data structure, and encrypting the verification information, it can prevent the transaction data structure from being intercepted and tampered with, ensure the security of the transaction data structure, and thus ensure the security of subsequent transaction processing.

[0397] Please refer to Figure 19 , Figure 19 which is another schematic flowchart of the transaction request method provided by the embodiment of the present application.

[0398] Before generating a transaction request according to the transaction input by the object and sending the transaction request to the target node, where the transaction request includes the target account address of the object, it is also necessary to implement the registration of the target account address and the communication address of the object.

[0399] Before generating a transaction request based on the object input transaction and sending the transaction request to the target node, the following steps are further included:

[0400] Step 1010: Generate registration associated data, and encrypt the registration associated data with the object's private key to generate a registration transaction signature;

[0401] Step 1020: Encrypt the communication address of the object with the public key of the target node to obtain an encrypted communication address;

[0402] Step 1030: Encrypt the registration associated data, the registration transaction signature, and the encrypted communication address with the object's private key to generate a registration object signature;

[0403] Step 1040: Generate a registration data structure based on the registration associated data, the registration transaction signature, the encrypted communication address, and the registration object signature;

[0404] Step 1050: Send the registration data structure to the target node to request the registration of the corresponding target account address and communication address in the registration data structure.

[0405] The following will describe steps 1010 to 1050 in detail.

[0406] In step 1010, registration associated data is generated, and the registration associated data is encrypted with the object's private key to generate a registration transaction signature.

[0407] The object inputs the target account address and communication address of the object at the client, and then the client can generate registration associated data according to the target account address, and then encrypt the registration associated data with the object's private key to generate a registration transaction signature. For example, first calculate the hash value corresponding to the registration associated data, and then encrypt the hash value with the object's private key to generate a registration transaction signature.

[0408] The registration transaction signature is used to verify the integrity of the registration associated data.

[0409] In step 1020, the communication address of the object is encrypted with the public key of the target node to obtain an encrypted communication address.

[0410] The encrypted communication address obtained by encrypting the communication address with the public key of the node can only be decrypted with the private key of the target node to read the communication address, thus preventing the communication address from being read by other devices.

[0411] In step 1030, the registration associated data, the registration transaction signature, and the encrypted communication address are encrypted with the object's private key to generate a registration object signature.

[0412] Among them, it is possible to calculate. For example, first calculate the hash values of the registration association data, the registration transaction signature, and the encrypted communication address, and then encrypt the hash value with the object private key to generate the registration object signature.

[0413] The registration object signature is used to verify the integrity of the registration association data, the registration transaction signature, and the encrypted communication address.

[0414] In step 1040, a registration data structure is generated based on the registration association data, the registration transaction signature, the encrypted communication address, and the registration object signature.

[0415] Among them, the registration data structure includes the registration association data, the registration transaction signature, the encrypted communication address, and the registration object signature. Through the registration data structure, these data can be sent to the target node at one time.

[0416] In step 1050, the registration data structure is sent to the target node to request the registration of the corresponding target account address and communication address in the registration data structure.

[0417] The client sends the registration data structure to the target node to request the registration of the corresponding target account address and communication address in the registration data structure. The target node verifies the registration data structure. After the verification passes, the target node saves the target account address and communication address of the object and returns the registration result to the client at the same time.

[0418] It can be seen from step 1010 to step 1050 that by setting the registration transaction signature, the registration object signature for the registration data structure, and encrypting the communication address, the security of the registration data structure is ensured, thus ensuring the security of the subsequent registration process.

[0419] The description of the virtual device and hardware provided in the embodiments of the present application.

[0420] Referring to Figure 20 , Figure 20 is the structural schematic diagram of the transaction processing device provided in the embodiments of the present application. The meanings of the nouns are the same as those in the above transaction processing method, and the specific implementation details can refer to the description in the method embodiments.

[0421] In the embodiments of the present application, the term "module" or "unit" refers to a computer program with a predetermined function or a part of a computer program, and works together with other related parts to achieve a predetermined goal, and can be fully or partially implemented by using software, hardware (such as a processing circuit or a memory), or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be a part of the overall module or unit that includes the function of the module or unit.

[0422] As Figure 20 shown, the transaction processing device 2000 includes:

[0423] A first receiving module 2010, configured to receive a transaction request sent by a client and return generated verification information according to the communication address corresponding to the transaction request;

[0424] A second receiving module 2020, configured to receive a transaction data structure generated by the client according to the verification information, where the transaction data structure includes a transaction signature encrypted according to transaction-related data, an encrypted verification information encrypted according to the verification information, and an object signature encrypted according to the transaction-related data, the transaction signature, and the encrypted verification information;

[0425] A verification module 2030, configured to perform a first verification of the digital signature of the transaction data structure according to the object signature and the transaction signature, and a second verification of the verification information of the transaction data structure according to the encrypted verification information, to obtain a target verification result;

[0426] A broadcast module 2040, configured to, when the target verification result indicates passing, broadcast the transaction data structure to other nodes of the same blockchain for broadcast verification, to obtain a broadcast verification result;

[0427] An execution module 2050, configured to execute the corresponding transaction in the transaction data structure when the broadcast verification result indicates passing.

[0428] In some embodiments, the transaction data structure is composed of a sub-transaction data structure and an object signature, and the sub-transaction data structure includes transaction-related data, a transaction signature, and encrypted verification information; the verification module 2030 further includes:

[0429] A first determining sub-module, configured to determine the object public key corresponding to the transaction data structure;

[0430] A first verification sub-module, configured to verify the object signature according to the object public key to obtain a first target verification result, where the first target verification result is used to verify the integrity of the sub-transaction data structure;

[0431] A second verification sub-module, configured to verify the transaction signature according to the object public key to obtain a second target verification result, where the second target verification result is used to verify the integrity of the transaction-related data;

[0432] A first decryption sub-module, configured to decrypt the encrypted verification information to obtain decrypted verification information when both the first target verification result and the second target verification result indicate passing;

[0433] A third verification sub-module, configured to verify the decrypted verification information according to the verification information to obtain a target verification result.

[0434] In some embodiments, the first decryption sub-module is further configured to:

[0435] When both the first target verification result and the second target verification result indicate passing, determine the node private key corresponding to the current node;

[0436] Decrypt the encrypted verification information according to the node private key to obtain the decrypted verification information, where the encrypted verification information is generated by the client according to the node public key of the current node.

[0437] In some embodiments, the broadcast module 2040 further includes:

[0438] The first signature sub-module is configured to encrypt the sub-transaction data structure according to the node private key of the current node to generate a node signature;

[0439] The first generation sub-module is configured to replace the object signature in the transaction data structure with the node signature to obtain a target transaction data structure;

[0440] The first broadcast sub-module is configured to broadcast the target transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result.

[0441] In some embodiments, the first broadcast sub-module is further configured to:

[0442] Broadcast the target transaction data structure to other nodes of the same blockchain, so that other nodes determine the node signature, transaction signature, object public key, and node public key corresponding to the target transaction data structure, verify the node signature according to the node public key to obtain a third target verification result, and verify the transaction signature according to the object public key to obtain a fourth target verification result, and obtain a broadcast verification result based on the third target verification result and the fourth target verification result;

[0443] Wherein, the third target verification result is used to verify the authenticity of the node corresponding to the target transaction data structure, and the fourth target verification result is used to verify the integrity of the transaction-associated data.

[0444] In some embodiments, before broadcasting the transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result, the broadcast module 2040 is further configured to:

[0445] Obtain the elapsed duration calculated from the generation of the verification information;

[0446] When the elapsed duration does not exceed a preset elapsed duration, broadcast the transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result.

[0447] In some embodiments, the first receiving module 2010 is further configured to:

[0448] Generate verification information according to the transaction request, and determine the target account address carried in the transaction request;

[0449] Query the communication address associated with the target account address in the blockchain ledger, and return the verification information through the communication address.

[0450] In some embodiments, the transaction processing device further includes a third receiving module, a first verification module, a second verification module, and a registration module, where:

[0451] The third receiving module is configured to receive the transaction request sent by the client, and before returning the generated verification information according to the communication address corresponding to the transaction request, receive the registration data structure sent by the client. The registration data structure includes a registration transaction signature encrypted according to the registration association data, an encrypted communication address encrypted according to the communication address, and a registration object signature encrypted according to the registration association data, the registration transaction signature, and the encrypted communication address;

[0452] The first verification module is configured to verify the digital signature of the registration data structure according to the registration object signature and the registration transaction signature, and verify the communication address of the registration data structure according to the encrypted communication address, to obtain a registration verification result;

[0453] The second verification module is configured to, when the registration verification result indicates passing, broadcast the registration data structure to other nodes for registration verification, to obtain a target registration verification result;

[0454] The registration module is configured to, when the target registration verification result indicates passing, implement the registration of the corresponding target account address and communication address in the registration data structure.

[0455] In some embodiments, the first verification module is further configured to:

[0456] Before verifying the digital signature of the registration data structure according to the registration object signature and the registration transaction signature, and verifying the communication address of the registration data structure according to the encrypted communication address, to obtain a registration verification result, determine the target fields in the registration association data, and the target fields at least include the fields corresponding to the transfer account address;

[0457] Determine whether the target fields are empty. When the target fields are empty, verify the digital signature of the registration data structure according to the registration object signature and the registration transaction signature, and verify the communication address of the registration data structure according to the encrypted communication address, to obtain a registration verification result.

[0458] In some embodiments, the registration data structure consists of a sub-registration data structure and a registration object signature. The sub-registration data structure includes registration associated data, a registration transaction signature, and an encrypted communication address; The first verification module further includes:

[0459] A second determination sub-module, configured to determine the object public key corresponding to the registration data structure;

[0460] A first registration verification sub-module, configured to verify the registration object signature according to the object public key to obtain a first registration verification result, and the first registration verification result is used to verify the integrity of the sub-registration data structure;

[0461] A second registration verification sub-module, configured to verify the registration transaction signature according to the object public key to obtain a second registration verification result, and the second registration verification result is used to verify the integrity of the registration associated data;

[0462] A second decryption sub-module, configured to decrypt the encrypted communication address with the node private key of the current node when both the first registration verification result and the second registration verification result indicate passing, to obtain a decrypted communication address;

[0463] A third registration verification sub-module, configured to perform authenticity verification on the decrypted communication address to obtain a registration verification result.

[0464] In some embodiments, the second verification module further includes:

[0465] A second signature sub-module, configured to encrypt the sub-registration data structure with the node private key of the current node to generate a registration node signature;

[0466] A second generation sub-module, configured to replace the registration object signature in the registration data structure with the registration node signature to obtain a target registration data structure;

[0467] A second broadcast sub-module, configured to broadcast the target registration data structure to other nodes for registration verification to obtain a target registration verification result.

[0468] In some embodiments, the registration module is further configured to:

[0469] Concatenate the strings corresponding to the object public key, the encrypted communication address, and the node public key of the current node in sequence to obtain an associated address corresponding to the target account address;

[0470] Write the associated address into the ledger corresponding to the blockchain.

[0471] In an embodiment of the present application, a verification message is generated and returned according to the communication address corresponding to the transaction request by receiving the transaction request sent by the client; the transaction data structure generated by the client according to the verification message is received, and the transaction data structure includes a transaction signature encrypted according to transaction-associated data, an encrypted verification message encrypted according to the verification message, and an object signature encrypted according to the transaction-associated data, the transaction signature, and the encrypted verification message; a first verification of the digital signature of the transaction data structure is performed according to the object signature and the transaction signature, and a second verification of the verification message of the transaction data structure is performed according to the encrypted verification message to obtain a target verification result; when the target verification result indicates passing, the transaction data structure is broadcast to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result; when the broadcast verification result indicates passing, the transaction corresponding to the transaction data structure is executed. In an embodiment of the present application, the current node can return the generated verification message according to the communication address corresponding to the transaction request, and then receive the transaction data structure returned by the client according to the verification message. The digital signature of the transaction data structure is verified through the object signature and the transaction signature in the transaction data structure. After the digital signature verification passes, the verification message of the encrypted verification message in the transaction data structure is also verified. When the verification message passes, it is confirmed that the transaction data structure is generated by the object's own operation. Finally, the transaction corresponding to the transaction data structure is executed. In this way, through the double verification of digital signature verification and verification message verification, it can be ensured that the transaction data structure is legally authorized by the object and is complete, thereby ensuring the security in the transaction processing process.

[0472] Please refer to Figure 21 , Figure 21 which is a schematic structural diagram of a transaction request device provided by an embodiment of the present application.

[0473] The transaction request device 3000 includes:

[0474] A sending module 3010, configured to generate a transaction request according to a transaction input by an object and send the transaction request to a target node, where the transaction request includes a target account address of the object;

[0475] An encryption module 3020, configured to receive the verification message generated by the target node according to the transaction request and returned through the communication address associated with the target account address, and encrypt the verification message according to the node public key of the target node to generate an encrypted verification message;

[0476] A first signature module 3030, configured to generate transaction-associated data based on the target account address and the transaction, and encrypt the transaction-associated data through the object private key of the object to generate a transaction signature;

[0477] A second signature module 3040, configured to encrypt the transaction-associated data, the transaction signature, and the encrypted verification message according to the object private key to generate an object signature;

[0478] A generation module 3050, configured to generate a transaction data structure according to transaction association data, a transaction signature, encryption verification information, and an object signature, and send the transaction data structure to a target node.

[0479] In some embodiments, the transaction request device further includes a registration request module, and the registration request module is configured to:

[0480] Before generating a transaction request according to the transaction input by the object and sending the transaction request to the target node, generate registration association data, and encrypt the registration association data with the object private key of the object to generate a registration transaction signature;

[0481] Encrypt the communication address of the object with the node public key of the target node to obtain an encrypted communication address;

[0482] Encrypt the registration association data, the registration transaction signature, and the encrypted communication address with the object private key to generate a registration object signature;

[0483] Generate a registration data structure according to the registration association data, the registration transaction signature, the encrypted communication address, and the registration object signature;

[0484] Send the registration data structure to the target node to request registration of the corresponding target account address and communication address in the registration data structure.

[0485] The embodiment of the present application further provides a server, as Figure 22 shown, which shows a schematic structural diagram of the server involved in the embodiment of the present application. Specifically:

[0486] The server may include a processor 4010 with one or more processing cores, a memory 4020 with one or more computer-readable storage media, a power supply 4030, an input unit 4040, and other components. Those skilled in the art can understand that Figure 22 the server structure shown in

[0487] does not constitute a limitation on the server, and may include more or fewer components than shown in the figure, or combine certain components, or arrange different components.

[0488] The processor 4010 is the control center of the server, connecting various parts of the entire server through various interfaces and lines. By running or executing software programs and / or modules stored in the memory 4020, and by invoking the data stored in the memory 4020, it performs various functions of the server and processes data, thereby exercising overall control over the server. Optionally, the processor 4010 may include one or more processing cores; preferably, the processor 4010 may integrate an application processor and a modem processor. Among them, the application processor mainly processes the operating system, user interface, application programs, etc., and the modem processor mainly processes wireless communications. It can be understood that the above-mentioned modem processor may not be integrated into the processor 4010 either.

[0489] The memory 4020 can be used to store software programs and modules. The processor 4010 executes various functional applications and data processing by running the software programs and modules stored in the memory 4020. The memory 4020 mainly includes a program storage area and a data storage area. Among them, the program storage area can store the operating system, application programs required for at least one function (such as the sound playback function, image playback function, etc.); the data storage area can store data created according to the use of the server, etc. In addition, the memory 4020 can include high-speed random access memory, and can also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage devices. Correspondingly, the memory 4020 can also include a memory controller to provide the processor 4010 with access to the memory 4020.

[0490] The computer device also includes a power supply 4030 that powers each component. Optionally, the power supply 4030 can be logically connected to the processor 4010 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. The power supply 4030 can also include any components such as one or more DC or AC power supplies, a recharge system, a power failure detection circuit, a power converter or inverter, and a power status indicator.

[0491] The computer device may also include an input unit 4040, which can be used to receive input digital or character information, and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0492] Although not shown, the computer device may further include a display unit and the like, which will not be elaborated here. Specifically, in this embodiment, the processor 4010 in the computer device will load the executable files corresponding to the processes of one or more application programs into the memory 4020 according to the following instructions, and the processor 4010 will run the application programs stored in the memory 4020, so as to implement the various method steps provided in the foregoing embodiments, as follows:

[0493] Receive a transaction request sent by a client, and return the generated verification information according to the communication address corresponding to the transaction request;

[0494] Receive the transaction data structure generated by the client according to the verification information. The transaction data structure includes a transaction signature encrypted according to the transaction associated data, an encrypted verification information encrypted according to the verification information, and an object signature encrypted according to the transaction associated data, the transaction signature, and the encrypted verification information;

[0495] Perform a first verification of the digital signature of the transaction data structure according to the object signature and the transaction signature, and perform a second verification of the verification information of the transaction data structure according to the encrypted verification information to obtain a target verification result;

[0496] When the target verification result indicates passing, broadcast the transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result;

[0497] When the broadcast verification result indicates passing, execute the transaction corresponding to the transaction data structure.

[0498] In the above embodiments, the descriptions of the respective embodiments have their own emphases. For the parts not elaborated in a certain embodiment, reference may be made to the detailed description of the transaction processing method in the foregoing text, which will not be elaborated here.

[0499] The embodiment of the present application further provides a computer device, and this computer device may be a terminal, such as Figure 23 shown, which shows a schematic structural diagram of the terminal involved in the embodiment of the present application. Specifically:

[0500] This computer device may include a radio frequency (RF) circuit 5010, a memory 5020 including one or more computer-readable storage media, an input unit 5030, a display unit 5040, a sensor 5050, an audio circuit 5060, a wireless fidelity (WiFi) module 5070, a processor 5080 including one or more processing cores, and a power supply 5090 and other components. Those skilled in the art can understand, Figure 23The terminal structure shown does not constitute a limitation on the terminal, and may include more or fewer components than shown, or combine certain components, or have a different component arrangement. Among them:

[0501] The RF circuit 5010 can be used for receiving and transmitting information or signals during a call. Specifically, after receiving the downlink information from the base station, it is handed over to one or more processors 5080 for processing; in addition, data related to the uplink is sent to the base station. Generally, the RF circuit 5010 includes, but is not limited to, antennas, at least one amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, etc. In addition, the RF circuit 5010 can also communicate with the network and other devices via wireless communication. The wireless communication can use any communication standard or protocol, including but not limited to the Global System of Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), etc.

[0502] The memory 5020 can be used to store software programs and modules. The processor 5080 executes various functional applications and information retrieval by running the software programs and modules stored in the memory 5020. The memory 5020 mainly includes a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for at least one function (such as a sound playback function, an image playback function, etc.); the data storage area can store data created according to the use of the terminal (such as audio data, a phone book, etc.). In addition, the memory 5020 can include high-speed random access memory, and can also include non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Correspondingly, the memory 5020 can also include a memory controller to provide access to the memory 5020 by the processor 5080 and the input unit 5030.

[0503] The input unit 5030 can be used to receive input numerical or character information, and generate keyboard, mouse, joystick, optical or trackball signal inputs related to object settings and function controls. Specifically, in a specific embodiment, the input unit 5030 may include a touch-sensitive surface and other input devices. The touch-sensitive surface, also known as a touch display screen or a touchpad, can collect touch operations of an object on or near it (such as operations of the object using any suitable object or accessory such as a finger or a stylus on or near the touch-sensitive surface), and drive corresponding connection devices according to a pre-set program. Optionally, the touch-sensitive surface may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the touch orientation of the object, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it to the processor 5080, and can receive and execute the commands sent by the processor 5080. In addition, various types such as resistive, capacitive, infrared, and surface acoustic wave can be used to implement the touch-sensitive surface. In addition to the touch-sensitive surface, the input unit 5030 may also include other input devices. Specifically, the other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, joysticks, etc.

[0504] The display unit 5040 can be used to display information input by an object or information provided to the object, as well as various graphical object interfaces of the terminal. These graphical object interfaces can be composed of graphics, text, icons, videos, and any combination thereof. The display unit 5040 may include a display panel. Optionally, the display panel can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc. Further, the touch-sensitive surface can cover the display panel. When the touch-sensitive surface detects a touch operation on or near it, it is transmitted to the processor 5080 to determine the type of touch event. Subsequently, the processor 5080 provides corresponding visual output on the display panel according to the type of touch event. Although in Figure 23 the touch-sensitive surface and the display panel are implemented as two independent components to achieve input and input functions, in some embodiments, the touch-sensitive surface and the display panel can be integrated to achieve input and output functions.

[0505] The terminal may further include at least one sensor 5050, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. Among them, the ambient light sensor can adjust the brightness of the display panel according to the brightness of the ambient light, and the proximity sensor can turn off the display panel and / or the backlight when the terminal is moved to the ear. As a kind of motion sensor, the gravity acceleration sensor can detect the magnitude of the acceleration in each direction (generally three axes). When stationary, it can detect the magnitude and direction of gravity, and can be used in applications for identifying the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. As for other sensors that the terminal may also be configured with, such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be elaborated here.

[0506] The audio circuit 5060, the speaker, and the microphone can provide an audio interface between the object and the terminal. The audio circuit 5060 can transmit the electrical signal converted from the received audio data to the speaker, and the speaker converts it into a sound signal for output. On the other hand, the microphone converts the collected sound signal into an electrical signal, which is received by the audio circuit 5060 and then converted into audio data. After the audio data is output to the processor 5080 for processing, it is sent through the RF circuit 5010 to, for example, another terminal, or the audio data is output to the memory 5020 for further processing. The audio circuit 5060 may also include an earphone jack to provide communication between the peripheral earphone and the terminal.

[0507] WiFi belongs to short - range wireless transmission technology. Through the WiFi module 5070, the terminal can help the object send and receive emails, browse the web, and access streaming media, etc. It provides the object with wireless broadband Internet access. Although Figure 23 the WiFi module 5070 is shown, it can be understood that it does not belong to the essential components of the terminal and can be omitted entirely within the scope of not changing the essence of the invention according to needs.

[0508] The processor 5080 is the control center of the terminal. It uses various interfaces and circuits to connect all parts of the entire mobile phone. By running or executing the software programs and / or modules stored in the memory 5020, and by calling the data stored in the memory 5020, it executes various functions of the terminal and processes data, thereby monitoring the mobile phone as a whole. Optionally, the processor 5080 may include one or more processing cores; preferably, the processor 5080 may integrate an application processor and a modem processor. Among them, the application processor mainly processes the operating system, the object interface, and application programs, etc., and the modem processor mainly processes wireless communication. It can be understood that the above - mentioned modem processor may not be integrated into the processor 5080 either.

[0509] The terminal further includes a power supply 5090 (such as a battery) for powering each component. Preferably, the power supply can be logically connected to the processor 5080 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. The power supply 5090 may further include any components such as one or more DC or AC power supplies, a recharge system, a power failure detection circuit, a power converter or inverter, and a power status indicator.

[0510] Although not shown, the terminal may further include a camera, a Bluetooth module, etc., which will not be elaborated here. Specifically, in this embodiment, the processor 5080 in the terminal will load the executable files corresponding to the processes of one or more application programs into the memory 5020 according to the following instructions, and the processor 5080 will run the application programs stored in the memory 5020 to implement various functions:

[0511] Receive a transaction request sent by a client, and return the generated verification information according to the communication address corresponding to the transaction request;

[0512] Receive the transaction data structure generated by the client according to the verification information. The transaction data structure includes a transaction signature encrypted according to transaction-related data, an encrypted verification information encrypted according to the verification information, and an object signature encrypted according to the transaction-related data, the transaction signature, and the encrypted verification information;

[0513] Perform a first verification of the digital signature of the transaction data structure according to the object signature and the transaction signature, and a second verification of the verification information of the transaction data structure according to the encrypted verification information to obtain a target verification result;

[0514] When the target verification result indicates passing, broadcast the transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result;

[0515] When the broadcast verification result indicates passing, execute the transaction corresponding to the transaction data structure.

[0516] In the above embodiments, the descriptions of each embodiment have their own emphases. For parts not elaborated in a certain embodiment, reference may be made to the detailed description of the transaction processing method above, which will not be elaborated here.

[0517] As can be seen from the above, in the embodiment of the present application, a transaction request sent by a client is received, and the generated verification information is returned according to the communication address corresponding to the transaction request; the transaction data structure generated by the client according to the verification information is received, and the transaction data structure includes a transaction signature encrypted according to transaction - associated data, an encrypted verification information encrypted according to the verification information, and an object signature encrypted according to the transaction - associated data, the transaction signature, and the encrypted verification information; a first verification of the digital signature of the transaction data structure is performed according to the object signature and the transaction signature, and a second verification of the verification information of the transaction data structure is performed according to the encrypted verification information to obtain a target verification result; when the target verification result indicates passing, the transaction data structure is broadcast to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result; when the broadcast verification result indicates passing, the transaction corresponding to the transaction data structure is executed. In the embodiment of the present application, the current node can return the generated verification information according to the communication address corresponding to the transaction request, and then receive the transaction data structure returned by the client according to the verification information. The digital signature of the transaction data structure is verified through the object signature and the transaction signature in the transaction data structure. After the digital signature verification passes, the verification information in the transaction data structure is also verified. When the verification information passes, it is confirmed that the transaction data structure is generated by the object's own operation. Finally, the transaction corresponding to the transaction data structure is executed. In this way, through the double verification of digital signature verification and verification information verification, it can be ensured that the transaction data structure is legally authorized by the object and is complete, thus ensuring the security in the transaction processing process.

[0518] In this embodiment, the processor 5080 in the terminal will load the executable files corresponding to the processes of one or more application programs into the memory 5020 according to the following instructions, and the processor 5080 will run the application programs stored in the memory 5020 to implement various functions:

[0519] Generate a transaction request according to the transaction input by the object, and send the transaction request to the target node. The transaction request includes the target account address of the object;

[0520] Receive the verification information generated by the target node according to the transaction request and returned through the communication address associated with the target account address, and encrypt the verification information according to the node public key of the target node to generate encrypted verification information;

[0521] Generate transaction - associated data based on the target account address and the transaction, and encrypt the transaction - associated data with the object private key of the object to generate a transaction signature;

[0522] Encrypt the transaction - associated data, the transaction signature, and the encrypted verification information with the object private key to generate an object signature;

[0523] Generate a transaction data structure based on transaction correlation data, a transaction signature, an encryption verification information, and an object signature, and send the transaction data structure to a target node.

[0524] In the above embodiments, the descriptions of the respective embodiments have their own emphases. For parts not detailed in a certain embodiment, reference may be made to the detailed description of the transaction request method above, and details will not be repeated here.

[0525] Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructions, or by controlling relevant hardware through instructions. The instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0526] For this reason, an embodiment of the present application provides a computer-readable storage medium, in which multiple instructions are stored, and the instructions can be loaded by a processor to execute the steps in any one of the transaction processing methods provided by the embodiments of the present application. For example, the instructions can perform the following steps:

[0527] Receive a transaction request sent by a client, and return the generated verification information according to the communication address corresponding to the transaction request;

[0528] Receive a transaction data structure generated by the client according to the verification information. The transaction data structure includes a transaction signature encrypted according to the transaction correlation data, an encryption verification information encrypted according to the verification information, and an object signature encrypted according to the transaction correlation data, the transaction signature, and the encryption verification information;

[0529] Perform a first verification of digital signature on the transaction data structure according to the object signature and the transaction signature, and perform a second verification of verification information on the transaction data structure according to the encryption verification information, to obtain a target verification result;

[0530] When the target verification result indicates passing, broadcast the transaction data structure to other nodes in the same blockchain for broadcast verification, to obtain a broadcast verification result;

[0531] When the broadcast verification result indicates passing, execute the transaction corresponding to the transaction data structure.

[0532] In the above embodiments, the descriptions of the respective embodiments have their own emphases. For parts not detailed in a certain embodiment, reference may be made to the detailed description of the transaction processing method above, and details will not be repeated here.

[0533] An embodiment of the present application provides a computer-readable storage medium, in which multiple instructions are stored, and the instructions can be loaded by a processor to execute the steps in any one of the transaction request methods provided by the embodiments of the present application. For example, the instructions can perform the following steps:

[0534] Generate a transaction request according to the transaction input by the object, and send the transaction request to the target node. The transaction request includes the target account address of the object;

[0535] Receive the verification information returned by the target node according to the transaction request and through the communication address associated with the target account address, and encrypt the verification information according to the node public key of the target node to generate encrypted verification information;

[0536] Generate transaction associated data based on the target account address and the transaction, and encrypt the transaction associated data with the object private key of the object to generate a transaction signature;

[0537] Encrypt the transaction associated data, the transaction signature, and the encrypted verification information with the object private key to generate an object signature;

[0538] Generate a transaction data structure according to the transaction associated data, the transaction signature, the encrypted verification information, and the object signature, and send the transaction data structure to the target node.

[0539] In the above embodiments, the descriptions of the respective embodiments have their own focuses. For the parts not detailed in a certain embodiment, reference may be made to the detailed description of the transaction request method above, and details are not repeated here.

[0540] The embodiments of the present application also provide a computer program product or a computer program. The computer program product or the computer program includes computer instructions, and the computer instructions are 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 or the transaction request method provided in the various optional implementation manners provided in the above embodiments.

[0541] For the specific implementation of each of the above operations, reference may be made to the previous embodiments, and details are not repeated here.

[0542] Among them, the computer-readable storage medium may include: read-only memory (ROM, Read Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk, etc.

[0543] Since the instructions stored in the computer-readable storage medium can execute the steps in any of the transaction processing methods provided in the embodiments of the present application or the steps in the transaction request method, the beneficial effects that can be achieved by any of the transaction processing methods or transaction request methods provided in the embodiments of the present application can be realized. For details, reference may be made to the previous embodiments, and details are not repeated here.

[0544] The above has introduced in detail a transaction processing method and related methods, devices, storage media and equipment provided by the embodiments of the present application. Specific examples are used in this article to elaborate on the principle and implementation manner of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application; at the same time, for those skilled in the art, according to the idea of the present application, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present application.

Claims

1. A transaction processing method, characterized in that, Including: Receiving a transaction request sent by a client and returning generated verification information according to the communication address corresponding to the transaction request; Receiving a transaction data structure generated by the client according to the verification information, where the transaction data structure includes a transaction signature encrypted according to transaction-associated data, an encrypted verification information encrypted according to the verification information, and an object signature encrypted according to the transaction-associated data, the transaction signature, and the encrypted verification information; Performing a first verification of digital signature on the transaction data structure according to the object signature and the transaction signature, and performing a second verification of verification information on the transaction data structure according to the encrypted verification information, to obtain a target verification result; When the target verification result indicates passing, broadcasting the transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result; When the broadcast verification result indicates passing, executing the transaction corresponding to the transaction data structure.

2. The transaction processing method according to claim 1, wherein The transaction data structure consists of a sub-transaction data structure and the object signature, and the sub-transaction data structure includes the transaction-associated data, the transaction signature, and the encrypted verification information; The performing a first verification of digital signature on the transaction data structure according to the object signature and the transaction signature, and performing a second verification of verification information on the transaction data structure according to the encrypted verification information, to obtain a target verification result, includes: Determining an object public key corresponding to the transaction data structure; Verifying the object signature according to the object public key to obtain a first target verification result, where the first target verification result is used to verify the integrity of the sub-transaction data structure; Verifying the transaction signature according to the object public key to obtain a second target verification result, where the second target verification result is used to verify the integrity of the transaction-associated data; When both the first target verification result and the second target verification result indicate passing, decrypting the encrypted verification information to obtain decrypted verification information; Verifying the decrypted verification information according to the verification information to obtain a target verification result.

3. The transaction processing method according to claim 2, characterized in that The decrypting the encrypted verification information to obtain decrypted verification information, includes: Determining a node private key corresponding to the current node; Decrypting the encrypted verification information according to the node private key to obtain decrypted verification information, where the encrypted verification information is encrypted by the client according to the node public key of the current node.

4. The transaction processing method according to claim 2, characterized in that, The broadcasting the transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result, includes: Encrypting the sub-transaction data structure according to the node private key of the current node to generate a node signature; Replacing the object signature in the transaction data structure with the node signature to obtain a target transaction data structure; Broadcasting the target transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result.

5. The transaction processing method according to claim 4, wherein The broadcasting the target transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result, includes: Broadcast the target transaction data structure to other nodes of the same blockchain, so that other nodes determine the node signature, transaction signature, object public key, and node public key corresponding to the target transaction data structure, verify the node signature according to the node public key to obtain a third target verification result, and verify the transaction signature according to the object public key to obtain a fourth target verification result, and obtain a broadcast verification result based on the third target verification result and the fourth target verification result; Among them, the third target verification result is used to verify the authenticity of the node corresponding to the target transaction data structure, and the fourth target verification result is used to verify the integrity of the transaction-related data.

6. The transaction processing method according to claim 1, wherein Before broadcasting and verifying the transaction data structure to other nodes of the same blockchain to obtain a broadcast verification result, it further includes: Obtain the continuous duration calculated from the generation of the verification information; The step of broadcasting and verifying the transaction data structure to other nodes of the same blockchain to obtain a broadcast verification result includes: When the continuous duration does not exceed a preset continuous duration, broadcast the transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result.

7. The transaction processing method according to claim 1, wherein The step of returning the generated verification information according to the communication address corresponding to the transaction request includes: Generate verification information according to the transaction request and determine the target account address carried in the transaction request; Query the communication address associated with the target account address in the ledger of the blockchain and return the verification information through the communication address.

8. The transaction processing method according to claim 1, characterized in that Before receiving the transaction request sent by the client and returning the generated verification information according to the communication address corresponding to the transaction request, it further includes: Receive the registration data structure sent by the client, where the registration data structure includes a registration transaction signature encrypted according to registration-related data, an encrypted communication address encrypted according to the communication address, and a registration object signature encrypted according to the registration-related data, the registration transaction signature, and the encrypted communication address; Verify the digital signature of the registration data structure according to the registration object signature and the registration transaction signature, and verify the communication address of the registration data structure according to the encrypted communication address to obtain a registration verification result; When the registration verification result indicates passing, broadcast the registration data structure to the other nodes for registration verification to obtain a target registration verification result; When the target registration verification result indicates passing, implement the registration of the target account address and communication address corresponding to the registration data structure.

9. The transaction processing method according to claim 8, characterized in that Before verifying the digital signature of the registration data structure according to the registration object signature and the registration transaction signature, and verifying the communication address of the registration data structure according to the encrypted communication address to obtain a registration verification result, it further includes: Determine the target fields in the registration-related data, where the target fields at least include the fields corresponding to the transfer account address; Verifying the digital signature of the registration data structure based on the registration object signature and the registration transaction signature, and verifying the communication address of the registration data structure based on the encrypted communication address, to obtain a registration verification result, including: Determine whether the target field is empty. When the target field is empty, verify the digital signature of the registration data structure based on the registration object signature and the registration transaction signature, and verify the communication address of the registration data structure based on the encrypted communication address, to obtain a registration verification result.

10. The transaction processing method according to claim 8, wherein The registration data structure consists of a sub-registration data structure and a registration object signature. The sub-registration data structure includes the registration associated data, the registration transaction signature, and the encrypted communication address; Verifying the digital signature of the registration data structure based on the registration object signature and the registration transaction signature, and verifying the communication address of the registration data structure based on the encrypted communication address, to obtain a registration verification result, including: Determine the object public key corresponding to the registration data structure; Verify the registration object signature based on the object public key to obtain a first registration verification result, which is used to verify the integrity of the sub-registration data structure; Verify the registration transaction signature based on the object public key to obtain a second registration verification result, which is used to verify the integrity of the registration associated data; When both the first registration verification result and the second registration verification result indicate passing, decrypt the encrypted communication address with the node private key of the current node to obtain a decrypted communication address; Verify the authenticity of the decrypted communication address to obtain a registration verification result.

11. The transaction processing method according to claim 10, wherein Broadcasting the registration data structure to the other nodes for registration verification to obtain a target registration verification result, including: Encrypt the sub-registration data structure with the node private key of the current node to generate a registration node signature; Replace the registration object signature in the registration data structure with the registration node signature to obtain a target registration data structure; Broadcast the target registration data structure to the other nodes for registration verification to obtain a target registration verification result.

12. The transaction processing method according to claim 10, wherein Implementing the registration of the corresponding target account address and communication address in the registration data structure, including: Sequentially concatenate the strings corresponding to the object public key, the encrypted communication address, and the node public key of the current node to obtain an associated address corresponding to the target account address; Write the associated address into the ledger corresponding to the blockchain.

13. A transaction request method, characterized in that, Including: Generate a transaction request according to the transaction input by the object, and send the transaction request to the target node. The transaction request includes the target account address of the object; Receive the verification information returned by the target node according to the transaction request and through the communication address associated with the target account address, and encrypt the verification information with the node public key of the target node to generate an encrypted verification information; Generate transaction - associated data based on the target account address and the transaction, and encrypt the transaction - associated data with the object's private key to generate a transaction signature; Encrypt the transaction - associated data, the transaction signature, and the encryption verification information with the object's private key to generate an object signature; Generate a transaction data structure based on the transaction - associated data, the transaction signature, the encryption verification information, and the object signature, and send the transaction data structure to the target node.

14. The transaction request method according to claim 13, wherein Before generating a transaction request according to the transaction input by the object and sending the transaction request to the target node, it further includes: Generate registration - associated data, and encrypt the registration - associated data with the object's private key to generate a registration transaction signature; Encrypt the communication address of the object with the public key of the target node to obtain an encrypted communication address; Encrypt the registration - associated data, the registration transaction signature, and the encrypted communication address with the object's private key to generate a registration object signature; Generate a registration data structure based on the registration - associated data, the registration transaction signature, the encrypted communication address, and the registration object signature; Send the registration data structure to the target node to request the registration of the corresponding target account address and communication address in the registration data structure.

15. A transaction processing device, characterized in that, It includes: A first receiving module, configured to receive a transaction request sent by a client and return the generated verification information according to the communication address corresponding to the transaction request; A second receiving module, configured to receive the transaction data structure generated by the client according to the verification information, where the transaction data structure includes a transaction signature encrypted based on transaction - associated data, an encryption verification information encrypted based on the verification information, and an object signature encrypted based on the transaction - associated data, the transaction signature, and the encryption verification information; A verification module, configured to perform a first verification of the digital signature of the transaction data structure according to the object signature and the transaction signature, and perform a second verification of the verification information of the transaction data structure according to the encryption verification information to obtain a target verification result; A broadcast module, configured to broadcast the transaction data structure to other nodes of the same blockchain for broadcast verification to obtain a broadcast verification result when the target verification result indicates passing; An execution module, configured to execute the corresponding transaction in the transaction data structure when the broadcast verification result indicates passing.

16. A transaction request device, characterized in that, It includes: A sending module, configured to generate a transaction request according to the transaction input by the object and send the transaction request to the target node, where the transaction request includes the target account address of the object; An encryption module, configured to receive the verification information generated by the target node according to the transaction request and returned through the communication address associated with the target account address, and encrypt the verification information with the public key of the target node to generate an encryption verification information; A first signature module, configured to generate transaction - associated data based on the target account address and the transaction, and encrypt the transaction - associated data with the object's private key to generate a transaction signature; A second signature module, configured to encrypt and generate an object signature for the transaction associated data, the transaction signature, and the encryption verification information according to the object private key; A generation module, configured to generate a transaction data structure according to the transaction associated data, the transaction signature, the encryption verification information, and the object signature, and send the transaction data structure to the target node.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores multiple instructions, and the instructions are adapted to be loaded by a processor to execute the transaction processing method according to any one of claims 1 to 12 or the transaction request method according to claims 13 to 14.

18. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the transaction processing method according to any one of claims 1 to 12 or the transaction request method according to claims 13 to 14.

19. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instruction is executed by the processor, it implements the transaction processing method according to any one of claims 1 to 12 or the transaction request method according to claims 13 to 14.

Images