Blockchain verification service management method and system

Abstract

The present application provides a blockchain verification service management method and system. A blockchain comprises a plurality of blockchain nodes. The blockchain verification service management system comprises a plurality of sharing nodes and a plurality of dedicated nodes. The sharing nodes and the dedicated nodes are used as blockchain nodes. Synchronization data of the blockchain is stored in the sharing nodes. The method comprises: receiving a user node creation request from a first user, and creating at least one dedicated node on the basis of data of a first sharing node among a plurality of sharing nodes, wherein the at least one dedicated node is used as a user node of the first user; receiving first data from a verification computation application of the first user; generating second data on the basis of the first data, wherein the second data comprises the first data, an identifier of the first user, and an identifier of the user node; and sending the second data to a plurality of blockchain nodes. The method and system can significantly improve the validity of the user nodes in the blockchain.

Description

Blockchain verification service management method and system

[0001] This application claims priority to the Chinese patent application with application number 202311763697.3 filed with the State Intellectual Property Office of China on December 20, 2023, priority to the Chinese patent application with invention name “Method and system for blockchain pledge”, priority to the Chinese patent application with application number 202410427496.4 filed with the State Intellectual Property Office of China on April 9, 2024, and priority to the Chinese patent application with invention name “Method and system for blockchain verification service management”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of cloud computing, and more specifically, to a blockchain verification service management method and system. Background Art

[0003] Ethereum is a smart contract platform based on blockchain technology. Blockchain nodes in Ethereum can participate in staking and become staking nodes. Specifically, Ethereum users can verify their identities through a validator client, becoming verified users. They can then process or verify transactions on the platform, add new blocks to the blockchain, or verify the validity of newly added blocks. The data generated by the validation application is then broadcasted to other nodes in the blockchain via at least one blockchain node.

[0004] Ethereum users typically deploy blockchain nodes, or user nodes, within the user node pool of a cloud service system to accelerate verification calculations, enhance broadcast coverage, and improve the average effectiveness of multiple nodes. Because verification calculation services consume significant computing resources, users often create user nodes temporarily when they want to participate in staking. However, this takes a long time to create user nodes, and user nodes may be unavailable during the target period. Furthermore, in Ethereum, the software architecture of each node requires periodic maintenance and upgrades to ensure its functionality is consistent with the overall blockchain protocol. If maintenance or upgrades occur during the execution of verification calculation services, the user node may also be unavailable during the target period.

[0005] Summary of the Invention

[0006] This application provides a blockchain verification service management method and system to improve the effectiveness of user nodes in the blockchain.

[0007] In a first aspect, an embodiment of the present application provides a blockchain verification service management method, wherein the blockchain includes multiple blockchain nodes; the method is used for a blockchain verification service management system, wherein the blockchain verification service management system includes multiple shared nodes and multiple 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 method includes: receiving a user node creation request from a first user, creating at least one dedicated node based on data of a first shared node among multiple shared nodes, and the at least one dedicated node is used as a user node of the first user; receiving first data of a verification computing application from the first user; generating second data based on the first data, wherein the second data includes the first data, an identifier of the first user, and an identifier of the user node; and sending the second data to multiple blockchain nodes.

[0008] The blockchain verification service management system provided in the embodiment of the present application includes multiple shared nodes, which store the synchronization data of the blockchain, and can increase the speed of creating user nodes, thereby improving the effectiveness of users in performing verification tasks.

[0009] In a possible implementation of the first aspect, generating the second data based on the first data includes: in the process of generating the second data, if the user node is available, the user node generating the second data based on the first data.

[0010] In a possible implementation of the first aspect, generating second data based on first data includes: in the process of generating the second data, if there is a first time period in which the user node is unavailable, within the first time period, the first shared node generates a part of the second data based on the first data; within 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.

[0011] In such an implementation, the first shared node can temporarily replace the unavailable user node to perform verification computing services. Regardless of whether the user node is available, the entire blockchain verification service management system can continue to receive the first data, thereby improving the broadcast efficiency and reliability of the first data.

