CN116939011A - Transaction processing method and device based on blockchain, equipment and medium - Google Patents

Transaction processing method and device based on blockchain, equipment and medium Download PDF

Info

Publication number
CN116939011A
CN116939011A CN202210335863.9A CN202210335863A CN116939011A CN 116939011 A CN116939011 A CN 116939011A CN 202210335863 A CN202210335863 A CN 202210335863A CN 116939011 A CN116939011 A CN 116939011A
Authority
CN
China
Prior art keywords
verification
transaction
node
service
execution result
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210335863.9A
Other languages
Chinese (zh)
Inventor
梁作栋
黄桂鸿
蓝虎
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN202210335863.9A priority Critical patent/CN116939011A/en
Publication of CN116939011A publication Critical patent/CN116939011A/en
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/12Applying verification of the received information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0807Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The application discloses a transaction processing method, a transaction processing device, transaction processing equipment and transaction processing media based on a blockchain. The method comprises the following steps: generating a transaction credential based on an execution result of the specified transaction by the service processing node on the basis of the blockchain network, verifying the execution result contained in the transaction credential by the verification node to generate a verification credential, and then transmitting the transaction credential and the verification credential to the blockchain network by the service processing node for association and uplink. The technical scheme of the application realizes verification of the execution result of the appointed transaction, has high verification efficiency and greatly optimizes the service processing scheme.

Description

