CN112199382A

CN112199382A - Node group creating method and node group-based transaction method in alliance chain network

Info

Publication number: CN112199382A
Application number: CN202011119486.2A
Authority: CN
Inventors: 杨文龙; 夏凝
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2020-05-28
Filing date: 2020-05-28
Publication date: 2021-01-08
Anticipated expiration: 2040-05-28
Also published as: WO2021239070A1; CN111382168B; CN112199382B; CN111382168A

Abstract

A method for creating a node group, a node group-based transaction method in a federation chain network is disclosed. The administrator of the first node in the alliance chain network can initiate a group creation transaction through the own alliance chain account, and the group creation transaction comprises a group creation sub-transaction. After the group creation transaction is broadcasted to the alliance chain network, when the first node executes the group creation transaction, a private chain is created locally according to the group creation sub-transaction, which is equivalent to creating a node group containing the first node. While other nodes do not create a private chain locally when executing the set of creation transactions. Eventually the first node and other nodes will write the set of created transactions into the local federation chain. By the scheme, the privacy of the service data butted by the nodes can be protected.

Description

Node group creating method and node group-based transaction method in alliance chain network

Technical Field

The embodiment of the specification relates to the technical field of information, in particular to a node group creating and node group-based transaction method in a alliance chain network.

Background

A federation chain network, also called a block chain network of federation type, generally includes a plurality of enterprises as federation members, and nodes controlled by the enterprises respectively form the federation chain network.

For each enterprise as a member of the federation, a user interfacing with the enterprise may encapsulate service data of an initiated service into a transaction (a data structure specified by a blockchain protocol) and submit the transaction to a node corresponding to the enterprise, and then the node corresponding to the enterprise broadcasts the transaction to the federation chain network, and then each node in the federation chain network recognizes the transaction and writes the transaction into a local blockchain. In this way, it can be ensured that the service data written in the blockchain is difficult to be tampered.

In order to pursue the non-falsification of the service data, the existing operation mechanism of the alliance-link network causes the service data butted by any node to be disclosed to the whole network.

Disclosure of Invention

In order to solve the problem that the privacy of service data of node docking cannot be protected in the prior art, an embodiment of the present specification provides a method for creating a node group in a federation network and a transaction based on the node group, where the scheme is as follows:

according to a 1 st aspect of embodiments herein, there is provided a method of creating a node group in a federation chain network, the federation chain network including a plurality of nodes, the method comprising:

the first node receives a group creation transaction constructed by a first administrator account; the group creation transaction comprises a group creation sub-transaction, the group creation sub-transaction comprising a group public key; the first administrator account is an account registered by an administrator of the first node in the federation chain network; the group public key is specified by a manager of the first node;

the first node broadcasting the group creation transaction to the alliance-link network;

the first node performs the group creation transaction, including: creating a private chain locally, and writing the group creation sub-transaction into the local private chain;

each other node than the first node performs the group creation transaction without creating a private chain;

each node in the alliance chain network writes the group establishing transaction and the corresponding execution result into a local alliance chain; the execution result corresponding to the group creation transaction includes a first node identification.

According to a 2 nd aspect of embodiments herein, there is provided a transaction method based on the node group created in the 1 st aspect, including:

the first node receives a business transaction constructed by the first management party account; the business transaction comprises a business sub-transaction, and the business sub-transaction comprises business data and a signature generated by using a group private key corresponding to the group public key;

the first node uses the group public key to verify the signature in the business sub-transaction, and if the signature passes the verification, the first node processes the business transaction, including: replacing the business sub-transaction with a hash value of the business sub-transaction;

the first node broadcasts the processed service transaction to the alliance chain network;

the first node performs the business transaction, including: writing the business sub-transaction into a local private chain;

the other nodes in the alliance chain network execute the business transaction under the condition that a private chain is not established;

and each node in the alliance chain network writes the service transaction into a local alliance chain.

According to the technical scheme provided by the embodiment of the specification, a manager of the first node in the alliance chain network can initiate a group creation transaction through the own alliance chain account, and the group creation transaction comprises a group creation sub-transaction. After the group creation transaction is broadcasted to the alliance chain network, when the first node executes the group creation transaction, a private chain is created locally according to the group creation sub-transaction, which is equivalent to creating a node group containing the first node. While other nodes do not create a private chain locally when executing the set of creation transactions. Eventually the first node and other nodes will write the set of created transactions into the local federation chain.

