Block chain verification service management method and system

Abstract

The invention provides a block chain verification service management method and system, a block chain comprises a plurality of block chain nodes, the block chain verification service management system comprises a plurality of shared nodes and a plurality of special nodes, and the shared nodes and the special nodes are used as the block chain nodes; and the shared node stores synchronous data of the block chain. The method comprises the following steps: receiving a user node creation request from a first user, creating at least one special node according to data of a first shared node in a plurality of shared nodes, and using the at least one special node as the user node of the first user; receiving first data from a first user verifying the computing application; second data are generated according to the first data, and the second data comprise the first data, the identifier of the first user and the identifier of the user node; and sending the second data to the plurality of block chain nodes. According to the method and the system, the effectiveness of the user node in the block chain can be remarkably improved.

Description

[0001] This application claims the priority of a Chinese patent application with the application number 202311763697.3 and the invention title "Method and System for Blockchain Pledge" submitted to the China National Intellectual Property Administration on December 20, 2023, the entire content of which is incorporated herein by reference. Technical Field

[0002] This application relates to the field of cloud computing, and more particularly, to a method and system for managing blockchain verification services. Background Art

[0003] Ethereum is a smart contract platform based on blockchain technology. Blockchain nodes in Ethereum can participate in pledge behaviors and become pledge nodes. Specifically, users of Ethereum can verify their identities through validator clients, become verified users, process or verify transaction information in the platform, add new blocks to the blockchain, or verify the validity of newly added blocks, and broadcast the data obtained from the verification calculation application to other nodes in the blockchain through at least one blockchain node.

[0004] Ethereum users usually deploy blockchain nodes, i.e., user nodes, in the user node pool of the cloud service system to accelerate verification calculations, enhance the broadcast coverage speed, and improve the average effectiveness of multiple nodes. Since verification calculation services consume a large amount of computing resources, users usually temporarily create user nodes when they want to participate in pledge behaviors. However, the time required to create user nodes is relatively long, and user nodes may be unavailable during the target period. In addition, in Ethereum, the software architecture of each node needs to be periodically maintained and upgraded to keep its functions consistent with the protocols in the entire blockchain. If, during the execution of verification calculation services, situations such as the software architecture maintenance and upgrade of user nodes occur, it will also cause user nodes to be unavailable during the target period. Summary of the Invention

[0005] This application provides a method and system for managing blockchain verification services, aiming to improve the effectiveness of user nodes in the blockchain.

[0006] In a first aspect, an embodiment of the present application provides a method for managing blockchain verification services. The blockchain includes multiple blockchain nodes. This method is used for a blockchain verification service management system, which includes multiple shared nodes and multiple dedicated nodes. The shared nodes and dedicated nodes serve as blockchain nodes. The shared nodes store the synchronized data of the blockchain. The method includes: receiving a user node creation request from a first user, creating at least one dedicated node according to the data of a first shared node among the multiple shared nodes, and using the at least one dedicated node as the user node of the first user; receiving first data of a verification computing application from the first user; generating second data according to the first data, where the second data includes the first data, the identifier of the first user, and the identifier of the user node; and sending the second data to the multiple blockchain nodes.

[0007] The blockchain verification service management system provided by the embodiment of the present application includes multiple shared nodes, and the shared nodes store the synchronized data of the blockchain, which can improve the creation speed of user nodes, thereby improving the effectiveness of users in performing verification tasks.

[0008] In a possible implementation manner of the first aspect, generating second data according to the first data includes: during the process of generating the second data, if the user node is available, the user node generates the second data according to the first data.

[0009] In a possible implementation manner of the first aspect, generating second data according to the first data includes: during the process of generating the second data, if there is a first period when the user node is unavailable, within the first period, the first shared node generates a part of the second data according to the first data; within a second period when the user node is available, the user node generates another part of the second data according to the first data; where the second data includes the first data, the identifier of the first user, the identifier of the user node, and the identifier of the first shared node.

[0010] In such an implementation manner, the first shared node can temporarily replace the unavailable user node to execute the verification computing service. Whether the user node is available or not, the entire blockchain verification service management system can continuously receive the first data, improving the broadcast efficiency and reliability of the first data.

[0011] In a possible implementation manner of the first aspect, the user node being unavailable includes: the user node is in the creation process, or the user node is in the upgrade and maintenance process.

[0012] The technical solution of the embodiment of the present application covers various situations where the user node is unavailable, and the blockchain verification service management system is stable and reliable.

[0013] In a possible implementation of the first aspect, the blockchain verification service management system further includes a verification computing application interface that receives first data from a verification computing application of a first user, including: the verification computing application interface receives first data from the verification computing application; the method further includes: if the user node is available, the verification computing application interface sends the first data to the user node; if the user node is unavailable, the verification computing application interface sends the first data to the first shared node.

[0014] Deploying a verification computing application interface in the blockchain verification computing service management system enables the verification computing application not to perform complex calculations to determine the node for receiving the first data, and the first shared node also does not need to perform complex calculations to determine whether it is used to receive the first data in each period, reducing the complexity of the entire system.

[0015] In a possible implementation of the first aspect, multiple shared nodes are deployed in multiple regions and send second data to multiple blockchain nodes, including: sending second data to a second shared node, where the second shared node is a shared node located in the same region as the user node; the second shared node sends the second data to multiple blockchain nodes.

[0016] In such an implementation, the user node can broadcast the second data in this region through the shared node in the same region.

[0017] In a possible implementation of the first aspect, the second shared node sending second data to multiple blockchain nodes includes: the second shared node sending the second data to a third shared node in the region where the target blockchain node is located; the third shared node sending the second data to the target blockchain node.

[0018] In such an implementation, the shared node is used to broadcast verification data to external blockchain nodes, increasing the broadcast coverage, reducing the broadcast delay, and reducing the traffic consumption of the user node, which can significantly improve the success rate of the user node in performing verification computing tasks.

