Unified execution method of management instructions for multiple blockchains, multi-blockchain system and storage medium

Abstract

The present application discloses a unified execution method for management instructions for multiple blockchains, a multi-blockchain system and a storage medium. In the embodiment of the present application, the management node determines the calling node for executing the management instruction for the target blockchain according to the received management instruction generated for at least one target blockchain in multiple application blockchains and the list of execution nodes, and the management node generates a call request according to the management instruction and the node information of the calling node, and performs management operations on the target blockchain according to the call request by the calling node. Therefore, the management instruction can be responded to by the management node in the management blockchain, and the call instruction generated according to the management instruction can be executed by the calling node for the target blockchain, thereby not only realizing the unified management of multiple application blockchains in a multi-blockchain environment, but also being able to respond to the management instruction for the application blockchain in real time and perform the corresponding management operation by calling the execution node, thereby greatly improving the execution timeliness of the management instruction for the application blockchain.

Description

Technical Field

[0001] The present application relates to the field of network technology, and in particular to a method for unified execution of management instructions for multiple blockchains, a multi-blockchain system, and a storage medium. Background Art

[0002] With the in-depth development of the Internet and digitalization, people's demand for transparent, secure and efficient information is increasing. At the same time, the idea of ​​decentralization is increasingly recognized and accepted. Blockchain was born and developed under such social needs and trends of the times. The core concept of blockchain is a global, tamper-proof ledger that records the transactions and information transmissions of all participants. Unlike traditional centralized systems, blockchain uses cryptography and consensus mechanisms to ensure the security and transparency of transactions.

[0003] However, the growing development of blockchain technology has also led to the existence of a variety of blockchains for users to use. These blockchains can meet the needs of users to use blockchain technology in different scenarios and applications by using various technologies. Therefore, different blockchains can attract different users with their own advantages. However, since different blockchains are operated by different developers or operators, this not only makes the multi-blockchain environment complex and unfriendly to users, but also lacks a unified management mechanism and operation.

[0004] To this end, a solution is needed to manage multiple blockchains in a multi-blockchain environment. Summary of the invention

[0005] The embodiments of the present application provide a unified execution method for management instructions for multiple blockchains, a multi-blockchain system, and a storage medium to solve the defect of inefficiency in the management of multiple blockchains in the prior art.

[0006] To achieve the above-mentioned purpose, the embodiment of the present application provides a method for unified execution of management instructions for multiple blockchains, wherein the multiple blockchains include a management blockchain and multiple application blockchains, and the method includes:

[0007] A management node in the management blockchain receives a management instruction generated for at least one target blockchain in the multiple application blockchains, wherein the management instruction includes blockchain identification information, management item information, and management target information of the target blockchain;

[0008] The management node obtains an execution node list according to the management instruction, wherein the execution node list includes at least one execution node currently available in the management blockchain, and the execution node is a node in the management blockchain used to perform management operations on the application blockchain;

[0009] The management node determines, according to the management instruction and the execution node list, an execution node in the execution node list as a calling node for executing the management instruction on the target blockchain;

[0010] The management node generates a call request for the calling node to execute the management instruction on the target blockchain according to the management instruction and the node information of the calling node;

[0011] The calling node performs a management operation on the target blockchain according to the calling request.

[0012] The embodiment of the present application also provides a multi-blockchain system, wherein the multi-blockchain system includes a management blockchain and multiple application blockchains.

[0013] The management blockchain includes a management node and a plurality of execution nodes, wherein the management node is used to obtain a management instruction for at least one target blockchain among the plurality of application blockchains, wherein the management instruction includes blockchain identification information, management item information, and management target information of the target blockchain; obtaining an execution node list according to the management instruction, wherein the execution node list includes at least one execution node currently available in the management blockchain, and the execution node is a node in the management blockchain used to perform management operations on the application blockchain; determining an execution node in the execution node list as a calling node for executing the management instruction on the target blockchain according to the management instruction and the execution node list; generating a call request for the calling node to execute the management instruction on the target blockchain according to the management instruction and the node information of the calling node;

[0014] The calling node is used to perform management operations on the target blockchain according to the calling request.

[0015] The present application also provides an electronic device, including:

[0016] Memory, used to store programs;

[0017] A processor is used to run the program stored in the memory, and when the program is run, the unified execution method of management instructions for multiple blockchains provided in an embodiment of the present application is executed.

[0018] An embodiment of the present application also provides a computer-readable storage medium, on which a computer program executable by a processor is stored, wherein when the program is executed by the processor, the method for unified execution of management instructions for multiple blockchains as provided in an embodiment of the present application is implemented.

[0019] The unified execution method of management instructions for multiple blockchains, the multi-blockchain system and the storage medium provided in the embodiments of the present application are determined by the management node according to the received management instructions generated for at least one target blockchain in multiple application blockchains and the list of execution nodes, and the management node generates a call request according to the management instructions and the node information of the call node, and the call node performs management operations on the target blockchain according to the call request. Therefore, the management node in the management blockchain can respond to the management instruction, and the call node can execute the call instruction generated according to the management instruction for the target blockchain, thereby not only realizing the unified management of multiple application blockchains in the multi-blockchain environment, but also being able to respond to the management instructions for the application blockchain in real time and perform the corresponding management operations by calling the execution node, thereby greatly improving the execution timeliness of the management instructions for the application blockchain.

[0020] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present application. Also, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0022] Figure 1 is a schematic diagram showing an application scenario of a multi-blockchain management solution according to an embodiment of the present application;

[0023] Figure 2 A flowchart of an embodiment of a method for unified execution of management instructions for multiple blockchains provided by this application;

[0024] Figure 3 A system block diagram of the multi-blockchain system provided for this application;

[0025] Figure 4 A schematic diagram of the structure of an electronic device embodiment provided in this application. DETAILED DESCRIPTION

[0026] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0027] Embodiment 1

[0028] The solution provided in the embodiments of the present application can be applied to any multi-blockchain system including multiple blockchains.

[0029] With the in-depth development of the Internet and digitalization, people's demand for transparent, secure and efficient information is increasing. At the same time, the idea of ​​decentralization is increasingly recognized and accepted. Blockchain was born and developed under such social needs and trends of the times. The core concept of blockchain is a global, tamper-proof ledger that records the transactions and information transmissions of all participants. Unlike traditional centralized systems, blockchain uses cryptography and consensus mechanisms to ensure the security and transparency of transactions.

[0030] However, as users’ demands for blockchain performance and applications diversify, more and more blockchains have emerged for users to use to meet the needs of different scenarios or different functions, and multi-blockchain systems consisting of multiple blockchains have also emerged so that users can use multiple blockchains at the same time. However, in such cases, the management of multiple blockchains, such as changes in pricing or transaction mechanisms, becomes complicated and difficult to implement because different blockchains have different management mechanisms or are managed by different operators. For example, Figure 1 In the multi-blockchain system shown in , multiple application blockchains 1-3 may be included. Users can log in to one or more of the application blockchains 1-3 to call contracts to execute desired transactions or implement desired functions. In the prior art, such multi-blockchain systems often lack unified management, and even if a unified management party is established, it is often just a management team that is responsible for the operation and management of all three blockchains. That is, in the prior art, the management of the multi-blockchain environment needs to be done manually. For example, the owner of application blockchain 1 wants to change the transaction price on application blockchain 1, for example, from the current amount A to amount B. Then in the prior art solution, if Figure 1 As shown in , the management team needs to manually modify the price configuration information of blockchain 1 and manually restart blockchain 1 after the modification is completed to make the new price take effect. Such manual operations are not only cumbersome, but also heavily dependent on the experience and ability of the executors, which is very easy to cause errors, thereby affecting the operating efficiency and reliability of the multi-blockchain system.

[0031] For this reason, Figure 1 As shown in , the embodiment of the present application proposes a unified execution method for management instructions for multiple blockchains, which can be applied to a multi-blockchain system or environment containing multiple blockchains, and the multiple blockchains can include a management blockchain and multiple application blockchains. Figure 1 As shown in, the multi-blockchain may include a management blockchain 4 and application blockchains 1-3. The management blockchain 4 may be a blockchain specifically used to manage application blockchains 1-3 in the multi-blockchain system, and the application blockchains 1-3 may be application blockchains built by their respective operators for users to call various smart contracts. In particular, in an embodiment of the present application, the management blockchain 4 may include a management node 401, multiple execution nodes 402, and one or more proposal nodes 403. Each proposal node 403 may be a node used by the owner or operator of the application blockchain or the application blockchain, and therefore each proposal node 403 may correspond to one or more application blockchains, and may initiate a proposal request based on the management requirements of the operator or owner of each application blockchain for the application blockchain. In an embodiment of the present application, a proposal request initiated by a proposal node 403 in the management blockchain may be verified and judged by the management node, and in particular, the management node 401 may be verified and judged based on consensus processing based on the feedback results of other proposal nodes 403 for the proposal request.

[0032] For example, the operator of application blockchain 1 wants to adjust the transaction fee for calling smart contracts on application blockchain 1, for example, from the current price A to price B. In this case, the operator can log in to the proposal node 403 assigned to it or designated by it to initiate the transaction fee adjustment proposal request, in which the operator can include the identification of the application blockchain it wants to adjust (for example, application blockchain 1), the item information it wants to manage (for example, transaction fee) and the management target information (for example, price B). In addition, the operator can further include the requirement information for the proposal to be passed in the proposal request, for example, the number of feedbacks that agree to the proposal in the consensus process or the number of proposal nodes that send consent feedback can be specified, or the identification of the proposal node that sends consent feedback, as well as the response time of effective feedback and other information. Of course, when the proposal request of the proposal node 403 that initiates the proposal does not contain such requirement information, the management node 401 can verify and judge the initiated proposal according to the proposal passing information preset on the management blockchain. For example, the management node 401 can perform consensus processing on the proposal proposed by the proposal node 403 to modify the transaction price of the application blockchain 1 based on the consensus mechanism in which all the proposal nodes 403 send consent feedback.

[0033] After the management node 401 processes the proposal request based on the feedback sent by each proposal node 403, for example, when the feedback sent by other proposal nodes 403 is all in agreement, the management node 401 can confirm the proposal request and generate a management instruction based on the proposal request, and the management instruction can include the identification information of the application blockchain 1 of the target blockchain as the management target, as well as the transaction price requested in the proposal request and the modification target of the transaction price. In the embodiment of the present application, the management node 401 can generate the management instruction by the generation module therein, or send the proposal request and its consensus result to the management instruction generation contract on the management blockchain to generate the management instruction, and the present application has no limitation on this.

[0034] The management node 401 can further obtain the execution node list according to the acquired management instruction. In the embodiment of the present application, the execution node list can be a list of execution nodes 402 on the management blockchain 4 that can be used to execute the management instruction for the application blockchain. The execution node list can be updated according to the connectivity of the execution node 402, or the execution node 402 with a load lower than a predetermined threshold can be included in the execution node list according to the load of the execution node 402.

[0035] The management node 401 can determine an execution node as a calling node for managing the target blockchain specified in the management instruction based on the management instruction and the acquired execution node list. For example, the management node 401 can obtain the current workload or execution information of each execution node in the execution node list, and sort the execution nodes in the execution node list according to the workload or execution information, so that the execution node sorted first can be regarded as the execution node with the smallest current workload, and it is determined as the calling node for executing the current management instruction. In an embodiment of the present application, the management node 401 can also select an execution node from the execution node list based on other information. For example, the management node 401 can obtain the network response time of each execution node in the execution node list for the target application blockchain, and determine the execution node with the shortest network response time as the calling node for executing the current management instruction.

[0036] The management node 401 can further generate a call request for instructing the calling node to execute the management instruction on the target blockchain based on the acquired management instruction and the determined node information of the calling node. In an embodiment of the present application, the call request can be sent to the smart contract on the management blockchain to call the calling node to execute the management instruction. For example, the calling node can generate a transaction request based on the call request generated by the management node 401 and the chain information of the target blockchain, such as the application blockchain 1, to send to each node on the target blockchain, or in an embodiment of the present application, the calling node can send the transaction request to any node on the application blockchain 1, and the node that receives the request forwards or broadcasts the transaction request to other nodes on the application blockchain 1.

[0037] In an embodiment of the present application, the transaction request may include management entry information and management target information of the management instruction. For example, the transaction request may include transaction fee information and transaction fee modification target information that needs to be modified to price B. Each node on the target blockchain can call the corresponding contract according to the transaction request to generate a transaction block locally at each node. For example, when the transaction fee information is included as management entry information in the transaction request, the node receiving the transaction request can call the transaction fee modification contract to change the transaction fee to the transaction fee modification target information included in the transaction request, that is, price B, and use the modification result as the transaction result of the transaction request to generate a block. Since each node in the application blockchain 1 modifies the transaction fee according to the transaction request and generates the corresponding block, the same block height can be reached in each node according to the same business logic, thereby realizing the change of the transaction price of the entire blockchain network. After generating the block, each node can feed back the execution result of the transaction request to the application blockchain 1, and send it to the calling node through the application blockchain 1, so that the calling node can determine whether the management operation is completed according to the transaction result fed back by the node in the application blockchain 1. For example, it can determine whether the management operation is completed according to the number of nodes that have fed back the successful execution of the transaction request, and generate corresponding operation result information to finally feed back to the management node 401.

[0038] The management node 401 can process according to a predetermined strategy based on the operation result information. For example, when the feedback is that the management operation is successful, the successful result can be fed back to the proposal node, and when the feedback is that the management operation is unsuccessful, or the number of nodes that successfully process the feedback transaction request is lower than a threshold, the management node 401 can instruct the calling node to execute the call instruction again, or it can also re-acquire the execution node list to re-determine the calling node, and use the newly determined calling node to execute the management instruction. Or in an embodiment of the present application, the management node 401 can also send the feedback result to the proposal node, and wait for the proposal node to generate a new management instruction. Of course, in an embodiment of the present application, the proposal node can directly generate a management instruction for the management node 401 for the management instruction that failed to execute, or it can also regenerate a proposal request, and the management node 401 can generate a new management instruction again based on the feedback from other proposal nodes.

[0039] Therefore, the multi-blockchain management solution provided by the embodiment of the present application is determined by the management node according to the received management instruction generated for at least one target blockchain in multiple application blockchains and the list of execution nodes, and the management node generates a call request according to the management instruction and the node information of the call node, and the call node performs management operations on the target blockchain according to the call request. Therefore, the management node in the management blockchain can respond to the management instruction, and the call node can execute the call instruction generated according to the management instruction for the target blockchain, thereby not only realizing the unified management of multiple application blockchains in a multi-blockchain environment, but also being able to respond to the management instruction for the application blockchain in real time and perform the corresponding management operation by calling the execution node, thereby greatly improving the execution timeliness of the management instruction for the application blockchain.

[0040] The above embodiments are illustrations of the technical principles and exemplary application frameworks of the embodiments of the present application. The specific technical solutions of the embodiments of the present application are further described in detail below through multiple embodiments.