[0012] In a possible implementation of the first aspect, 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.

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

[0014] In a possible implementation of the first aspect, the blockchain verification service management system also includes a verification computing application interface, which receives first data from the verification computing application of the first user, including: the verification computing application interface receives the first data from the verification computing application; the method also 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.

[0015] A verification computing application interface is deployed 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 used to receive the first data, and the first shared node does not need to perform complex calculations to determine whether each time period is used to receive the first data, thereby reducing the complexity of the entire system.

[0016] In a possible implementation of the first aspect, multiple shared nodes are deployed in multiple areas, and sending second data to multiple blockchain nodes includes: sending the second data to a second shared node, wherein the second shared node is a shared node located in the same area as the user node; the second shared node sends the second data to multiple blockchain nodes.

[0017] In such an implementation, the user node may broadcast the second data in the local area through the shared node in the same area.

[0018] In a possible implementation of the first aspect, the second shared node sends the second data to 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; and the third shared node sends the second data to the target blockchain node.

[0019] In this implementation, shared nodes are used to broadcast verification data to external blockchain nodes, increasing broadcast coverage, reducing broadcast latency, and lowering user node traffic consumption, which can significantly improve the success rate of user nodes performing verification calculation tasks.

[0020] In a possible implementation of the first aspect, the blockchain verification service management system also includes a verification calculation application interface, and the second shared node sends the second data to multiple blockchain nodes, including: the second shared node sends the second data to multiple blockchain nodes through the verification calculation application interface.

[0021] In such an implementation, the user node can fully utilize the network performance between multiple verification computing application interfaces, broadcast the second data to multiple shared nodes, and reduce the delay of internal broadcasting of the second data.

[0022] In a possible implementation of the first aspect, the blockchain verification service management system also includes a human-computer interaction interface, which is used to deploy multiple shared nodes and multiple dedicated nodes; the method includes: the human-computer interaction interface receives a user node creation request from a first user; when the user node creation is completed, outputs a creation success response to the first user.

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

[0024] In a second aspect, an embodiment of the present application provides a blockchain verification service management system, wherein the blockchain includes multiple blockchain nodes; the blockchain verification service management system includes multiple shared nodes and multiple dedicated nodes, and the shared nodes and 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: receive a user node creation request from a first user, create at least one dedicated node based on the data of a first shared node among multiple 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 based on the first data, wherein 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 multiple blockchain nodes.

[0025] In a possible implementation manner 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.

[0026] In a possible implementation of the second aspect, in the process of generating the second data, if there is a first time period in which the user node is unavailable, during the first time period, the first shared node is used to generate a part of the second data based on the first data; during the second time period in which the user node is available, the user node is used to generate 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.

[0027] In a possible implementation manner of the second aspect, 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.

[0028] In a possible implementation of the second aspect, the blockchain verification service management system also 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.

[0029] In a possible implementation of the second aspect, multiple shared nodes are deployed in multiple areas, and the user node and / or the first shared node is used to send the second data to the second shared node, wherein the second shared node is a shared node located in the same area as the user node; the second shared node is used to send the second data to multiple blockchain nodes.

[0030] 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 area to which the target blockchain node belongs; and the third shared node is used to send the second data to the target blockchain node.

[0031] In a possible implementation of the second aspect, the blockchain verification service management system also 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.

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

[0033] In a third aspect, an embodiment of the present application provides a computing device cluster, 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 used to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method described in any implementation manner of the first aspect.

[0034] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium comprising computer program instructions. When the computer program instructions are executed by a blockchain verification service management system, the blockchain verification service management system executes the method described in any implementation of the first aspect.

[0035] In a fifth aspect, an embodiment of the present application provides a computer program product. When the computer program product is run on a blockchain verification service management system, the blockchain verification service management system executes the method described in any implementation method of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] FIG1 is a schematic diagram of an application scenario of an embodiment of the present application.

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

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

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

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

[0041] FIG6 is a schematic flowchart of receiving verification data according to an embodiment of the present application.

[0042] FIG7 is a schematic block diagram of a verification data application interface according to an embodiment of the present application.