[0019] In a possible implementation of the first aspect, the blockchain verification service management system further includes a verification computing application interface, and the second shared node sending second data to multiple blockchain nodes includes: the second shared node sending the second data to multiple blockchain nodes through the verification computing application interface.

[0020] In such an implementation, the user node can make full use of the network performance between multiple verification computing application interfaces to broadcast the second data to multiple shared nodes, reducing the delay of internal broadcast of the second data.

[0021] In a possible implementation of the first aspect, the blockchain verification service management system further includes a human-computer interaction interface, which is used to deploy a plurality of shared nodes and a plurality of dedicated nodes; the method includes: the human-computer interaction interface receives a user node creation request from a first user; upon completion of the creation of the user node, a creation success response is output to the first user.

[0022] The human-computer interaction interface can receive a user node creation request from a user or receive configuration information set by an administrator, making the blockchain verification service management system easy to maintain.

[0023] In a second aspect, an embodiment of the present application provides a blockchain verification service management system, where the blockchain includes a plurality of blockchain nodes; the blockchain verification service management system includes a plurality of shared nodes and a plurality of dedicated nodes, and the shared nodes and the dedicated nodes are used as blockchain nodes; the shared nodes store synchronization data of the blockchain; the blockchain verification service management system is configured to: receive a user node creation request from a first user, create at least one dedicated node according to the data of a first shared node among the plurality of shared nodes, and the at least one dedicated node is used as the user node of the first user; receive first data of a verification computing application from the first user; generate second data according to the first data, where the second data includes the first data, an identifier of the first user, and an identifier of the user node; and send the second data to the plurality of blockchain nodes.

[0024] In a possible implementation of the second aspect, during the process of generating the second data, if the user node is available, the user node is used to generate the second data according to the first data.

[0025] In a possible implementation of the second aspect, during the process of generating the second data, if there is a first period when the user node is unavailable, within the first period, the first shared node is used to generate a part of the second data according to the first data; within a second period when the user node is available, the user node is used to generate another part of the second data according to the first data; where the second data includes the first data, an identifier of the first user, an identifier of the user node, and an identifier of the first shared node.

[0026] In a possible implementation of the second aspect, the unavailability of the user node includes: the user node is in the creation process, or the user node is in the upgrade and maintenance process.

[0027] In a possible implementation of the second aspect, the blockchain verification service management system further includes a verification computing application interface, which is used to: receive first data from the verification computing application; if the user node is available, send the first data to the user node; if the user node is unavailable, send the first data to the first shared node.

[0028] In a possible implementation of the second aspect, multiple shared nodes are deployed in multiple regions, and the user node and / or the first shared node are used to send second data to the second shared node, where the second shared node is a shared node in the same region as the user node; the second shared node is used to send the second data to multiple blockchain nodes.

[0029] In a possible implementation of the second aspect, the second shared node is used to send the second data to a third shared node in the region where the target blockchain node is located; the third shared node is used to send the second data to the target blockchain node.

[0030] In a possible implementation of the second aspect, the blockchain verification service management system further includes a verification computing application interface, and the second shared node is used to send the second data to multiple blockchain nodes through the verification computing application interface.

[0031] In a possible implementation of the second aspect, the blockchain verification service management system further includes a human-computer interaction interface, and the human-computer interaction interface is used to: deploy multiple shared nodes and multiple dedicated nodes; and send a creation success response to the first user when the user node is successfully created.

[0032] In a third aspect, an embodiment of the present application provides a computing device cluster, including at least one computing device, and each computing device includes a processor and a memory; the processor of the at least one computing device is used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any implementation manner of the first aspect.

[0033] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, including computer program instructions, and when the computer program instructions are executed by the blockchain verification service management system, the blockchain verification service management system executes the method according to any implementation manner of the first aspect.

[0034] In a fifth aspect, an embodiment of the present application provides a computer program product, and when the computer program product runs on the blockchain verification service management system, the blockchain verification service management system is enabled to execute the method according to any implementation manner of the first aspect. Description of the Drawings

[0035] Figure 1 is a schematic diagram of an application scenario of an embodiment of the present application.

[0036] Figure 2 is a schematic block diagram of a blockchain verification service management system according to an embodiment of the present application.

[0037] Figure 3It is a schematic block diagram of a blockchain verification service management system according to an embodiment of the present application.

[0038] Figure 4 It is a schematic block diagram of a human - machine interaction interface of a blockchain verification service management system according to an embodiment of the present application.

[0039] Figure 5 It is a schematic flowchart of a blockchain verification service management method according to an embodiment of the present application.

[0040] Figure 6 It is a schematic flowchart of receiving verification data according to an embodiment of the present application.

[0041] Figure 7 It is a schematic block diagram of a verification data application interface according to an embodiment of the present application.

[0042] Figure 8 It is a schematic flowchart of a user node sending second data to a second shared node in an embodiment of the present application.

[0043] Figure 9 It is a schematic block diagram of a blockchain pledge device according to an embodiment of the present application.

[0044] Figure 10 It is a schematic block diagram of a controller according to an embodiment of the present application. Detailed implementation manners

[0045] The present application will present various aspects, embodiments or features around a system including multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in connection with the accompanying drawings. In addition, combinations of these solutions may also be used.

[0046] In addition, in the embodiments of the present application, words such as "exemplary", "for example", etc. are used to indicate examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of the word "exemplary" is intended to present concepts in a specific manner.

[0047] In the embodiments of the present application, "corresponding" and "corresponding" can sometimes be used interchangeably. It should be noted that when not emphasizing their differences, the meanings they convey are the same.

[0048] This embodiment involves some new functional modules or units divided by function or logic, such as a validating hub (VH) and its sub-modules. As is known to those of ordinary skill in the art, with the evolution of network architectures and the emergence of new service scenarios, modules or units with similar functions and definitions may have different names, and the difference in names should not be regarded as a limitation to the technical solution of this application.

[0049] The service scenarios described in the embodiments of this application are for more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation to the technical solutions provided by the embodiments of this application. As is known to those of ordinary skill in the art, with the evolution of network architectures and the emergence of new service scenarios, the technical solutions provided by the embodiments of this application are equally applicable to similar technical problems.

[0050] The following briefly introduces the commonly used technical terms in this field.

[0051] Cloud computing is a computing model that provides dynamically scalable virtualized resources in the form of services through a network. Platform as a service (PaaS) is one of the main multi-tenant models of cloud computing. Different tenants will be registered on the PaaS platform and use the resources and services of the PaaS platform. The shared cloud services of the PaaS platform can provide blockchain as a service (BaaS) for public cloud tenants.

[0052] In the field of cloud computing, regions and availability zones (AZs) are concepts used to divide data centers and server resources. A region refers to a geographical area that usually contains multiple data centers, and each data center contains multiple AZs. Each AZ is usually an independent data center with its own power, network, and physical equipment. For example, global regions can be divided into Asian regions, American regions, European regions, and domestic regions can be divided into East China regions, North China regions, Central China regions, etc.

[0053] Blockchain refers to a distributed database technology in which multiple nodes in a peer-to-peer network jointly maintain a continuously growing chain list ledger constructed by timestamps and ordered data blocks through a consensus mechanism designed based on cryptographic technologies. In this technical solution, any number of blockchain nodes participating in the blockchain calculate and record all the data exchanged within the system for a period of time through cryptographic algorithms into a data block, and generate the fingerprint of the data block for linking and verifying the next data block. All nodes in the system jointly verify the authenticity and validity of the data.

[0054] The block height refers to the height of the latest block that has been confirmed on the blockchain network. Whenever a new block is added to the blockchain, the block height increases. Therefore, the block height can be used to represent the current state and progress of the blockchain network. When a node is running properly and synchronized with the blockchain network, it continuously receives new blocks and updates its block height. Therefore, by checking the block height of a node, it can be determined whether the node is running properly and synchronized with the network. If a node has not updated its block height for a long time, or there is a significant deviation between its block height and that of other nodes, it may indicate that the node has a problem and is unable to run properly or has lost connection with the network, that is, it is in an unavailable state.

[0055] A general PoS chain refers to a blockchain network based on the proof of stake (PoS) consensus mechanism, and its main feature is that it can support various types of applications and smart contracts. Ethereum is a blockchain based on a general PoS chain. In Ethereum, a new block is generated in each time slot. Blockchain nodes in Ethereum can participate in the staking behavior and become staking nodes. Specifically, Ethereum users have digital signatures, verification computing clients, and multiple verification nodes. They can verify their identities through the validator client and become verified users. Subsequently, the verified users process or verify transaction information in the platform through multiple validators in the validator client, add new blocks to the blockchain, or verify the validity of newly added blocks, and broadcast the data obtained by the validators to other nodes in the blockchain through at least one blockchain node.

[0056] In the embodiments of the present application, users participating in the staking behavior can be referred to as verified users or staking users, participating in the staking behavior can be referred to as performing verification services, the data obtained by processing or verification can be referred to as staking data or verification data, the nodes performing verification services can be referred to as staking nodes or user nodes, and the verification computing application can be referred to as a validator. The mixed use of specific names should not be regarded as a limitation to the technical solution of the present application. The subsequent embodiments use Ethereum as an example to illustrate methods, devices, systems, etc. applied to general PoS chains, and should not be understood as a limitation to the technical solution of the present application.

[0057] Specifically, the selection rule of staking nodes in Ethereum is determined by randomness. Ethereum uses the RANDAO algorithm to achieve randomness. This algorithm mixes a hash value from the block proposer with a seed that is updated with each block to generate a random number, which is used to select a specific staking node among all staking nodes to perform verification services. Therefore, activities in the blockchain system usually involve global regions.

[0058] Specifically, a blockchain node can be hardware, virtual hardware, or a container, and each blockchain node has an IP address and a digital signature. As Figure 1 shown, multiple verification computing clients can obtain the latest data of the current blockchain from at least one arbitrary node in the blockchain, perform specific verification calculations, and send the verification data to multiple user nodes. The multiple user nodes respectively broadcast the verification data to most nodes in the blockchain to prove the effectiveness of the staking behavior. Among them, a verification user can deploy a verification computing client for each user node, and each verification computing client includes multiple verification computing applications that can perform parallel computing to accelerate the speed of verification computing.

[0059] Ethereum users usually deploy blockchain nodes, that is, user nodes, in the user node pool of the cloud service system to accelerate verification computing, enhance the broadcast coverage speed, and improve the average effectiveness of multiple nodes. Since the verification computing service consumes a large amount of computing resources, users usually temporarily create user nodes when they want to participate in the staking behavior. However, the time required to create user nodes is relatively long, and the user nodes may be unavailable during the target period. In addition, in Ethereum, the software architecture of each node needs to be periodically maintained and upgraded to keep its functions consistent with the protocols in the entire blockchain. If the software architecture of the user node is maintained and upgraded during the execution of the verification computing service, etc., it will also cause the user node to be unavailable during the target period.

[0060] Furthermore, if all user nodes are located in the same region, it may lead to high network latency for broadcasting data to other regions, low data transmission traffic, and message loss (miss) by most nodes in other regions during the current time slot, resulting in multiple verification task failures and low effectiveness of the nodes in the blockchain. At the same time, user nodes need to broadcast verification data to all nodes in the blockchain in each time slot, consuming a large amount of traffic.

[0061] In view of this, the embodiments of the present application provide a blockchain verification service management method and system to improve the effectiveness of user nodes in the blockchain.

[0062] Next, in combination with Figure 2 describe a blockchain verification service management system provided by the present application. As Figure 2 shown, the blockchain includes multiple blockchain nodes. The blockchain verification service management method is used for the system. The node pool of the blockchain verification service management system includes multiple shared nodes and multiple user nodes, and the shared nodes and user nodes are used as blockchain nodes. Among them, each shared node pool periodically synchronizes the blockchain data in the external blockchain nodes and stores it in its own storage device.

[0063] In some embodiments, instead of directly sending verification data to the user node, the verification computing client sends the verification data to the verification computing application interface. When the user node is available, the verification computing application interface sends the verification data to the user node; when the user node is unavailable, for example, the user node is in the creation process or in the upgrade and maintenance process, the verification computing application interface sends the verification data to the shared node, and the shared node serves as the user node. In addition, the latest blockchain data can be directly obtained from the shared node for initializing the user node, improving the creation speed of the user node.

[0064] The blockchain verification service management system provided by the embodiments of the present application includes multiple shared nodes. The shared nodes store the synchronized data of the blockchain, which can improve the creation speed of the user node, thereby improving the effectiveness of the user to execute the verification task.

[0065] The above solution is applicable to the scenario of establishing a single node pool in the area where the user node is located. This solution can also be further extended to establish multiple node pools in multiple regions, improving the availability of the user node in multiple regions, and more precisely managing the user node and the shared node. The following combines Figure 3 The schematic block diagram of the blockchain verification service management system shown to illustrate the logical relationship of some entities in a blockchain verification service management system of this embodiment.

[0066] The embodiments of the present application provide a blockchain verification service management system with data centers in multiple regions. It should be understood that the regions in the present application mainly refer to regions globally. The administrator of the blockchain verification service management system can configure in the system to create multiple blockchain nodes respectively in multiple hosts / virtual machines / containers in each region. The blockchain nodes can be virtual machines / containers and are deployed in the data center. Specifically, the blockchain nodes described in this embodiment can be divided into shared nodes and dedicated nodes. Multiple shared nodes are deployed in the data center of each region, and multiple dedicated nodes are deployed in the data center of at least one region. Among them, both the shared node and the dedicated node include a software layer and a storage device, and the dedicated node includes a software layer and a dynamic capacity storage device.

[0067] Furthermore, all the shared nodes in each region are grouped together to form a shared node pool in each region respectively; all the dedicated nodes in each region are grouped together to form a dedicated node pool in at least one region respectively.

[0068] In one embodiment, as Figure 4As shown in the figure, the blockchain verification service management system includes a human-computer interaction interface, and the human-computer interaction interface includes an administrator interface. The administrator of the blockchain verification service management system can, through the administrator interface, deploy a shared node pool and a dedicated node pool, or manage the shared node pool and the dedicated node pool deployed in each region. Specifically, the division method of the region can be changed, the number of shared nodes or dedicated nodes can be adjusted, and the memory resources, storage capacity, network bandwidth, etc. of the nodes can be set.

[0069] The following combines Figure 5 The schematic flowchart shown in the figure to illustrate the process of the blockchain verification service management method.

[0070] S510, receive a user node creation request from a user, and create at least one dedicated node to be used as a user node according to the data of the first shared node among multiple shared nodes.

[0071] When a user wants to create a user node and participate in the pledge behavior of the blockchain, a request to create a user node is made in the blockchain verification service management system. The blockchain verification service management system creates a dedicated node in the dedicated node pool in at least one region as the user node. That is to say, the dedicated node pool can include user nodes of multiple different users.

[0072] It should be understood that each node in the blockchain periodically obtains the latest blockchain data at the current moment from other nodes and stores the synchronized data of the blockchain to ensure the consistency of data among nodes. The period of this synchronized data can be described by a period and a slot. Specifically, a period includes multiple slots. According to the protocol regulations of the blockchain, some data needs to be synchronized in each slot, while some other data only needs to be synchronized in each period, and each node needs to perform at least one synchronization within each period.

[0073] For ease of description, in this application, the shared nodes or dedicated nodes in the blockchain verification service management system are referred to as internal nodes, and the other blockchain nodes outside the blockchain verification service management system are referred to as external nodes. In addition, in the following embodiments, an example is given where the duration of a period is 384 seconds and the duration of a slot is 12 seconds.

[0074] In the blockchain verification service management system, each shared node pool periodically synchronizes the blockchain data in external nodes respectively. Among them, each node in a shared node pool has the same data synchronization period, but different data synchronization times. In one embodiment, the synchronization period of a shared node pool is the duration of a time period, i.e., 384 seconds. Some shared nodes synchronize at the 384K + 12th second, some shared nodes synchronize at the 384K + 24th second, and some shared nodes synchronize at the 384K + 36th second, where K is a natural number, and so on. When the number of shared nodes in the shared node pool is greater than or equal to 32, at least one shared node's data in the shared node pool is consistent with the latest blockchain data of the external nodes in the current time slot. These shared nodes store the latest synchronized data of the blockchain and are called the first shared nodes.

[0075] Optionally, after each data synchronization, the shared node can store the successfully obtained blockchain data in the backup data storage to further improve data security.

[0076] In one embodiment, the blockchain verification service management system creates a user node at the 384K + 15th second, and the user node can be initialized with the blockchain data at the 384K + 12th second in the shared node pool of the current region.

[0077] Multiple shared nodes in the shared node pool synchronize the blockchain data in different time slots of the blockchain time period. The blockchain verification service management system can create a user node according to the latest blockchain data in the shared node pool of the current region, with low latency and high effectiveness for the initialization operation.

[0078] In one embodiment, as Figure 4 shown, the human-computer interaction interface of the blockchain verification service management system includes a user interface. The user can initiate a user node creation request through the user interface, perform upgrade and maintenance on the user node, view the log, or access the user node to view various information in the blockchain. Each user manages their own user node respectively. For example, user 411 can manage user node 421, and user 412 can manage user node 422.

[0079] Furthermore, the blockchain verification service management system outputs a creation success response to the user when the user node creation is completed.

[0080] The human-computer interaction interface can receive the user node creation request from the user or receive the configuration information set by the administrator, making the blockchain verification service management system easy to maintain.

[0081] S520, Receive the first data from the verification computing application.

[0082] In one embodiment, a validating hub (VH) is deployed in a blockchain verification service management system. The VH can be used to receive first data from a validation computing application, send the first data to a user node and / or a first shared node, receive data from a validation computing application interface, or send data to a validation computing application interface.

[0083] Specifically, the VH is a module with high-performance network communication components and can forward a large amount of data. For example, it can receive first data from multiple validation computing clients simultaneously and forward it to a specified internal node. It should be understood that the above components and modules are only a logical division and can be software, hardware, or a combination of software and hardware.

[0084] It should be understood that the validation computing application in the validation computing client needs to obtain the current latest blockchain data for validation computing. In one embodiment, the validation computing client can obtain blockchain data from an internal node in the area where the VH is located through the VH; in another embodiment, the validation computing client can obtain blockchain data through an external node that has already established a connection. For the convenience of description, in subsequent embodiments, the validation computing application and the validation computing client will not be distinguished, and the validation computing application will be used for unified description.

[0085] In the embodiments of the present application, the validation computing application and the VH establish a long connection, and the VH provides high reliability for the long connection. A long connection means that after a connection is established between two communication parties, the connection state is maintained for a period of time, and multiple data transmissions are carried out. In a long connection, once the connection is established, the two communication parties can send and receive data at any time without having to re-establish the connection for each communication.

[0086] For the convenience of description, the connection between the validation computing application and the VH is called an external connection, and the connection between the internal node and the VH is called an internal connection.

[0087] S521, when the user node is available, the user node receives first data from the validation computing application.

[0088] In the foregoing embodiment, the process of creating a user node takes several minutes. If the first user node is in a state where it has not been created yet, it is considered that the first user node is unavailable. In addition, if the software layer of the first user node is under maintenance and upgrade, it is also considered that the first user node is unavailable.

[0089] For the convenience of description, the VH in the same area as the validation computing application is called the first validation computing application interface, and the VH in the same area as the user node is called the second validation computing application interface. The following combines Figure 6 The schematic flowchart shown is used to elaborate on the reception of the first data in detail.

[0090] In one embodiment, as shown in (a) of Figure 6 , the second verification calculation application interface receives the first data from the verification calculation application, and the second verification calculation application interface sends the first data to the first user node.

[0091] In one embodiment, as shown in (b) of Figure 6 , the first verification calculation application interface receives the first data from the verification calculation application, the second verification calculation application interface receives the first data from the first verification calculation application interface, and the second verification calculation application interface sends the first data to the first user node.

[0092] In such an implementation, the network quality between the verification calculation application and the first verification calculation application interface is high, and the network performance between multiple verification calculation application interfaces can be fully utilized to improve the rate of sending the first data internally.

[0093] In the above embodiment, when the first user node is available, VH sends the first data to the first user node. However, in some embodiments, when the first user node is in an available state, the first user node receives the first data directly sent by the verification calculation application to the first user node, and VH in the blockchain verification service management system is optional.

[0094] S522, when the user node is unavailable, the first shared node receives the first data from the verification calculation application.

[0095] In some embodiments, the shared node pool in each region includes at least one first shared node, and the first shared node can be used as the second user node. Specifically, when the second user node is unavailable, VH in the same region as the second user node analyzes the working states of all shared nodes in this region, selects a first shared node according to specific rules, switches the network traffic for transmitting the first data from the unavailable second user node to this first shared node, so that the first shared node replaces the second user node to receive the first data, and performs other functions of the second user node, such as synchronizing blockchain data, providing access to the blockchain browser for users, etc.

[0096] Specifically, selecting the first shared node according to specific rules can be to select the first shared node with the lowest current workload among all first shared nodes in the current region, where the workload includes parameters such as memory usage rate and network traffic usage rate; it can also be to select the first shared node in the same AZ as the user node; it can also be to select the first shared node in the current region with higher validity in the blockchain, or to select the first shared node according to the block height of multiple shared nodes, etc. This embodiment does not limit this.

[0097] In the above embodiments, when the second user node is unavailable, the VH sends the first data to the first shared node. However, in some embodiments, when the second user node is in an unavailable state, the first shared node receives the first data directly sent by the verification computing application to the first shared node, and the VH in the blockchain verification service management system is optional.

[0098] Furthermore, the availability of the second user node can be confirmed by detecting the block height.

[0099] Furthermore, the VH can switch the network traffic for transmitting the first data from the unavailable user node to the first shared node through methods such as message queue, heartbeat detection, and service registration and discovery.

[0100] It should be understood that the process of the verification computing application sending the first data to the first shared node is similar to the process of sending the first data to the first user node.

[0101] It should be understood that when the second user node resumes availability, the VH can switch the network traffic for transmitting the first data from the first shared node to the second user node, enabling the second user node to continue receiving the first data.

[0102] In some embodiments, if the VH is not set up in the blockchain verification service management system, steps such as selecting the first shared node, determining the availability of the second user node, and switching network traffic can be implemented by other network management systems deployed by users.

[0103] In some embodiments, when the second user node is available, the first shared node can also receive the first data from the verification computing application. For example, if the network bandwidth of the second user node is small or the computing resources are scarce, and it takes a long time to independently complete the verification computing task while there are many idle first shared nodes, the first shared node can also jointly execute the verification computing task with the second user node.

[0104] Deploy a verification computing application interface in the blockchain verification computing service management system, so that the verification computing application does not need to perform complex calculations to determine the node for receiving the first data, and the first shared node does not need to perform complex calculations to determine whether to receive the first data in each period, reducing the complexity of the entire system.

[0105] In such an implementation manner, the first shared node can temporarily replace an unavailable user node to execute the verification calculation service. Whether the user node is available or not, the entire blockchain verification service management system can continuously receive the first data, improving the broadcast efficiency and reliability of the first data.

[0106] S530. Generate second data based on the first data.

[0107] The first data is the data obtained by the user's verification calculation application, including the user's digital signature and excluding the digital signature of the blockchain node. The user node needs to send the first data to the user node for further conversion and processing to generate the second data, such as appending the digital signature of the user node, modifying the timestamp, etc., and then broadcast the second data to most nodes in the blockchain.

[0108] Specifically, the first data can be the data to be verified generated in the blockchain system, such as the input parameters of a smart contract, a transaction request, or other relevant information. The second data can be the result data after calculation, verification, or processing, such as the execution result of a smart contract, the confirmation information of a transaction, or other relevant data, which is used to update the state of the blockchain network or execute the logic of the smart contract.

[0109] S531. If the user node is available, the user node generates the second data based on the first data.

[0110] It should be understood that each blockchain node has a corresponding digital signature. If the user node is available throughout the process of generating the second data, the finally obtained second data includes the user's digital signature and the digital signature of the user node. It should be understood that the digital signature is a type of identifier.

[0111] S532. If there is a period when the user node is unavailable, the user node and the first shared node respectively generate a part of the second data based on the first data.

[0112] Specifically, during the process of generating the second data, if there is a first period when the user node is unavailable, within the first period, the first shared node generates a part of the second data based on the first data; within the second period when the user node is available, the user node generates another part of the second data based on the first data. Among them, the second data includes the digital signature of the user node and the digital signature of the first shared node.

[0113] S540. Send the second data to an external node.

[0114] This embodiment takes the user node as an example to illustrate the process of sending the second data to an external node. It should be understood that the functions performed by the user node in this embodiment can also be completed by the first shared node. In the subsequent embodiments, the meanings of "broadcast" and "send" are similar and can be used interchangeably, which does not constitute a limitation to the technical solution of this application.

[0115] S541, Obtain the information of the external node.

[0116] In one embodiment, the shared node pool in each region periodically obtains the information of the external nodes in this region. The external nodes in this application refer to the external nodes obtained through this periodic acquisition.

[0117] Specifically, the information of the external nodes in this region can be periodically obtained through a blockchain browser, node public information, or a node discovery protocol. Some blockchain browsers provide the IP address information of nodes. By viewing the node information on the blockchain browser, the IP address information of some nodes can be obtained; some nodes may publicly disclose their IP address information through official websites or social media accounts; some blockchain networks use a node discovery protocol to help nodes discover and connect to each other. By participating in the node discovery protocol, the IP address information of some nodes can be obtained.

[0118] S542, The user node and / or the first shared node send the second data to the second shared node.

[0119] In one embodiment, multiple shared nodes are respectively selected from each shared node pool for sending the second data to the external node. Among them, the second shared node is a shared node located in the same region as the user node, and the second shared node is used to send the second data to the external node.

[0120] In another embodiment, as Figure 7 shown, the verification computing application interface includes an external connection module, a shared node routing module, and a dedicated node routing module. Specifically, the external connection module is used to receive the first data from the verification computing application, receive the data from a VH, or send data to a VH; the shared node routing module is used to send the first data or the second data to the shared node, and the dedicated node routing module is used to send the first data to the user node, or receive the second data sent by the user node.

[0121] Furthermore, the administrator of the blockchain verification service management system can configure the parameters of the above-mentioned modules through a human-computer interaction interface.

[0122] The user node needs to send the second data to the second shared node, so that the second shared node broadcasts the second data to the external node. First, in combination with Figure 8The schematic flowchart shown illustrates the process of a user node sending second data to a second shared node.

[0123] In some embodiments, as Figure 8 shown in (a) of

[0124] the user node sends second data to the second shared node, and the second shared node sends the second data to an external node.

[0125] In some embodiments, as Figure 8 shown in (b) of

[0126] Secondly, the process of the user node sending second data to a third shared node is described in conjunction with Figure 8 where the third shared node is a shared node in a different region from the user node and is used to send the second data to an external node. In some embodiments, as Figure 8 shown in (a) of

[0127] the third verification calculation application interface receives the second data from the second verification calculation application interface and sends the second data to the third shared nodes in the region to which the target blockchain node belongs. Among them, the third verification calculation application interface is a verification calculation application interface in a different region from the second verification calculation application interface.

[0128] In such an implementation, the user node can make full use of the network performance between multiple verification calculation application interfaces to broadcast the second data to multiple shared nodes, reducing the latency of internally broadcasting the second data.

[0129] In some embodiments, if VH is not set in the blockchain verification service management system, the user node can directly broadcast the second data to all second shared nodes.

[0130] S543, the second shared node sends the second data to an external node.

[0131] In some embodiments, as Figure 8 shown in (a) of

[0132] In such an implementation manner, the shared nodes are used to broadcast verification data to external blockchain nodes, increasing the broadcast coverage, reducing the broadcast delay, and reducing the traffic consumption of user nodes, which can significantly improve the success rate of user nodes in performing verification calculation tasks.

[0133] S544, the user node sends the second data to an external node.

[0134] In some embodiments, the user node directly sends the second data to an external node. When a large number of shared nodes in some regions are unavailable due to failures or cyberattacks, etc., the user node can still send the second data to the external nodes in these regions according to the obtained external node information.