[0041] Embodiment 2

[0042] Figure 2The flowchart of the embodiment of the unified execution method of management instructions for multiple blockchains provided by the present application, the execution subject of the method can be various terminals or server devices deployed on the blockchain as nodes or modules in the nodes, or it can be a device or chip integrated on these devices. In particular, the multi-blockchain to which the method of the embodiment of the present application can be applied may include a management blockchain and multiple application blockchains. The management blockchain may be a blockchain in the multi-blockchain specifically used to manage each application blockchain, and the application blockchain may be an application blockchain built by the respective operators for users to call various smart contracts. In particular, in the embodiment of the present application, the management blockchain may include a management node, multiple execution nodes, and one or more proposal nodes. Each proposal node may be a node used by the owner or operator of the application blockchain or the application blockchain, and therefore each proposal node may correspond to one or more application blockchains, and a proposal request may be initiated according to the management requirements of the operator or owner of each application blockchain for the application blockchain, and the management node may respond to the proposal request to perform corresponding processing in the multi-blockchain. For example, in the embodiment of the present application, the unified execution method of management instructions for multiple blockchains may include:

[0043] S201, a management node in a management blockchain obtains a management instruction for at least one target blockchain among multiple application blockchains.

[0044] In step S201, the management node in the management blockchain may obtain a management instruction, which may be a management instruction for at least one target blockchain in multiple application blockchains. For example, the management instruction may include the blockchain identification information, management item information, and management target information of the target blockchain. In an embodiment of the present application, the management instruction may be a management instruction initiated by the operator of the application blockchain by calling the management contract on the management blockchain, or the operator may initiate a proposal request through a proposal node assigned to the operator of the application blockchain, and then the management node generates a management instruction based on the proposal request. For example, in an embodiment of the present application, the operator may initiate a proposal request in the management blockchain through its proposal node according to its management needs, and the proposal request may be verified and judged by the management node. In particular, the management node may verify and judge based on consensus processing based on the feedback results of other proposal nodes for the proposal request.

[0045] For example, the operator of one of the multiple application blockchains wants to adjust the transaction fee for calling a smart contract on the application blockchain, for example, from the current price A to price B. In this case, the operator can log in to the proposal node assigned to it or designated by it to initiate the transaction fee adjustment proposal request, in which the operator can include the identification of the application blockchain it wants to adjust, the item information it wants to manage (for example, transaction fee), and the management target information (for example, price B). In addition, the operator can further include the requirement information for the proposal to pass in the proposal request, for example, the number of feedbacks that agree to the proposal or the number of proposal nodes that send consent feedback in the consensus process can be specified, or the identification of the proposal node that sends consent feedback, as well as the response time of effective feedback and other information. Of course, when the proposal request of the proposal node that initiates the proposal does not contain such requirement information, the management node can verify and judge the initiated proposal based on the proposal pass information preset on the management blockchain. For example, the management node can perform consensus processing on the proposal node's proposal to modify the transaction price of the application blockchain based on the consensus mechanism that all proposal nodes send consent feedback.

[0046] After the management node processes the proposal request based on the feedback sent by each proposal node, for example, when the feedback sent by other proposal nodes is all in agreement, the management node can confirm the proposal request, and can generate a management instruction based on the proposal request in the management blockchain, and the management instruction can include the identification information of the application blockchain of the target blockchain as the management target, as well as the transaction price requested in the proposal request and the modification target of the transaction price, etc. In the embodiment of the present application, the management node can generate the management instruction by the generation module therein, or send the proposal request and its consensus result to the management instruction generation contract on the management blockchain to generate the management instruction, and the present application has no limitation on this.

[0047] S202: The management node obtains an execution node list according to the management instruction.

[0048] In step S202, the management node may obtain a list of execution nodes according to the management instruction obtained in step S201. For example, in an embodiment of the present application, the list of execution nodes may be a list of execution nodes on the management blockchain that can be used to execute the management instruction on the application blockchain. The list of execution nodes may be updated according to the connectivity of the execution nodes, or the execution nodes with a load lower than a predetermined threshold may be included in the list of execution nodes according to the load of the execution nodes.

[0049] S203, the management node determines, according to the management instruction and the execution node list, an execution node in the execution node list as a calling node for executing the management instruction on the target blockchain.

[0050] In step S203, the management node can determine one or more execution nodes as the calling nodes for managing the target blockchain specified in the management instruction according to the management instruction obtained in step S201 and the execution node list obtained in step S202. For example, the management node can obtain the current workload or execution information of each execution node in the execution node list in step S203, and sort the execution nodes in the execution node list according to the workload or execution information, so that the execution node ranked first can be regarded as the execution node with the smallest current workload, and it is determined as the calling node for executing the current management instruction. In an embodiment of the present application, the management node can also select two or more execution nodes in the execution node list as the execution nodes for executing management of the target blockchain. For example, the management node can first sort according to the workload and select the execution node ranked first, that is, the execution node with the smallest workload load as one of the calling nodes, and then sort based on the computing resources of the execution node, and select the execution node ranked first in resources as another calling node.