Therefore, when a first manager initiates a service transaction to a first node through a self alliance chain account, if the first node determines that the service sub-transaction included in the service transaction carries a signature of a group private key, the first node determines that the service sub-transaction specifies a node group corresponding to the group private key, and the content of the service sub-transaction cannot be disclosed to an alliance chain. Finally, each node in the federation chain network writes the business transaction containing the hash value of the business sub-transaction into the local federation chain.

Through the technical scheme provided by the embodiment of the specification, on one hand, the service data plaintext butted by the first node is only stored in the private chain of the node group where the first node is located, so that the service data privacy of the first node is protected; on the other hand, the hash value of the service data corresponding to the first node is stored in the federation chain again, so that the effect of storing the certificate (non-falsification) is achieved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of embodiments of the invention.

In addition, any one of the embodiments in the present specification is not required to achieve all of the effects described above.

Drawings

In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present specification, and other drawings can be obtained by those skilled in the art according to the drawings.

FIG. 1 is a block chain system of the prior art;

FIG. 2 is a block chain system according to an embodiment of the present disclosure;

FIG. 3 is a flowchart illustrating a method for creating a node group in a federation chain network according to an embodiment of the present specification;

fig. 4 is a schematic diagram of a first node locally maintaining a federation chain and a private chain according to an embodiment of the present specification;

fig. 5 is a schematic flow chart of a node group-based transaction method provided in an embodiment of the present specification;

fig. 6 is a flowchart illustrating a method for joining a node group according to an embodiment of the present specification;

fig. 7 is a schematic diagram of a second node locally maintaining a federation chain and a private chain according to an embodiment of the present specification;

fig. 8 is a schematic flowchart of a node group-based transaction method provided in an embodiment of the present specification;

fig. 9 is a schematic diagram of an apparatus for configuring a method according to an embodiment of the present disclosure.

Detailed Description

Fig. 1 is a schematic diagram of a conventional blockchain system. As shown in fig. 1, in the prior art, a federation chain account may send a transaction through any node, the transaction containing traffic data, and the transaction may be broadcast to the entire network so that each node caches the transaction locally. In the consensus stage, the nodes A to D generate blocks based on a consensus algorithm, a plurality of transactions are packaged in the blocks, each node executes the transactions in the blocks generated by consensus, and writes the blocks into a local alliance chain (which is equivalent to writing each transaction in the blocks into the local alliance chain), so that the transaction execution and the uplink storage of the transactions are realized.

The blockchain system described in fig. 1 would disclose the service data butted by each node in plain text in the federation chain, and all nodes in the federation chain network can check each other for the service data, so that protection of service data privacy cannot be achieved.

The scheme is used for realizing data isolation between nodes (data isolation between node groups, and data isolation between nodes and node groups) in a alliance chain network, so that the service data privacy of the nodes is protected.

The architecture of the blockchain system to which the present solution is applied will be described first. The blockchain system includes a federation chain network, and the federation chain network is composed of a plurality of nodes, and each node is deployed with a blockchain maintained by the federation chain network (for convenience of description, the blockchain maintained by the federation chain network is referred to as a federation chain). Each node in the federation chain network, in addition to maintaining a local federation chain, may also maintain at least one local private blockchain (referred to as a private chain for ease of description).

It should be noted that "private" as used herein refers to the private property of a node group, and does not refer to the private property of a node. Nodes maintaining the same private chain form a node group, and a node may create or join one or more than one node group. If a certain node group only comprises one node, the local private chain of the node is the private chain maintained by the node group; if a node group includes more than one node, then the private chain local to each node in the node group is the same, which is the private chain maintained by the node group.

In the scheme, any node can create or join a node group, nodes in the same node group maintain the same private chain, and the service data plaintext butted by the nodes in the same node group can be only written into the private chain of the node group, so that data isolation between the inside and the outside of the node group is realized.

Fig. 2 is a schematic structural diagram of a block chain system according to an embodiment of the present disclosure. As shown in fig. 2, the federation chain network includes a node a, a node B, a node C, and a node D, where nodes a to D all maintain locally the same federation chain, which is the block chain maintained by the federation chain network. In addition, node a and node D belong to the same node group, maintain the same private chain 1, share service data with each other, node C itself creates a node group, which only includes node C, node C maintains the private chain 2 alone (of course, node A, B, D may be allowed to join the node group later), node B does not create or join any node group, and service data docked by node B is shared to the whole network.

It should be noted that the service data of the node a and the node D are not shared to the node B and the node C, which realizes data isolation between node groups and between nodes. The service data of the node C can not be shared by other nodes, and the data isolation between the nodes is realized.

It can be seen that the architecture of the block chain system in this scheme is actually a two-layer network nested structure, the outer layer is a federation chain network, and a plurality of private chain networks (one private chain network is a node group) can be formed inside the federation chain network.

In addition, several concepts that may appear in the description of the present solution need to be explained.

Trading: refers to a transaction initiated by an account registered in the federation chain network (e.g., a manager account registered in the federation chain network by a manager of a certain node, and a user account registered in the federation network by a common user served by the manager), which is a concept at the federation chain network level, and the transaction is further written into the federation chain after being broadcast to each node in the federation chain network. For example, group creation transactions, group join transactions, business transactions.

Sub-transaction: refers to nested data structures within a transaction, which is a concept at the private chain network level. A child transaction specifies the private chain to which it is written, and all nodes maintaining the private chain write the child transaction to the private chain. For example, group creation sub-transactions, group joining sub-transactions, business sub-transactions.

As is well known, in the field of block chains, transactions are divided into executable transactions and credit-type transactions, and for executable transactions, a node not only needs to write the executable transactions into a block chain, but also needs to execute operations based on some data parameters in the executable transactions to obtain execution results; for the deposit card type transaction, the node does not need to execute, and only writes the deposit card type transaction into the block chain for deposit card.

The transaction on the federation chain level in the scheme is usually an execution type transaction, and the sub-transaction on the private chain level can be a deposit-certificate type transaction or an execution type transaction.

A first node: for convenience of description, a certain node in the federation chain network that creates a node group is referred to as a first node.

The second node: for convenience of description, some other node in the federation chain network that joins the node group created by the first node is referred to as a second node.

In order to make those skilled in the art better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all the embodiments. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of protection.

The technical solutions provided by the embodiments of the present description are described in detail below with reference to the accompanying drawings.

Fig. 3 is a flowchart of a method for creating a node group in a federation chain network, provided by an embodiment of the present specification, including the following steps:

s300: the first node receives a group creation transaction constructed by a first administrator account.

The first administrator account is an account registered by an administrator of the first node in the federation chain network. Generally, the administrator of a node is the organization (e.g., a bank) that provides business services to users. Typically, a centralized server on the node's administrator will interface with several users. For a user, a management party of a node provides centralized service, the user initiates a service to a centralized server of the management party of the node, and the centralized server encapsulates corresponding service data into a service transaction through an account of a first management party and submits the service transaction to the first node, so that the alliance-link network processes and stores the service transaction.

However, for the node group creation operation and the node group join operation, the operations are usually initiated by the administrator of the node and are not initiated by the user who the administrator of the node interfaces with.

In this embodiment of the present specification, the group creation transaction includes a creation sub-transaction (of course, other parameters are also included in general), and the creation sub-transaction includes a group public key, which is specified by the administrator of the first node and is used as a public key corresponding to the created node group. It will be appreciated that the administrator of the first node now specifies the group public key and, of course, also the group private key.

It should be noted here that the transaction is a data structure known in the field of blockchain technology, and the transaction usually includes other parameters (such as an account address, a hash value of the transaction, a signature of the transaction from the account initiating the transaction, etc.) in addition to the data (data) to be processed, where the other parameters in the transaction are not important for the present solution, and the other parameters are not emphasized below, and only data included in the transaction is important.

S302: the first node broadcasts the group creation transaction to the alliance-link network.

S304: the first node performs the group creation transaction.

S306: each other node than the first node performs the group creation transaction without creating a private chain.

S308: and each node in the alliance chain network writes the group establishing transaction and the corresponding execution result into a local alliance chain.

From the network level of the alliance chain, after accepting the group creation transaction initiated by the first manager account, the first node broadcasts the group creation transaction to the whole network. Each node in the alliance-link network packages the group creation transaction into a block based on a consensus algorithm (it is understood that there are other transactions in the block, and the other transactions are not necessarily other group creation transactions, and may be group join transactions or business transactions). After the block is generated by this consensus, each node needs to perform each transaction in the block and write the block into the local federation chain. It is noted here that a node will typically execute transactions based on locally deployed smart contracts or firmware.

Because the first node is the main body of the node group created this time, the private chain can be created only when the first node is local, and the private chain cannot be created when other nodes are local. This means that the first node performs the group creation transaction differently than the other nodes.

When the first node executes the group creation transaction, a private chain is created locally, and the group creation sub-transaction embedded in the group creation transaction is extracted and written into the local private chain.

And each other node except the first node does not create the private chain when executing the group creation transaction, and actually executes the group creation transaction under the condition that the private chain is not created. The other nodes may perform the group creation transaction "symbolically", and in order to implement different manners of performing the group creation transaction by the first node and the other nodes, the following implementation may be specifically adopted:

two groups of creation transaction execution logics can be deployed on each node, and the two groups of creation transaction execution logics respectively correspond to two different logic triggering conditions. The group creation transaction execution logic 1 may be to create a private chain locally and write a group creation sub-transaction into the local private chain, where the corresponding trigger condition is that the execution node is a node that accepts and broadcasts the group creation transaction; the group creation transaction execution logic 2 may be any execution logic that does not actually execute the group creation transaction, with the corresponding trigger condition being that the executing node is not the node that accepted and broadcast the group creation transaction. It is worth emphasizing here that the present specification does not specifically define the group creation transaction execution logic 2, as long as "symbolic" execution of the group creation transaction without creating a private chain is satisfied.

It will be appreciated that the results of the execution of the group creation transaction will of course also be written into the federation chain, and the results of the execution written into the federation chain by each node will of course be identical. In a specific implementation, the group creation transaction execution logic 1 and the group creation transaction execution logic 2 may be set to generate a logic of a same execution result, and the execution result corresponding to the group creation transaction may be set to include a group public key and a first node identifier, which indicate a public key corresponding to a node group created by the group creation transaction and an identity of a node creating the node group. For example, the execution result may include a first node identification.

It is to be understood that the writing of the execution result into the federation chain (or private chain) herein does not necessarily mean storing the execution result in plaintext into the federation chain (or private chain), and may also mean storing the execution result in plaintext locally and anchoring the hash value of the execution result in plaintext onto the federation chain (private chain).

The above description of "symbolic" execution of a group creation transaction is also applicable to the case of "symbolic" execution of other transactions, and the specific principles will not be described again later when "symbolic" execution is mentioned.

In addition, in practical applications, more than one node group may be created in the federation chain network, in which case, the group public key of the node group may be used as a unique identifier to distinguish different node groups, or a group identifier may be set for the node group.

Specifically, the group creation sub-transaction may further include a group identifier, and accordingly, an execution result corresponding to the group creation transaction may also include the group identifier.

In an embodiment of the present specification, the group creation sub-transaction may further include a signature generated using a group private key, so that the first node may verify the signature before broadcasting the group creation transaction to the whole network, and if the verification is passed, the group creation transaction is authorized to be initiated by the holder of the group private key, and a node group may be created based on the group creation transaction.

In this embodiment, it can be understood that the first node writes the group creation sub-transaction into the locally created private chain, and actually the first node writes the private chain creation block (which usually includes several group join sub-transactions or business transactions accepted after the creation of the private chain) wrapped with the group creation sub-transaction into the locally created private chain.

As can be seen, for a group creation transaction and its embedded group creation sub-transactions, the group creation transaction is packed into a block of a federation chain and written into the federation chain, and the group creation sub-transactions are packed into a creation block of a private chain local to the first node. In order to clarify the association relationship between the federation chain block and the private chain block and facilitate the record lookup, the first node may write a pointer object in the private chain block (which may specifically be in the block header) encapsulating the group creation sub-transaction, for pointing to the federation chain block encapsulating the group creation transaction.

Fig. 4 is a schematic diagram of a first node locally maintaining a federation chain and a private chain according to an embodiment of the present specification. As shown in fig. 4, the private chain creation block (packed with group creation sub-transactions) of the private chain local to the first node points to a federation chain block in the locally maintained federation chain in which the group creation transactions are packed by a pointer object.

The node group in the scheme can only comprise one node, and the node can write the service data butted by the node into a local private chain in a clear text manner. For this reason, how to trade in the case where only one node is included in the node group will be described first.

Fig. 5 is a schematic flowchart of a node group-based transaction method provided in an embodiment of the present specification, including the following steps:

s500: and the first node receives the business transaction constructed by the first management party account.

The business transaction comprises a business sub-transaction, and the business sub-transaction comprises business data and a signature generated by using a group private key corresponding to the group public key.

In the scenario of the scheme, a manager of the first node may accept a service request of a user, determine corresponding service data according to the service request, submit the service data to the first node in a two-layer nested service transaction form, so that the federation chain network executes a service transaction, and write the service transaction into the federation chain.

The business sub-transaction can be a deposit card type transaction or an execution type transaction. When the business sub-transaction is a credit card type transaction, the business data can be a data result obtained after the management party executes operation according to the business request; when the service sub-transaction is an execution type transaction, the service data may be a service request itself, and the nodes in the node group need to execute the service sub-transaction on the private chain network level to obtain an execution result, and both the service sub-transaction and the execution result are written into the private chain.

The inclusion of the signature in the business sub-transaction serves to prove that the business sub-transaction has the right to invoke the nodes in the node group to process the transaction. In addition, when more than one node group exists in the alliance-link network, the service sub-transaction may further include a group identifier for indicating the node group to be invoked by the service sub-transaction. And the first node verifies the signature in the business sub-transaction by using the group public key corresponding to the group identifier.

S502: and the first node verifies the signature in the business sub-transaction by using the group public key, and if the verification is passed, the business transaction is processed.

S504: the first node broadcasts the processed service transaction to the federation network.

The processing comprises the following steps: and replacing the business sub-transaction with the hash value of the business sub-transaction. On one hand, service data relates to data privacy and cannot be shared to a node group, on the other hand, on the network level of a alliance chain, service transactions including service sub-transactions need to be written into the alliance chain, through the processing, the first node can acquire plaintext of the service sub-transactions, and other nodes can only acquire hash values of the service sub-transactions.

S506: the first node performs the business transaction.

When the first node executes the business transaction, if the business sub-transaction is found to be a deposit-certificate type transaction, the business sub-transaction is written into a local private chain, if the business sub-transaction is found to be an execution type transaction, the business sub-transaction is executed, a corresponding execution sub-result is obtained, and the business sub-transaction and the corresponding execution sub-result are written into the local private chain.

S508: and other nodes in the alliance chain network execute the business transaction under the condition that a private chain is not created.

Here, the other nodes actually "symbolically" perform the traffic transaction.

S510: and each node in the alliance chain network writes the service transaction into a local alliance chain.

In addition, the first node may write a pointer object in the private chain block in which the service sub-transaction is encapsulated, for pointing to the federation chain block in which the processed service transaction is encapsulated.

A method of joining a node group is described below. It should be noted that, after the foregoing principle description of creating a node group is referred to, details of the principle communication will not be repeated.

Fig. 6 is a flowchart of a method for joining a node group according to an embodiment of the present specification, where the method includes the following steps:

s600: the second node receives a group join transaction constructed by the second administrator account.

The group join transaction comprises a group join sub-transaction, and the group join sub-transaction comprises a signature generated by using a group private key corresponding to the group public key; the second administrator account is an account registered by an administrator of the second node in the federation chain network.

After the first node creates the node group, the administrator of the second node may enable the second node to join the node group as well, sharing the service data with the first node. The administrator of the first node may provide the group private key to the administrator of the second node online.

S602: and the second node verifies the signature in the group joining sub-transaction by using the group public key, and if the signature passes the verification, the second node broadcasts the group joining transaction to the alliance chain network.

S604: the second node performs the group join transaction.

Specifically, the second node creates the private chain locally, synchronizes private chain history data from other nodes (such as the first node and other nodes that have joined the same group of nodes) that store the same private chain, and writes the group join sub-transaction to the local private chain.

S606: the other nodes storing the same private chain perform the group join transaction.

Specifically, the group join sub-transaction is written into the local private chain by other nodes storing the same private chain.

S608: and other nodes in the alliance chain network, which do not store the same private chain, execute the group join transaction without creating the private chain.

The other nodes in the alliance chain network, which do not store the same private chain, are other nodes which join the node group.

S610: and each node in the alliance chain network writes the group joining transaction and the corresponding execution result into a local alliance chain.

It can be understood that each node in the federation chain network writes the execution result corresponding to the group join transaction into a local federation chain. For example, the execution result corresponding to the group join transaction may include the second node identification.

Further, the group join transaction further includes a group identifier, and the second node verifies the signature of the group join sub-transaction using the group public key corresponding to the group identifier.

In addition, the second node and other nodes storing the same private chain write a pointer object in the private chain block encapsulating the group join sub transaction, for pointing to the federation chain block encapsulating the group join transaction.

Fig. 7 is a schematic diagram of locally maintaining a federation chain and a private chain by a second node according to an embodiment of the present specification. As shown in fig. 7, the second node requests to join the node group after the first node maintains the private chain for a while, before that, the private chain maintained by the first node stores two private chain blocks, the group join sub-transaction is packaged into a third private chain block, and meanwhile, the third private chain block is also associated with a certain alliance chain block packaged with the group join transaction.

The node group in the scheme can comprise more than one node, and each node in the same node group can share the service data butted by the node. A description is made herein of how to trade in the case where more than one node is included in a node group. It should be noted that, after the foregoing description of the principle of how to perform transactions in the case where only one node is included in the node group is referred to, details of the principle will not be repeated.

Fig. 8 is a flowchart of a node group-based transaction method provided in an embodiment of the present specification, where the method includes:

s800: and the second node receives the business transaction constructed by the second management party account.

The business transaction comprises a business sub-transaction comprising business data and a signature generated using the group private key.

S802: and the second node verifies the signature in the business sub-transaction by using the group public key, and if the verification is passed, the second node sends the business sub-transaction to other nodes storing the same private chain and processes the business transaction.

Since the node group includes not only the second node but also at least the first node (and possibly more nodes), the second node needs to send the service sub-transaction in the accepted service transaction to other nodes in the same node group on the private link network level.

In addition, the second node also needs to replace the business sub-transaction with the hash value of the business sub-transaction.

S804: and the second node broadcasts the processed service transaction to the alliance chain network.

S806: and the second node executes the service transaction with other nodes storing the same private chain.

S808: and executing the processed business transaction by other nodes which do not store the same private chain in the alliance chain network under the condition that the private chain is not created.

S810: and each node in the alliance chain network writes the processed business transaction into a local alliance chain.

Specifically, if the service sub-transaction is a credit-type transaction, the second node writes the service sub-transaction into a local private chain with other nodes storing the same private chain. And if the business sub-transaction is an execution type transaction, the second node executes the business sub-transaction with other nodes storing the same private chain, and writes the business sub-transaction and a corresponding execution sub-result into the local private chain.

Further, the service sub-transaction further includes a group identifier, and the second node may verify a signature in the service sub-transaction using the group public key corresponding to the group identifier.

Further, the second node and other nodes storing the same private chain write a pointer object in the private chain block encapsulating the service sub-transaction, which is used for pointing to the alliance chain block encapsulating the processed service transaction.

In addition, for each other node storing the same private chain, if the other node determines that the service sub-transaction is received, the other node returns a signature to the second node. In this way, if the second node determines that the number of the received signatures of the other nodes meets the preset distributed fault-tolerant condition, the second node processes the service transaction.

The distributed fault tolerance condition may be that the number of received signatures reaches a specified number. For example, if the number of nodes in the same node group is not less than 4, the specified number may be 2f +1, where f ═ N-1)/3, and N is the number of nodes in the node group.

In addition, the embodiments of the present specification also provide a block chain system, including a federation chain network, the federation chain network including a plurality of nodes;

the first node receives a group creation transaction constructed by a first administrator account; the group creation transaction comprises a group creation sub-transaction, the group creation sub-transaction comprising a group public key; the first administrator account is an account registered by an administrator of the first node in the federation chain network; the group public key is specified by a manager of the first node; broadcasting the group creation transaction to the federation chain network; executing the group creation transaction, including: creating a private chain locally, and writing the group creation sub-transaction into the local private chain;

each other node than the first node, performing the group creation transaction without creating a private chain;

The first node receives a business transaction constructed by the first manager account; the business transaction comprises a business sub-transaction, and the business sub-transaction comprises business data and a signature generated by using a group private key corresponding to the group public key; using the group public key to verify the signature in the business sub-transaction, and if the verification is passed, processing the business transaction, including: replacing the business sub-transaction with a hash value of the business sub-transaction; broadcasting the processed business transaction to the alliance chain network; performing the business transaction, including: writing the business sub-transaction into a local private chain;

the other nodes in the alliance chain network execute the business transaction under the condition that a private chain is not created;

The second node receives a group joining transaction constructed by the account of the second management party; the group join transaction comprises a group join sub-transaction, and the group join sub-transaction comprises a signature generated by using a group private key corresponding to the group public key; the second administrator account is an account registered by an administrator of the second node in the federation chain network; verifying the signature in the group joining sub-transaction by using the group public key, and broadcasting the group joining transaction to the alliance chain network if the signature passes the verification; performing the group join transaction, including: creating a private chain locally, synchronizing private chain historical data from other nodes storing the same private chain, and writing the group joining sub-transaction into the local private chain;

other nodes storing the same private chain, performing the group join transaction, including: writing the group join sub-transaction into a local private chain;

other nodes of the same private chain are not stored in the alliance chain network, and the group joining transaction is executed under the condition that the private chain is not created;

each node in the alliance chain network writes the group joining transaction and the corresponding execution result into a local alliance chain; and the execution result corresponding to the group joining transaction comprises a second node identifier.

The second node receives the business transaction constructed by the second manager account; the business transaction comprises a business sub-transaction, and the business sub-transaction comprises business data and a signature generated by using the group private key; using the group public key to verify the signature in the business sub-transaction, if the verification is passed, sending the business sub-transaction to other nodes storing the same private chain, and processing the business transaction, including: replacing the business sub-transaction with a hash value of the business sub-transaction; broadcasting the processed business transaction to the alliance chain network; and executing the business transaction with other nodes storing the same private chain, wherein the business transaction comprises the following steps: writing the business sub-transaction into a local private chain;

other nodes of the same private chain are not stored in the alliance chain network, and the processed business transaction is executed under the condition that the private chain is not created;

and each node in the alliance chain network writes the processed business transaction into a local alliance chain.

Embodiments of the present specification also provide a computer device, which at least includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the functions of the node in the embodiments of the present specification when executing the program.

Fig. 9 is a schematic diagram illustrating a more specific hardware structure of a computing device according to an embodiment of the present disclosure, where the computing device may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050. Wherein the processor 1010, memory 1020, input/output interface 1030, and communication interface 1040 are communicatively coupled to each other within the device via bus 1050.

The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present disclosure.

The Memory 1020 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like. The memory 1020 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 1020 and called to be executed by the processor 1010.

The input/output interface 1030 is used for connecting an input/output module to input and output information. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.

The communication interface 1040 is used for connecting a communication module (not shown in the drawings) to implement communication interaction between the present apparatus and other apparatuses. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).

Bus 1050 includes a path that transfers information between various components of the device, such as processor 1010, memory 1020, input/output interface 1030, and communication interface 1040.

It should be noted that although the above-mentioned device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040 and the bus 1050, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.

Embodiments of the present specification also provide a computer-readable storage medium on which a computer program is stored, which when executed by a processor, implements the functions of a node in the embodiments of the present specification.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

From the above description of the embodiments, it is clear to those skilled in the art that the embodiments of the present disclosure can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the embodiments of the present specification may be embodied in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, or the like, and includes several instructions for enabling a computer device (which may be a personal computer, a service device, or a network device) to execute the methods described in the embodiments or some parts of the embodiments of the present specification.

The systems, methods, modules or units described in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to some descriptions of the method embodiment for relevant points. The above-described apparatus embodiments are merely illustrative, and the modules described as separate components may or may not be physically separate, and the functions of the modules may be implemented in one or more software and/or hardware when implementing the embodiments of the present disclosure. And part or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

The foregoing is only a specific embodiment of the embodiments of the present disclosure, and it should be noted that, for those skilled in the art, a plurality of modifications and decorations can be made without departing from the principle of the embodiments of the present disclosure, and these modifications and decorations should also be regarded as the protection scope of the embodiments of the present disclosure.

Claims

1. A method of creating a node group in a federation chain network, the federation chain network including a plurality of nodes, the method comprising:

the first node receives a group creation transaction constructed by a first administrator account; the group creation transaction comprises a group creation sub-transaction, the group creation sub-transaction comprising a group public key;

2. The method of claim 1, the group creation sub-transaction further comprising a group identification;

the execution result corresponding to the group creation transaction also contains the group identification.

3. The method of claim 1, the group creation sub-transaction further comprising a signature generated using a group private key to which the group public key corresponds;

the first node broadcasting the group creation transaction to the alliance-link network, comprising:

and the first node verifies the signature in the group creation sub-transaction by using the group public key, and if the verification is passed, the group creation transaction is broadcasted to the alliance chain network.

4. The method of claim 1, further comprising:

and the first node writes a pointer object in the private chain block encapsulated with the group creation sub transaction, and the pointer object is used for pointing to the alliance chain block encapsulated with the group creation transaction.

5. A method of trading node groups created based on the method of creating node groups in a federation chain network of any one of claims 1 to 4, comprising:

6. The method of claim 5, the business sub-transaction further comprising a group identification;

the first node uses the group public key to verify the signature in the business sub-transaction, and the method comprises the following steps:

and the first node verifies the signature in the business sub-transaction by using the group public key corresponding to the group identifier.

7. The method of claim 5, further comprising:

and the first node writes a pointer object in the private chain block encapsulated with the service sub-transaction, and the pointer object is used for pointing to the alliance chain block encapsulated with the processed service transaction.

8. A method of joining a node group created based on the method of creating a node group in a federation chain network of any one of claims 1 to 4, comprising:

the second node receives a group joining transaction constructed by a second administrator account; the group join transaction comprises a group join sub-transaction, and the group join sub-transaction comprises a signature generated by using a group private key corresponding to the group public key;

the second node verifies the signature in the group joining sub-transaction by using the group public key, and if the signature passes the verification, the group joining transaction is broadcasted to the alliance chain network;

the second node performing the group join transaction, including: creating a private chain locally, synchronizing private chain historical data from other nodes storing the same private chain, and writing the group joining sub-transaction into the local private chain;

the other nodes storing the same private chain perform the group join transaction, including: writing the group join sub-transaction into a local private chain;

executing the group join transaction by other nodes which do not store the same private chain in the alliance chain network under the condition that the private chain is not established;

9. The method of claim 8, the group join transaction further comprising a group identification;

the second node verifies the signature of the group joining in the sub-transaction by using the group public key, and the verification comprises the following steps:

and the second node verifies the signature added into the sub-transaction by the group by using the group public key corresponding to the group identification.

10. The method of claim 8, further comprising:

and the second node and other nodes storing the same private chain write a pointer object in the private chain block in which the group joining sub transaction is encapsulated, so as to point to the alliance chain block in which the group joining transaction is encapsulated.

11. A method of trading a node group according to any one of claims 8 to 10 in a method of joining a node group, comprising:

the second node receives the business transaction constructed by the second management party account; the business transaction comprises a business sub-transaction, and the business sub-transaction comprises business data and a signature generated by using the group private key;

the second node verifies the signature in the business sub-transaction by using the group public key, if the verification is passed, the business sub-transaction is sent to other nodes storing the same private chain, and the business transaction is processed, wherein the method comprises the following steps: replacing the business sub-transaction with a hash value of the business sub-transaction;

the second node broadcasts the processed business transaction to the alliance chain network;

the second node executes the service transaction with other nodes storing the same private chain, including: writing the business sub-transaction into a local private chain;

the other nodes which do not store the same private chain in the alliance chain network execute the processed business transaction under the condition that the private chain is not established;

12. The method of claim 11, the business sub-transaction further comprising a group identification;

the second node uses the group public key to verify the signature in the business sub-transaction, and the method comprises the following steps:

and the second node verifies the signature in the business sub-transaction by using the group public key corresponding to the group identifier.

13. The method of claim 11, the method further comprising:

and the second node and other nodes storing the same private chain write a pointer object in the private chain block in which the service sub-transaction is encapsulated, so as to point to the alliance chain block in which the processed service transaction is encapsulated.

14. The method of claim 11, the method further comprising:

for each other node storing the same private chain, if the other node determines to receive the service sub-transaction, returning a signature to the second node;

the second node processes the business transaction, including:

and if the second node determines that the number of the received signatures of other nodes meets the preset distributed fault-tolerant condition, processing the service transaction.

15. A blockchain system comprising a federation chain network comprising a plurality of nodes;

the first node receives a group creation transaction constructed by a first administrator account; the group creation transaction comprises a group creation sub-transaction, the group creation sub-transaction comprising a group public key; broadcasting the group creation transaction to the federation chain network; executing the group creation transaction, including: creating a private chain locally, and writing the group creation sub-transaction into the local private chain;

16. The system of claim 15, the first node, receiving a business transaction constructed by the first administrator account; the business transaction comprises a business sub-transaction, and the business sub-transaction comprises business data and a signature generated by using a group private key corresponding to the group public key; using the group public key to verify the signature in the business sub-transaction, and if the verification is passed, processing the business transaction, including: replacing the business sub-transaction with a hash value of the business sub-transaction; broadcasting the processed business transaction to the alliance chain network; performing the business transaction, including: writing the business sub-transaction into a local private chain;

17. The system of claim 15, the second node receiving a group join transaction constructed from the second administrator account; the group join transaction comprises a group join sub-transaction, and the group join sub-transaction comprises a signature generated by using a group private key corresponding to the group public key; verifying the signature in the group joining sub-transaction by using the group public key, and broadcasting the group joining transaction to the alliance chain network if the signature passes the verification; performing the group join transaction, including: creating a private chain locally, synchronizing private chain historical data from other nodes storing the same private chain, and writing the group joining sub-transaction into the local private chain;

18. The system of claim 17, the second node, receiving the business transaction constructed by the second administrator account; the business transaction comprises a business sub-transaction, and the business sub-transaction comprises business data and a signature generated by using the group private key; using the group public key to verify the signature in the business sub-transaction, if the verification is passed, sending the business sub-transaction to other nodes storing the same private chain, and processing the business transaction, including: replacing the business sub-transaction with a hash value of the business sub-transaction; broadcasting the processed business transaction to the alliance chain network; and executing the business transaction with other nodes storing the same private chain, wherein the business transaction comprises the following steps: writing the business sub-transaction into a local private chain;

19. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the functions of the node in the method of any one of claims 1-14 when executing the program.