[0135] The blockchain verification service management system provided by the embodiments of the present application deploys a shared node pool including a plurality of shared nodes pre-created in multiple regions. The shared nodes are used to accelerate the creation of user nodes and temporarily replace unavailable user nodes to perform verification calculation services; the shared nodes are also used to broadcast verification data to external blockchain nodes, increasing the broadcast coverage, reducing the broadcast delay, and reducing the traffic consumption of user nodes. These two functions can significantly improve the effectiveness of user nodes in the blockchain.

[0136] Figure 9 It is a schematic block diagram of the device for blockchain verification service management according to the embodiments of the present application. Figure 9 The shown device 900 can be used to execute the method for blockchain verification service management of the present application.

[0137] As Figure 9 shown, the device includes an acquisition unit 910, a processing unit 920, and an output unit 930. The term "unit" here can be implemented in the form of software and / or hardware, and no specific limitation is made thereto.

[0138] For example, the "unit" can be a software program, a hardware circuit, or a combination of the two that implements the above functions, and can include code running on a computing instance. Exemplarily, next, taking the processing unit as an example, the implementation manner of the processing unit will be introduced. Similarly, the implementation manners of the acquisition unit and the output unit can refer to the implementation manner of the processing unit.

[0139] Specifically, the processing unit may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers for running this code may be distributed in the same region or in different regions. Further, the multiple hosts / virtual machines / containers for running this code may be distributed in the same availability zone (AZ) or in different AZs. Each AZ includes one data center or multiple geographically proximate data centers. Usually, one region may include multiple AZs.

[0140] Similarly, the multiple hosts / virtual machines / containers for running this code may be distributed in the same virtual private cloud (VPC) or in multiple VPCs. Usually, one VPC is set within one region. For cross-region communication between two VPCs within the same region and between VPCs in different regions, a communication gateway needs to be set in each VPC, and the interconnection between VPCs is achieved through the communication gateway.

[0141] As an example of a hardware functional unit, the processing unit may include at least one computing device, such as a server, etc. Alternatively, the processing unit may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). Among them, the above PLD may be implemented by a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0142] The multiple computing devices included in the processing unit may be distributed in the same region or in different regions. The multiple computing devices included in the processing unit may be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the processing unit may be distributed in the same VPC or in multiple VPCs. Among them, the multiple computing devices may be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0143] Therefore, the modules of the examples described in the embodiments of the present application can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0144] The present application also provides a controller 1000. As Figure 10 shown, the controller 1000 includes: a processor 1004 and a communication interface 1008. Further, the controller 1000 may also include a bus 1002 and a memory 1006. It should be understood that the bus 1002 and the memory 1006 are optional. The processor 1004, the memory 1006, and the communication interface 1008 communicate through the bus 1002. Exemplarily, the controller 1000 may be a computing device or a device in a computing device for implementing the method of the embodiments of the present application. The controller 1000 may be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in the controller 1000.

[0145] The bus 1002 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 10 only one line is shown in the figure, but it does not mean that there is only one bus or one type of bus. The bus 1004 may include a path for transmitting information between various components of the controller 1000 (for example, the memory 1006, the processor 1004, the communication interface 1008).

[0146] The processor 1004 may include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0147] The memory 1006 may include volatile memory, such as random access memory (RAM). The memory 1006 may also include non-volatile memory, such as read-only memory (ROM), flash memory, a hard disk drive (HDD), or a solid state drive (SSD).

[0148] The executable program code is stored in the memory 1006, and the processor 1004 executes the executable program code to respectively implement the functions of the aforementioned acquisition unit and processing unit, thereby implementing the method for blockchain verification service management. That is, instructions for the method for blockchain verification service management are stored on the memory 1006.

[0149] The communication interface 1008 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the controller 1000 and other devices or a communication network (for example, multiple servers). The communication interface may also be referred to as an interface circuit.

[0150] The embodiment of the present application also provides a cluster of computing devices. The cluster of computing devices includes the controller 1000 and multiple computing devices. The computing devices may be servers, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing devices may also be terminal devices such as a desktop computer, a laptop computer, or a smart phone. The multiple computing devices may be the multiple servers described above. The cluster of computing devices can be used to implement a blockchain verification service management system.

[0151] In a possible implementation manner, the controller 1000 is one of the multiple computing devices or a device in the computing devices for implementing the method described above.

[0152] In another possible implementation manner, the controller 1000 is a computing device other than the multiple computing devices or a device in other computing devices for implementing the method described above.

[0153] The embodiment of the present application also provides a computer program product containing instructions. The computer program product may be software or a program product containing instructions that can run on a computing device or be stored in any available medium. When the computer program product runs on at least one computing device, at least one computing device is caused to execute the method in the embodiment of the present application.

[0154] Embodiments of the present application also provide a computer-readable storage medium. The computer-readable storage medium may be any available medium that can be stored by a computing device or a data storage device such as a data center that includes one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid state drives), etc. The computer-readable storage medium includes instructions that direct the computing device to execute the methods in the embodiments of the present application, or direct the computing device to execute the methods in the embodiments of the present application.

[0155] It should be understood that in various embodiments of the present application, the magnitudes of the sequence numbers of the above processes do not mean the order of execution is prior or posterior. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0156] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0157] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be described in detail herein.

[0158] In several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in an electrical, mechanical, or other form.

[0159] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0160] In addition, in each embodiment of the present application, each functional unit can be integrated into one processing unit, can exist physically alone for each unit, or two or more units can be integrated into one unit.