Transaction processing method and device based on blockchain, equipment and medium
Technical Field
The present application relates to the field of computer technology, and in particular, to a blockchain-based transaction processing method, a blockchain-based transaction processing device, an electronic apparatus, and a computer readable medium.
Background
In the related art, when a service party has a corresponding service requirement, the service requirement is realized through corresponding processing logic deployed on the blockchain network, and as more and more processing logic is deployed on the blockchain network, the processing efficiency of part of services is easy to be low, and because the number of the processing logic is more, the processing logic may be mutually influenced, and the maintenance is relatively difficult.
It can be seen that how to improve the efficiency of service processing is a problem to be solved.
Disclosure of Invention
In order to solve the technical problems, the embodiment of the application provides a transaction processing method, a device, equipment and a medium based on a blockchain, which further improves the efficiency of business processing at least to a certain extent.
According to one aspect of an embodiment of the present application, there is provided a blockchain-based transaction processing method, the method including: receiving a verification request from a service processing node, wherein the verification request carries a transaction credential generated by the service processing node for a first execution result of a specified transaction, and the first execution result is an execution result of the specified transaction obtained by the service processing node from a blockchain network; acquiring a second execution result matched with the specified transaction from a blockchain network based on the verification request; verifying a first execution result contained in the transaction credential based on the second execution result, and generating a verification credential for the verification result; and sending the verification certificate to the service processing node so that the service processing node sends the transaction certificate and the verification certificate to the blockchain network for associated uplink processing.
According to one aspect of an embodiment of the present application, there is provided a blockchain-based transaction processing method, the method including: receiving a first execution result sent by a blockchain network for a specified transaction, wherein the first execution result is an execution result of the blockchain network for the specified transaction; signing the first execution result to generate a transaction credential corresponding to the first execution result of the appointed transaction; generating a verification request based on the transaction credential and sending the verification request to a verification node, so that the verification node obtains a second execution result matched with the appointed transaction from the blockchain network based on the verification request, verifies a first execution result contained in the transaction credential based on the second execution result, and generates a verification credential aiming at the verification result; and receiving verification credentials from the verification node, and sending the transaction credentials and the verification credentials to the blockchain network so that the blockchain network performs associated uplink processing on the transaction credentials and the verification credentials.
According to an aspect of an embodiment of the present application, there is provided a blockchain-based transaction processing device configured at an authentication node, the device including: a first receiving module configured to receive a verification request from a service processing node; the verification request carries transaction credentials generated by the service processing node aiming at a first execution result of a specified transaction, wherein the first execution result is an execution result of the specified transaction obtained by the service processing node from a blockchain network; an acquisition module configured to acquire a second execution result matching the specified transaction from a blockchain network based on the verification request; the verification and generation module is configured to verify a first execution result contained in the transaction credential based on the second execution result and generate a verification credential aiming at the verification result; and the sending module is configured to send the verification certificate to the service processing node so that the service processing node sends the transaction certificate and the verification certificate to the blockchain network for associated uplink processing.
In one embodiment of the present application, based on the foregoing solution, the verification and generation module is specifically configured to: detecting whether the second execution result is matched with the first execution result; if so, determining that the first execution result contained in the transaction certificate is successfully verified; if the first execution result and the second execution result are not matched, determining that verification of the first execution result contained in the transaction certificate fails.
In one embodiment of the present application, based on the foregoing solution, the verification and generation module is specifically configured to: signing the verification result based on a private key of the verification node to obtain signature data aiming at the verification result; the signature data is used as verification credentials for the verification result.
In one embodiment of the present application, based on the foregoing solution, the first receiving module is specifically configured to: receiving a verification request sent by the service processing node; or receiving a verification request from the service processing node forwarded by a node distributor, wherein the verification request is forwarded by the node distributor after receiving the verification request sent by the service processing node and selecting a corresponding verification node according to the verification request.
In one embodiment of the present application, based on the foregoing scheme, the apparatus further includes: a first determining module configured to determine, based on the acquired verification service identifier, a target verification service matching the verification service identifier from among a plurality of verification services deployed; the target verification service is used for acquiring a second execution result matched with the appointed transaction from the blockchain network based on the verification request, verifying a first execution result contained in the transaction credential based on the second execution result and generating a verification credential aiming at the verification result.
In one embodiment of the present application, based on the foregoing scheme, the apparatus further includes: the third receiving module is configured to receive a verification service deployment request sent by a service generator, wherein the verification service deployment request carries verification service to be deployed; the first deployment and generation module is configured to deploy the verification service to be deployed based on the verification service deployment request and generate a verification service identifier corresponding to the deployed verification service; the sending module is further configured to send the authentication service identification to the service generator.
According to an aspect of an embodiment of the present application, there is provided a blockchain-based transaction processing device configured to a service processing node, the device including: the second receiving module is configured to receive a first execution result sent by the blockchain network and aiming at a specified transaction, wherein the first execution result is an execution result of the blockchain network on the specified transaction; the signature and generation module is configured to sign the first execution result and generate a transaction credential corresponding to the first execution result of the appointed transaction; the generation and transmission module is configured to generate a verification request based on the transaction credential and transmit the verification request to a verification node, so that the verification node obtains a second execution result matched with the appointed transaction from the blockchain network based on the verification request, verifies a first execution result contained in the transaction credential based on the second execution result, and generates a verification credential aiming at the verification result; and the receiving and transmitting module is configured to receive the verification credentials from the verification node and transmit the transaction credentials and the verification credentials to the blockchain network so that the blockchain network performs associated uplink processing on the transaction credentials and the verification credentials.
In one embodiment of the present application, based on the foregoing solution, the generating and transmitting module is specifically configured to: receiving a first transaction execution request; the first transaction execution request carries a verification node list, wherein the verification node list comprises at least two appointed verification node identifiers; and sending the verification request to verification nodes matched with the at least two specified verification node identifiers in the verification node cluster.
In one embodiment of the present application, based on the foregoing solution, the generating and transmitting module is specifically configured to: receiving a second transaction execution request; the second transaction execution request carries the number of verification nodes, and the number of the verification nodes is at least two; and determining verification nodes matched with the verification nodes in number from the verification node cluster, and sending the verification request to the verification nodes.
In one embodiment of the present application, based on the foregoing solution, the generating and sending module is further specifically configured to: sending a verification node allocation request to a node allocation formula based on the verification node number, so that the node allocation formula determines verification nodes matched with the verification node number from a verification node cluster based on the verification node allocation request, and returns an identification of the verification nodes; and sending the verification request to a verification node matched with the identification of the verification node.
In one embodiment of the present application, based on the foregoing solution, the generating and transmitting module is specifically configured to: receiving a second transaction execution request; the second transaction execution request carries the number of verification nodes, and the number of the verification nodes is at least two; and sending the verification node number and the verification request to a node distribution formula, so that the node distribution formula determines verification nodes matched with the verification node number from a verification node cluster, and forwards the verification request to the verification nodes.
In one embodiment of the present application, based on the foregoing scheme, the receiving and transmitting module is specifically configured to: receiving authentication credentials from a plurality of authentication nodes for the specified transaction; if the verification credentials exceeding the preset quantity threshold value exist in the plurality of verification credentials to represent that the verification of the appointed transaction is successful, determining that the verification of the appointed transaction is successful; and encapsulating the transaction certificate and the verification certificate which characterizes the verification success of the appointed transaction in the plurality of verification certificates to obtain an encapsulation certificate, and sending the encapsulation certificate to the blockchain network so that the blockchain network carries out uplink processing on the encapsulation certificate.
In one embodiment of the present application, based on the foregoing scheme, the apparatus further includes: a second determining module configured to determine, based on the acquired business process service identifier, a target business process service matching the business process service identifier from a plurality of business process services deployed; the target business processing service is used for signing the first execution result and generating a transaction credential corresponding to the first execution result of the appointed transaction.
In one embodiment of the present application, based on the foregoing scheme, the apparatus further includes: a fourth receiving module, configured to receive a service processing service deployment request sent by a service generator, where the service processing service deployment request carries a service processing service to be deployed; the second deployment and generation module is configured to deploy the service processing service to be deployed based on the service processing service deployment request and generate a service processing service identifier corresponding to the deployed service processing service; the receiving and transmitting module is further configured to transmit the business processing service identifier to the service generator.
According to one aspect of an embodiment of the present application, an electronic device is provided, including one or more processors; and storage means for storing one or more programs that, when executed by the one or more processors, cause the electronic device to implement the blockchain-based transaction processing method as described above.
According to one aspect of an embodiment of the present application, there is provided a computer readable medium having stored thereon a computer program which, when executed by a processor, implements a blockchain-based transaction processing method as described above.
According to one aspect of an embodiment of the present application, there is provided a computer program product comprising computer instructions which, when executed by a processor, implement a blockchain-based transaction processing method as described above.
In the technical scheme provided by the embodiment of the application: generating a transaction credential based on an execution result of the specified transaction by the service processing node on the basis of the blockchain network, verifying the execution result contained in the transaction credential by the verification node to generate a verification credential, and then transmitting the transaction credential and the verification credential to the blockchain network by the service processing node for association and uplink. Thus, verification of the execution result of the specified transaction is realized under the chain, and compared with deployment of verification logic in a blockchain network, the verification efficiency is improved to a certain extent; in addition, as the verification logic is not deployed in the blockchain network, other processing logic cannot be affected by modifying the verification logic, the coupling is low, and the later maintenance is more convenient; meanwhile, the transaction certificate and the verification certificate are used as evidence to be associated and uplink to the blockchain for storage, so that later inquiry according to actual conditions is facilitated, and support is provided for corresponding service requirements.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application. It is evident that the drawings in the following description are only some embodiments of the present application and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art.
FIG. 1 is a schematic diagram of a blockchain network.
FIG. 2 is a schematic diagram of the connection of blocks in a blockchain.
FIG. 3 is a schematic diagram of an exemplary implementation environment in which the techniques of embodiments of the present application may be applied.
FIG. 4 is a flow chart illustrating a blockchain-based transaction processing method in accordance with an exemplary embodiment of the present application.
FIG. 5 is a flow chart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 6 is a flow chart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 7 is a flowchart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 8 is a flow chart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 9 is a flowchart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 10 is a flow chart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 11 is a flowchart illustrating a blockchain-based transaction processing method in accordance with an exemplary embodiment of the present application.
FIG. 12 is a flowchart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 13 is a flowchart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 14 is a flowchart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 15 is a flowchart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 16 is a flow chart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 17 is a flowchart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 18 is a flowchart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 19 is a flowchart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 20 is a flowchart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 21 is a flowchart illustrating a blockchain-based transaction processing method in accordance with another exemplary embodiment of the present application.
FIG. 22 is a block diagram of a blockchain-based transaction processing device shown in accordance with another exemplary embodiment of the present application.
FIG. 23 is a block diagram of a blockchain-based transaction processing device shown in accordance with another exemplary embodiment of the present application.
Fig. 24 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the application.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The embodiments described in the following exemplary examples do not represent all embodiments identical to the present application. Rather, they are merely examples of apparatus and methods that are identical to some aspects of the present application as detailed in the appended claims.
The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, the functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.
In the present application, the term "plurality" means two or more. "and/or" describes an association relationship of an association object, meaning that there may be three relationships, e.g., a and/or B may represent: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
In the related art, when a service party has a corresponding service requirement, the service requirement is realized through corresponding processing logic deployed on the blockchain network, and as more and more processing logic is deployed on the blockchain network, the processing efficiency of part of services is easy to be low, and because the number of the processing logic is more, the processing logic may be mutually influenced, and the maintenance is relatively difficult.
To facilitate understanding, taking the service requirement as an example of the verification transaction requirement, the verification transaction requirement is realized through the verification logic deployed on the blockchain network, but the processing efficiency of the verification transaction corresponding to the verification logic may be low due to the large number of processing logic deployed on the blockchain network, and if the verification logic is to be modified, other processing logic in the blockchain network may be affected, so that maintenance is relatively difficult, and a certain trouble is brought to related workers.
Before describing the technical scheme of the embodiment of the application, the blockchain technology used in the embodiment of the application is described first.
Blockchain (Blockchain) is a new application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanisms, encryption algorithms, and the like. Blockchains are essentially a de-centralized database, which is a series of data blocks (i.e., blocks) that are generated in association using cryptographic methods, each of which contains information from a batch of network transactions for verifying the validity (anti-counterfeiting) of the information and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer.
As above, a blockchain is essentially a de-centralized database, and the blockchain is commonly maintained by nodes in the blockchain network. For example, referring to fig. 1, in the blockchain network shown in fig. 1, a plurality of nodes 101 may be included, and the plurality of nodes 101 may be respective clients forming the blockchain network. Each node 101 may receive input information while operating normally and maintain shared data within the blockchain network based on the received input information. In order to ensure information intercommunication in the blockchain network, information connection can exist between every two nodes in the blockchain network, and information transmission can be carried out between the nodes through the information connection. For example, when any node in the blockchain network receives input information, other nodes in the blockchain network acquire the input information according to a consensus algorithm, and store the input information as shared data, so that the data stored on all the nodes in the blockchain network are consistent.
For each node in the blockchain network, there is a node identification corresponding thereto, and each node in the blockchain network may store the node identifications of other nodes for subsequent broadcasting of the generated blocks to other nodes in the blockchain network based on the node identifications of the other nodes. Each node can maintain a node identification list, and the node names and the node identifications are correspondingly stored in the node identification list. The node identifier may be an IP (Internet Protocol, protocol interconnecting between networks) address, or any other information that can be used to identify the node.
Each node in the blockchain network stores one and the same blockchain. Referring to fig. 2, the block chain is composed of a plurality of blocks, the starting block comprises a block head and a block body, the block head stores input information characteristic values, version numbers, time stamps, difficulty values and the like, and the block body stores input information; the next block of the starting block takes the starting block as a father block, the next block also comprises a block head and a block body, the block head stores the input information characteristic value of the current block, the block head characteristic value, the version number, the timestamp, the difficulty value and the like of the father block, and the like, so that the block data stored in each block in the block chain are associated with the block data stored in the father block, and the safety of the input information in the block is ensured.
Each node in the blockchain network may be a server or a terminal device. The server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a Cloud server providing Cloud services, cloud databases, cloud Computing (Cloud Computing), cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs (Content Delivery Network, content distribution networks), basic Cloud Computing services such as big data and intelligent platforms, and the like. The terminal device may be, but not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, etc. The nodes may be directly or indirectly connected through wired or wireless communication, and the present application is not limited herein.
The cloud computing refers to a delivery and use mode of an IT infrastructure, and specifically refers to obtaining required resources in an on-demand and easily-expandable manner through a network; generalized cloud computing refers to the delivery and usage patterns of services, meaning that the required services are obtained in an on-demand, easily scalable manner over a network. Such services may be IT, software, internet related, or other services. Cloud Computing is a product of fusion of traditional computer and network technology developments such as Grid Computing (Grid Computing), distributed Computing (Distributed Computing), parallel Computing (Parallel Computing), utility Computing (Utility Computing), network storage (Network Storage Technologies), virtualization (Virtualization), load balancing (Load balancing), and the like. With the development of the internet, real-time data flow and diversification of connected devices, and the promotion of demands of search services, social networks, mobile commerce, open collaboration and the like, cloud computing is rapidly developed. Unlike the previous parallel distributed computing, the generation of cloud computing will promote the revolutionary transformation of the whole internet mode and enterprise management mode in concept.
Based on the blockchain technology described above and the problem of low transaction verification efficiency in the related art, the embodiment of the application provides a blockchain-based transaction processing scheme. Specifically, in an application scenario of the present application, referring to fig. 3, a service party 301, a hosting network 302, and a blockchain network 303 are mainly included.
It will be appreciated that business 301, which is the party initiating the demand associated with the transaction; where transaction-related requirements include, but are not limited to, transaction execution requests, transaction verification requests, and the like. It can initiate transaction related request by any electronic device with input interface; the electronic device includes, but is not limited to, a smart phone, a tablet, a notebook computer, a computer, an intelligent voice interaction device, an intelligent household appliance, a vehicle-mounted terminal, an aircraft and the like, wherein the input interface includes, but is not limited to, a touch screen, a keyboard, physical keys, an audio pick-up device and the like.
It will be appreciated that the escrow network 302 is the party that responds to the transaction verification request to verify the transaction. The method can be obtained by deployment through any server; the server may be a server providing various services, which may be an independent physical server, or may be a server cluster or a distributed system formed by a plurality of physical servers, or may be a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, basic cloud computing services such as big data and intelligent platforms, which are not limited herein.
It will be appreciated that the blockchain network 303 is the blockchain network described above, and is a party that responds to a transaction execution request to execute a transaction, and transaction data corresponding to the transaction after the transaction is executed is uploaded in the blockchain network, that is, stored in the blockchain network. Where the blockchain network 303 may be one or more, this is not limiting.
Referring to fig. 3 again, the managed network 302 mainly includes a service processing node cluster 3021, an authentication node cluster 3022, a gold processing gateway 3023 and a node distributor 3024; wherein:
service processing node cluster 3021 includes at least two service processing nodes (only 3 service processing nodes are illustrated in fig. 3), each of which may be used to: receiving a first execution result sent by the blockchain network for the specified transaction, wherein the first execution result is the execution result of the blockchain network for the specified transaction; then signing the first execution result to generate a transaction certificate corresponding to the first execution result of the appointed transaction; then generating a verification request based on the transaction credential and sending the verification request to a verification node, so that the verification node obtains a second execution result matched with the appointed transaction from the blockchain network based on the verification request, verifies the first execution result contained in the transaction credential based on the second execution result, and generates a verification credential aiming at the verification result; and then receiving the verification certificate from the verification node, and sending the transaction certificate and the verification certificate to the blockchain network so that the blockchain network performs associated uplink processing on the transaction certificate and the verification certificate.
The authentication node cluster 3022 includes at least two authentication nodes (only 3 authentication nodes are illustrated in fig. 3), each of which may be used to: receiving a verification request from a service processing node, wherein the verification request carries a transaction credential generated by the service processing node aiming at a first execution result of a specified transaction, and the first execution result is an execution result of the specified transaction obtained by the service processing node from a blockchain network; then, based on the verification request, obtaining a second execution result matched with the appointed transaction from the blockchain network; then, verifying the first execution result contained in the transaction certificate based on the second execution result, and generating a verification certificate aiming at the verification result; and then sending the verification certificate to the service processing node so that the service processing node sends the transaction certificate and the verification certificate to the blockchain network for associated uplink processing.
The guaranteed gold processing gateway 3023 may be used to: nodes (such as service processing nodes and/or verification nodes) added into the managed network are managed in a manner of guaranty gold mortgages, and guaranties corresponding to different nodes can be the same or different. Wherein if a node normally performs a corresponding service during joining the escrow network without causing a disfigurement or the like, its guard can be returned entirely when it exits the escrow network, if a node does not normally perform a corresponding service during joining the escrow network even with causing a disfigurement or the like, its guard can be collected, and a higher amount of guard can be added or it can be obligated to exit the escrow network or the like, which can be performed according to a specification between the escrow network and the node. It will be appreciated that each node joining the hosted network typically corresponds to a different resource provider, which may select a node having a corresponding computing resource when a business party initiates a demand associated with a transaction; wherein the computing resources include, but are not limited to, central processing units (Central Processing Unit, CPU), memory, hard disk, etc., and each computing resource may be priced by a resource provider to form a de-centralized network resource market, achieving stability of the network resource market.
Node allocator 3024 (also referred to as a node allocator) may be used to: nodes (e.g., business processing nodes and/or authentication nodes) joining the hosted network are assigned, which may or may not be located in the hosted network.
According to the technical scheme, verification of the execution result of the specified transaction is achieved under the chain through the hosting network, and compared with the fact that verification logic is deployed in the blockchain network, verification efficiency is improved to a certain extent; and because the verification logic is not deployed in the blockchain network, the modification of the verification logic does not affect other processing logic, the coupling is low, and the later maintenance is more convenient. Meanwhile, the hosting network comprises a business processing node cluster and a verification node cluster, namely the hosting network is a virtually decentralised hosting network, and verification of the execution result of the appointed transaction is realized through interaction between the business processing nodes contained in the business processing node cluster and the verification nodes contained in the verification node cluster, so that verification safety and accuracy are improved to a certain extent.
It should be noted that, in the specific embodiment of the present application, the data related to the object is required to obtain the license or consent of the object when the embodiment of the present application is applied to the specific product or technology, and the collection, use and processing of the related data are required to comply with the related laws and regulations and standards of the related country and region.
Various implementation details of the technical solution of the embodiment of the present application are set forth in detail below:
referring to fig. 4, fig. 4 is a flow chart of a method that may be performed by the authentication nodes in the authentication node cluster 3022 shown in fig. 3 according to one embodiment of the application. As shown in fig. 4, the blockchain-based transaction processing method at least includes steps S401 to S404, which are described in detail below:
step S401, receiving a verification request from a service processing node, where the verification request carries a transaction credential generated by the service processing node for a first execution result of a specified transaction, where the first execution result is an execution result of the specified transaction obtained by the service processing node from a blockchain network.
In the embodiment of the application, the verification request is a request for indicating the verification node to verify the transaction data related to a specific transaction; the verification request carries transaction credentials generated by the service processing node for a first execution result of the appointed transaction.
The first execution result in the embodiment of the application is the result of the block chain network executing the appointed transaction; the first execution result may be that the service processing node actively obtains from the blockchain network, or the blockchain network actively sends the first execution result to the service processing node to enable the service processing node to obtain.
It may be understood that, in the embodiment of the present application, the service processing node may first obtain an execution result (i.e., a first execution result) of a specified transaction from the blockchain network, then sign the first execution result, generate a transaction credential corresponding to the first execution result, and then generate a verification request based on the transaction credential and send the verification request to the verification node; accordingly, the authentication node receives an authentication request from the service processing node, wherein the source of the authentication request is the service processing node.
Based on the technical solution of the embodiment shown in fig. 4, in an embodiment of the present application, referring to fig. 5, the process of receiving the authentication request from the service processing node in step S401 may include step S501, which is described in detail below:
step S501, a verification request sent by a service processing node is received.
That is, the authentication node in an alternative embodiment may be a directly received authentication request sent by the service processing node without the aid of an intermediate forwarder, e.g. a node distribution recipe. In short, both the source and the sender of the authentication request received by the authentication node are service processing nodes.
Based on the technical solution of the embodiment shown in fig. 4, in an embodiment of the present application, referring to fig. 6, the process of receiving the authentication request from the service processing node in step S401 may include step S601, which is described in detail below:
Step S601, receiving an authentication request from a service processing node forwarded by a node distributor, wherein the authentication request is forwarded after the node distributor receives the authentication request sent by the service processing node and selects a corresponding authentication node according to the authentication request.
That is, in an alternative embodiment, the verification node may indirectly receive the verification request sent by the service processing node, specifically, the service processing node sends the verification request to the node allocation formula, and then the node allocation formula forwards the verification request to the verification node, and accordingly, the verification node receives the verification request forwarded by the node allocation party from the service processing node. In short, the source of the authentication request received by the authentication node is the service processing node, and the sender is the node allocation formula.
Thus, by implementing the alternative embodiment, the verification node can obtain the verification request from the service processing node in at least two ways, so that the method can be suitable for wider application scenarios and provides support for realizing the subsequent transaction verification based on the verification request.
Step S402, obtaining a second execution result matched with the appointed transaction from the blockchain network based on the verification request.
In the embodiment of the application, the verification node receives the verification request from the service processing node, and then can acquire the second execution result matched with the appointed transaction from the blockchain network based on the verification request.
The second execution result in the embodiment of the application is the execution result which is acquired by the verification node from the blockchain network based on the verification request and matched with the appointed transaction.
Based on the technical solution of the embodiment shown in fig. 4, in one embodiment of the present application, referring to fig. 7, before the process of obtaining, based on the verification request, the second execution result matching the specified transaction from the blockchain network in step S402, step S701 may further include the following detailed description:
step S701, based on the acquired verification service identifier, determining a target verification service matching the verification service identifier from the plurality of verification services deployed; the target verification service is used for acquiring a second execution result matched with the appointed transaction from the blockchain network based on the verification request, verifying the first execution result contained in the transaction credential based on the second execution result, and generating a verification credential aiming at the verification result.
That is, in an alternative embodiment, the verification node may determine, based on the obtained verification service identifier, a target verification service that matches the verification service identifier from the plurality of verification services that are deployed, and then perform a corresponding verification procedure through the target verification service.
In an alternative embodiment, the corresponding verification process is performed by the target verification service, which may specifically be that the target verification service is operated, that is, the second execution result matched with the specified transaction is obtained from the blockchain network based on the verification request by the target verification service, and the first execution result contained in the transaction credential is verified based on the second execution result, and the verification credential for the verification result is generated.
In an alternative embodiment, the verification node may deploy a plurality of verification services, where each verification service may implement verification for a different service, and the verification service is a service developed by a service party or a third party trusted by the service party and used for implementing verification for a certain service, and after development is completed, the verification service is deployed in the verification node in advance, and then verification of the service for which the verification service is aimed can be implemented by running the verification service.
Wherein, the verification service identifier in the alternative embodiment is identification information for uniquely characterizing the verification service, so as to be used for distinguishing different verification services; the authentication service identity obtained by the authentication node may be sent by the service party or by a third party trusted by the service party.
Wherein the target verification service in the alternative embodiment is a verification service that is determined by the verification node to match the verification service identifier from a plurality of deployed verification services based on the obtained verification service identifier.
In this way, by implementing the alternative embodiment, the verification node determines the target verification service matched with the acquired verification service identifier, so as to realize a corresponding verification process based on the target verification service, and the verification efficiency is higher; and different verification services realize verification aiming at different businesses, and all the verification services are not mutually influenced, so that the later maintenance is more convenient.
Based on the technical solution of the embodiment shown in fig. 7, in an embodiment of the present application, referring to fig. 8, before the process of determining, in step S701, the target verification service matching the verification service identifier from the plurality of verification services deployed based on the obtained verification service identifier, step S801 to step S803 may further include the following detailed description:
step S801, receiving a verification service deployment request sent by a service generator, wherein the verification service deployment request carries verification service to be deployed;
step S802, deploying verification service to be deployed based on a verification service deployment request, and generating a verification service identifier corresponding to the deployed verification service;
Step S803, the authentication service identification is sent to the service generator.
That is, in an alternative embodiment, the verification node deploys a verification service, which specifically may be that a verification service deployment request sent by a service generator is received, where the verification service deployment request carries a verification service to be deployed, and then the verification service to be deployed is deployed based on the verification service deployment request, and a verification service identifier corresponding to the deployed verification service is generated, and then the verification service identifier is sent to the service generator.
In an alternative embodiment, the service generator is a party that generates the verification service, for example, the verification service may be developed by the service party or a third party trusted by the service party, so that the service party or the third party trusted by the service party is the service generator.
In the optional embodiment, the verification service deployment request is a request for indicating the verification node to deploy a certain verification service, where the verification service deployment request carries the verification service to be deployed, so that the verification node can acquire the verification service to be deployed from the verification service deployment request to deploy.
In an alternative embodiment, the verification node deploys verification services to be deployed based on the verification service deployment request, generates a verification service identifier corresponding to the deployed verification services, and then needs to send the verification service identifier to the service generator, so that the later service generator can know the deployed verification service identifier, and therefore a service party or a third party trusted by the service party can send the verification service identifier to inform the verification node of which verification service to run when the requirements exist, and a corresponding verification process is realized through the running verification services.
Thus, by implementing an alternative embodiment, the authentication node deploys the authentication service based on the authentication service deployment request sent by the service generator, so as to provide support for implementing corresponding authentication based on the authentication service at a later stage.
Step S403, verifying the first execution result contained in the transaction credential based on the second execution result, and generating a verification credential for the verification result.
In the embodiment of the application, the verification node acquires the second execution result matched with the appointed transaction from the blockchain network based on the verification request, and then can verify the first execution result contained in the transaction certificate based on the second execution result and generate the verification certificate aiming at the verification result.
Based on the technical solution of the embodiment shown in fig. 4, in one embodiment of the present application, referring to fig. 9, the process of verifying the first execution result contained in the transaction credential based on the second execution result in step S403 may include steps S901 to S903, which are described in detail below:
step S901, detecting whether the second execution result is matched with the first execution result;
step S902, if the first execution result contained in the transaction certificate is successfully verified;
Step S903, if not, determining that the verification of the first execution result contained in the transaction credential fails.
That is, in an alternative embodiment, the verification node verifies the first execution result included in the transaction credential based on the second execution result, specifically, may detect whether the second execution result matches the first execution result, and then determine the verification result based on the matching condition. If the matching condition is that the second execution result is matched with the first execution result, the first execution result contained in the transaction certificate can be confirmed to be successfully verified, namely, the verification result at the moment is verification success; if the matching condition is that the second execution result is not matched with the first execution result, the first execution result contained in the transaction certificate can be determined to be failed to verify, namely, the verification result at the moment is failed to verify.
For example, let r1 be the first execution result contained in the transaction credential for the specified transaction 1, and obtain the second execution result matching the specified transaction 1 from the blockchain network; if the second execution result is r1, it is detected that the second execution result is matched with the first execution result at this time, it may be determined that verification of the first execution result r1 contained in the transaction certificate is successful, and if the second execution result is r2, it is detected that the second execution result is not matched with the first execution result at this time, it may be determined that verification of the first execution result r1 contained in the transaction certificate is failed.
Thus, by implementing the alternative embodiment, the verification node detects whether the second execution result matches the first execution result, and verification of the first execution result contained in the transaction credential may be implemented simply and quickly.
Based on the technical solution of the embodiment shown in fig. 4, in one embodiment of the present application, referring to fig. 10, the process of generating the verification credential for the verification result in step S403 may include steps S1001 to S1002, which are described in detail below:
step S1001, signing the verification result based on a private key of the verification node to obtain signature data aiming at the verification result;
step S1002, the signature data is used as an authentication credential for the authentication result.
That is, in an alternative embodiment, the verification node generates a verification credential for the verification result, specifically, may sign the verification result based on a private key of the verification node, to obtain signature data for the verification result, and uses the signature data as the verification credential for the verification result.
In an alternative embodiment, the private key of the authentication node is matched with the public key of the authentication node, and the private key can be sent to the service processing node in advance, so that the service processing node authenticates the authentication node based on the public key of the authentication node.
In the optional embodiment, no matter whether the verification result is successful or failed, the verification node needs to sign the verification result by using its own private key, and the obtained signature data for the verification result is the verification credential for the verification result.
Thus, by implementing the alternative embodiment, the verification node uses the signed verification result as a verification credential for the verification result, so that the responsible party can be traced or positioned according to the signature data in the later stage.
Step S404, the verification certificate is sent to the service processing node, so that the service processing node sends the transaction certificate and the verification certificate to the blockchain network for associated uplink processing.
In the embodiment of the application, the verification node verifies the first execution result contained in the transaction certificate based on the second execution result, generates the verification certificate aiming at the verification result, and then sends the verification certificate to the service processing node, so that the service processing node can send the transaction certificate and the verification certificate to the blockchain network for association and uplink processing.
In the embodiment of the application, the verification of the execution result of the appointed transaction is realized under the chain, and the verification efficiency is higher compared with the verification logic deployed in the blockchain network; in addition, as the verification logic is not deployed in the blockchain network, other processing logic cannot be affected by modifying the verification logic, the coupling is low, and the later maintenance is more convenient; meanwhile, the transaction certificate and the verification certificate are used as evidence to be associated and uplink to the blockchain for storage, so that later inquiry is facilitated.
The embodiments shown in fig. 4 to 10 are explained from the point of view of the authentication node, and implementation details of the technical solution of the embodiment of the present application are explained in detail below from the point of view of the traffic processing node in connection with fig. 13 to 18:
referring now to fig. 11, fig. 11 is a flow chart illustrating a method that may be performed by a service processing node in the cluster 3021 of service processing nodes shown in fig. 3 according to one embodiment of the present application. As shown in fig. 11, the blockchain-based transaction processing method at least includes steps S1101 to S1104, and is described in detail as follows:
step S1101, receiving a first execution result for the specified transaction sent by the blockchain network, where the first execution result is an execution result of the specified transaction by the blockchain network.
In the embodiment of the present application, the blockchain network may send the first execution result for the specified transaction to the service processing node, and accordingly, the service processing node receives the first execution result for the specified transaction sent by the blockchain network, where the description of the foregoing embodiment is omitted herein for the relevant content of the first execution result.
Step S1102, signing the first execution result, and generating a transaction credential corresponding to the first execution result for the specified transaction.
In the embodiment of the application, after receiving the first execution result for the specified transaction sent by the blockchain network, the service processing node can sign the first execution result to generate the transaction credential corresponding to the first execution result for the specified transaction.
Based on the technical solution of the embodiment shown in fig. 11, in one embodiment of the present application, referring to fig. 12, before signing the first execution result in step S1102 and generating a transaction credential corresponding to the first execution result for the specified transaction, step S1201 may be further included, which is described in detail below:
step S1201, based on the acquired service identifier, determining a target service matching the service identifier from the deployed plurality of service identifiers; the target business processing service is used for signing the first execution result and generating a transaction credential corresponding to the first execution result of the appointed transaction.
That is, in an alternative embodiment, the service processing node may determine, based on the acquired service processing service identifier, a target service processing service that matches the service processing service identifier from the deployed plurality of service processing services, and then execute a corresponding transaction credential generation process through the target service processing service.
In an alternative embodiment, the corresponding transaction credential generating process is executed through the target service processing service, specifically, the target service processing service is operated, that is, the first execution result is signed through the operated target service processing service, so as to generate the transaction credential corresponding to the first execution result of the specified transaction.
In an alternative embodiment, the service processing node may deploy a plurality of service processing services, where each service processing service may be a service developed by a service party or a third party trusted by the service party for implementing generation of a transaction credential for a certain service, and after development is completed, the service processing node deploys the service processing service in advance, and then, by running the service processing service, generation of the transaction credential for the service for which the service processing service is implemented.
Wherein, in the alternative embodiment, the service processing service identifier is identifier information for uniquely characterizing the service processing service, so as to distinguish different service processing services; the service processing service identifier acquired by the service processing node may be sent by the service party or by a third party trusted by the service party.
In an alternative embodiment, the target service processing service is a service processing service that is determined by the service processing node based on the acquired service processing service identifier and matches the service processing service identifier from the deployed plurality of service processing services.
In this way, by implementing the alternative embodiment, the service processing node determines the target service processing service matched with the acquired service processing service identifier, so as to implement a corresponding transaction credential generation process based on the target service processing service, and the transaction credential generation efficiency is higher; and different business processing services realize generation of transaction certificates aiming at different businesses, and all business processing services are not mutually influenced, so that later maintenance is facilitated.
Based on the technical solution of the embodiment shown in fig. 12, in an embodiment of the present application, referring to fig. 13, before determining, in step S1201, a process of determining, from the deployed plurality of business processing services, a target business processing service matching the business processing service identifier based on the acquired business processing service identifier, steps S1301 to S1303 may be further included, and the following is described in detail:
step S1301, receiving a service processing service deployment request sent by a service generator, where the service processing service deployment request carries a service processing service to be deployed;
Step S1302, deploy the service processing service to be deployed based on the service processing service deployment request, and generate a service processing service identifier corresponding to the deployed service processing service;
step S1303, the business processing service identifier is sent to the service generator.
That is, in an alternative embodiment, the service processing node deploys a service processing service, specifically, may receive a service processing service deployment request sent by the service generator, where the service processing service deployment request carries a service processing service to be deployed, then deploy the service processing service to be deployed based on the service processing service deployment request, generate a service processing service identifier corresponding to the deployed service processing service, and then send the service processing service identifier to the service generator.
In an alternative embodiment, the service generating party is a party that generates the service processing service, for example, the service processing service may be developed by the service party or a third party trusted by the service party, so that the service party or the third party trusted by the service party is the service generating party.
In an alternative embodiment, the service processing service deployment request is a request for instructing the service processing node to deploy a certain service processing service, where the service processing service deployment request carries the service processing service to be deployed, so that the service processing node may obtain the service processing service to be deployed from the service processing service deployment request to deploy the service processing service.
In an alternative embodiment, the service processing node deploys the service processing service to be deployed based on the service processing service deployment request, generates a service processing service identifier corresponding to the deployed service processing service, and then needs to send the service processing service identifier to the service generator, so that the post-service generator can know the deployed service processing service identifier, and thus the service generator or a third party trusted by the service generator can send the service processing service identifier to inform the service processing node of which service processing service is operated when the service processing node needs to realize a corresponding transaction credential generation process through the operated service processing service.
Thus, by implementing an alternative embodiment, the service processing node deploys the service processing service based on the service processing service deployment request sent by the service generator, to provide support for implementing corresponding transaction credential generation based on the service processing service at a later time.
Step S1103 generates a verification request based on the transaction credential and sends the verification request to the verification node, so that the verification node obtains a second execution result matched with the specified transaction from the blockchain network based on the verification request, verifies the first execution result contained in the transaction credential based on the second execution result, and generates a verification credential for the verification result.
In the embodiment of the application, the service processing node signs the first execution result to generate the transaction certificate corresponding to the first execution result of the appointed transaction, then the verification request can be generated based on the transaction certificate and sent to the verification node, so that the verification node can acquire the second execution result matched with the appointed transaction from the blockchain network based on the verification request, verify the first execution result contained in the transaction certificate based on the second execution result, and generate the verification certificate aiming at the verification result.
Based on the technical solution of the embodiment shown in fig. 11, in an embodiment of the present application, referring to fig. 14, the process of sending the authentication request to the authentication node in step S1103 may include steps S1401 to S1402, which are described in detail as follows:
step S1401, receiving a first transaction execution request; the first transaction execution request carries a verification node list, wherein the verification node list comprises at least two appointed verification node identifiers;
step S1402, the authentication request is sent to an authentication node in the authentication node cluster that matches at least two specified authentication node identities.
That is, in an alternative embodiment, the service processing node receives the first transaction execution request carrying the list of verification nodes, and then sends the verification request to the verification node in the verification node cluster, where the verification node matches with at least two specified verification node identifiers.
Wherein, in the optional embodiment, the first transaction execution request is a request for instructing the service processing node to send the verification request to a specific verification node for verification; the first transaction execution request received by the service processing node may be sent by the service party or by a third party trusted by the service party.
In the optional embodiment, the first transaction execution request carries a verification node list, where the verification node list includes at least two specified verification node identifiers, that is, the first transaction execution request has been specified to be verified by which verification nodes, and the service processing node only needs to send the verification request to those specified verification nodes.
For example, the verification node list carried in the first transaction execution request received by the service processing node includes verification node identifiers q1-q3, and then the service processing node sends the verification request to the verification nodes corresponding to the verification node identifiers q1-q3, and accordingly, the verification nodes corresponding to the verification node identifiers q1-q3 perform corresponding verification, and relevant verification content is referred to the description of the foregoing embodiment and will not be repeated herein.
In this way, by implementing the optional embodiment, the service processing node can simply and quickly send the verification request to the verification node matched with the verification node identifier contained in the verification node list for verification based on the verification node list carried in the first transaction execution request; and the number of the verification nodes is at least two, so that the phenomenon that a certain verification node is wrongly prevented, and the verification accuracy is improved to a certain extent.
Based on the technical solution of the embodiment shown in fig. 11, in an embodiment of the present application, referring to fig. 15, the process of sending the authentication request to the authentication node in step S1103 may include steps S1501 to S1502, which are described in detail as follows:
step S1501, receiving a second transaction execution request; the second transaction execution request carries the number of verification nodes, and the number of the verification nodes is at least two;
step S1502, determining verification nodes matching the number of verification nodes from the verification node cluster, and sending a verification request to the verification nodes.
That is, in an alternative embodiment, the service processing node receives the second transaction execution request carrying the number of verification nodes, then determines verification nodes matching the number of verification nodes from the verification node cluster, and sends the verification request to the verification nodes matching the number of verification nodes.
The second transaction execution request in the optional embodiment is also a request for instructing the service processing node to send the verification request to a specific verification node for verification; the second transaction execution request received by the service processing node may be sent by the service party or by a third party trusted by the service party.
In the optional embodiment, the second transaction execution request carries at least two verification nodes, which is different from the first transaction execution request, that is, the second transaction execution request only specifies a certain number of verification nodes to perform verification, but does not specify which verification nodes to perform verification, so that the service processing node needs to determine the verification nodes matched with the verification nodes from the verification node cluster according to the number of the verification nodes carried in the second transaction execution request, and then sends the verification request to the determined verification nodes.
For example, if the number of verification nodes carried in the second transaction execution request received by the service processing node is 3, and if the service processing node determines that the verification nodes corresponding to the verification node identifiers q1-q3 from the verification node cluster, the service processing node sends the verification request to the verification nodes corresponding to the verification node identifiers q1-q3 respectively, and accordingly, the verification nodes corresponding to the verification node identifiers q1-q3 respectively perform corresponding verification, and relevant content of the verification is referred to the description of the foregoing embodiment and is not repeated herein.
In this way, by implementing the alternative embodiment, the service processing node can simply and quickly implement sending the verification request to the verification node matched with the verification node number for verification based on the verification node number carried in the second transaction execution request; and the number of the verification nodes is at least two, so that the phenomenon that a certain verification node is wrongly prevented, and the verification accuracy is improved to a certain extent.
Based on the technical solution of the embodiment shown in fig. 15, in one embodiment of the present application, referring to fig. 16, a process of determining, in step S1502, a verification node matching the number of verification nodes from the verification node cluster and sending a verification request to the verification node may include steps S1601 to S1602, which are described in detail below:
step S1601, sending a verification node allocation request to the node allocation formula based on the number of verification nodes, so that the node allocation formula determines verification nodes matching the number of verification nodes from the verification node cluster based on the verification node allocation request, and returns the identification of the verification nodes;
step S1602, the authentication request is sent to an authentication node that matches the identity of the authentication node.
That is, in an alternative embodiment, the service processing node determines, from the verification node cluster, a verification node that matches the number of verification nodes, and sends a verification request to the verification node, specifically may send a verification node allocation request to the node allocation formula based on the number of verification nodes, so that the node allocation formula determines, from the verification node cluster, the verification node that matches the number of verification nodes based on the verification node allocation request, and returns an identifier of the verification node, and correspondingly, the service processing node receives the identifier of the verification node, and sends the verification request to the verification node that matches the identifier of the verification node.
In the alternative embodiment, the node distribution formula is used for determining the verification nodes matched with the verification node number, namely the node distribution formula is used for designating which verification nodes are used for verification, and the service processing node only needs to receive the identification of the verification nodes returned by the node distribution formula and then sends the verification request to the designated verification nodes.
For example, the number of verification nodes carried in the second transaction execution request received by the service processing node is 3, and then the service processing node sends a verification node allocation request to the node allocation formula based on the 3 verification nodes; the node allocation formula determines the verification node corresponding to the verification node identifier q1-q3 from the verification node cluster based on the verification node allocation request, and returns the verification node q1-q3 to the service processing node, so that the service processing node sends the verification request to the verification node corresponding to the verification node identifier q1-q3 respectively, and correspondingly, the verification nodes corresponding to the verification node identifiers q1-q3 respectively perform corresponding verification, and relevant verification content is described in the foregoing embodiments and is not repeated herein.
Thus, by implementing the alternative embodiment, the verification node for verification is determined by the node allocation formula, the processing pressure of the service processing node can be reduced to a certain extent, and the method can be suitable for a wider application scene.
Based on the technical solution of the embodiment shown in fig. 11, in an embodiment of the present application, referring to fig. 17, the process of sending the authentication request to the authentication node in step S1103 may include steps S1701 to S1702, which are described in detail as follows:
step S1701, receiving a second transaction execution request; the second transaction execution request carries the number of verification nodes, and the number of the verification nodes is at least two;
step S1702, the number of verification nodes and the verification request are sent to the node allocation formula, so that the node allocation formula determines verification nodes matching the number of verification nodes from the verification node cluster, and forwards the verification request to the verification nodes.
That is, in an alternative embodiment, the service processing node receives the second transaction execution request carrying the number of verification nodes, and then sends the number of verification nodes and the verification request to the node distribution formula, so that the node distribution formula can determine verification nodes matching the number of verification nodes from the verification node cluster, and forward the verification request to the verification nodes.
In the optional embodiment, the content related to the second transaction execution request is referred to the description of the foregoing embodiment, which is not repeated here.
In an alternative embodiment, the node allocation is also used, wherein the node allocation determines not only the authentication nodes matching the number of authentication nodes, but also forwards the authentication requests sent by the service processing nodes to the determined authentication nodes after determining the authentication nodes matching the number of authentication nodes. I.e. by the node allocation formula, which authentication nodes authenticate and forwarding the authentication request sent by the traffic handling node to those authentication nodes specified.
For example, the number of verification nodes carried in the first transaction execution request received by the service processing node is 3, and then the service processing node sends a verification node allocation request and a verification request to the node allocation formula based on the 3 verification nodes; the node allocation formula determines the verification nodes corresponding to the verification node identifiers q1-q3 from the verification node cluster based on the verification node allocation request, and forwards the verification request to the verification nodes corresponding to the verification node identifiers q1-q3 respectively, accordingly, the verification nodes corresponding to the verification node identifiers q1-q3 respectively perform corresponding verification, and the relevant verification content is referred to the description of the foregoing embodiment and is not repeated here.
Thus, by implementing the alternative embodiment, the node distribution formula determines the verification node for verification and forwards the verification request to the verification node, the processing pressure of the service processing node can be further reduced, and the method can be suitable for a wider application scenario.
Step S1104, receiving the verification credential from the verification node, and sending the transaction credential and the verification credential to the blockchain network, so that the blockchain network performs association uplink processing on the transaction credential and the verification credential.
The service processing node in the embodiment of the application can also receive the verification certificate from the verification node and send the transaction certificate and the verification certificate to the blockchain network, so that the blockchain network can carry out association and uplink processing on the transaction certificate and the verification certificate.
Based on the technical solution of the embodiment shown in fig. 11, in an embodiment of the present application, referring to fig. 18, step S1104 of receiving the authentication credentials from the authentication node may include step S1801, which is described in detail below:
step S1801, receiving an authentication credential sent by the authentication node.
That is, the service processing node in an alternative embodiment may be a direct receipt of the authentication credentials sent by the authentication node without resorting to an intermediate forwarder such as a node distribution recipe. In short, both the source and the sender of the authentication credentials received by the service processing node are authentication nodes.
Based on the technical solution of the embodiment shown in fig. 11, in an embodiment of the present application, referring to fig. 19, step S1104 of receiving the authentication credentials from the authentication node may include step S1901, which is described in detail below:
in step S1901, the authentication credentials forwarded by the node dispatcher from the authentication node are received, and the authentication credentials are forwarded by the node dispatcher after receiving the authentication credentials sent by the authentication node.
That is, in an alternative embodiment, the service processing node may indirectly receive the authentication credential sent by the authentication node, specifically, the authentication node sends the authentication credential to the node allocation formula, and then the node allocation formula forwards the authentication credential to the service processing node, and accordingly, the service processing node receives the authentication credential forwarded by the node allocation party and coming from the authentication node. In short, the source of the authentication credentials received by the service processing node is the authentication node and the sender is the node distribution formula.
Thus, by implementing the alternative embodiment, the service processing node can obtain the verification credential from the verification node in at least two ways, so that the method can be suitable for a wider application scenario, and support is provided for subsequently sending the transaction credential and the verification credential to the blockchain network.
Based on the technical solution of the embodiment shown in fig. 11, in one embodiment of the present application, referring to fig. 20, the process of receiving the verification credential from the verification node in step S1104 and sending the transaction credential and the verification credential to the blockchain network may include steps S2001 to S2003, which are described in detail below:
step S2001, receiving verification credentials for a specified transaction from a plurality of verification nodes;
step S2002, if the verification credentials exceeding the preset quantity threshold value exist in the verification credentials to represent that the verification of the appointed transaction is successful, the verification of the appointed transaction is determined to be successful;
step S2003, the package transaction certificate and the verification certificate which characterizes the verification success of the appointed transaction in the verification certificates are packaged, the package certificate is obtained, and the package certificate is sent to the blockchain network, so that the blockchain network carries out uplink processing on the package certificate.
That is, in an alternative embodiment, the service processing node receives verification credentials from the plurality of verification nodes for the specified transaction, and then detects whether verification credentials exceeding a preset number threshold value represent successful verification of the specified transaction in the plurality of verification credentials, and determines a verification result of the specified transaction according to the detection result. If the detection result is that the verification credentials exceeding the preset quantity threshold value exist in the plurality of verification credentials to represent the verification success of the specified transaction, the verification success of the specified transaction can be determined, namely the verification result of the specified transaction is the verification success at the moment; if the detection result is that the verification credentials exceeding the preset quantity threshold value do not exist in the plurality of verification credentials to represent that the verification of the specified transaction is successful, the verification failure of the specified transaction can be determined, namely the verification result of the specified transaction at the moment is the verification failure.
For example, let the verification credentials received from the verification nodes corresponding to the verification node identifiers q1-q10 for the specified transaction 1, and let the verification credentials of the verification nodes corresponding to the verification node identifiers q1-q8 all represent the verification success of the specified transaction 1, the verification credentials of the verification nodes corresponding to the verification node identifiers q9-q10 all represent the verification failure of the specified transaction 1, and the preset number threshold is 7; obviously, if more than 7 verification certificates exist in the 10 verification certificates at this time to represent that the verification of the specified transaction is successful, the verification of the specified transaction 1 can be determined to be successful.
In an alternative embodiment, the preset number threshold may be flexibly set according to the number of the plurality of verification nodes, for example, when 100 verification nodes generate verification credentials for the same transaction (i.e. the designated transaction), the preset number threshold may be valued at 80, 90, etc., and when 10 verification nodes generate verification credentials for the same transaction (i.e. the designated transaction), the preset number threshold may be valued at 8, 9, etc. I.e. the preset number threshold may be a certain proportional value of the number of authentication nodes.
In an alternative embodiment, the service processing node sends the transaction credential and the verification credential to the blockchain network, specifically may encapsulate the transaction credential and the verification credential characterizing that the verification of the specified transaction is successful in the multiple verification credentials, so as to obtain an encapsulated credential, and send the encapsulated credential to the blockchain network, so that the blockchain network can perform uplink processing on the encapsulated credential.
In an alternative embodiment, the service processing node sends the transaction credential and the verification credential to the blockchain network, or encapsulates the transaction credential and a verification credential characterizing a verification failure for a specified transaction in the multiple verification credentials, so as to obtain an encapsulated credential, and sends the encapsulated credential to the blockchain network, so that the blockchain network can perform uplink processing on the encapsulated credential.
In an alternative embodiment, the service processing node sends the transaction credential and the verification credential to the blockchain network, or encapsulates the transaction credential and the verification credential characterizing the success and failure of verification on the specified transaction in the multiple verification credentials, so as to obtain an encapsulated credential, and sends the encapsulated credential to the blockchain network, so that the blockchain network can perform uplink processing on the encapsulated credential.
Thus, by implementing the alternative embodiment, the service processing node can send the transaction certificate and the verification certificates from the plurality of verification nodes aiming at the appointed transaction to the blockchain network for uplink processing so as to be reserved as a certificate, so that a responsible party can be traced or positioned at a later stage.
In the embodiment of the application, the verification of the execution result of the appointed transaction is realized under the chain, and the verification efficiency is higher compared with the verification logic deployed in the blockchain network; in addition, as the verification logic is not deployed in the blockchain network, other processing logic cannot be affected by modifying the verification logic, the coupling is low, and the later maintenance is more convenient; meanwhile, the transaction certificate and the verification certificate are used as evidence to be associated and uplink to the blockchain for storage, so that later inquiry is facilitated.
The technical solutions of the embodiments of the present application are described above from the angles of the verification node and the service processing node, respectively, and a specific application scenario of the embodiments of the present application is described in detail below based on the implementation environment shown in fig. 3:
referring to fig. 21, fig. 21 is a flow chart of a method according to an embodiment of the application. As shown in fig. 21, the blockchain-based transaction processing method at least includes steps S2101 to S2106, which are described in detail below:
in step S2101, the service party sends a transaction execution request to the service processing node.
Optionally, the transaction execution request carries a designated service processing node identifier and a service processing service identifier, so that the transaction execution request can be sent to a service processing node matched with the designated service processing node identifier based on the designated service processing node identifier, and a service processing service (specifically, a service processing service is executed in a container dock) deployed on the service processing node and matched with the service processing service identifier.
Optionally, the transaction execution request carries a number of verification nodes, where the number of verification nodes is at least two, and whether the node allocator (i.e., the node allocation formula) is used.
Optionally, the transaction execution request carries a verification node list, where the verification node list includes at least two specified verification node identifiers, which may not be processed by the node dispatcher, and specifically please refer to the technical solution in the foregoing embodiment.
In step S2102, the service processing node receives a first execution result for a specified transaction sent by the blockchain network, signs the first execution result, generates a transaction credential corresponding to the first execution result for the specified transaction, generates a verification request based on the transaction credential, and sends the verification request and the transaction execution request to the node allocator.
Alternatively, running the business process service may obtain an execution result (different from the first execution result and the second execution result); the running service processing service may sign any one or more of the service processing node identifier, the service processing service identifier, the number of verification nodes, the verification node list, whether to use the node allocator, and the verification request carried in the received transaction execution request, and generate an execution result based on the original data (i.e., any one or more of the service processing node identifier, the service processing service identifier, the number of verification nodes, the verification node list, whether to use the node allocator, and the verification request) and/or the signature data.
Optionally, if the service party indicates that processing by the node dispatcher is required, the service processing node may send the execution result to the node dispatcher, and if the service party does not indicate that processing by the node dispatcher is required, the service processing node may send the execution result to the authentication node.
In step S2103, the node allocator determines a verification node matching the number of verification nodes from the verification node cluster, and forwards the verification request to the verification node.
In step S2103, only one case is exemplified in which the node allocator processes the result, and the execution result received in the node allocator contains the corresponding number of verification nodes, and in the actual application scenario, the corresponding processing needs to be performed according to the execution result obtained by the service processing node running the service processing service.
Optionally, step S2103 refers to the solution in the foregoing embodiment.
In step S2104, the verification node obtains a second execution result matching the specified transaction from the blockchain network based on the verification request, verifies the first execution result contained in the transaction credential based on the second execution result, signs the verification result based on the private key of the verification node, obtains signature data for the verification result, and sends the verification credential to the node dispatcher with the signature data as the verification credential for the verification result.
Optionally, step S2104 refers to the solution in the foregoing embodiment.
In step S2105, the node dispatcher receives authentication credentials for a specified transaction from a plurality of authentication nodes and returns to the service processing node.
Optionally, if the verification credentials exceeding the preset number threshold value are present in the plurality of verification credentials to characterize the verification of the specified transaction to be successful, determining that the verification of the specified transaction is successful; if the verification credentials exceeding the preset quantity threshold value do not exist in the plurality of verification credentials, the verification credentials represent that the verification of the appointed transaction is successful, and the verification of the appointed transaction is determined to be failed.
In step S2106, the service processing node sends the transaction credential and the authentication credential to the blockchain network, so that the blockchain network performs association and uplink processing on the transaction credential and the authentication credential.
Optionally, the service processing node encapsulates the transaction credential and an authentication credential of the plurality of authentication credentials that characterizes an authentication success for the specified transaction, obtains the encapsulated credential, and sends the encapsulated credential to the blockchain network to enable the blockchain network to perform a uplink processing on the encapsulated credential.
Thus, verification of the execution result of the specified transaction and the uplink processing of the generated corresponding evidence are completed.
Optionally, referring also to step Sa1, the service processing node may send the deposit to the deposit processing gateway to mortgage the deposit in the deposit processing gateway. Further, step Sa2 is also involved, where the guaranty gold processing gateway may send the mortgage gold, the signature of the guaranty gold processing gateway, and the signature of the service processing node to the blockchain network, so that the blockchain network performs the association uplink processing.
Optionally, referring also to step Sb1, the authentication node may send the deposit to the deposit processing gateway to mortgage the deposit in the deposit processing gateway. Further, step Sb2 is also involved, where the guaranty gold processing gateway may send the mortgage gold, the signature of the guaranty gold processing gateway, and the signature of the verification node to the blockchain network to enable the blockchain network to perform the associated uplink processing.
Optionally, the service processing service deployed in the service processing node may invoke an external service and perform external storage according to the service requirement.
Optionally, the verification service deployed in the verification node may invoke an external service and perform external storage according to the traffic demand.
The managed network in the embodiment of the application comprises the business processing node cluster and the verification node cluster, namely the managed network is the virtually decentralized managed network, and the verification of the execution result of the appointed transaction is realized by the interaction between the business processing nodes contained in the business processing node cluster and the verification nodes contained in the verification node cluster, so that the verification security and accuracy are higher.
FIG. 22 is a block diagram of a blockchain-based transaction processing device shown in an embodiment of the present application. As shown in fig. 22, the blockchain-based transaction processing device is configured in the authentication node, and includes:
a first receiving module 2201 configured to receive an authentication request from a service processing node; the verification request carries transaction credentials generated by the service processing node aiming at a first execution result of the appointed transaction, wherein the first execution result is an execution result of the appointed transaction obtained by the service processing node from the blockchain network;
an acquisition module 2202 configured to acquire a second execution result matching the specified transaction from the blockchain network based on the verification request;
a verification and generation module 2203 configured to verify the first execution result contained in the transaction credential based on the second execution result and generate a verification credential for the verification result;
the sending module 2204 is configured to send the verification credential to the service processing node, so that the service processing node sends the transaction credential and the verification credential to the blockchain network for association and uplink processing.
In one embodiment of the application, the verification and generation module 2203 is specifically configured to:
Detecting whether the second execution result is matched with the first execution result;
if so, determining that the verification of the first execution result contained in the transaction certificate is successful;
if the first execution result and the second execution result are not matched, the first execution result contained in the transaction certificate is determined to be failed to be verified.
In one embodiment of the application, the verification and generation module 2203 is specifically configured to:
signing the verification result based on the private key of the verification node to obtain signature data aiming at the verification result;
the signature data is used as a verification credential for the verification result.
In one embodiment of the present application, the first receiving module 2201 is specifically configured to:
receiving a verification request sent by a service processing node; or alternatively
And receiving the verification request from the service processing node forwarded by the node distributor, wherein the verification request is forwarded after the node distributor receives the verification request sent by the service processing node and selects the corresponding verification node according to the verification request.
In one embodiment of the application, the apparatus further comprises:
a first determining module configured to determine a target verification service matching the verification service identifier from among the plurality of verification services deployed based on the acquired verification service identifier; the target verification service is used for acquiring a second execution result matched with the appointed transaction from the blockchain network based on the verification request, verifying the first execution result contained in the transaction credential based on the second execution result, and generating a verification credential aiming at the verification result.
In one embodiment of the application, the apparatus further comprises:
the third receiving module is configured to receive a verification service deployment request sent by the service generator, wherein the verification service deployment request carries verification service to be deployed;
the first deployment and generation module is configured to deploy verification services to be deployed based on the verification service deployment request and generate verification service identifiers corresponding to the deployed verification services;
and the sending module is further configured to send the verification service identification to the service generator.
FIG. 23 is a block diagram of a blockchain-based transaction processing device shown in an embodiment of the present application. As shown in fig. 23, the blockchain-based transaction processing device is configured in a service processing node, and the blockchain-based transaction processing device includes:
a second receiving module 2301 configured to receive a first execution result for a specified transaction sent by the blockchain network, where the first execution result is an execution result of the specified transaction by the blockchain network;
a signature and generation module 2302 configured to sign the first execution result and generate a transaction credential corresponding to the first execution result for the specified transaction;
a generating and transmitting module 2303 configured to generate a verification request based on the transaction credential and transmit the verification request to the verification node, so that the verification node obtains a second execution result matched with the specified transaction from the blockchain network based on the verification request, verifies the first execution result contained in the transaction credential based on the second execution result, and generates a verification credential for the verification result;
The receiving and sending module 2304 is configured to receive the validation credentials from the validation node and send the transaction credentials and the validation credentials to the blockchain network to enable the blockchain network to perform an associated uplink processing of the transaction credentials and the validation credentials.
In one embodiment of the present application, the generating and transmitting module 2303 is specifically configured to:
receiving a first transaction execution request; the first transaction execution request carries a verification node list, wherein the verification node list comprises at least two appointed verification node identifiers;
and sending the verification request to verification nodes matched with at least two appointed verification node identifiers in the verification node cluster.
In one embodiment of the present application, the generating and transmitting module 2303 is specifically configured to:
receiving a second transaction execution request; the second transaction execution request carries the number of verification nodes, and the number of the verification nodes is at least two;
and determining verification nodes matched with the verification node number from the verification node cluster, and sending a verification request to the verification nodes.
In one embodiment of the present application, the generating and transmitting module 2303 is further specifically configured to:
sending a verification node allocation request to the node allocation formula based on the verification node number, so that the node allocation formula determines verification nodes matched with the verification node number from the verification node cluster based on the verification node allocation request, and returns the identification of the verification nodes;
The authentication request is sent to an authentication node that matches the identity of the authentication node.
In one embodiment of the present application, the generating and transmitting module 2303 is specifically configured to:
receiving a second transaction execution request; the second transaction execution request carries the number of verification nodes, and the number of the verification nodes is at least two;
and sending the number of the verification nodes and the verification request to the node distribution formula so that the node distribution formula determines verification nodes matched with the number of the verification nodes from the verification node cluster, and forwarding the verification request to the verification nodes.
In one embodiment of the application, the receiving and transmitting module 2304 is specifically configured to:
receiving authentication credentials from a plurality of authentication nodes for a specified transaction;
if the verification credentials exceeding the preset quantity threshold value exist in the verification credentials, the verification credentials represent that the verification of the appointed transaction is successful, and the verification of the appointed transaction is determined to be successful;
and the packaged transaction certificate and the verification certificate which characterizes the verification success of the specified transaction in the verification certificates are packaged to obtain the packaged certificate, and the packaged certificate is sent to the blockchain network so that the blockchain network carries out uplink processing on the packaged certificate.
In one embodiment of the application, the apparatus further comprises:
A second determining module configured to determine, based on the acquired business process service identifier, a target business process service matching the business process service identifier from the deployed plurality of business process services; the target business processing service is used for signing the first execution result and generating a transaction credential corresponding to the first execution result of the appointed transaction.
In one embodiment of the application, the apparatus further comprises:
the fourth receiving module is configured to receive a service processing service deployment request sent by a service generator, wherein the service processing service deployment request carries service processing services to be deployed;
the second deployment and generation module is configured to deploy the service processing service to be deployed based on the service processing service deployment request and generate a service processing service identifier corresponding to the deployed service processing service;
the receiving and sending module is further configured to send the business processing service identifier to the service generator.
It should be noted that, the apparatus provided in the foregoing embodiment and the method provided in the foregoing embodiment belong to the same concept, and the specific manner in which each module and unit perform the operation has been described in detail in the method embodiment, which is not repeated herein.
The embodiment of the application also provides electronic equipment, which comprises: one or more processors; and a storage means for storing one or more programs which, when executed by the one or more processors, cause the electronic device to implement a blockchain-based transaction processing method as before.
Fig. 24 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the application.
It should be noted that, the computer system 2400 of the electronic device shown in fig. 24 is only an example, and should not impose any limitation on the functions and the application scope of the embodiments of the present application.
As shown in fig. 24, the computer system 2400 includes a CPU2401 that can perform various appropriate actions and processes, such as performing the methods in the above-described embodiments, according to a program stored in a Read-Only Memory (ROM) 2402 or a program loaded from a storage portion 2408 into a random access Memory (Random Access Memory, RAM) 2403. In the RAM 2403, various programs and data required for system operation are also stored. The CPU2401, ROM 2402, and RAM 2403 are connected to each other through a bus 2404. An Input/Output (I/O) interface 2405 is also connected to bus 2404.
The following components are connected to the I/O interface 2405: an input portion 2406 including a keyboard, a mouse, and the like; an output portion 2407 including a Cathode Ray Tube (CRT), a liquid crystal display (Liquid Crystal Display, LCD), and a speaker; a storage portion 2408 including a hard disk or the like; and a communication section 2409 including a network interface card such as a LAN (Local Area Network ) card, a modem, or the like. The communication section 2409 performs communication processing via a network such as the internet. The drive 2410 is also connected to the I/O interface 2405 as needed. A removable medium 2411 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed on the drive 2410 as needed, so that a computer program read out therefrom is installed into the storage section 2408 as needed.
In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising a computer program for performing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via the communication portion 2409, and/or installed from the removable medium 2411. When executed by a Central Processing Unit (CPU) 2401, performs various functions defined in the system of the present application.
It should be noted that, the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable medium can be, for example, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-Only Memory (ROM), an erasable programmable read-Only Memory (Erasable Programmable Read Only Memory, EPROM), flash Memory, an optical fiber, a portable compact disc read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with a computer-readable computer program embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. A computer program embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. Where each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
Yet another aspect of the application provides a computer readable medium having stored thereon a computer program which, when executed by a processor, implements a blockchain-based transaction processing method as before. The computer-readable medium may be included in the electronic device described in the above embodiment or may exist alone without being incorporated in the electronic device.
Yet another aspect of the application provides a computer program product or computer program comprising computer instructions stored in a computer readable medium. The processor of the computer device reads the computer instructions from the computer readable medium and executes the computer instructions to cause the computer device to perform the blockchain-based transaction processing method provided in the various embodiments described above.
The foregoing is merely illustrative of the preferred embodiments of the present application and is not intended to limit the embodiments of the present application, and those skilled in the art can easily make corresponding variations or modifications according to the main concept and spirit of the present application, so that the protection scope of the present application shall be defined by the claims.