[0051] In addition, in an embodiment of the present application, the management node may also select an execution node from the execution node list based on other information. For example, the management node may obtain the network response time of each execution node in the execution node list to the target application blockchain, and determine the execution node with the shortest network response time as the calling node for executing the current management instruction.

[0052] S204, the management node generates a call request for the calling node to execute the management instruction on the target blockchain according to the management instruction and the node information of the calling node.

[0053] S205, the calling node performs management operations on the target blockchain according to the calling request.

[0054] In step S204, the management node may further generate a call request for instructing the calling node to execute the management instruction on the target blockchain according to the management instruction obtained in step S201 and the node information of the calling node determined in step S203. In step S205, the calling node may perform a management operation on the target blockchain according to the call request generated in step S204. For example, in an embodiment of the present application, the call request may be sent to a smart contract on the management blockchain to call the calling node to execute the management instruction. For example, the calling node determined in step S203 may generate a transaction request according to the call request generated by the management node and the chain information of the target blockchain, such as the application blockchain, to be sent to each node on the target blockchain, or in an embodiment of the present application, the calling node may send the transaction request to any node on the application blockchain, and the node that receives the request may forward or broadcast the transaction request to other nodes on the application blockchain.

[0055] In an embodiment of the present application, the transaction request used in step S205 may include management entry information and management target information of the management instruction. For example, the transaction request may include transaction fee information and transaction fee modification target information that needs to be modified to price B. Each node on the target blockchain can call the corresponding contract according to the transaction request to generate a transaction block locally at each node. For example, when the transaction fee information is included as management entry information in the transaction request, the node receiving the transaction request can call the transaction fee modification contract to change the transaction fee to the transaction fee modification target information included in the transaction request, that is, price B, and use the modification result as the transaction result of the modified transaction request to generate a block. Since each node in the application blockchain modifies the transaction fee according to the transaction request and generates the corresponding block, the same block height can be reached in each node according to the same business logic, thereby realizing the change of the transaction price of the entire blockchain network. After generating the block, each node can feed back the execution result of the transaction request to the application blockchain, and send it to the calling node through the application blockchain, so that the calling node can determine whether the management operation is completed according to the transaction result fed back by the node in the application blockchain. For example, it can determine whether the management operation is completed according to the number of nodes that have fed back the successful execution of the transaction request, and generate corresponding operation result information to finally feed back to the management node.

[0056] In addition, in an embodiment of the present application, after the calling node performs a management operation on the target blockchain in step S205, the management node can process according to a predetermined strategy based on the operation result information. For example, when the feedback is that the management operation is successful, the success result can be fed back to the proposal node, and when the feedback is that the management operation is unsuccessful, or the number of nodes that successfully process the feedback transaction request is lower than a threshold, the management node can instruct the calling node to execute the call instruction again, or it can also re-acquire the execution node list to re-determine the calling node, and use the newly determined calling node to execute the management instruction. Or in an embodiment of the present application, the management node can also send the feedback result to the proposal node and wait for the proposal node to generate a new management instruction. Of course, in an embodiment of the present application, the proposal node can directly generate a management instruction for the management node for the management instruction that failed to execute, or it can also regenerate a proposal request, and the management node generates a new management instruction again based on the feedback of other proposal nodes.

[0057] Therefore, the unified execution method of management instructions for multiple blockchains provided in the embodiment of the present application is determined by the management node according to the received management instructions generated for at least one target blockchain in multiple application blockchains and the list of execution nodes to determine the calling node for executing the management instructions for the target blockchain, and the management node generates a call request according to the management instructions and the node information of the calling node, and the calling node performs management operations on the target blockchain according to the call request. Therefore, the management node in the management blockchain can respond to the management instruction, and the calling node can execute the call instruction generated according to the management instruction for the target blockchain, thereby not only realizing the unified management of multiple application blockchains in a multi-blockchain environment, but also being able to respond to the management instructions for the application blockchain in real time and perform the corresponding management operations by calling the execution node, thereby greatly improving the execution timeliness of the management instructions for the application blockchain.

[0058] Embodiment 3

[0059] Figure 3 This is a system block diagram of a multi-blockchain system provided by the present application. The multi-blockchain system can be used to implement, for example, Figure 2The described embodiment of the present application provides a unified execution method for management instructions for multiple blockchains. The multi-blockchain system may include: a management blockchain 311 and multiple application blockchains 312. The management blockchain 311 may be a blockchain specifically used to manage each application blockchain 312 in the multi-blockchain system, and the application blockchain 312 may be an application blockchain built by each operator for users to call various smart contracts. In particular, in an embodiment of the present application, the management blockchain 311 may include a management node 3111, multiple execution nodes 3112, and one or more proposal nodes 3113. Each proposal node 3113 may be a node used by the owner or operator of the application blockchain 312 or the application blockchain 312, and therefore each proposal node 3113 may correspond to one or more application blockchains 312, and may initiate a proposal request according to the management requirements of the operator or owner of each application blockchain 312 for the application blockchain 312, and the management node 3111 may respond to the proposal request to perform corresponding processing in the multi-blockchain system. The application blockchain 312 may include multiple application nodes 3121.

[0060] The management node 3111 can be used to obtain management instructions for at least one target blockchain among the multiple application blockchains 312; obtain an execution node list according to the management instructions; determine an execution node in the execution node list as a calling node for executing the management instruction on the target blockchain according to the management instructions and the execution node list; and generate a calling request for the calling node to execute the management instruction on the target blockchain according to the management instructions and the node information of the calling node.

[0061] For example, the management node 3111 in the management blockchain 311 can obtain a management instruction, which can be a management instruction for at least one target blockchain in the multiple application blockchains 312. For example, the management instruction can include the blockchain identification information, management item information, and management target information of the target blockchain. In an embodiment of the present application, the management instruction can be a management instruction initiated by the operator of the application blockchain 312 by calling the management contract on the management blockchain 311, or it can be a proposal request initiated by the operator through the proposal node 3113 assigned to the operator of the application blockchain 312, and then the management node 3111 generates a management instruction based on the proposal request. For example, in an embodiment of the present application, the operator can initiate a proposal request in the management blockchain 311 through its proposal node 3113 according to its management needs, and the proposal request can be verified and judged by the management node 3111. In particular, the management node 3111 can be verified and judged based on consensus processing based on the feedback results of other proposal nodes 3113 for the proposal request.

[0062] For example, the operator of an application blockchain 312 among multiple application blockchains wants to adjust the transaction fee for calling a smart contract on the application blockchain, for example, from the current price A to price B. In this case, the operator can log in to the proposal node 3113 assigned to it or designated by it to initiate the transaction fee adjustment proposal request, in which the operator can include the identification of the application blockchain 312 that it wants to adjust, the item information that it wants to manage (for example, transaction fee), and the management target information (for example, price B). In addition, the operator can further include the requirement information for the proposal to be passed in the proposal request, for example, the number of feedbacks that agree with the proposal in the consensus process or the number of proposal nodes that send consent feedback can be specified, or the identification of the proposal node that sends consent feedback, as well as the response time of effective feedback and other information. Of course, when the proposal request of the proposal node that initiates the proposal does not contain such requirement information, the management node 3111 can verify and judge the initiated proposal according to the proposal passing information preset on the management blockchain 311. For example, the management node 3111 can perform consensus processing on the proposal put forward by the proposal node 3113 to modify the transaction price of the application blockchain 312 based on a consensus mechanism in which all the proposal nodes 3113 send consent feedback.

[0063] After the management node 3111 processes the proposal request based on the feedback sent by each proposal node 3113, for example, when the feedback sent by other proposal nodes 3113 is all in agreement, the management node 3111 can confirm the proposal request, and can generate a management instruction based on the proposal request in the management blockchain 311, and the management instruction can include the identification information of the application blockchain 312 of the target blockchain as the management target, and the transaction price requested in the proposal request and the modification target of the transaction price. In the embodiment of the present application, the management node 3111 can generate the management instruction by the generation module therein, or send the proposal request and its consensus result to the management instruction generation contract on the management blockchain 311 to generate the management instruction, and the present application has no limitation on this.

[0064] In addition, the management node 3111 can also obtain the execution node list according to the management instruction it obtains. For example, in the embodiment of the present application, the execution node list can be a list of execution nodes 3112 on the management blockchain 311 that can be used to execute the management instruction for the application blockchain 312. The execution node list can be updated according to the connectivity of the execution node 3112, or the execution node with a load lower than a predetermined threshold can be included in the execution node list according to the load of the execution node 3112.

[0065] The management node 3111 can determine one or more execution nodes 3112 as the calling node for managing the target blockchain specified in the management instruction according to the acquired management instruction and the acquired execution node list. For example, the management node 3111 can obtain the current workload or execution information of each execution node 3112 in the execution node list, and sort the execution nodes 3112 in the execution node list according to the workload or execution information, so that the execution node 3112 ranked first can be regarded as the execution node with the smallest current workload, and it is determined as the calling node for executing the current management instruction. In an embodiment of the present application, the management node 3111 can also select two or more execution nodes 3112 in the execution node list as the execution nodes for executing management of the target blockchain. For example, the management node 3111 can first sort according to the workload and select the execution node ranked first, that is, the execution node with the smallest workload load as one of the calling nodes, and then sort based on the computing resources of the execution node 3112, and select the execution node ranked first in resources as another calling node.

[0066] In addition, in an embodiment of the present application, the management node 3111 may also select an execution node 3112 from the execution node list based on other information. For example, the management node 3111 may obtain the network response time of each execution node in the execution node list for the target application blockchain, and determine the execution node 3112 with the shortest network response time as the calling node for executing the current management instruction.

[0067] The management node 3111 can also further generate a call request for instructing the calling node to execute the management instruction on the target blockchain based on the acquired management instruction and the determined node information of the calling node.

[0068] The calling node may perform management operations on the target blockchain according to the generated call request. For example, in an embodiment of the present application, the call request may be sent to a smart contract on the management blockchain 311 to call the calling node to execute the management instruction. For example, the calling node determined by the management node 3111 may generate a transaction request based on the call request generated by the management node 3111 and the chain information of the target blockchain, such as the application blockchain, to be sent to each node 3121 on the target blockchain, or in an embodiment of the present application, the calling node may send the transaction request to any node 3121 on the application blockchain, and the node 3121 that receives the request may forward or broadcast the transaction request to other nodes on the application blockchain.

[0069] In an embodiment of the present application, the transaction request may include management entry information and management target information of the management instruction. For example, the transaction request may include transaction fee information and transaction fee modification target information that needs to be modified to price B. Each node 3121 on the target blockchain can call the corresponding contract according to the transaction request to generate a transaction block locally at each node. For example, when the transaction fee information is included as management entry information in the transaction request, the node 3121 that receives the transaction request can call the transaction fee modification contract to change the transaction fee to the transaction fee modification target information included in the transaction request, that is, price B, and use the modification result as the transaction result of the modified transaction request to generate a block. Since each node 3121 in the application blockchain modifies the transaction fee according to the transaction request and generates the corresponding block, the same block height can be reached in each node 3121 according to the same business logic, thereby realizing the change of the transaction price of the entire blockchain network. After generating the block, each node 3121 can feed back the execution result of the transaction request to the application blockchain, and send it to the calling node through the application blockchain, so that the calling node can determine whether the management operation is completed based on the transaction results fed back by the nodes in the application blockchain. For example, it can determine whether the management operation is completed based on the number of nodes that have fed back the successful execution of the transaction request, and generate corresponding operation result information to ultimately feed back to the management node 3111.

[0070] In addition, in an embodiment of the present application, after the calling node performs a management operation on the target blockchain, the management node can process according to a predetermined strategy based on the operation result information. For example, when the feedback is that the management operation is successful, the success result can be fed back to the proposal node 3113, and when the feedback is that the management operation is unsuccessful, or the number of nodes that successfully process the feedback transaction request is lower than the threshold, the management node 3111 can instruct the calling node to execute the call instruction again, or it can also re-acquire the execution node list to re-determine the calling node, and use the newly determined calling node to execute the management instruction. Or in an embodiment of the present application, the management node 3111 can also send the feedback result to the proposal node 3113, and wait for the proposal node 3113 to generate a new management instruction. Of course, in an embodiment of the present application, the proposal node 3113 can directly generate a management instruction for the management node 3111 for the management instruction that failed to execute, or it can also regenerate a proposal request, and the management node 3111 can generate a new management instruction again based on the feedback of other proposal nodes.

[0071] Therefore, the multi-blockchain system provided by the embodiment of the present application determines the calling node for executing the management instruction for the target blockchain according to the received management instruction generated for at least one target blockchain in multiple application blockchains and the list of execution nodes by the management node of the management blockchain, and generates a call request according to the management instruction and the node information of the calling node, and executes the management operation on the target blockchain according to the call request by the calling node. Therefore, the management node in the management blockchain can respond to the management instruction, and the calling node can execute the call instruction generated according to the management instruction for the target blockchain, thereby not only realizing the unified management of multiple application blockchains in the multi-blockchain environment, but also being able to respond to the management instruction for the application blockchain in real time and perform the corresponding management operation by calling the execution node, thereby greatly improving the execution timeliness of the management instruction for the application blockchain.

[0072] Embodiment 4

[0073] The above describes a method for unified execution of management instructions for multiple blockchains, which can be implemented as an electronic device. Figure 4 This is a schematic diagram of the structure of an electronic device embodiment provided by this application. Figure 4 As shown, the electronic device includes a memory 41 and a processor 42 .

[0074] The memory 41 is used to store programs. In addition to the above programs, the memory 41 can also be configured to store various other data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on the electronic device, contact data, phone book data, messages, pictures, videos, etc.

[0075] The memory 41 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0076] The processor 42 is not limited to a processor (CPU), but may also be a processing chip such as a graphics processing unit (GPU), a field programmable gate array (FPGA), an embedded neural network processor (NPU) or an artificial intelligence (AI) chip. The processor 42 is coupled to the memory 41 and executes the program stored in the memory 41 to execute the unified execution method of management instructions for multiple blockchains in the above-mentioned embodiment 2.

[0077] Further, if Figure 4As shown, the electronic device may also include: a communication component 43, a power component 44, an audio component 45, a display 46 and other components. Figure 4 Only some components are shown schematically, which does not mean that the electronic device only includes Figure 4 Components shown.

[0078] The communication component 43 is configured to facilitate wired or wireless communication between the electronic device and other devices. The electronic device can access a wireless network based on a communication standard, such as WiFi, 3G, 4G or 5G, or a combination thereof. In an exemplary embodiment, the communication component 43 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 43 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0079] The power supply assembly 44 provides power to various components of the electronic device. The power supply assembly 44 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device.

[0080] The audio component 45 is configured to output and / or input audio signals. For example, the audio component 45 includes a microphone (MIC), and when the electronic device is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 41 or sent via the communication component 43. In some embodiments, the audio component 45 also includes a speaker for outputting audio signals.

[0081] The display 46 includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

[0082] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0083] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for unified execution of management instructions for multiple blockchains, characterized in that: The multiple blockchains include a management blockchain and multiple application blockchains, and the method includes: A management node in the management blockchain obtains a management instruction for at least one target blockchain in the multiple application blockchains, wherein the management instruction includes blockchain identification information, management item information, and management target information of the target blockchain; The management node obtains an execution node list according to the management instruction, wherein the execution node list includes at least one execution node currently available in the management blockchain, and the execution node is a node in the management blockchain used to perform management operations on the application blockchain; The management node determines, according to the management instruction and the execution node list, an execution node in the execution node list as a calling node for executing the management instruction on the target blockchain; The management node generates a call request for the calling node to execute the management instruction on the target blockchain according to the management instruction and the node information of the calling node; The calling node performs a management operation on the target blockchain according to the calling request.

2. The method for unified execution of management instructions for multiple blockchains according to claim 1 is characterized in that: The performing of a management operation on the target blockchain by the calling node according to the calling request includes: The calling node generates a transaction request according to the calling request and the chain information of the target blockchain, and sends it to each node on the target blockchain, wherein the transaction request includes management item information and management target information of the management instruction; Each node on the target blockchain calls a corresponding contract according to the transaction request to generate a transaction block locally on each node; When the transaction block generated in each node reaches the block height determined according to the transaction request, each node on the target blockchain simultaneously executes the modification of the management entry according to the management entry information and the management target information in the transaction request; The calling node generates operation result information of the management operation according to the transaction results fed back by a predetermined number of nodes in the target blockchain.

3. The method for unified execution of management instructions for multiple blockchains according to claim 2 is characterized in that: The management blockchain further includes a plurality of proposal nodes, wherein each proposal node corresponds to an application blockchain among the plurality of application blockchains, and the obtaining, by the management node in the management blockchain, a management instruction for at least one target blockchain among the plurality of application blockchains includes: One of the multiple proposal nodes in the management blockchain acts as an initiating node to send a proposal request to the management node, wherein the proposal request includes blockchain identification information, management item information, management target information, and proposal approval requirement information of the target blockchain; The management node broadcasts the proposal request to at least one proposal node among the multiple proposal nodes except the initiating node; The management node generates a consensus result for the proposal request according to the proposal feedback information sent by the at least one proposal node and the proposal passing requirement information; The management instruction is generated according to the consensus result.

4. The method for unified execution of management instructions for multiple blockchains according to claim 3 is characterized in that: The management item information includes a price, and the management target information includes an adjustment target of a price to be adjusted.

5. The method for unified execution of management instructions for multiple blockchains according to claim 1 is characterized in that: The step of determining, by the management node according to the management instruction and the execution node list, an execution node in the execution node list as a calling node for executing the management instruction on the target blockchain includes: The management node obtains the execution information of each execution node in the execution node list; sorting each execution node according to the execution information; The calling node is determined according to the sorting result.

6. A multi-blockchain system, characterized in that: The multi-blockchain system includes a management blockchain and multiple application blockchains. The management blockchain includes a management node and a plurality of execution nodes, wherein the management node is used to obtain a management instruction for at least one target blockchain among the plurality of application blockchains, wherein the management instruction includes blockchain identification information, management item information, and management target information of the target blockchain; obtaining an execution node list according to the management instruction, wherein the execution node list includes at least one execution node currently available in the management blockchain, and the execution node is a node in the management blockchain used to perform management operations on the application blockchain; determining an execution node in the execution node list as a calling node for executing the management instruction on the target blockchain according to the management instruction and the execution node list; generating a call request for the calling node to execute the management instruction on the target blockchain according to the management instruction and the node information of the calling node; The calling node is used to perform management operations on the target blockchain according to the calling request.

7. The multi-blockchain system according to claim 6, characterized in that: The calling node is further used to: A transaction request is generated according to the call request and the chain information of the target blockchain, so as to be sent to each node on the target blockchain, wherein the transaction request contains the management entry information and the management target information of the management instruction, and Each node on the target blockchain is used to: call the corresponding contract according to the transaction request to generate a transaction block locally at each node; when the transaction block generated in each node reaches the block height determined according to the transaction request, each node on the target blockchain simultaneously executes the change of the management item according to the management item information and the management target information in the transaction request, and The calling node is further used to generate operation result information of the management operation according to the transaction results fed back by a predetermined number of nodes in the target blockchain.

8. The multi-blockchain system according to claim 7, characterized in that: The management blockchain further includes a plurality of proposal nodes, and One of the multiple proposal nodes is used as an initiating node to send a proposal request to the management node, wherein the proposal request includes blockchain identification information, management item information, management target information and proposal approval requirement information of the target blockchain, and The management node is further used to broadcast the proposal request to at least one proposal node among the multiple proposal nodes except the initiating node; generate a consensus result for the proposal request based on the proposal feedback information sent by the at least one proposal node and the proposal passing requirement information; and generate the management instruction based on the consensus result.

9. A computer-readable storage medium having a computer program executable by a processor stored thereon, characterized in that: When the program is executed by a processor, the method for unified execution of management instructions for multiple blockchains as described in any one of claims 1 to 5 is implemented.

Images