[0161] If the above-mentioned function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0162] The above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed in the present application should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A blockchain verification service management method, characterized in that: The blockchain includes a plurality of blockchain nodes; the method is used for a blockchain verification service management system, the blockchain verification service management system includes a plurality of shared nodes and a plurality of dedicated nodes, the shared nodes and the dedicated nodes are used as blockchain nodes; The shared node stores synchronization data of the blockchain; The method comprises: receiving a user node creation request from a first user, and creating at least one dedicated node according to data of a first shared node among the plurality of shared nodes, wherein the at least one dedicated node is used as a user node of the first user; receiving first data from a verification computing application of the first user; generating second data according to the first data, wherein the second data includes the first data, an identifier of the first user, and an identifier of the user node; Send the second data to the multiple blockchain nodes.

2. The method according to claim 1, characterized in that: The generating second data according to the first data comprises: In the process of generating the second data, if the user node is available, the user node generates the second data according to the first data.

3. The method according to claim 1 or 2, characterized in that: The generating second data according to the first data comprises: In the process of generating the second data, if there is a first period of time during which the user node is unavailable, the first sharing node generates a part of the second data according to the first data during the first period of time; During a second time period in which the user node is available, the user node generates another part of the second data based on the first data; wherein the second data includes the first data, an identifier of the first user, an identifier of the user node, and an identifier of the first shared node.

4. The method according to claim 3, characterized in that The user node is unavailable, including: The user node is in the process of being created, or the user node is in the process of being upgraded and maintained.

5. The method according to any one of claims 1 to 4, characterized in that The blockchain verification service management system further includes a verification computing application interface, wherein the receiving of first data from the verification computing application of the first user includes: The verification computing application interface receives the first data from the verification computing application; The method further comprises: If the user node is available, the verification computing application interface sends the first data to the user node; If the user node is unavailable, the verification computing application interface sends the first data to the first shared node.

6. The method according to any one of claims 1 to 5, characterized in that The multiple shared nodes are deployed in multiple areas, and the sending the second verification data to the multiple blockchain nodes includes: Sending the second data to a second sharing node, wherein the second sharing node is a sharing node located in the same area as the user node; The second sharing node sends the second data to the multiple blockchain nodes.

7. The method according to claim 6, characterized in that The second sharing node sends the second data to the multiple blockchain nodes, including: The second shared node sends the second data to a third shared node in the area to which the target blockchain node belongs; The third sharing node sends the second data to the target blockchain node.

8. The method according to claim 6 or 7, characterized in that: The blockchain verification service management system further includes a verification calculation application interface, and the second shared node sends the second data to the multiple blockchain nodes, including: The second shared node sends the second data to the multiple blockchain nodes through the verification computing application interface.

9. The method according to any one of claims 1 to 8, characterized in that The blockchain verification service management system further includes a human-computer interaction interface, which is used to deploy the multiple shared nodes and the multiple dedicated nodes; the method includes: The human-computer interaction interface receives a user node creation request from the first user; When the user node is created, a creation success response is output to the first user.

10. A blockchain verification service management system, characterized in that: The blockchain includes a plurality of blockchain nodes; the blockchain verification service management system includes a plurality of shared nodes and a plurality of dedicated nodes, the shared nodes and the dedicated nodes are used as blockchain nodes; the shared nodes store synchronization data of the blockchain; The blockchain verification service management system is used to: receiving a user node creation request from a first user, and creating at least one dedicated node according to data of a first shared node among the plurality of shared nodes, wherein the at least one dedicated node is used as a user node of the first user; receiving first data from a verification computing application of the first user; generating second data according to the first data, wherein the second data includes the first data, an identifier of the first user, an identifier of the first user, and an identifier of the user node; Send the second data to the multiple blockchain nodes.

11. The blockchain verification service management system according to claim 10, characterized in that: In the process of generating the second data, if the user node is available, the user node is used to generate the second data according to the first data.

12. The blockchain verification service management system according to claim 10 or 11, characterized in that: In the process of generating the second data, if there is a first time period during which the user node is unavailable, the first sharing node is used to generate a part of the second data according to the first data during the first time period; During a second time period in which the user node is available, the user node is used to generate another part of the second data according to the first data; wherein the second data includes the first data, an identifier of the user node and an identifier of the first shared node.

13. The blockchain verification service management system according to claim 12, characterized in that: The user node is unavailable, including: The user node is in the process of being created, or the user node is in the process of being upgraded and maintained.

14. The blockchain verification service management system according to any one of claims 10 to 13, characterized in that: It also includes a verification calculation application interface, which is used to: receiving the first data from the verification computing application; If the user node is available, sending the first data to the user node; If the user node is unavailable, the first data is sent to the first shared node.

15. The blockchain verification service management system according to claim 14, characterized in that: The multiple shared nodes are deployed in multiple areas; The user node and / or the first sharing node is used to send the second data to a second sharing node, wherein the second sharing node is a sharing node located in the same area as the user node; The second shared node is used to send the second data to the multiple blockchain nodes.

16. The blockchain verification service management system according to claim 14 or 15, characterized in that: The second shared node is used to send the second data to a third shared node in the area to which the target blockchain node belongs; The third shared node is used to send the second data to the target blockchain node.

17. The blockchain verification service management system according to any one of claims 14 to 16, characterized in that: It also includes a verification computing application interface, and the second shared node is used to send the second data to the multiple blockchain nodes through the verification computing application interface.

18. The blockchain verification service management system according to any one of claims 10 to 17, characterized in that: It also includes a human-computer interaction interface, which is used to: deploying the plurality of shared nodes and the plurality of dedicated nodes; When the user node is created, a creation success response is output to the first user.

19. A computing device cluster, characterized in that: comprising at least one computing device, each computing device comprising a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 1 to 9.

20. A computer-readable storage medium, characterized in that: The method comprises computer program instructions, and when the computer program instructions are executed by a blockchain verification service management system, the blockchain verification service management system performs the method as described in any one of claims 1 to 9.

21. A computer program product, characterized in that When the computer program product runs on a blockchain verification service management system, the blockchain verification service management system executes the method as described in any one of claims 1 to 9.

Images