Claims (19)

1. A blockchain-based transaction processing method, the method comprising:
receiving a verification request from a service processing node, wherein the verification request carries a transaction credential generated by the service processing node for a first execution result of a specified transaction, and the first execution result is an execution result of the specified transaction obtained by the service processing node from a blockchain network;
acquiring a second execution result matched with the specified transaction from a blockchain network based on the verification request;
verifying a first execution result contained in the transaction credential based on the second execution result, and generating a verification credential for the verification result;
and sending the verification certificate to the service processing node so that the service processing node sends the transaction certificate and the verification certificate to the blockchain network for associated uplink processing.
2. The method of claim 1, wherein verifying the first execution result contained in the transaction credential based on the second execution result comprises:
detecting whether the second execution result is matched with the first execution result;
If so, determining that the first execution result contained in the transaction certificate is successfully verified;
if the first execution result and the second execution result are not matched, determining that verification of the first execution result contained in the transaction certificate fails.
3. The method of claim 1, wherein the generating the validation credentials for the validation result comprises:
signing the verification result based on a private key of the verification node to obtain signature data aiming at the verification result;
the signature data is used as verification credentials for the verification result.
4. The method of claim 1, wherein the receiving the authentication request from the service processing node comprises:
receiving a verification request sent by the service processing node; or alternatively
And receiving a verification request forwarded by a node distributor from the service processing node, wherein the verification request is forwarded by the node distributor after receiving the verification request sent by the service processing node and selecting a corresponding verification node according to the verification request.
5. The method of any of claims 1-4, wherein prior to obtaining a second execution result from a blockchain network that matches the specified transaction based on the validation request, the method further comprises:
Determining a target verification service matched with the verification service identifier from a plurality of deployed verification services based on the acquired verification service identifier; the target verification service is used for acquiring a second execution result matched with the appointed transaction from the blockchain network based on the verification request, verifying a first execution result contained in the transaction credential based on the second execution result and generating a verification credential aiming at the verification result.
6. The method of claim 5, wherein prior to the determining a target verification service from the plurality of verification services deployed that matches the verification service identification based on the obtained verification service identification, the method further comprises:
receiving a verification service deployment request sent by a service generator, wherein the verification service deployment request carries verification service to be deployed;
deploying the verification service to be deployed based on the verification service deployment request, and generating a verification service identifier corresponding to the deployed verification service;
and sending the verification service identification to the service generator.
7. A method of transaction processing, the method comprising:
Receiving a first execution result sent by a blockchain network for a specified transaction, wherein the first execution result is an execution result of the blockchain network for the specified transaction;
signing the first execution result to generate a transaction credential corresponding to the first execution result of the appointed transaction;
generating a verification request based on the transaction credential and sending the verification request to a verification node, so that the verification node obtains a second execution result matched with the appointed transaction from the blockchain network based on the verification request, verifies a first execution result contained in the transaction credential based on the second execution result, and generates a verification credential aiming at the verification result;
and receiving verification credentials from the verification node, and sending the transaction credentials and the verification credentials to the blockchain network so that the blockchain network performs associated uplink processing on the transaction credentials and the verification credentials.
8. The method of claim 7, wherein the sending the authentication request to an authentication node comprises:
receiving a first transaction execution request; the first transaction execution request carries a verification node list, wherein the verification node list comprises at least two appointed verification node identifiers;
And sending the verification request to verification nodes matched with the at least two specified verification node identifiers in the verification node cluster.
9. The method of claim 7, wherein the sending the authentication request to the authentication node comprises:
receiving a second transaction execution request; the second transaction execution request carries the number of verification nodes, and the number of the verification nodes is at least two;
and determining verification nodes matched with the verification nodes in number from the verification node cluster, and sending the verification request to the verification nodes.
10. The method of claim 9, wherein the determining from the cluster of authentication nodes an authentication node that matches the number of authentication nodes and sending the authentication request to the authentication node comprises:
sending a verification node allocation request to a node allocation formula based on the verification node number, so that the node allocation formula determines verification nodes matched with the verification node number from a verification node cluster based on the verification node allocation request, and returns an identification of the verification nodes;
and sending the verification request to a verification node matched with the identification of the verification node.
11. The method of claim 7, wherein the sending the authentication request to an authentication node comprises:
receiving a second transaction execution request; the second transaction execution request carries the number of verification nodes, and the number of the verification nodes is at least two;
and sending the verification node number and the verification request to a node distribution formula, so that the node distribution formula determines verification nodes matched with the verification node number from a verification node cluster, and forwards the verification request to the verification nodes.
12. The method of claim 7, wherein the receiving authentication credentials from the authentication node comprises:
receiving authentication credentials from a plurality of authentication nodes for the specified transaction;
if the verification credentials exceeding the preset quantity threshold value exist in the plurality of verification credentials to represent that the verification of the appointed transaction is successful, determining that the verification of the appointed transaction is successful;
the sending the transaction credential and the validation credential to the blockchain network includes:
and encapsulating the transaction certificate and the verification certificate which characterizes the verification success of the appointed transaction in the plurality of verification certificates to obtain an encapsulation certificate, and sending the encapsulation certificate to the blockchain network so that the blockchain network carries out uplink processing on the encapsulation certificate.
13. The method of any of claims 7 to 12, wherein prior to said signing the first execution result, generating a corresponding transaction credential for the first execution result of the specified transaction, the method further comprises:
determining a target business processing service matched with the business processing service identifier from a plurality of deployed business processing services based on the acquired business processing service identifier; the target business processing service is used for signing the first execution result and generating a transaction credential corresponding to the first execution result of the appointed transaction.
14. The method of claim 13, wherein prior to the determining a target business process service from the deployed plurality of business process services that matches the business process service identification based on the obtained business process service identification, the method further comprises:
receiving a service processing service deployment request sent by a service generator, wherein the service processing service deployment request carries service processing services to be deployed;
deploying the service to be deployed based on the service deployment request, and generating a service processing service identifier corresponding to the deployed service processing service;
And sending the business processing service identifier to the service generator.
15. A blockchain-based transaction processing device, the device being configured at a verification node, the device comprising:
a first receiving module configured to receive a verification request from a service processing node; the verification request carries transaction credentials generated by the service processing node aiming at a first execution result of a specified transaction, wherein the first execution result is an execution result of the specified transaction obtained by the service processing node from a blockchain network;
an acquisition module configured to acquire a second execution result matching the specified transaction from a blockchain network based on the verification request;
the verification and generation module is configured to verify a first execution result contained in the transaction credential based on the second execution result and generate a verification credential aiming at the verification result;
and the sending module is configured to send the verification certificate to the service processing node so that the service processing node sends the transaction certificate and the verification certificate to the blockchain network for associated uplink processing.
16. A blockchain-based transaction processing device, the device being configured at a traffic processing node, the device comprising:
the second receiving module is configured to receive a first execution result sent by the blockchain network and aiming at a specified transaction, wherein the first execution result is an execution result of the blockchain network on the specified transaction;
the signature and generation module is configured to sign the first execution result and generate a transaction credential corresponding to the first execution result of the appointed transaction;
the generation and transmission module is configured to generate a verification request based on the transaction credential and transmit the verification request to a verification node, so that the verification node obtains a second execution result matched with the appointed transaction from the blockchain network based on the verification request, verifies a first execution result contained in the transaction credential based on the second execution result, and generates a verification credential aiming at the verification result;
and the receiving and transmitting module is configured to receive the verification credentials from the verification node and transmit the transaction credentials and the verification credentials to the blockchain network so that the blockchain network performs associated uplink processing on the transaction credentials and the verification credentials.
17. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs that, when executed by the electronic device, cause the electronic device to implement the blockchain-based transaction processing method of any of claims 1-14.
18. A computer readable medium having stored thereon a computer program, which when executed by a processor implements the blockchain-based transaction processing method of any of claims 1 to 14.
19. A computer program product comprising computer instructions which, when executed by a processor, implement the blockchain-based transaction processing method of any of claims 1 to 14.
CN202210335863.9A 2022-03-31 2022-03-31 Transaction processing method and device based on blockchain, equipment and medium Pending CN116939011A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210335863.9A CN116939011A (en) 2022-03-31 2022-03-31 Transaction processing method and device based on blockchain, equipment and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210335863.9A CN116939011A (en) 2022-03-31 2022-03-31 Transaction processing method and device based on blockchain, equipment and medium