[0043] FIG8 is a schematic flowchart of a user node sending second data to a second shared node in an embodiment of the present application.

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

[0045] FIG10 is a schematic block diagram of a controller according to an embodiment of the present application. DETAILED DESCRIPTION

[0046] This application will present various aspects, embodiments, or features around systems 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 of the devices, components, modules, etc. discussed in conjunction with the figures. Furthermore, combinations of these aspects may also be used.

[0047] Additionally, in the embodiments of this application, words such as "exemplary" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete manner.

[0048] In the embodiments of the present application, “corresponding” and “relevant” may sometimes be used interchangeably. It should be noted that when the distinction between them is not emphasized, the meanings they intend to express are consistent.

[0049] This embodiment involves some new functional modules or units divided according to function or logic, such as the validation computing application interface (validating hub, VH) and its sub-modules. Those skilled in the art will know that with the evolution of network architecture and the emergence of new business 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.

[0050] The business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person skilled in the art will appreciate that, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

[0051] The following is a brief introduction to the commonly used technical terms in this field.

[0052] Cloud computing is a computing model that provides dynamically scalable, virtualized resources as a service over the Internet. Platform as a Service (PaaS) is one of the primary multi-tenant models of cloud computing. Different tenants are registered on a PaaS platform and use its resources and services. The shared cloud services of a PaaS platform can provide blockchain as a service (BaaS) to public cloud tenants.

[0053] In cloud computing, regions and availability zones (AZs) are concepts used to divide data centers and server resources. A region is a geographical area, typically encompassing multiple data centers, each of which in turn contains multiple AZs. Each AZ is typically an independent data center with its own power, network, and physical equipment. For example, global regions can be divided into Asia, Americas, and Europe, while domestic regions can be divided into East China, North China, and Central China.

[0054] Blockchain refers to a distributed database technology that uses a consensus mechanism based on cryptography to maintain a continuously growing, linked list ledger consisting of time-stamped and ordered data blocks across multiple nodes in a peer-to-peer network. In this technology, any number of participating blockchain nodes cryptographically calculate and record all information exchanged within the system over a period of time into a single data block. They also generate a fingerprint for this data block, which is used to link and verify the next data block. All nodes in the system jointly verify the authenticity and validity of the data.

[0055] Block height refers to the height of the latest confirmed block on a blockchain network. Each time a new block is added to the blockchain, the block height increases. Therefore, block height can be used to indicate the current state and progress of the blockchain network. When a node is operating normally and synchronized with the blockchain network, it continuously receives new blocks and updates its block height. Therefore, by checking a node's block height, you can determine whether it is operating normally and synchronized with the network. If a node has not updated its block height for an extended period of time, or if its block height deviates significantly from that of other nodes, this may indicate a problem with the node, causing it to be malfunctioning or disconnected from the network, effectively becoming unavailable.

[0056] A general-purpose PoS chain refers to a blockchain network based on the proof-of-stake (PoS) consensus mechanism. Its key feature is its ability to support a wide variety of applications and smart contracts. Ethereum is a general-purpose PoS chain. In Ethereum, a new block is generated during each time slot, and blockchain nodes within the Ethereum blockchain can participate in staking, becoming staking nodes. Specifically, Ethereum users possess digital signatures, a verification client, and multiple validation nodes. They verify their identity through a validator client and become verified users. Validators then use multiple validator applications within the client to process or verify transaction information within the platform, add new blocks to the blockchain, or verify the validity of newly added blocks. The data generated by the validator applications is broadcast to other nodes in the blockchain via at least one blockchain node.

[0057] In the embodiments of this application, users participating in staking can be referred to as verification users or staking users, participating in staking can be referred to as performing verification services, data processed or verified can be referred to as pledge data or verification data, nodes performing verification services can be referred to as pledge nodes or user nodes, and verification computing applications can be referred to as verifiers. The intermixing of specific names should not be considered a limitation on the technical solutions of this application. Subsequent embodiments use Ethereum as an example to illustrate methods, devices, systems, and the like applicable to general-purpose PoS chains, and should not be construed as limiting the technical solutions of this application.

[0058] Specifically, the selection rules for staking nodes in Ethereum are determined by randomness. Ethereum uses the RANDAO algorithm to implement randomness. This algorithm combines a hash value from the block proposer with a seed that is updated with each block to generate a random number. This number is then used to select a specific staking node from among all staking nodes to perform validation services. Therefore, activities within blockchain systems often involve global regions.

[0059] Specifically, blockchain nodes can be hardware, virtual hardware, or containers, each with an IP address and digital signature. As shown in Figure 1, multiple verification computation clients can obtain the latest data from at least one arbitrary node in the blockchain, perform specific verification computations, and send the verification data to multiple user nodes. These multiple user nodes then broadcast the verification data to the majority of nodes in the blockchain to prove the validity of the pledge. A validating user can deploy a verification computation client for each user node. Each verification computation client includes multiple verification computation applications that can perform parallel computations to accelerate the verification computation.

[0060] Ethereum users typically deploy blockchain nodes, or user nodes, within the user node pool of a cloud service system to accelerate verification calculations, enhance broadcast coverage, and improve the average effectiveness of multiple nodes. Because verification calculation services consume significant computing resources, users often create user nodes temporarily when they want to participate in staking. However, this takes a long time to create user nodes, and user nodes may be unavailable during the target period. Furthermore, in Ethereum, the software architecture of each node requires periodic maintenance and upgrades to ensure its functionality is consistent with the overall blockchain protocol. If maintenance or upgrades occur during the execution of verification calculation services, the user node may also be unavailable during the target period.

[0061] Furthermore, if all user nodes are located in the same region, network latency for broadcasting data to other regions may be high, resulting in low data throughput. This can cause most nodes in other regions to lose messages during the current time slot, leading to multiple verification failures and low node effectiveness in the blockchain. Furthermore, user nodes must broadcast verification data to all nodes in the blockchain during each time slot, consuming significant data throughput.

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

[0063] The following describes a blockchain verification service management system provided by this application, with reference to Figure 2. As shown in Figure 2, a blockchain includes multiple blockchain nodes. A blockchain verification service management method is used in the system. The node pool of the blockchain verification service management system includes multiple shared nodes and multiple user nodes, with the shared nodes and user nodes serving as blockchain nodes. Each shared node pool periodically synchronizes blockchain data from external blockchain nodes and stores it on its own storage device.

[0064] In some embodiments, the verification computing client does not send verification data directly to the user node, but instead sends verification data to the verification computing application interface. When the user node is available, the verification computing application interface sends verification data to the user node. When the user node is unavailable, such as when the user node is being created or undergoing an upgrade or maintenance, the verification computing application interface sends verification data to a shared node, which then serves as the user node. Furthermore, the latest blockchain data can be directly obtained from the shared node to initialize the user node, speeding up the creation of user nodes.

[0065] The blockchain verification service management system provided in the embodiment of the present application includes multiple shared nodes, which store the synchronization data of the blockchain, and can increase the speed of creating user nodes, thereby improving the effectiveness of users in performing verification tasks.

[0066] The above solution is applicable to scenarios where a single node pool is established in the region to which the user node belongs. This solution can also be further expanded to establish multiple node pools in multiple regions, thereby improving the availability of user nodes in multiple regions and more accurately managing user nodes and shared nodes. The following, combined with the schematic block diagram of the blockchain verification service management system shown in Figure 3, illustrates the logical relationships of some entities in a blockchain verification service management system of this embodiment.

[0067] This embodiment provides a blockchain verification service management system with data centers located in multiple regions. It should be understood that the regions in this application primarily refer to regions worldwide. Administrators of the blockchain verification service management system can configure the system to create multiple blockchain nodes on multiple hosts / virtual machines / containers in each region. Blockchain nodes can be virtual machines / containers deployed in data centers. Specifically, the blockchain nodes described in this embodiment can be divided into shared nodes and dedicated nodes. Multiple shared nodes are deployed in each regional data center, and multiple dedicated nodes are deployed in at least one regional data center. Both shared and dedicated nodes include a software layer and storage devices, while dedicated nodes include a software layer and dynamic capacity storage devices.

[0068] Furthermore, all shared nodes in each area are respectively gathered together to form a shared node pool in each area; all dedicated nodes in each area are respectively gathered together to form a dedicated node pool in at least one area.

[0069] In one embodiment, as shown in FIG4 , the blockchain verification service management system includes a human-computer interaction interface, which includes an administrator interface. Through the administrator interface, the administrator of the blockchain verification service management system can deploy shared node pools and dedicated node pools, or manage shared node pools and dedicated node pools deployed in various regions. Specifically, the administrator can change the region division method, adjust the number of shared nodes or dedicated nodes, and set the node's memory resources, storage capacity, or network bandwidth.

[0070] The following describes the process of the blockchain verification service management method with reference to the schematic flowchart shown in FIG5 .

[0071] S510 , receiving a user node creation request from a user, and creating at least one dedicated node as a user node based on data of a first shared node among a plurality of shared nodes.

[0072] When a user wants to create a user node and participate in blockchain staking, they request the creation of a user node in the blockchain verification service management system. The blockchain verification service management system creates a dedicated node as the user node in a dedicated node pool in at least one region. In other words, the dedicated node pool can include user nodes from multiple different users.

[0073] It should be understood that each node in a blockchain periodically obtains the latest blockchain data from other nodes and stores blockchain synchronization data to ensure data consistency across nodes. This synchronization period can be described by periods and slots. Specifically, a period includes multiple slots. According to the blockchain protocol, some data needs to be synchronized in every slot, while other data only needs to be synchronized in every period. Each node needs to synchronize at least once within each period.

[0074] For ease of description, this application refers to shared nodes or dedicated nodes in the blockchain verification service management system as internal nodes, and other blockchain nodes outside the blockchain verification service management system as external nodes. In addition, the subsequent embodiments use a time period of 384 seconds and a time slot of 12 seconds as an example for illustration.

[0075] In the blockchain verification service management system, each shared node pool periodically synchronizes the blockchain data in the external nodes, wherein each node in a shared node pool synchronizes data at the same period, but at different 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 384K+12 seconds, some shared nodes synchronize at 384K+24 seconds, and some shared nodes synchronize at 384K+36 seconds, 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, the data of at least one shared node in the shared node pool is consistent with the latest blockchain data of the external node in the current time slot. These shared nodes store the latest synchronized data of the blockchain and are called first shared nodes.

[0076] Optionally, after each data synchronization, the shared node can store the successfully acquired blockchain data in a backup data storage device to further improve data security.

[0077] In one embodiment, the blockchain verification service management system creates a user node at 384K+15 seconds, and the user node can be initialized using the blockchain data at 384K+12 seconds in the shared node pool of the current area.

[0078] Multiple shared nodes in the shared node pool synchronize blockchain data at different time slots during the blockchain period. The blockchain verification service management system can create user nodes based on the latest blockchain data in the shared node pool in the current area. The initialization operation has low latency and high effectiveness.

[0079] In one embodiment, as shown in FIG4 , the human-computer interaction interface of the blockchain verification service management system includes a user interface, through which users can initiate user node creation requests, perform upgrades and maintenance on user nodes, view logs, or access user nodes to view various information in the blockchain. Each user manages their own user node. For example, user 411 can manage user node 421, and user 412 can manage user node 422.

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

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

[0082] S520, receiving first data from a verification computing application.

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

[0084] Specifically, the VH is a module with high-performance network communication components that can forward high-volume data. For example, it can simultaneously receive first data from multiple verification computing clients and forward it to a designated internal node. It should be understood that the aforementioned components and modules are merely a logical division and can be software, hardware, or a combination of both.

[0085] It should be understood that the verification calculation application in the verification calculation client needs to obtain the latest blockchain data to perform verification calculations. In one embodiment, the verification calculation client can obtain blockchain data from an internal node in the region to which the VH belongs through the VH; in another embodiment, the verification calculation client can obtain blockchain data from an external node with which it has established a connection. For ease of description, the subsequent embodiments will no longer distinguish between the verification calculation application and the verification calculation client, and will uniformly describe the verification calculation application.

[0086] In this embodiment of the present application, the verification computing application establishes a persistent connection with the VH, which provides high reliability for the persistent connection. A persistent connection means that after the communicating parties establish a connection, the connection remains connected for a period of time and multiple data transmissions are performed. In a persistent connection, once the connection is established, the communicating parties can send and receive data at any time without having to re-establish the connection for each communication.

[0087] For ease of description, the connection between the verification 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.

[0088] S521: When the user node is available, the user node receives first data from the verification computing application.

[0089] In the aforementioned embodiment, the process of creating a user node takes several minutes. If the first user node is not yet created, the first user node is considered to be in an unavailable state. In addition, if the software layer of the first user node is undergoing maintenance and upgrades, the first user node is also considered to be in an unavailable state.

[0090] For ease of description, the VH located in the same region as the verification computing application is referred to as the first verification computing application interface, and the VH located in the same region as the user node is referred to as the second verification computing application interface.

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

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

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

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

[0095] S522: When the user node is unavailable, the first shared node receives first data from the verification computing application.

[0096] In some embodiments, the shared node pool in each region includes at least one first shared node, which can be used as a second user node. Specifically, when the second user node is unavailable, the VH located in the same region as the second user node analyzes the working status of all shared nodes in the region, selects a first shared node according to specific rules, and switches the network traffic transmitting the first data from the unavailable second user node to the first shared node, allowing the first shared node to receive the first data instead of the second user node and perform other functions of the second user node, such as synchronizing blockchain data and providing users with access to a blockchain browser.

[0097] Specifically, the first shared node is selected according to specific rules. The first shared node with the lowest current workload among all the first shared nodes in the current area can be selected. The workload includes parameters such as memory usage and network traffic usage. Alternatively, the first shared node located in the same AZ as the user node can be selected. Alternatively, the first shared node in the current area with higher validity in the blockchain can be selected. Alternatively, the first shared node can be selected based on the block height of multiple shared nodes, etc. This embodiment does not limit this.

[0098] In the above embodiment, 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 unavailable, the first shared node receives the first data sent directly to the first shared node by the verification computing application. The VH in the blockchain verification service management system is optional.

[0099] Furthermore, whether the second user node is available can be confirmed by detecting the block height.

[0100] Furthermore, the VH may 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.

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

[0102] It should be understood that when the second user node becomes available again, the VH can switch the network traffic for transmitting the first data from the first shared node to the second user node, so that the second user node continues to receive the first data.

[0103] In some embodiments, if VH is not set in the blockchain verification service management system, the steps of selecting the first shared node, determining whether the second user node is available, switching network traffic, etc. can be implemented by other network management systems deployed by the user.

[0104] In some embodiments, when the second user node is available, the first shared node may 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 relatively few, and it takes a long time to complete the verification computing task independently, and there are a large number of idle first shared nodes, then the first shared node may also perform the verification computing task together with the second user node.

[0105] A verification computing application interface is deployed 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 used to receive the first data, and the first shared node does not need to perform complex calculations to determine whether each time period is used to receive the first data, thereby reducing the complexity of the entire system.

[0106] In such an implementation, the first shared node can temporarily replace the unavailable user node to perform verification computing services. Regardless of whether the user node is available, the entire blockchain verification service management system can continue to receive the first data, thereby improving the broadcast efficiency and reliability of the first data.

[0107] S530: Generate second data according to the first data.

[0108] The first data is the data obtained by the user's verification calculation application, including the user's digital signature, but not the blockchain node's digital signature. 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 user node's digital signature and modifying the timestamp. The second data is then broadcast to most nodes in the blockchain.

[0109] Specifically, the first data can be data generated in the blockchain system to be verified, such as smart contract input parameters, transaction requests, or other related information. The second data can be calculated, verified, or processed result data, such as smart contract execution results, transaction confirmation information, or other related data used to update the state of the blockchain network or execute the logic of the smart contract.

[0110] S531: If the user node is available, the user node generates second data according to the first data.

[0111] It should be understood that each blockchain node has a corresponding digital signature. If the user node is available during the entire process of generating the second data, the final second data will include the user's digital signature and the user node's digital signature. It should be understood that a digital signature is a type of identifier.

[0112] S532: If there is a period during which the user node is unavailable, the user node and the first sharing node respectively generate a portion of the second data according to the first data.

[0113] Specifically, during the process of generating the second data, if there is a first period during which the user node is unavailable, the first shared node generates a portion of the second data based on the first data during the first period; and during a second period during which the user node is available, the user node generates another portion of the second data based on the first data. The second data includes the digital signature of the user node and the digital signature of the first shared node.

[0114] S540: Send second data to the external node.

[0115] This embodiment uses a 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 subsequent embodiments, the meanings of "broadcast" and "send" are similar and can be used interchangeably, and do not constitute a limitation on the technical solution of this application.

[0116] S541, obtain information of external nodes.

[0117] In one embodiment, the shared node pool of each area periodically obtains the external node information of the area. The external node in this application refers to the external node obtained periodically.

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

[0119] S542: The user node and / or the first sharing node sends second data to the second sharing node.

[0120] In one embodiment, multiple shared nodes are selected in each shared node pool for sending the second data to the external node, wherein the second shared node is a shared node located in the same area as the user node, and the second shared node is used to send the second data to the external node.

[0121] In another embodiment, as shown in Figure 7, 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 first data from the verification computing application, receive data from a VH, or send data to a VH; the shared node routing module is used to send first data or second data to a shared node, and the dedicated node routing module is used to send first data to a user node or receive second data sent by the user node.

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

[0123] 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 nodes. First, the process of the user node sending the second data to the second shared node is described with reference to the schematic flow chart shown in FIG8 .

[0124] In some embodiments, as shown in (a) of FIG8 , the user node sends the second data to the second sharing node, and the second sharing node sends the second data to the external node.

[0125] In such an implementation, the user node may broadcast the second data in the local area through the shared node in the same area.

[0126] In some embodiments, as shown in (b) of FIG8 , the second verification computing application interface receives second data from the user node and sends the second data to a plurality of second sharing nodes.

[0127] Next, the process of sending the second data from the user node to the third shared node will be described in conjunction with FIG8 , wherein the third shared node is a shared node located in a different region from the user node, and the third shared node is used to send the second data to the external node. In some embodiments, as shown in FIG8 (a), the third verification computing application interface receives the second data from the second verification computing application interface and sends the second data to the third shared node in the region to which the target blockchain node belongs. The third verification computing application interface is a verification computing application interface located in a different region from the second verification computing application interface.

[0128] In some embodiments, if the third sharing node does not exist in some areas, the second sharing node sends the second data to the external nodes in these areas.

[0129] In such an implementation, the user node can fully utilize the network performance between multiple verification computing application interfaces, broadcast the second data to multiple shared nodes, and reduce the delay of internal broadcasting of the second data.

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

[0131] S543: The second shared node sends second data to the external node.

[0132] In some embodiments, as shown in (a) of Figure 8 , a second shared node sends the second data to multiple external nodes in the same area as the second shared node. In other embodiments, a second shared node sends the second data to multiple external nodes in any area.

[0133] In this implementation, shared nodes are used to broadcast verification data to external blockchain nodes, increasing broadcast coverage, reducing broadcast latency, and lowering user node traffic consumption, which can significantly improve the success rate of user nodes performing verification calculation tasks.

[0134] S544: The user node sends second data to the external node.

[0135] In some embodiments, the user node directly sends the second data to the external node. When a large number of shared nodes in a certain area are unavailable due to a failure or network attack, the user node can still send the second data to the external nodes in these areas based on the acquired external node information.

[0136] The blockchain verification service management system provided in this application embodiment deploys a pre-created shared node pool consisting of multiple shared nodes in multiple regions. The shared nodes are used to accelerate the creation of user nodes and temporarily replace unavailable user nodes to perform verification computing services. The shared nodes are also used to broadcast verification data to external blockchain nodes, increasing broadcast coverage, reducing broadcast latency, and lowering user node data consumption. These two functions can significantly improve the effectiveness of user nodes in the blockchain.

[0137] Figure 9 is a schematic block diagram of an apparatus for blockchain authentication service management according to an embodiment of the present application. The apparatus 900 shown in Figure 9 can be used to execute the method for blockchain authentication service management according to the present application.

[0138] As shown in Figure 9, the apparatus includes an acquisition unit 910, a processing unit 920, and an output unit 930. The term "unit" herein can be implemented in software and / or hardware, and is not specifically limited thereto.

[0139] For example, a "unit" can be a software program, hardware circuit, or a combination of the two that implements the aforementioned functionality, and can include code running on a computing instance. For example, the following describes the implementation of a processing unit using the processing unit as an example. Similarly, the implementation of the acquisition unit and the output unit can refer to the implementation of the processing unit.

[0140] 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 used to run the code can be distributed in the same region or in different regions. Furthermore, the multiple hosts / virtual machines / containers used to run the code can be distributed in the same availability zone (AZ) or in different AZs, each AZ including one data center or multiple geographically close data centers. Typically, a region can include multiple AZs.

[0141] Similarly, multiple hosts / virtual machines / containers running the code can be distributed within the same virtual private cloud (VPC) or across multiple VPCs. Typically, a VPC is set up within a region. Cross-region communication between two VPCs within the same region, or between VPCs in different regions, requires a communication gateway within each VPC to interconnect the VPCs.

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

[0143] The multiple computing devices included in a processing unit can be distributed in the same region or in different regions. They can also be distributed in the same AZ or in different AZs. Similarly, they can be distributed in the same VPC or across multiple VPCs. These multiple computing devices can be any combination of servers, ASICs, PLDs, CPLDs, FPGAs, GALs, and other computing devices.

[0144] Therefore, the modules of each example described in the embodiments of this application can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0145] The present application also provides a controller 1000. As shown in Figure 10, the controller 1000 includes: a processor 1004 and a communication interface 1008. Furthermore, 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 with each other via the bus 1002. Exemplarily, the controller 1000 can be a computing device or an apparatus in a computing device for implementing the method of an embodiment of the present application. The controller 1000 can 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.

[0146] Bus 1002 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, among others. Buses may be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG10 illustrates a single bus line, but this does not imply a single bus or type of bus. Bus 1002 may include a path for transmitting information between various components of controller 1000 (e.g., memory 1006, processor 1004, and communication interface 1008).

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

[0148] 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, hard disk drive (HDD), or solid state drive (SSD).

[0149] The memory 1006 stores executable program code, and the processor 1004 executes the executable program code to implement the functions of the aforementioned acquisition unit and processing unit, thereby implementing the method for managing blockchain verification services. In other words, the memory 1006 stores instructions for the method for managing blockchain verification services.

[0150] 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 communication networks (eg, multiple servers). The communication interface may also be referred to as an interface circuit.

[0151] Embodiments of the present application also provide a computing device cluster. The computing device cluster includes a controller 1000 and multiple computing devices. The computing devices can be servers, such as central servers, edge servers, or local servers in a local data center. In some embodiments, the computing devices can also be terminal devices such as desktop computers, laptop computers, or smartphones. The multiple computing devices can be the multiple servers described above. This computing device cluster can be used to implement a blockchain verification service management system.

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

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

[0154] The present application also provides a computer program product including instructions. The computer program product may be software or a program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, the at least one computing device executes the method of the present application.

[0155] The present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by a computing device or a data storage device such as a data center that contains one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the method in the embodiment of the present application, or instruct the computing device to execute the method in the embodiment of the present application.

[0156] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0157] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0158] Those skilled in the art will 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 aforementioned method embodiments and will not be repeated here.

[0159] In the several embodiments provided in this 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 schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as 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 mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0161] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0162] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the 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 enabling 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 method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0163] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection 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 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 regions, and the sending the second 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