Block chain management method and system, block chain node and readable storage medium

Abstract

The invention provides a block chain management method and system, a block chain node and a readable storage medium, relates to the technical field of block chains, and can reduce the management pressure of the management node and improve the block chain management efficiency. The method is applied to a consensus node of a block chain, the block chain further comprises a management node and a target node, and the method comprises the following steps: receiving a verification request message of the management node; the verification request message comprises a target identifier of the target management request information; determining target verification information in the target management request information based on the target identifier; the target verification information is used for verifying the target management request information; sending a verification response message to the management node; the verification response message comprises target verification information; receiving an indication message of the management node; the indication message is used for indicating that the verification result of the target management request information is passed; determining the state of the target management request information as a first state; the first state is used for indicating that the target node is allowed to execute the target management operation on the block chain.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and in particular to a blockchain management method, system, blockchain node and readable storage medium. Background Art

[0002] In order to manage a blockchain, an existing solution is that a node with management authority in the blockchain, such as a management node, performs management operations on the blockchain.

[0003] However, with the increase in the number of blockchain nodes, the management pressure on the management node is relatively large, and the existing centralized management solution will lead to a decrease in the efficiency of blockchain management. Summary of the Invention

[0004] The present application provides a blockchain management method, system, blockchain node and readable storage medium, which can reduce the management pressure on the management node and improve the efficiency of blockchain management.

[0005] To achieve the above object, the present application adopts the following technical solutions:

[0006] In a first aspect, a blockchain management method is provided. The method is applied to a consensus node of a blockchain. The blockchain further includes a management node and a target node. The consensus node stores target management request information of the target node. The target management request information is used to request management authority for the target node to perform a target management operation on the blockchain. The method includes: receiving a verification request message from the management node; the verification request message includes a target identifier of the target management request information; determining target verification information in the target management request information based on the target identifier; the target verification information is used to verify the target management request information; sending a verification response message to the management node; the verification response message includes the target verification information; receiving an indication message from the management node; the indication message is used to indicate that the verification result of the target management request information is passed; determining that the status of the target management request information is a first status; the first status is used to indicate that the target node is allowed to perform the target management operation on the blockchain.

[0007] Based on this solution, compared with the existing solution where only the management node can perform management operations on the blockchain, in the solution of this application, the consensus node receives a verification request message from the management node that includes the target identifier of the target management request information. Then, based on the target identifier, it determines the target verification information used to verify the target management request information in the target management request information. Then, it sends a verification response message including the target verification information to the management node. After receiving an indication message from the management node indicating that the verification result of the target management request information is passed, it determines that the status of the target management request information is the first status. Since the first status is used to indicate that the target node is allowed to perform target management operations on the blockchain, therefore, it can enable the management operations to be executed by the target node, and the management operations no longer need to be executed by the management node, thereby reducing the management pressure on the management node and improving the efficiency of blockchain management.

[0008] In combination with the first aspect, in some embodiments of the first aspect, the method further includes: receiving an authorization signature request message from the target node; the authorization signature request message includes a target identifier; determining the target management request information according to the target identifier, and when the status of the target management request information is the first status, sending an authorization signature response message to the target node; the authorization signature response message includes the authorization signature of the consensus node.

[0009] Based on this solution, the consensus node receives an authorization signature request message from the target node that includes a target identifier. Then, when the status of the target management request information is the first status, it sends an authorization signature response message including the authorization signature of the consensus node to the target node, enabling the target node to obtain the authorization signature for the target node to manage the blockchain.

[0010] In combination with the first aspect, in some embodiments of the first aspect, the method further includes: receiving a transaction request message from the target node; the transaction request message includes the operation result of the target management operation and at least one authorization signature; when the number of target authorization signatures is greater than a preset threshold, determining that the operation result takes effect; the target authorization signature is a valid authorization signature among the at least one authorization signature.

[0011] Based on the solution, the consensus node receives a transaction request message from the target node that includes the operation result of the target management operation and at least one authorization signature. When the number of target authorization signatures is greater than a preset threshold, it can determine that the operation content takes effect.

[0012] In combination with the first aspect, in some embodiments of the first aspect, the method further includes: receiving a management request message of a target node; the management request message includes target management request information; generating a target identifier according to the target management request information, and storing the target identifier and the target management request information; determining that the status of the target management request information is a second status; the second status is used to indicate that the target management request information is to be verified.

[0013] Based on this solution, the consensus node can obtain the target identifier and the target management request information, and determine that the status of the target management request information is the second status by receiving the management request message of the target node including the target management request information, then generating the target identifier and storing the target identifier and the target management request information, and finally determining that the status of the target management request information is the second status for indicating that the target management request information is to be verified.

[0014] In combination with the first aspect, in some embodiments of the first aspect, the method further includes: receiving an identifier request message of a management node; the identifier request message is used to request the identifier of the management request information with the status of the second status; sending an identifier response message to the management node; the identifier response message includes the target identifier.

[0015] Based on this solution, the consensus node can enable the management node to obtain the target identifier by receiving the identifier request message of the management node for requesting the identifier of the management request information with the status of the second status, and then sending the identifier response message including the target identifier to the management node.

[0016] In a second aspect, a blockchain management method is provided. The method is applied to a management node of a blockchain. The blockchain further includes a consensus node and a target node. The method includes: sending a verification request message to the consensus node; the verification request message includes the target identifier of the target management request information, and the target management request information is used to request the management permission for the target node to perform a target management operation on the blockchain; receiving a verification response message of the consensus node; the verification response message includes target verification information, and the target verification information is used to verify the target management request information; verifying the target verification information, and in the case where the verification result is passed, sending an indication message to the consensus node; the indication message is used to indicate that the verification result of the target management request information is passed.

[0017] Based on this solution, the management node can enable the consensus node to know that the verification result of the target management request information is passed by sending the verification request message including the target identifier of the target management request information to the consensus node of the blockchain, then receiving the verification response message including the target verification information of the consensus node, and finally verifying the target verification information and sending the indication message for indicating that the verification result of the target management request information is passed to the consensus node in the case where the verification result is passed.

[0018] In combination with the second aspect, in some embodiments of the second aspect, the method further includes: sending an identification request message to the consensus node; the identification request message is used to request the identification of the management request information with the second status, and the second status is used to indicate that the target management request information is to be verified; receiving an identification response message from the consensus node; the identification response message includes the target identification.

[0019] Based on this solution, the management node can obtain the target identification by sending an identification request message for requesting the identification of the management request information with the second status to the consensus node, and then receiving the identification response message including the target identification from the consensus node.

[0020] In a third aspect, a blockchain management method is provided. The method is applied to a target node of a blockchain, and the blockchain further includes consensus nodes. The method includes: sending a management request message to the consensus node; the management request message includes target management request information, and the target management request information is used to request the management permission for the target node to perform a target management operation on the blockchain; receiving a management response message from the consensus node; the management response message is used to indicate that the status of the target management request information is the second status, and the second status is used to indicate that the target management request information is to be verified.

[0021] Based on this solution, the target node can know that the target management request information is to be verified by sending a management request message including the target management request information to the consensus node and then receiving the management response message from the consensus node. Since the management response message is used to indicate that the status of the target management request information is the second status, and the second status is used to indicate that the target management request information is to be verified.

[0022] In combination with the third aspect, in some embodiments of the third aspect, the method further includes: sending an authorization signature request message to the consensus node; the authorization signature request message includes the target identification, and the target identification is used to identify the target management request information; receiving an authorization signature response message from the consensus node; the authorization signature response message includes the authorization signature of the consensus node.

[0023] Based on this solution, the target node can obtain the authorization signature of the consensus node by sending an authorization signature request message including the target identification to the consensus node and then receiving the authorization signature response message including the authorization signature of the consensus node from the consensus node.

[0024] In combination with the third aspect, in some embodiments of the third aspect, the method further includes: sending a transaction request message to the consensus node; the transaction request message includes the operation result of the target management operation and at least one authorization signature; receiving a transaction response message from the consensus node; the transaction response message is used to indicate that the operation result takes effect.

[0025] Based on this solution, the target node sends a transaction request message including the operation result of the target management operation and at least one authorized signature to the consensus node, and then receives a transaction response message from the consensus node. Since the transaction response message is used to indicate that the operation result takes effect, it can be known that the operation result takes effect.

[0026] In a fourth aspect, a consensus node of a blockchain is provided for implementing the blockchain management method in the first aspect above. The consensus node includes corresponding modules, units, or means for implementing the above method, and the modules, units, or means can be implemented by hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0027] In combination with the fourth aspect, in some embodiments of the fourth aspect, the consensus node includes a transceiver module and a processing module. The blockchain further includes a management node and a target node. The consensus node stores target management request information of the target node, and the target management request information is used to request the management authority for the target node to perform a target management operation on the blockchain. The transceiver module is used to receive a verification request message from the management node; the verification request message includes the target identifier of the target management request information; the processing module is used to determine the target verification information in the target management request information based on the target identifier; the target verification information is used to verify the target management request information; the transceiver module is further used to send a verification response message to the management node; the verification response message includes the target verification information; the transceiver module is further used to receive an indication message from the management node; the indication message is used to indicate that the verification result of the target management request information is passed; the processing module is further used to determine that the status of the target management request information is the first status; the first status is used to indicate that the target node is allowed to perform a target management operation on the blockchain.

[0028] In combination with the fourth aspect, in some embodiments of the fourth aspect, the transceiver module is further used to receive an authorized signature request message from the target node; the authorized signature request message includes the target identifier; the processing module is further used to determine the target management request information according to the target identifier, and in the case where the status of the target management request information is the first status, send an authorized signature response message to the target node; the authorized signature response message includes the authorized signature of the consensus node.

[0029] In combination with the fourth aspect, in some embodiments of the fourth aspect, the transceiver module is further used to receive a transaction request message from the target node; the transaction request message includes the operation result of the target management operation and at least one authorized signature; the processing module is further used to determine that the operation result takes effect in the case where the number of target authorized signatures is greater than a preset threshold; the target authorized signature is a valid authorized signature among at least one authorized signature.

[0030] In combination with the fourth aspect, in some embodiments of the fourth aspect, the transceiver module is further configured to receive a management request message from a target node; the management request message includes target management request information; the processing module is further configured to generate a target identifier according to the target management request information, and store the target identifier and the target management request information; the processing module is further configured to determine that the status of the target management request information is a second status; the second status is used to indicate that the target management request information is to be verified.

[0031] In combination with the fourth aspect, in some embodiments of the fourth aspect, the transceiver module is further configured to receive an identifier request message from a management node; the identifier request message is used to request the identifier of the management request information whose status is the second status; the processing module is further configured to send an identifier response message to the management node; the identifier response message includes the target identifier.

[0032] In a fifth aspect, a management node of a blockchain is provided, which is used to implement the blockchain management method of the second aspect above. The management node includes corresponding modules, units, or means for implementing the above method, and the modules, units, or means can be implemented by hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0033] In combination with the fifth aspect, in some embodiments of the fifth aspect, the management node includes a transceiver module and a processing module, and the blockchain further includes a consensus node and a target node. The transceiver module is configured to send a verification request message to the consensus node; the verification request message includes the target identifier of the target management request information, and the target management request information is used to request the management permission for the target node to perform a target management operation on the blockchain; the transceiver module is further configured to receive a verification response message from the consensus node; the verification response message includes target verification information, and the target verification information is used to verify the target management request information; the processing module is configured to verify the target verification information, and in the case where the verification result passes, send an indication message to the consensus node; the indication message is used to indicate that the verification result of the target management request information passes.

[0034] In combination with the fifth aspect, in some embodiments of the fifth aspect, the transceiver module is further configured to send an identifier request message to the consensus node; the identifier request message is used to request the identifier of the management request information whose status is the second status, and the second status is used to indicate that the target management request information is to be verified; the transceiver module is further configured to receive an identifier response message from the consensus node; the identifier response message includes the target identifier.

[0035] In a sixth aspect, a target node of a blockchain is provided for implementing the blockchain management method in the above-mentioned third aspect. The management node includes corresponding modules, units, or means for implementing the above method, and the modules, units, or means can be implemented by hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0036] In combination with the sixth aspect, in some embodiments of the sixth aspect, the target node includes a transceiver module and a processing module. The blockchain further includes a consensus node. The transceiver module is configured to send a management request message to the consensus node. The management request message includes target management request information, and the target management request information is used to request the management permission for the target node to perform a target management operation on the blockchain. The processing module is configured to receive a management response message from the consensus node. The management response message is used to indicate that the status of the target management request information is a second status, and the second status is used to indicate that the target management request information is to be verified.

[0037] In combination with the sixth aspect, in some embodiments of the sixth aspect, the transceiver module is further configured to send an authorization signature request message to the consensus node. The authorization signature request message includes a target identifier, and the target identifier is used to identify the target management request information. The transceiver module is further configured to receive an authorization signature response message from the consensus node. The authorization signature response message includes the authorization signature of the consensus node.

[0038] In combination with the sixth aspect, in some embodiments of the sixth aspect, the transceiver module is further configured to send a transaction request message to the consensus node. The transaction request message includes the operation result of the target management operation and at least one authorization signature. The transceiver module is configured to receive a transaction response message from the consensus node. The transaction response message is used to indicate that the operation result takes effect.

[0039] In a seventh aspect, a consensus node of a blockchain is provided, including: at least one processor and a memory for storing instructions executable by the processor; wherein, the processor is configured to execute the instructions to implement the method provided in the first aspect and any possible implementation manner thereof.

[0040] In an eighth aspect, a management node of a blockchain is provided, including: at least one processor and a memory for storing instructions executable by the processor; wherein, the processor is configured to execute the instructions to implement the method provided in the second aspect and any possible implementation manner thereof.

[0041] In a ninth aspect, a target node of a blockchain is provided, including: at least one processor and a memory for storing instructions executable by the processor; wherein, the processor is configured to execute the instructions to implement the method provided in the third aspect and any possible implementation manner thereof.

[0042] In a tenth aspect, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of a consensus node of a data blockchain, the consensus node is enabled to execute the method provided in the first aspect and any possible implementation manner thereof.

[0043] In an eleventh aspect, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of a management node of a blockchain, the management node is enabled to execute the method provided in the second aspect and any possible implementation manner thereof.

[0044] In a twelfth aspect, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of a target node of a blockchain, the management node of the blockchain is enabled to execute the method provided in the third aspect and any possible implementation manner thereof.

[0045] In a thirteenth aspect, a computer program product containing instructions is provided. When it runs on a computer, the computer can execute the method provided in the first aspect and any possible implementation manner thereof.

[0046] In a fourteenth aspect, a computer program product containing instructions is provided. When it runs on a computer, the computer can execute the method provided in the second aspect and any possible implementation manner thereof.

[0047] In a fifteenth aspect, a computer program product containing instructions is provided. When it runs on a computer, the computer can execute the method provided in the third aspect and any possible implementation manner thereof.

[0048] In a sixteenth aspect, a chip system is provided, including: a processor and an interface circuit; the interface circuit is configured to receive a computer program or instructions and transmit them to the processor; the processor is configured to execute the computer program or instructions so that the chip system executes the method provided in the first aspect and any possible implementation manner thereof.

[0049] In a seventeenth aspect, a chip system is provided, including: a processor and an interface circuit; the interface circuit is configured to receive a computer program or instructions and transmit them to the processor; the processor is configured to execute the computer program or instructions so that the chip system executes the method provided in the second aspect and any possible implementation manner thereof.

[0050] In an eighteenth aspect, a chip system is provided, including: a processor and an interface circuit; the interface circuit is configured to receive a computer program or instructions and transmit them to the processor; the processor is configured to execute the computer program or instructions so that the chip system executes the method provided in the third aspect and any possible implementation manner thereof.

[0051] In the nineteenth aspect, a blockchain management system is provided. The system includes a consensus node of the blockchain, a management node of the blockchain, and a target node of the blockchain. The consensus node is used to execute the method provided in the first aspect and any possible implementation manner thereof as described above. The management node is used to execute the method provided in the second aspect and any possible implementation manner thereof as described above. The target node is used to execute the method provided in the third aspect and any possible implementation manner thereof as described above.

[0052] Among them, for the technical effects brought by any implementation manner from the third aspect to the nineteenth aspect, reference can be made to the technical effects brought by different implementation manners of the corresponding aspects as described above, and details are not repeated herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 It is a schematic diagram of the architecture of a blockchain management system provided by this application;

[0054] Figure 2 It is a schematic flowchart of a blockchain management method provided by this application;

[0055] Figure 3 It is a schematic flowchart of another blockchain management method provided by this application;

[0056] Figure 4 It is a schematic flowchart of another blockchain management method provided by this application;

[0057] Figure 5 It is a schematic flowchart of another blockchain management method provided by this application;

[0058] Figure 6 It is a schematic flowchart of another blockchain management method provided by this application;

[0059] Figure 7 It is a schematic flowchart of another blockchain management method provided by this application;

[0060] Figure 8 It is a schematic flowchart of another blockchain management method provided by this application;

[0061] Figure 9 It is a schematic flowchart of another blockchain management method provided by this application;

[0062] Figure 10 It is a schematic flowchart of another blockchain management method provided by this application;

[0063] Figure 11 It is a schematic flowchart of another blockchain management method provided by this application;

[0064] Figure 12 A flowchart diagram of another blockchain management method provided by this application;

[0065] Figure 13 A schematic structural diagram of a blockchain node provided by this application;

[0066] Figure 14 Another schematic structural diagram of a blockchain node provided by this application. Detailed implementation manners

[0067] In the description of this application, unless otherwise specified, "a plurality" means two or more than two. "At least one (item)" or similar expressions thereof refer to any combination of these items, including any combination of single item (s) or plural item (s). For example, at least one (item) of a, b, or c can represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, c can be single or multiple.

[0068] In addition, for the convenience of clearly describing the technical solutions of the embodiments of this application, in the embodiments of this application, terms such as "first" and "second" are used to distinguish identical items or similar items with basically the same functions and roles. Those skilled in the art can understand that the terms "first" and "second" do not limit the quantity and execution order, and the terms "first" and "second" do not necessarily mean different.

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

[0070] It can be understood that the "embodiments" mentioned throughout the specification mean that specific features, structures, or characteristics related to the embodiments are included in at least one embodiment of this application. Therefore, the various embodiments mentioned throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics can be combined in one or more embodiments in any suitable manner. It can be understood that in the various embodiments of this application, the magnitude of the serial numbers of the various processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of this application.

[0071] It can be understood that in this application, "when", "if", and "in case" all refer to corresponding processing under certain objective circumstances, rather than limiting time, and it is not required that there must be a judgment action during implementation, nor does it mean the existence of other limitations.

[0072] It can be understood that some optional features in the embodiments of this application can, in some scenarios, be implemented independently without relying on other features, such as the current solution they are based on, to solve corresponding technical problems and achieve corresponding effects. In some scenarios, they can also be combined with other features according to requirements. Correspondingly, the devices given in the embodiments of this application can also implement these features or functions accordingly, which will not be elaborated here.

[0073] In this application, unless otherwise specified, the same or similar parts among various embodiments can be referred to each other. In various embodiments of this application and each implementation method in the embodiments, if there is no special specification and logical conflict, the terms and / or descriptions among different embodiments and among each implementation method in the embodiments are consistent and can be mutually referenced. The technical features in different embodiments and among each implementation method in the embodiments can be combined according to their internal logical relationships to form new embodiments, implementation manners, implementation methods, or implementation approaches. The following implementation manners of this application do not constitute a limitation on the protection scope of this application.

[0074] Figure 1 It is a schematic diagram of the architecture of a blockchain management system provided by this application. The technical solutions of the embodiments of this application can be applied to Figure 1 the blockchain management system shown, such as Figure 1 shown, the blockchain management system 10 includes a consensus node 11, a management node 12, and a target node 13.

[0075] Among them, the consensus node 11 is respectively communicatively connected to the management node 12 and the target node 13.

[0076] The target node 13 can also be referred to as the user node 13.

[0077] Furthermore, the consensus node 11 can include an online audit module, a consensus module, an authorization module, and a verification module.

[0078] Among them, the online audit module is used to audit information, the consensus module is used to perform consensus processing on the target node, the authorization module is used to perform authorization processing on the target node, and the verification module is used to verify the legality of messages.

[0079] The management node 12 can include a first transaction construction module and an offline audit module.

[0080] Among them, the first transaction construction module is used to construct transactions, and the offline audit module is used to audit information.

[0081] The target node 13 may include a second transaction construction module and a signature module.

[0082] Among them, the second transaction construction module is used to construct transactions, and the signature module is used to obtain an authorized signature.

[0083] In practical applications, the blockchain management method provided by this application embodiment can be applied to the consensus node 11, the management node 12, or the target node 13, or can also be applied to the devices included in the consensus node 11, the management node 12, or the target node 13.

[0084] Next, in conjunction with the accompanying drawings, taking the blockchain management method applied to the consensus node 11, the management node 12, or the target node 13 as an example, the blockchain management method provided by this application embodiment will be described.

[0085] Figure 2 It is a schematic flowchart of a blockchain management method provided by this application. This method is applied to the consensus node of the blockchain. The blockchain also includes a management node and a target node. The consensus node stores the target management request information of the target node. The target management request information is used to request the management permission for the target node to perform target management operations on the blockchain, such as Figure 2 As shown, this method includes the following multiple steps:

[0086] S201. The consensus node receives the verification request message from the management node.

[0087] Among them, the verification request message includes the target identifier of the target management request information.

[0088] It should be noted that the target management request information may include the type of management operation, the name of the management operation, the version of the management operation, and / or the content of the management operation.

[0089] Exemplarily, the type of management operation may be type = 1, the name of the management operation may be name = mycc, the version of the management operation may be version = 1.0, and the content of the management operation may be value = smartContract.

[0090] The verification request message may also be referred to as a smart contract content acquisition transaction.

[0091] The target identifier may be the name of the management operation and / or the version of the management operation.

[0092] Exemplarily, if the name of the management operation is name = mycc and the version of the management operation is version = 1.0, then the target identifier may be mycc:1.0.

[0093] As a possible implementation, the consensus node receives a verification request message from the management node through the data transmission channel.

[0094] S202. The consensus node determines the target verification information in the target management request information based on the target identifier.

[0095] Among them, the target verification information is used to verify the target management request information.

[0096] It should be noted that the target verification information may include the content of the smart contract.

[0097] As a possible implementation, the consensus node locates the corresponding target management request information through the target identifier, and then determines the verification information in the target management request information as the target verification information.

[0098] S203. The consensus node sends a verification response message to the management node.

[0099] Among them, the verification response message includes the target verification information.

[0100] As a possible implementation, the consensus node encapsulates the target verification information to obtain a verification response message, and then sends the verification response message to the management node through the data transmission channel.

[0101] S204. The consensus node receives an instruction message from the management node.

[0102] Among them, the instruction message is used to indicate that the verification result of the target management request information is passed.

[0103] It should be noted that the instruction message can also be referred to as a smart contract audit status update transaction, and the instruction message may include the target identifier.

[0104] The verification result may include passed or not passed. Passed can be represented as true, and not passed can be represented as false.

[0105] As a possible implementation, the consensus node receives an instruction message from the management node through the data transmission channel.

[0106] S205. The consensus node determines that the status of the target management request information is the first status.

[0107] Among them, the first status is used to indicate that the target node is allowed to perform target management operations on the blockchain.

[0108] It should be noted that the first status can be represented as approved.

[0109] As a possible implementation, the consensus node configures the status of the target management request information to the first status.

[0110] Based on this solution, compared with the existing solution where only the management node can perform management operations on the blockchain, in the solution of this application, the consensus node receives a verification request message from the management node that includes the target identifier of the target management request information. Then, based on the target identifier, the consensus node determines the target verification information in the target management request information for verifying the target management request information. Then, the consensus node sends a verification response message that includes the target verification information to the management node. After receiving an indication message from the management node indicating that the verification result of the target management request information is passed, the consensus node determines the status of the target management request information to be the first status. Since the first status is used to indicate that the target node is allowed to perform target management operations on the blockchain, it is possible to enable the management operations to be performed by the target node instead of the management node, thereby reducing the management pressure on the management node and improving the efficiency of blockchain management.

[0111] The above is a general description of the blockchain management method provided by this application. Next, the blockchain management method provided by this application will be further described with reference to the accompanying drawings.

[0112] In one design, Figure 3 is a schematic flowchart of another blockchain management method provided by this application. As Figure 3 shown, after S205, the blockchain management method provided by this application may further include the following multiple steps:

[0113] S301. The consensus node receives an authorization signature request message from the target node.

[0114] Among them, the authorization signature request message includes the target identifier.

[0115] It should be noted that the authorization signature request message can also be referred to as a smart contract authorization signature acquisition transaction.

[0116] As a possible implementation, the consensus node receives the authorization signature request message from the target node through the data transmission channel.

[0117] S302. The consensus node determines the target management request information according to the target identifier. When the status of the target management request information is the first status, the consensus node sends an authorization signature response message to the target node.

[0118] Among them, the authorization signature response message includes the authorization signature of the consensus node.

[0119] It should be noted that the authorization signature can also be referred to as AuthSignature.

[0120] As a possible implementation, the consensus node searches for the target management request information corresponding to the target identifier, determines whether the status of the target management request information is the first status. When the status of the target management request information is the first status, it determines that the authorization signature is AuthSignature = Sig(mycc||1.0||smartContract). Then, it encapsulates the authorization signature to obtain an authorization signature response message. Finally, it sends the authorization signature response message to the target node through the data transmission channel.

[0121] Based on this solution, the consensus node receives an authorization signature request message including the target identifier from the target node. Then, when the status of the target management request information is the first status, it sends an authorization signature response message including the authorization signature of the consensus node to the target node, enabling the target node to obtain the authorization signature for managing the blockchain.

[0122] In one design, Figure 4 is a flowchart of another blockchain management method provided by this application. As Figure 4 shown, after S302, the blockchain management method provided by this application may further include the following multiple steps:

[0123] S401. The consensus node receives a transaction request message from the target node.

[0124] Among them, the transaction request message includes the operation result of the target management operation and at least one authorization signature.

[0125] It should be noted that the transaction request message may also be referred to as a smart contract deployment transaction.

[0126] As a possible implementation, the consensus node receives the transaction request message from the target node through the data transmission channel.

[0127] S402. When the number of target authorization signatures is greater than the preset threshold, the consensus node determines that the operation result takes effect.

[0128] Among them, the target authorization signature is the valid authorization signature among at least one authorization signature.

[0129] It should be noted that the preset threshold may be 5, or the preset threshold may also be 10. This application does not make specific restrictions on this.

[0130] As a possible implementation, the consensus node verifies each authorization signature in at least one authorization signature based on the name of the management operation, the version of the management operation, and / or the content of the management operation in the target management request information through a consensus algorithm, and then counts the number of target authorization signatures. When the number of target authorization signatures is greater than a preset threshold, it is determined that the operation result takes effect; when the number of target authorization signatures is not greater than the preset threshold, it is determined that the operation result does not take effect.

[0131] Based on the solution, the consensus node receives a transaction request message of the target node including the operation result of the target management operation and at least one authorization signature, and can determine that the operation content takes effect when the number of target authorization signatures is greater than a preset threshold.

[0132] In one design, Figure 5 is a schematic flowchart of another blockchain management method provided by this application. As Figure 5 shown, before S201, the blockchain management method provided by this application may further include the following multiple steps:

[0133] S501. The consensus node receives a management request message of the target node.

[0134] Among them, the management request message includes target management request information.

[0135] It should be noted that the management request message can also be referred to as an intelligent contract management request transaction.

[0136] As a possible implementation, the consensus node receives a management request message from the target node through a data transmission channel.

[0137] S502. The consensus node generates a target identifier according to the target management request information, and stores the target identifier and the target management request information.

[0138] As a possible implementation, taking the target management request information including the type of the management operation, the name of the management operation, the version of the management operation, and the content of the management operation as an example, the consensus node uses the name of the management operation and the version of the management operation as the target identifier, and then stores the target identifier and the target management request information in the local hard disk.

[0139] S503. The consensus node determines that the status of the target management request information is the second status.

[0140] Among them, the second status is used to indicate that the target management request information is to be verified.

[0141] It should be noted that the second status can also be expressed as Checking.

[0142] As a possible implementation, the consensus node configures the status of the target management request information to the second status.

[0143] Based on this solution, the consensus node receives a management request message including the target management request information from the target node, then generates a target identifier and stores the target identifier and the target management request information, and finally determines that the status of the target management request information is the second status for indicating that the target management request information is to be verified, so as to obtain the target identifier and the target management request information and determine that the status of the target management request information is the second status.

[0144] In one design, Figure 6 is a schematic flowchart of another blockchain management method provided by this application. As Figure 6 shown, before and after S503, the blockchain management method provided by this application may further include the following multiple steps:

[0145] S601. The consensus node receives an identity request message from the management node.

[0146] Among them, the identity request message is used to request the identity of the management request information with the status of the second status.

[0147] It should be noted that the identity request message can also be referred to as a query request transaction for a smart contract to be verified.

[0148] As a possible implementation, the consensus node receives an identity request message from the management node through the data transmission channel.

[0149] S602. The consensus node sends an identity response message to the management node.

[0150] Among them, the identity response message includes the target identifier.

[0151] As a possible implementation, the consensus node determines the identity of at least one piece of management request information with the status of the second status, encapsulates the identity of at least one piece of management request information with the status of the second status to obtain an identity response message, and then sends the identity response message to the management node through the data transmission channel.

[0152] Among them, the identity of at least one piece of management request information with the status of the second status includes the target identifier.

[0153] Based on this solution, the consensus node receives an identity request message from the management node for requesting the identity of the management request information with the status of the second status, and then sends an identity response message including the target identifier to the management node, enabling the management node to obtain the target identifier.

[0154] The above is an explanation of the blockchain management method provided by this application from the perspective of consensus nodes. Next, the blockchain management method provided by this application will be explained from the perspective of management nodes.

[0155] Figure 7 It is a schematic flowchart of another blockchain management method provided by this application. This method is applied to the management node of the blockchain. The blockchain also includes consensus nodes and target nodes. As Figure 7 shown, the blockchain management method provided by this application may specifically include the following multiple steps:

[0156] S701. The management node sends a verification request message to the consensus node.

[0157] Among them, the verification request message includes the target identifier of the target management request information, and the target management request information is used to request the management permission for the target node to perform a target management operation on the blockchain.

[0158] As a possible implementation manner, the management node sends a verification request message to the consensus node through a data transmission channel.

[0159] S702. The management node receives the verification response message from the consensus node.

[0160] Among them, the verification response message includes target verification information, and the target verification information is used to verify the target management request information.

[0161] As a possible implementation manner, the management node receives the verification response message from the consensus node through a data transmission channel.

[0162] S703. The management node verifies the target verification information. When the verification result is passed, it sends an indication message to the consensus node.

[0163] Among them, the indication message is used to indicate that the verification result of the target management request information is passed.

[0164] As a possible implementation manner, taking the target verification information as the content of the smart contract as an example, the management node deserializes the content of the smart contract to obtain the source code of the smart contract, and then verifies the source code of the smart contract to obtain the verification result.

[0165] When the verification result is passed, it sends an indication message to the consensus node to indicate that the verification result of the target management request information is passed.

[0166] When the verification result is not passed, it sends a verification error message to the consensus node to indicate that the verification result of the target management request information is not passed.

[0167] Based on this solution, the management node sends a verification request message including the target identifier of the target management request information to the consensus node of the blockchain. Then, it receives a verification response message including the target verification information from the consensus node. Finally, it verifies the target verification information. When the verification result passes, it sends an indication message to the consensus node to indicate that the verification result of the target management request information passes, enabling the consensus node to know that the verification result of the target management request information passes.

[0168] In one design, Figure 8 is a schematic flowchart of another blockchain management method provided by this application. As shown in Figure 8 , before S701, the blockchain management method provided by this application may further include the following multiple steps:

[0169] S801. The management node sends an identifier request message to the consensus node.

[0170] Among them, the identifier request message is used to request the identifier of the management request information whose status is the second status, and the second status is used to indicate that the target management request information is to be verified.

[0171] As a possible implementation, the management node periodically sends an identifier request message to the consensus node through the data transmission channel.

[0172] S802. The management node receives the identifier response message from the consensus node.

[0173] Among them, the identifier response message includes the target identifier.

[0174] As a possible implementation, the management node receives the identifier response message from the consensus node through the data transmission channel.

[0175] Based on this solution, the management node can obtain the target identifier by sending an identifier request message for requesting the identifier of the management request information whose status is the second status to the consensus node, and then receiving the identifier response message including the target identifier from the consensus node.

[0176] The above is an explanation of the blockchain management method provided by this application from the perspective of the management node. Next, the blockchain management method provided by this application will be explained from the perspective of the target node.

[0177] Figure 9 is a schematic flowchart of another blockchain management method provided by this application. The method is applied to the target node of the blockchain, and the blockchain further includes a consensus node. As shown in Figure 9 , the blockchain management method provided by this application may specifically include the following multiple steps:

[0178] S901. The target node sends a management request message to the consensus node.

[0179] Among them, the management request message includes target management request information, and the target management request information is used to request the management permission for the target node to perform target management operations on the blockchain.

[0180] As a possible implementation, the target node sends the management request message to the consensus node through the data transmission channel.

[0181] S902. The target node receives the management response message from the consensus node.

[0182] Among them, the management response message is used to indicate that the status of the target management request information is the second status, and the second status is used to indicate that the target management request information is to be verified.

[0183] As a possible implementation, the target node receives the management response message from the consensus node through the data transmission channel.

[0184] Based on this solution, the target node sends a management request message including target management request information to the consensus node, and then receives the management response message from the consensus node. Since the management response message is used to indicate that the status of the target management request information is the second status, and the second status is used to indicate that the target management request information is to be verified, it can be known that the target management request information is to be verified.

[0185] In one design, Figure 10 is a schematic flow diagram of another blockchain management method provided by this application. As Figure 10 shown, after S902, the blockchain management method provided by this application may further include the following multiple steps:

[0186] S1001. The target node sends an authorization signature request message to the consensus node.

[0187] Among them, the authorization signature request message includes a target identifier, and the target identifier is used to identify the target management request information.

[0188] As a possible implementation, the target node sends the authorization signature request message to the consensus node through the data transmission channel.

[0189] It should be noted that the target node can send the authorization signature request message to multiple consensus nodes.

[0190] S1002. The target node receives the authorization signature response message from the consensus node.

[0191] Among them, the authorization signature response message includes the authorization signature of the consensus node.

[0192] As a possible implementation, the target node receives the authorized signature response message of the consensus node through the data transmission channel.

[0193] It should be noted that the target node can receive the authorized signature response messages of multiple consensus nodes.

[0194] Based on this solution, the target node can obtain the authorized signature of the consensus node by sending an authorized signature request message including the target identifier to the consensus node, and then receiving the authorized signature response message including the authorized signature of the consensus node.

[0195] In one design, Figure 11 is a schematic flowchart of another blockchain management method provided by this application. As Figure 11 shown, after S1002, the blockchain management method provided by this application may further include the following multiple steps:

[0196] S1101. The target node sends a transaction request message to the consensus node.

[0197] Among them, the transaction request message includes the operation result of the target management operation and at least one authorized signature.

[0198] As a possible implementation, the target node sends a transaction request message to the consensus node through the data transmission channel.

[0199] S1102. The target node receives the transaction response message of the consensus node.

[0200] Among them, the transaction response message is used to indicate that the operation result takes effect.

[0201] As a possible implementation, the target node receives the transaction response message of the consensus node through the data transmission channel.

[0202] Based on this solution, the target node sends a transaction request message including the operation result of the target management operation and at least one authorized signature to the consensus node, and then receives the transaction response message of the consensus node. Since the transaction response message is used to indicate that the operation result takes effect, it can be known that the operation result takes effect.

[0203] The above is an explanation of the blockchain management method provided by this application from the perspective of the node. Next, the blockchain management method provided by this application will be explained from the perspective of node interaction.

[0204] Figure 12 is a schematic flowchart of another blockchain management method provided by this application. As Figure 12 shown, the blockchain management method provided by this application can be applied to Figure 1The blockchain management system shown, the method may specifically include the following multiple steps:

[0205] S1201. The target node sends a management request message to the consensus node.

[0206] It should be noted that for the specific description of S1201, reference can be made to the relevant description of S901, and details will not be elaborated in this application.

[0207] S1202. The consensus node receives the management request message from the target node.

[0208] It should be noted that for the specific description of S1202, reference can be made to the relevant description of S501, and details will not be elaborated in this application.

[0209] S1203. The consensus node verifies the management request message.

[0210] As a possible implementation, the consensus node verifies the basic information of the management request message to determine whether the basic information is correct. If it is correct, the consensus node executes S1204; if it is incorrect, the process ends.

[0211] It should be noted that for the specific solution of this possible implementation, reference can be made to existing solutions, and details will not be elaborated in this application.

[0212] In subsequent steps, after a node receives a message, it can verify the message. The verification method can refer to the above possible implementation. For the sake of easy description and to avoid redundancy, the subsequent steps will no longer show that the node verifies the message, and a unified description is given here.

[0213] S1204. The consensus node generates a target identifier according to the target management request information, and stores the target identifier and the target management request information.

[0214] It should be noted that for the specific description of S1204, reference can be made to the relevant description of S502, and details will not be elaborated in this application.

[0215] S1205. The consensus node determines that the status of the target management request information is the second status.

[0216] It should be noted that for the specific description of S1205, reference can be made to the relevant description of S503, and details will not be elaborated in this application.

[0217] S1206. The consensus node sends a management response message to the target node.

[0218] As a possible implementation, the consensus node generates a management response message and sends the management response message to the target node through the data transmission channel.

[0219] S1207. The target node receives the management response message from the consensus node.

[0220] It should be noted that for the specific description of S1207, reference can be made to the relevant description of S902, which will not be elaborated herein in this application.

[0221] S1208. The management node sends an identity request message to the consensus node.

[0222] It should be noted that for the specific description of S1208, reference can be made to the relevant description of S801, which will not be elaborated herein in this application.

[0223] S1209. The consensus node receives the identity request message from the management node.

[0224] It should be noted that for the specific description of S1209, reference can be made to the relevant description of S601, which will not be elaborated herein in this application.

[0225] S1210. The consensus node sends an identity response message to the management node.

[0226] It should be noted that for the specific description of S1210, reference can be made to the relevant description of S602, which will not be elaborated herein in this application.

[0227] S1211. The management node receives the identity response message from the consensus node.

[0228] It should be noted that for the specific description of S1211, reference can be made to the relevant description of S802, which will not be elaborated herein in this application.

[0229] S1212. The management node sends a verification request message to the consensus node.

[0230] It should be noted that for the specific description of S1212, reference can be made to the relevant description of S701, which will not be elaborated herein in this application.

[0231] S1213. The consensus node receives the verification request message from the management node.

[0232] It should be noted that for the specific description of S1213, reference can be made to the relevant description of S201, which will not be elaborated herein in this application.

[0233] S1214. The consensus node determines the target verification information in the target management request message based on the target identity.

[0234] It should be noted that for the specific description of S1214, reference can be made to the relevant description of S202, which will not be elaborated herein in this application.

[0235] S1215. The consensus node sends a verification response message to the management node.

[0236] It should be noted that for the specific description of S1215, reference can be made to the relevant description of S203, and details will not be elaborated herein in this application.

[0237] S1216. The management node receives the verification response message from the consensus node.

[0238] It should be noted that for the specific description of S1216, reference can be made to the relevant description of S702, and details will not be elaborated herein in this application.

[0239] S1217. The management node verifies the target verification information, and in the case where the verification result passes, sends an indication message to the consensus node.

[0240] It should be noted that for the specific description of S1217, reference can be made to the relevant description of S703, and details will not be elaborated herein in this application.

[0241] S1218. The consensus node receives the indication message from the management node.

[0242] It should be noted that for the specific description of S1218, reference can be made to the relevant description of S204, and details will not be elaborated herein in this application.

[0243] S1219. The consensus node determines that the status of the target management request information is the first status.

[0244] It should be noted that for the specific description of S1219, reference can be made to the relevant description of S205, and details will not be elaborated herein in this application.

[0245] S1220. The consensus node sends a notification message to the target node.

[0246] Among them, the notification message is used to indicate that the status of the target management request information is the first status.

[0247] S1221. The target node sends an authorized signature quantity request message to the consensus node.

[0248] Among them, the authorized signature quantity request message is used to request the quantity of authorized signatures that the target node needs to collect.

[0249] S1222. The consensus node sends an authorized signature quantity response message to the target node.

[0250] Among them, the authorized signature quantity response message includes the quantity of authorized signatures that the target node needs to collect.

[0251] S1223. The target node sends an authorized signature request message to the consensus node.

[0252] It should be noted that for the specific description of S1223, reference can be made to the relevant description of S1001, and details will not be elaborated herein in this application.

[0253] S1224. The consensus node receives an authorization signature request message from the target node.

[0254] It should be noted that the specific description of S1224 can refer to the relevant description of S301, which will not be elaborated herein in this application.

[0255] S1225. The consensus node determines the target management request information according to the target identifier. When the status of the target management request information is the first status, an authorization signature response message is sent to the target node.

[0256] It should be noted that the specific description of S1225 can refer to the relevant description of S302, which will not be elaborated herein in this application.

[0257] S1226. The target node receives the authorization signature response message from the consensus node.

[0258] It should be noted that the specific description of S1226 can refer to the relevant description of S1002, which will not be elaborated herein in this application.

[0259] S1227. The target node sends a transaction request message to the consensus node.

[0260] It should be noted that the specific description of S1227 can refer to the relevant description of S1101, which will not be elaborated herein in this application.

[0261] S1228. The consensus node receives the transaction request message from the target node.

[0262] It should be noted that the specific description of S1228 can refer to the relevant description of S401, which will not be elaborated herein in this application.

[0263] S1229. When the number of target authorization signatures is greater than the preset threshold, the consensus node determines that the operation result takes effect.

[0264] It should be noted that the specific description of S1229 can refer to the relevant description of S402, which will not be elaborated herein in this application.

[0265] S1230. The consensus node sends a transaction response message to the target node.

[0266] As a possible implementation, the company node generates a transaction response message and sends the transaction response message to the target node through the data transmission channel.

[0267] S1231. The target node receives the transaction response message from the consensus node.

[0268] It should be noted that for the specific description of S1231, reference can be made to the relevant description of S1102, which will not be elaborated herein. The above mainly introduces the solution provided by the embodiments of the present application from the perspective of blockchain nodes executing the blockchain management method. To implement the above functions, the blockchain nodes include the corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0269] The embodiments of the present application can divide the functional modules of the blockchain nodes according to the above method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. Optionally, the division of modules in the embodiments of the present application is illustrative, only a logical functional division, and there can be other division methods in actual implementation. In addition, the "module" here can refer to a specific application-specific integrated circuit (ASIC), a circuit, a processor and a memory executing one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions.

[0270] In the case of adopting functional module division, Figure 13 FIG. shows a schematic structural diagram of a blockchain node. The blockchain node includes a consensus node, a management node, or a target node. As Figure 13 shown, the blockchain node 130 includes a transceiver module 1301 and a processing module 1302.

[0271] In some embodiments, the blockchain node 130 may further include a storage module ( Figure 13 not shown in the figure) for storing program instructions and data.

[0272] Wherein, when the blockchain node 130 is a consensus node, the transceiver module 1301 is configured to receive a verification request message from the management node; the verification request message includes the target identifier of the target management request information; the processing module 1302 is configured to determine the target verification information in the target management request information based on the target identifier; the target verification information is used to verify the target management request information; the transceiver module 1301 is further configured to send a verification response message to the management node; the verification response message includes the target verification information; the transceiver module 1301 is further configured to receive an indication message from the management node; the indication message is used to indicate that the verification result of the target management request information is passed; the processing module 1302 is further configured to determine that the status of the target management request information is the first status; the first status is used to indicate that the target node is allowed to perform a target management operation on the blockchain.

[0273] Optionally, the transceiver module 1301 is further configured to receive an authorization signature request message from the target node; the authorization signature request message includes the target identifier; the processing module 1302 is further configured to determine the target management request information based on the target identifier, and when the status of the target management request information is the first status, send an authorization signature response message to the target node; the authorization signature response message includes the authorization signature of the consensus node.

[0274] Optionally, the transceiver module 1301 is further configured to receive a transaction request message from the target node; the transaction request message includes the operation result of the target management operation and at least one authorization signature; the processing module 1302 is further configured to determine that the operation result takes effect when the number of target authorization signatures is greater than a preset threshold; the target authorization signature is a valid authorization signature among the at least one authorization signature.

[0275] Optionally, the transceiver module 1301 is further configured to receive a management request message from the target node; the management request message includes the target management request information; the processing module 1302 is further configured to generate a target identifier according to the target management request information, and store the target identifier and the target management request information; the processing module 1302 is further configured to determine that the status of the target management request information is the second status; the second status is used to indicate that the target management request information is to be verified.

[0276] Optionally, the transceiver module 1301 is further configured to receive an identifier request message from the management node; the identifier request message is used to request the identifier of the management request information whose status is the second status; the processing module 1302 is further configured to send an identifier response message to the management node; the identifier response message includes the target identifier.

[0277] When the blockchain node 130 is a management node, the transceiver module 1301 is configured to send a verification request message to the consensus node; the verification request message includes a target identifier of the target management request information, and the target management request information is used to request the management permission for the target node to perform a target management operation on the blockchain; the transceiver module 1301 is further configured to receive a verification response message from the consensus node; the verification response message includes target verification information, and the target verification information is used to verify the target management request information; the processing module 1302 is configured to verify the target verification information, and when the verification result is passed, send an indication message to the consensus node; the indication message is used to indicate that the verification result of the target management request information is passed.

[0278] Optionally, the transceiver module 1301 is further configured to send an identifier request message to the consensus node; the identifier request message is used to request an identifier of the management request information in the second state, and the second state is used to indicate that the target management request information is to be verified; the transceiver module 1301 is further configured to receive an identifier response message from the consensus node; the identifier response message includes the target identifier.

[0279] When the blockchain node 130 is a target node, the transceiver module 1301 is configured to send a management request message to the consensus node; the management request message includes target management request information, and the target management request information is used to request the management permission for the target node to perform a target management operation on the blockchain; the processing module 1302 is configured to receive a management response message from the consensus node; the management response message is used to indicate that the state of the target management request information is the second state, and the second state is used to indicate that the target management request information is to be verified.

[0280] Optionally, the transceiver module 1301 is further configured to send an authorization signature request message to the consensus node; the authorization signature request message includes a target identifier, and the target identifier is used to identify the target management request information; the transceiver module 1301 is further configured to receive an authorization signature response message from the consensus node; the authorization signature response message includes the authorization signature of the consensus node.

[0281] Optionally, the transceiver module 1301 is further configured to send a transaction request message to the consensus node; the transaction request message includes an operation result of the target management operation and at least one authorization signature; receive a transaction response message from the consensus node; the transaction response message is used to indicate that the operation result takes effect.

[0282] All relevant contents of each step involved in the above method embodiments can be cited in the function descriptions of the corresponding functional modules, and will not be elaborated here.

[0283] In the case of implementing the functions of the above functional modules in the form of hardware, Figure 14 shows a schematic structural diagram of another blockchain node. As Figure 14As shown, the blockchain node 140 includes a processor 1401, a memory 1402, and a bus 1403. The processor 1401 and the memory 1402 can be connected via the bus 1403.

[0284] The processor 1401 is the control center of the blockchain node 140 and can be a single processor or a collective term for multiple processing elements. For example, the processor 1401 can be a general-purpose central processing unit (CPU) or other general-purpose processors. Among them, the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0285] As an embodiment, the processor 1401 can include one or more CPUs, such as Figure 14 CPU 0 and CPU 1 shown in

[0286] The memory 1402 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage medium, or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0287] As a possible implementation, the memory 1402 can exist independently of the processor 1401. The memory 1402 can be connected to the processor 1401 via the bus 1403 for storing instructions or program codes. When the processor 1401 calls and executes the instructions or program codes stored in the memory 1402, the blockchain management method provided by the embodiments of the present application can be implemented.

[0288] In another possible implementation, the memory 1402 can also be integrated with the processor 1401.

[0289] The bus 1403 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. This bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 14 only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0290] It should be noted that Figure 14 the structure shown does not constitute a limitation on the blockchain node 140. Except Figure 14 for the components shown, the blockchain node 140 may include more or fewer components than those shown in the figure, or combine certain components, or have a different component layout.

[0291] As an example, in combination with Figure 13 , the functions implemented by the transceiver module 1301 and the processing module 1302 in the blockchain node 130 are the same as Figure 14 the functions of the processor 1401 in

[0292] Optionally, as shown in Figure 14 , the blockchain node 140 provided by the embodiments of the present application may further include a communication interface 1404.

[0293] The communication interface 1404 is used to connect to other devices through a communication network. The communication network can be an Ethernet, a wireless access network, a wireless local area network (WLAN), etc. The communication interface 1404 may include a receiving unit for receiving data and a sending unit for sending data.

[0294] In a possible implementation manner, in the blockchain node 140 provided by the embodiments of the present application, the communication interface 1404 may also be integrated in the processor 1401, and the embodiments of the present application do not make specific limitations on this.

[0295] As a possible product form, the blockchain node according to the embodiments of the present application may also be implemented using the following: one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout the present application.

[0296] Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and conciseness of description, only the above division of each functional unit is used as an example for illustration. In actual applications, the above functions can be assigned to different functional units as needed, that is, the internal structure of the device is divided into different functional units to complete all or part of the functions described above. The specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0297] The embodiments of the present application further provide a computer-readable storage medium, on which a computer program or instruction is stored. When the computer program or instruction is executed, the computer is caused to execute each step in the method flow shown in the foregoing method embodiments.

[0298] The embodiments of the present application provide a computer program product containing instructions. When the instructions run on a computer, the computer is caused to execute each step in the method flow shown in the foregoing method embodiments.

[0299] The embodiments of the present application provide a chip system, including: a processor and an interface circuit; the interface circuit is configured to receive a computer program or instruction and transmit it to the processor; the processor is configured to execute the computer program or instruction so that the chip system executes each step in the method flow shown in the foregoing method embodiments.

[0300] Among them, a computer-readable storage medium can be, for example, but not limited to, a system, device, or component of electricity, magnetism, light, electromagnetic, infrared ray, or semiconductor, or any combination of the above. More specific examples (a non-exhaustive list) of the computer-readable storage medium include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a register, a hard disk, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above, or any other form of computer-readable storage medium known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in a specific application ASIC. In the embodiments of the present application, the computer-readable storage medium can be any tangible medium that contains or stores a program, and the program can be used by or in combination with an instruction execution system, device, or component.

[0301] Since the blockchain node, computer-readable storage medium, and computer program product provided in this embodiment can be applied to the blockchain management method provided above, the technical effects that can be obtained can also refer to the method embodiments above, and are not elaborated herein in the embodiments of the present application.

[0302] Although the present application is described in combination with various embodiments herein, however, in the process of implementing the claimed present application, those skilled in the art can understand and implement other changes of the disclosed embodiments by viewing the drawings, the disclosure content, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "one" does not exclude a plurality of cases. A single processor or other unit can implement several functions listed in the claims. Certain measures are recited in mutually different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0303] Although the present application has been described in connection with specific features and their embodiments, it will be apparent that various modifications and combinations can be made without departing from the spirit and scope of the present application. Accordingly, this specification and the accompanying drawings are merely exemplary illustrations of the present application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these changes and modifications.

Claims

1. A blockchain management method, characterized in that, The method is applied to a consensus node of a blockchain. The blockchain further includes a management node and a target node. The consensus node stores target management request information of the target node, and the target management request information is used to request management authority for the target node to perform a target management operation on the blockchain. The method includes: Receiving a verification request message from the management node; the verification request message includes a target identifier of the target management request information; Determining target verification information in the target management request information based on the target identifier; the target verification information is used to verify the target management request information; Sending a verification response message to the management node; the verification response message includes the target verification information; Receiving an indication message from the management node; the indication message is used to indicate that the verification result of the target management request information is passed; Determining that the status of the target management request information is a first status; the first status is used to indicate that the target node is allowed to perform the target management operation on the blockchain.

2. The method according to claim 1, characterized in that The method further includes: Receiving an authorization signature request message from the target node; the authorization signature request message includes the target identifier; Determining the target management request information according to the target identifier, and sending an authorization signature response message to the target node when the status of the target management request information is the first status; the authorization signature response message includes an authorization signature of the consensus node.

3. The method according to claim 2, wherein The method further includes: Receiving a transaction request message from the target node; the transaction request message includes an operation result of the target management operation and at least one authorization signature; Determining that the operation result takes effect when the number of target authorization signatures is greater than a preset threshold; the target authorization signature is a valid authorization signature among the at least one authorization signature.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Receiving a management request message from the target node; the management request message includes the target management request information; Generating the target identifier according to the target management request information, and storing the target identifier and the target management request information; Determining that the status of the target management request information is a second status; the second status is used to indicate that the target management request information is to be verified.

5. The method according to claim 4, wherein The method further includes: Receiving an identifier request message from the management node; the identifier request message is used to request an identifier of management request information with the second status; Sending an identifier response message to the management node; the identifier response message includes the target identifier.

6. A blockchain management method, characterized in that, The method is applied to a management node of a blockchain. The blockchain further includes a consensus node and a target node. The method includes: Sending a verification request message to the consensus node; the verification request message includes a target identifier of target management request information, and the target management request information is used to request management authority for the target node to perform a target management operation on the blockchain; Receiving a verification response message from the consensus node; the verification response message includes the target verification information, and the target verification information is used to verify the target management request information; Verify the target verification information, and send an indication message to the consensus node when the verification result passes; the indication message is used to indicate that the verification result of the target management request information passes.

7. The method according to claim 6, characterized in that, The method further includes: Send an identification request message to the consensus node; the identification request message is used to request the identification of the management request information in the second state, and the second state is used to indicate that the target management request information is to be verified; Receive the identification response message from the consensus node; the identification response message includes the target identification.

8. A blockchain management method, characterized in that, The method is applied to a target node of a blockchain, and the blockchain further includes a consensus node. The method includes: Send a management request message to the consensus node; the management request message includes target management request information, and the target management request information is used to request the management permission for the target node to perform a target management operation on the blockchain; Receive the management response message from the consensus node; the management response message is used to indicate that the state of the target management request information is the second state, and the second state is used to indicate that the target management request information is to be verified.

9. The method according to claim 8, characterized in that, The method further includes: Send an authorization signature request message to the consensus node; the authorization signature request message includes a target identification, and the target identification is used to identify the target management request information; Receive the authorization signature response message from the consensus node; the authorization signature response message includes the authorization signature of the consensus node.

10. The method according to claim 9, characterized in that, The method further includes: Send a transaction request message to the consensus node; the transaction request message includes the operation result of the target management operation and at least one authorization signature; Receive the transaction response message from the consensus node; the transaction response message is used to indicate that the operation result takes effect.

11. A blockchain management system, characterized in that, The system includes a consensus node of a blockchain, a management node of the blockchain, and a target node of the blockchain; The consensus node is used to execute the method according to any one of claims 1-5; The management node is used to execute the method according to any one of claims 6-7; The target node is used to execute the method according to any one of claims 8-10.

12. A blockchain node, characterized in that, Includes: A functional unit for executing the method according to any one of claims 1 to 5, or a functional unit for executing the method according to any one of claims 6 to 7, or a functional unit for executing the method according to any one of claims 8 to 10; Wherein, the actions performed by the functional unit are implemented by hardware or by hardware executing corresponding software.

13. A blockchain node, characterized in that, The blockchain node includes: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the programs or instructions are executed by the processor, the node is caused to execute the method according to any one of claims 1 to 5, or the node is caused to execute the method according to any one of claims 6 to 7, or the node is caused to execute the method according to any one of claims 8 to 10.

14. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instruction is executed, it causes the computer to execute the method according to any one of claims 1 to 5, or when the computer program or instruction is executed, it causes the computer to execute the method according to any one of claims 6 to 7, or when the computer program or instruction is executed, it causes the computer to execute the method according to any one of claims 8 to 10.

Images