Publications (1)

Publication Number Publication Date
CN116939011A true CN116939011A (en) 2023-10-24

Family

ID=88375974

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210335863.9A Pending CN116939011A (en) 2022-03-31 2022-03-31 Transaction processing method and device based on blockchain, equipment and medium

Country Status (1)

Country Link
CN (1) CN116939011A (en)

Similar Documents

Publication Publication Date Title
CN107993149B (en) Account information management method, system and readable storage medium
US11811722B2 (en) Method for processing cloud service in cloud system, apparatus, and device
US11716207B1 (en) System and method for a dynamic-PKI for a social certificate authority
CN108769230B (en) Transaction data storage method, device, server and storage medium
US20210192446A1 (en) Anonymity system for goods delivery
CN108876669B (en) Course notarization system and method applied to multi-platform education resource sharing
CN109493052B (en) Cross-chain contract system based on main chain and parallel multiple sub-chains
CN110601896B (en) Data processing method and equipment based on block chain nodes
CN112910660B (en) Certificate issuing method, adding method and transaction processing method of blockchain system
CN107908979B (en) Method and electronic device for configuration and endorsement in blockchain
JP2024505692A (en) Data processing methods, devices and computer equipment based on blockchain networks
CN110992035A (en) Block chain link point management method, device and system
CN114567643B (en) Cross-blockchain data transfer method, device and related equipment
CN112311779B (en) Data access control method and device applied to block chain system
US9800567B2 (en) Authentication of network nodes
CN113129008B (en) Data processing method, device, computer readable medium and electronic equipment
CN111866993B (en) Wireless local area network connection management method, device, software program and storage medium
CN115114630A (en) Data sharing method and device and electronic equipment
CN116939011A (en) Transaction processing method and device based on blockchain, equipment and medium
CN112926981B (en) Transaction information processing method, device and medium for block chain and electronic equipment
CN115098840A (en) Identity authentication method, device, equipment, medium and product
CN116186749A (en) Block chain-based service processing method and device, electronic equipment and readable medium
CN116938484A (en) Transaction processing method and device based on blockchain, equipment and medium
CN118118550A (en) Business processing method, device, equipment and medium based on block chain network
US20230283485A1 (en) Method and device for dynamic public key infrastructure

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination