CN112667601B

CN112667601B - Block chain identification management method, terminal equipment and computer readable storage medium

Info

Publication number: CN112667601B
Application number: CN202011609697.4A
Authority: CN
Inventors: 李伟; 蔡亮; 邱炜伟; 汪小益; 张帅; 楼嵩
Original assignee: Hangzhou Qulian Technology Co Ltd
Current assignee: Hangzhou Qulian Technology Co Ltd
Priority date: 2020-12-30
Filing date: 2020-12-30
Publication date: 2023-06-20
Anticipated expiration: 2040-12-30
Also published as: CN112667601A

Abstract

The application is applicable to the technical field of computer application, and provides a management method, terminal equipment and a computer readable storage medium for block chain identification, wherein the method comprises the following steps: receiving attribute information sent by a block chain, wherein the attribute information comprises identification information of the block chain; based on the attribute information, sending a transaction request to a relay chain in a cross-chain network, wherein the transaction request is used for indicating the relay chain to audit the attribute information; and if the verification is passed, receiving the instruction fed back by the relay chain, and executing the operation requirement associated with the identification information. According to the method and the device, the problem of management of the identity of the blockchain in the whole cross-chain network in a scene of realizing large-scale blockchain intercommunication can be solved.

Description

Block chain identification management method, terminal equipment and computer readable storage medium

Technical Field

The application belongs to the technical field of computer application, and particularly relates to a management method of blockchain identification, terminal equipment and a computer readable storage medium.

Background

With the development and innovation of the blockchain technology, blockchain networks with different characteristics and different scene requirements are generated in different fields, and an independent value system is formed. Blockchain cross-chain technology is an important means for achieving interconnection and value transfer between heterogeneous blockchains.

As the internet contains many sub-networks, with the expansion of the cross-link network, for a large cross-link network that connects all cross-link networks, many sub-cross-link networks are also contained, and the connection between different sub-cross-link networks may be based on different cross-link technologies. Also, for each sub-span chain network that contains any blockchain, the sub-span chain network may contain many smaller sub-networks. Therefore, to implement the interworking of large-scale blockchains, management of blockchain identities in the entire cross-chain network is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a management method, terminal equipment and a computer readable storage medium for blockchain identification, which can solve the problem of managing the identity identification of blockchains in a whole cross-chain network for realizing the intercommunication of large-scale blockchains.

In a first aspect, an embodiment of the present application provides a method for managing blockchain identification, where the method is applied to a cross-chain gateway, and the method includes:

receiving attribute information sent by a block chain, wherein the attribute information comprises identification information of the block chain; based on the attribute information, sending a transaction request to a relay chain in a cross-chain network, wherein the transaction request is used for indicating the relay chain to audit the attribute information; and if the verification is passed, receiving the instruction fed back by the relay chain, and executing the operation requirement associated with the identification information.

In a possible implementation manner of the first aspect, the attribute information includes a chain identifier to be registered of the blockchain; the sending the transaction request to the relay link in the cross-link network based on the attribute information comprises the following steps:

sending a registration request to a root relay chain in the cross-chain network, wherein the registration request is used for indicating the root relay chain to audit attribute information containing the chain identifier;

correspondingly, if the auditing is passed, receiving the instruction fed back by the relay chain, and executing the operation requirement associated with the identification information, including:

and if the verification is passed, receiving a synchronization instruction fed back by the root relay chain, and synchronizing the chain identifier to a chain identifier table of a relay chain of the sub-network to which the block chain belongs.

In a possible implementation manner of the first aspect, the attribute information includes a chain information document of the blockchain; the method further comprises the steps of:

and storing the chain information document under the chain, and sending a storage address of the chain information document to the root relay chain to instruct the root relay chain to acquire the content of the chain information document according to the storage address.

In a possible implementation manner of the first aspect, the attribute information includes update information; the sending the transaction request to the relay link in the cross-link network based on the attribute information comprises the following steps:

Sending an update request to a root relay chain in the cross-chain network, wherein the update request is used for indicating the root relay chain to audit the update information;

and if the verification is passed, receiving an updating instruction fed back by the root relay chain, and updating the stored chain information document of the block chain according to the updating information.

In a possible implementation manner of the first aspect, the method further includes:

receiving a chain identifier to be analyzed sent by a block chain; based on the chain identifier to be resolved, sending a resolving request to a relay chain in the cross-chain network; if the chain identifier table of the relay chain does not comprise the chain identifier to be analyzed, receiving an address of an upper relay chain fed back by the relay chain; if the chain identifier table of the relay chain contains the chain identifier to be analyzed and the access request received by the relay chain reaches the preset number, receiving the address of the lower relay chain fed back by the relay chain; the analysis request is sent to the upper relay chain or the lower relay chain again according to the address of the upper relay chain or the address of the lower relay chain; receiving an analysis result fed back by the relay chain, or an analysis result fed back by the upper relay chain, or an analysis result fed back by the lower relay chain; caching the analysis result to a chain identification cache table of the cross-chain gateway; and sending the analysis result to the block chain requesting analysis.

Illustratively, a chain identifier to be parsed sent by a blockchain is received; and if the chain identification cache table contains the chain information corresponding to the chain identifier to be analyzed, the chain information is sent to the block chain requesting analysis.

In a possible implementation manner of the first aspect, the method further includes: sending an application request of a preset chain identifier to a root relay chain in the cross-chain network, wherein the application request is used for indicating the root relay chain to audit the preset chain identifier; and if the root relay chain passes the audit, receiving information of passing application fed back by the relay chain.

In a second aspect, an embodiment of the present application provides a method for managing blockchain identification, where the method is applied to a relay chain, and the method includes: receiving a transaction request sent by a cross-chain gateway, wherein the transaction request is generated by the cross-chain gateway based on attribute information of a blockchain, and the attribute information comprises identification information of the blockchain; auditing the attribute information according to the transaction request; and if the verification is passed, feeding back an instruction to the cross-chain gateway, wherein the instruction is used for indicating the cross-chain gateway to execute the operation requirement associated with the identification information.

In a possible implementation manner of the second aspect, if the relay chain is a root relay chain in the cross-chain network, the receiving a transaction request sent by a cross-chain gateway, and auditing the attribute information according to the transaction request includes:

receiving a registration request sent by the cross-link gateway, wherein the registration request is generated by the cross-link gateway based on attribute information containing a chain identifier to be registered; auditing attribute information containing the chain identifier to be registered;

correspondingly, if the auditing is passed, feeding back an instruction to the cross-link gateway, including:

if the verification is passed, updating a chain identification table and sending a synchronization instruction to the cross-chain gateway, wherein the synchronization instruction is used for indicating the cross-chain gateway to synchronize the chain identifier to a chain identification table of a relay chain of a sub-network to which the blockchain belongs; and/or

Receiving an update request sent by the cross-chain gateway, wherein the update request is generated by the cross-chain gateway based on the update information of the blockchain; auditing the updated information;

if the verification is passed, updating a chain identification table and sending an update instruction to the cross-chain gateway, wherein the update instruction is used for indicating the cross-chain gateway to update the stored chain information document of the blockchain according to the update information.

In a possible implementation manner of the second aspect, the method further includes:

receiving an analysis request sent by the cross-chain gateway, wherein the analysis request is generated by the cross-chain gateway based on a chain identifier to be analyzed sent by a blockchain; if the chain identification table of the relay chain contains the chain identifier to be analyzed, analyzing the chain identifier to be analyzed to obtain an analysis result, and sending the analysis result to the cross-chain gateway; if the chain identification table of the relay chain contains the chain identifier to be analyzed and the access request received by the relay chain reaches the preset number, sending an address of a lower relay chain to the inter-chain gateway, wherein the address of the lower relay chain is used for indicating the inter-chain gateway to send the analysis request to the lower relay chain; and if the chain identification table of the relay chain does not contain the chain identifier to be analyzed, sending an address of an upper relay chain to the cross-chain gateway, wherein the address of the upper relay chain is used for indicating the cross-chain gateway to send the analysis request to the upper relay chain.

In a possible implementation manner of the second aspect, if the relay chain is a root relay chain in the cross-chain network, the method further includes:

Receiving an application request of a preset chain identifier sent by the cross-chain gateway; auditing the preset chain identifier; if the verification is passed, the ownership of the preset chain identifier is recorded in a chain identifier table, and information of passing application is sent to the cross-chain gateway.

In a third aspect, an embodiment of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the method when executing the computer program.

In a fourth aspect, embodiments of the present application provide a computer readable storage medium storing a computer program that when executed by a processor implements the method.

In a fifth aspect, embodiments of the present application provide a computer program product, which, when run on a terminal device, causes the terminal device to perform the method of any one of the first or second aspects above.

It will be appreciated that the advantages of the second to fifth aspects may be found in the relevant description of the first aspect, and are not described here again.

Compared with the prior art, the embodiment of the application has the beneficial effects that: according to the embodiment of the application, the terminal equipment of the cross-chain gateway node receives attribute information sent by a blockchain, wherein the attribute information comprises identification information of the blockchain; based on the attribute information, sending a transaction request to a relay chain in a cross-chain network, wherein the transaction request is used for indicating the relay chain to audit the attribute information; if the verification is passed, receiving an instruction fed back by the relay chain, and executing an operation requirement associated with the identification information; the management of the identity of the blockchain in the whole cross-chain network can be realized in the intercommunication scene of the large-scale blockchain, so that the identification information of the blockchain is based on the relay chain, and the centralization risk is reduced; has stronger usability and practicability.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required for the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic system architecture diagram of an application scenario provided in an embodiment of the present application;

FIG. 2 is a flowchart of a blockchain identification management method according to an embodiment of the present application;

FIG. 3 is a flowchart illustrating a blockchain identification management method according to another embodiment of the present application;

FIG. 4 is a schematic diagram of an interactive flow of a blockchain management method according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a block chain identifier resolution process according to one embodiment of the present application;

fig. 6 is a schematic structural diagram of a cross-link gateway node provided in an embodiment of the present application;

fig. 7 is a schematic structural diagram of a relay link node provided in an embodiment of the present application;

fig. 8 is a schematic structural diagram of a terminal device provided in an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system configurations, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.

As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".

In addition, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.

Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.

With the development of blockchain cross-chain technology, a large cross-chain network that communicates all cross-chain networks may include multiple sub-cross-chain networks, and different sub-cross-chain networks may be based on different cross-chain technologies, e.g., a blockchain system that communicates with a BitXHub technology may be one of the sub-cross-chain networks. Each sub-cross-link network may contain a plurality of smaller sub-networks.

Currently, a general scheme adopted for a management method of chain identifiers of blockchains is to register identity names to relay chains through application chains; when there are multiple relay chains in a cross-chain network, registration of different application chains with different relay chains may result in duplicate names. Even if the identification of the blockchain is generated by the relay chain, such as a hash with a large number of digits or a random number with a large space, collision probability still exists in theory, the chain identifier has no specific meaning, the expansion of a cross-chain network is difficult to support, and the blockchain self-selection identification cannot be realized.

The embodiment of the application provides a management method of chain identifiers of blockchains based on W3C DID standard format definition, which can ensure the uniqueness of the identity identifier of each blockchain aiming at the inside or the outside of a sub-cross-chain network in a large-cross-chain network, and enables the constitution of the blockchain identity identifier to be structured and expandable, thereby supporting the continuous increase of the scale of the cross-chain network and realizing the access of heterogeneous application chains.

Referring to fig. 1, a schematic system architecture of an application scenario provided in an embodiment of the present application may include a plurality of sub-span networks, such as a sub-span network 1, a sub-span network 2, and a sub-span network 3, in a large span network as shown in fig. 1. In the sub-inter-link network 1, B2, B3, B4 represent relay links, C1, C2, C3, C4 represent application links, and P1, P2, P3, P4, P5, P6, P7 represent inter-link gateways. A cross-chain gateway is a single node that connects two blockchains, delivering cross-chain messages for both chains to which it is connected.

Wherein P1 is used for connecting B1 and B2; p2 is used for connecting B1 and B3; p3 is used for connecting B2 and C1; p4 is used for connecting B2 and C2; p5 is used for connecting B3 and C3; p6 is used for connecting B3 and B4; p7 is used for connecting B4 and C4.

In addition, the sub-inter-link network 1 may include a hierarchical architecture, possibly including multiple relay links and inter-link gateways. For example, B1 in the figure is a root relay chain in the network, B2 and B3 are second layer relay chains, and B4 is a third layer relay chain.

It should be noted that any interaction and communication between two chains must be supported by a cross-chain gateway in the middle. Some low-level relay chains can be connected to the application chains to complete functions such as verification of the application chain cross-chain transaction and the like, and the cross-chain transaction is realized; for example, the relay link B2 of the second layer and the application links (C1, C2) to which it is connected form a smaller sub-network. Smaller sub-networks communicate with other small sub-networks through the relay of a higher-level relay chain (e.g., B1). For example, the sub-network B2 (sub-network having the relay chain B2 as the root relay chain) includes B2, C1, and C2; the sub-network B4 comprises B4 and C4; the sub-network B3 includes B3, C3, B4, and C4.

For example, to implement management of chain identifiers of blockchains, relay chains, application chains, and cross-chain gateways are provided with some sub-functional modules. For example, the modules on the application chain and the relay chain include: the chain management module and the chain identification table. The chain management module is used for receiving requests of various operations and carrying out corresponding processing; the chain identification table is used for recording information and states of the blockchain identity. The cross-chain gateway comprises the following modules: a storage engine, a message forwarding module and a chain identification cache table. The storage engine is used for interacting with the under-chain storage and carrying out storage operation on the chain information document. Thus, the relay chain may hand over the relatively time consuming operation of the I/O read-write portion directly with the off-chain store to the cross-chain gateway for processing; the operation of reading and writing data in the identity storage network is transparent to the relay chain, so that heterogeneous identity storage networks can be supported. The message forwarding module is used for transferring the cross-link messages between the application chains, between the relay chains and the application chains and between the relay chains. The chain identification cache table is used for caching the chain information requested during partial parsing.

The chain management module of each relay chain processes requests sent by the blockchain through the cross-chain gateway. Furthermore, each relay chain stores a chain identification table that records the chain identifiers of the blockchains known to itself, such as the root relay chain B1 stores identity information of all blockchains (including relay chains and application chains) in the entire sub-across-chain network 1. And the relay chain B2 of the second layer needs to store identity information of the blockchain in the network connected with itself, namely B2, C1 and C2.

The method for managing blockchain identities in a cross-chain network is further described below by way of an embodiment, referring to fig. 2, which is a schematic flowchart of blockchain identity management provided in an embodiment of the present application, where an execution body of the method is a terminal device deployed by a cross-chain gateway node in the cross-chain network. As shown in fig. 2, the method comprises the steps of:

step S201, receiving attribute information sent by a block chain, wherein the attribute information comprises identification information of the block chain;

in some embodiments, the blockchain may communicate to the relay chain or other blockchain through a cross-chain gateway that receives attribute information sent by the blockchain. The attribute information may include a chain identifier, an affiliated subnet, a chain identity information document, and the like. The subnet to which the application chain C1 belongs is an identity of a root relay chain B2 in the subnet to which the application chain C1 belongs in fig. 1. The identification information of the blockchain can be a chain identifier of the blockchain, a registered chain identifier, a chain identifier to be registered, and a chain identifier to be applied. The terminal device of the cross-chain gateway node can receive attribute information sent by the blockchain and make different responses according to different attribute information.

The identification information or the chain identifier may be an identifier in a specific format, for example, an identifier set based on a W3C DID specification format, has a uniform format architecture, and different fields represent different meanings, for example, an identifier "DID: bischub 1: appchain001".

Step S202, based on the attribute information, a transaction request is sent to a relay chain in a cross-chain network, wherein the transaction request is used for indicating the relay chain to audit the attribute information.

In some embodiments, the transaction request is a request associated with the identification information in the attribute information, and may include an application request for a chain identifier, a registration request for a chain identifier, an update request for chain information, or an parse request for a chain identifier, etc.

For example, the cross-chain gateway may store attribute information of the blockchain under the chain while sending a request to the relay chain, save a chain information document of the blockchain, and provide an address storing the chain information document to the relay chain.

When the terminal equipment of the cross-chain gateway node sends a transaction request to the relay chain, parameters such as a chain identifier of the blockchain, an address of a sub-network to which the request belongs, an address of a chain information document or a hash value of the content of the chain information document are sent, and the relay chain is instructed to audit the information.

The terminal device that is the main body of the method may be any node that deploys a cross-link gateway connected to the relay link.

And step S203, if the verification is passed, receiving the instruction fed back by the relay chain, and executing the operation requirement associated with the identification information.

In some embodiments, if the attribute information of the blockchain is checked and approved by the relay chain, the cross-chain gateway receives a command fed back by the relay chain; the instructions may include a synchronization instruction, and the cross-link gateway synchronizes the chain identifier of the newly added blockchain according to the synchronization instruction and notifies other relay chains in the cross-link network; the instructions may also be update instructions, the cross-chain gateway updates stored chain information of the blockchain, etc., according to the update instructions. Thereby realizing the management of the association relationship between the blockchain identification and the blockchain.

In some embodiments, the attribute information includes a chain identifier of the blockchain to be registered; based on the attribute information, sending a transaction request to a relay chain in a cross-chain network, comprising: and sending a registration request to a root relay chain in the cross-chain network, wherein the registration request is used for indicating the root relay chain to audit the attribute information containing the chain identifier.

Correspondingly, if the auditing is passed, receiving a command fed back by the relay chain, and executing the operation requirement associated with the identification information, wherein the method comprises the following steps: if the verification is passed, a synchronization instruction fed back by the root relay chain is received, and the chain identifier is synchronized to a chain identifier table of the relay chain of the sub-network to which the block chain belongs.

In some embodiments, the chain identifier to be registered is a chain identifier that the blockchain is used; the root relay chain in the cross-chain network is the root relay chain of the sub-cross-chain network to which the block chain applied for registration belongs, for example, the root relay chain B1 in the sub-cross-chain network 1 to which the block chain C1 in fig. 1 belongs.

The process of checking by the relay chain can be that the relay chain acquires document content according to the address of the chain information document in the attribute information, hashes the document content to obtain a hash value, compares the hash value with the hash value of the chain document content sent by the terminal equipment of the cross-chain gateway node, judges whether the hash value is consistent, and if so, indicates that the checking is passed; voting decisions may also be made by individual nodes deployed in the relay chain. It should be noted that, the auditing process is a process of verifying the identity of the blockchain, and the specific auditing mode is not limited.

In addition, after the verification is passed, the chain identifier of the blockchain is successfully registered, the terminal equipment of the cross-chain gateway node receives a synchronization instruction fed back by the root relay chain, and the association relationship between the blockchain and the chain identifier is notified to other relay chains in the cross-chain network. The relay chain of the sub-network to which the blockchain belongs is a sub-network of a smaller unit in a sub-span chain network in which the blockchain belongs, for example, in fig. 1, the sub-network of the sub-span chain network to which the application chain C1 belongs is a sub-network of which the relay chain B2 is the root relay chain.

In some embodiments, the attribute information includes a chain information document of a blockchain; the method further comprises the steps of: and storing the chain information document under the chain, and sending the storage address of the chain information document to the root relay chain to instruct the root relay chain to acquire the content of the chain information document according to the storage address.

For example, the cross-link gateway obtains information such as a chain information document, a chain identifier, a subnet to which the registered chain belongs (i.e. an identity of the root relay chain of the subnet) and the like, which are formed by information of the blockchain C1, and the cross-link gateway is any gateway connected with the relay chain B1, for example, the cross-link gateway P1 or P2. The cross-chain gateway stores the chain information document under the chain. Then, the cross-chain gateway initiates a registration request to the root relay chain B1, providing: parameters such as a chain identifier, a subnet to which the registered chain belongs (i.e. an identity of the subnet root relay chain), a storage address of the chain information document, a hash value of the content of the chain information document, and the like. The root relay chain B1 acquires the chain information document content according to the address of the chain information document, hashes the chain information document content, compares the hash value of the received chain information document content with the hash value of the received chain information document content, and checks the identification registration request. If the verification is passed, the root relay chain B1 updates its own chain identification table to complete association and update of the blockchain and its identifier, chain information document and the like. Meanwhile, the root relay chain B1 synchronizes the chain identification table to the low-level relay chains (e.g., B2, B3) through the cross-chain gateway, and the low-level relay chains update the entries of the identifiers of the blockchains in the sub-network rooted at the low-level relay chains themselves. For example, C1 registers successfully, and C1 is in the network B2, so the relay chain B2 needs to update its chain identification table. If C1 is not in the B2 network but in the B4 network, all the relay links from the root relay link B1 to C1 synchronize the newly added entries, i.e. update the link indication tables of B3 and B4.

In some embodiments, the attribute information includes update information; based on the attribute information, sending a transaction request to a relay chain in a cross-chain network, comprising: and sending an update request to a root relay chain in the cross-chain network, wherein the update request is used for indicating the root relay chain to audit the update information.

Correspondingly, if the auditing is passed, receiving a command fed back by the relay chain, and executing the operation requirement associated with the identification information, wherein the method comprises the following steps: and if the verification is passed, receiving an updating instruction fed back by the root relay chain, and updating the stored chain information document of the block chain according to the updating information.

In some embodiments, when information of a blockchain is updated, an update request needs to be initiated to a root relay chain of a cross-chain network in which the blockchain resides. The update information includes an address of the chain information document or a hash value of the content of the chain information document, or the like. The root relay chain in the cross-chain network is the root relay chain of the sub-cross-chain network to which the block chain applying for update belongs, for example, the root relay chain B1 in the sub-cross-chain network 1 to which the block chain C1 in fig. 1 belongs.

In addition, after the checking is passed, the information of the blockchain is successfully updated, the terminal equipment of the cross-link gateway node receives an updating instruction fed back by the root relay chain, and the stored chain information document of the blockchain is updated according to the updating information, including notifying other relay chains in the cross-link network, updating the chain information document corresponding to and associated with the chain identifier in the table entry of the chain identification table, and the like. The relay chain of the sub-network to which the blockchain belongs is a sub-network of a smaller unit in a sub-span chain network in which the blockchain belongs, for example, in fig. 1, the sub-network of the sub-span chain network to which the application chain C1 belongs is a sub-network of which the relay chain B2 is the root relay chain.

For example, the cross-chain gateway obtains the updated information such as a chain information document, a chain identifier, a subnet to which the updated chain belongs (i.e. the identity of the root relay chain of the subnet) which is newly formed by the information of the blockchain C1, and the cross-chain gateway is any gateway connected with the relay chain B1, for example, the cross-chain gateway P1 or P2. The cross-chain gateway stores the chain information document under the chain. Then, the cross-chain gateway initiates an update request to the root relay chain B1, providing: parameters such as a chain identifier, a subnet to which the updated chain belongs (i.e. the identity of the subnet root relay chain), a storage address of the chain information document, a hash value of the content of the chain information document, and the like. The root relay chain B1 acquires the chain information document content according to the address of the chain information document, hashes the chain information document content, compares the hash value of the received chain information document content with the hash value of the received chain information document content, and checks the update request. If the verification is passed, the root relay chain B1 updates its own chain identification table to complete the updating of the blockchain and the chain information document of the chain identifier. Meanwhile, the root relay chain B1 informs the chain identification table to the low-level relay chains (such as B2 and B3) through the cross-chain gateway to update information, and the low-level relay chains update the table items of the identifiers of the blockchains in the sub-network taking the root of the low-level relay chains. For example, C1 registers successfully, and C1 is in the network B2, so the relay chain B2 needs to update its chain identification table. If C1 is not in the B2 network but in the B4 network, all the relay links from the root relay link B1 to C1 update the link information of the corresponding table entry, i.e. update the link information of the link indication tables of B3 and B4.

In order to ensure that the blockchain uniquely corresponds to the chain identifier, the update information of the blockchain can only modify information other than the chain identifier, such as an address of the chain information document or a hash value of the content of the chain information document.

In some embodiments, the method further comprises: sending an application request of a preset chain identifier to a root relay chain in a cross-chain network, wherein the application request is used for indicating the root relay chain to audit the preset chain identifier; and if the root relay chain passes the verification, receiving information fed back by the relay chain and applied for passing.

In some embodiments, a user agent terminal or a terminal device of a blockchain node sends a preset identifier in a specific format to a cross-link gateway, and the cross-link gateway initiates an application request to a root relay link in a cross-link network; checking the identified application request by the root relay chain, voting by each node in the root relay chain in the checking process, and if the identifier is not applied by the block chain or the user known by each node, checking is passed; the audit may also be performed in other ways. If the verification is passed, the root relay chain B1 records that the applicant obtains ownership of the blockchain identifier in a chain identifier list; if the audit is not passed, the identifier still does not belong to any entity.

The applied chain identifier may be an identifier field set based on the W3C DID specification format, for example, a preset specific format identifier of DID: bischub 1: appchain001.

In some embodiments, the method further comprises: the cross-chain gateway receives a chain identifier to be analyzed, which is sent by a block chain; based on the chain identifier to be analyzed, the cross-chain gateway sends an analysis request to a relay chain in the cross-chain network; if the chain identifier table of the relay chain does not comprise the chain identifier to be analyzed, the cross-chain gateway receives the address of the upper relay chain fed back by the relay chain; if the chain identifier list of the relay chain contains the chain identifier to be analyzed and the access request received by the relay chain reaches the preset number, the cross-chain gateway receives the address of the lower relay chain fed back by the relay chain; according to the address of the upper relay chain or the address of the lower relay chain, the cross-chain gateway sends an analysis request to the upper relay chain or the lower relay chain again; the cross-link gateway receives the analysis result fed back by the relay link, or the analysis result fed back by the upper relay link, or the analysis result fed back by the lower relay link; caching the analysis result to a chain identification cache table of the cross-chain gateway; and sending the analysis result to the block chain requesting analysis.

In some embodiments, the blockchain may initiate an id resolution request to any relay chain in the cross-chain network through the cross-chain gateway, where the feedback received by the cross-chain gateway includes three cases:

(1) The chain identification table of the requested relay chain does not have the identifier entry and returns the address of its upper relay chain.

(2) The chain identification table of the requested relay chain has the identifier table item, but the current request to be processed of the relay chain is too many, so as to improve the response speed of the whole system, and at the moment, the address of another relay chain (generally the lower relay chain of the relay chain) is returned; for example: the root relay chain B1 needs to process too many requests, and when it processes the identifier resolution request of C2, it may return the address of B2, letting B2 share some load instead.

(3) The chain identification table of the requested relay chain has the identifier table item, and the relay chain needs not more requests to be processed currently, the table is checked and the analysis result is returned.

It should be noted that, when the parsing result is returned by the relay chain, the chain information of the table entry will be cached by the cross-chain gateway. If the relay chain returns an address of another relay chain, the cross-chain gateway re-initiates an analysis request of the identity identifier to the address of the new relay chain.

In addition, if a certain cross-link gateway forwarding the above analysis request has the identifier table entry, the result is directly returned. The cross-link gateway directly obtains the information document according to the link information document address in the table entry and the hash-down storage of the information document. Then the hash is compared with the hash of the information document returned on the chain, and then the document content and the comparison result are returned (if the hash does not accord, the document content is falsified).

It should be noted that, the root relay chain B1 has only one in the sub-span chain network 1. The application, registration and update requests are only authorized to be processed by the root relay chain B1 as long as the application is in the sub-cross-chain network 1. The consistency of the identifiers is ensured, and no conflict exists.

Illustratively, the chain information document may be in JSON format, or may be in other formats such as JSON-LD, YAML, TOML, XML format, in which information about the chain is stored, for example:

{

"id": "did: bitxuub: appchain001"; a// identifier definition;

"type": "appchain"; a// blockchain type definition;

"admins" [.+ -.); a// default user name definition, etc.;

...

}

in the foregoing embodiment, the implementation process of the relay chain has been described corresponding to the implementation process of the cross-chain gateway, and based on the same implementation principle, details are not repeated herein. As shown in fig. 3, the implementation flow of the method includes:

In step S301, the relay chain receives a transaction request sent by the cross-chain gateway, where the transaction request is generated by the cross-chain gateway based on attribute information of the blockchain, and the attribute information includes identification information of the blockchain.

And step S302, the relay chain carries out auditing on the attribute information according to the transaction request.

Step S303, if the audit is passed, the relay chain feeds back an instruction to the cross-chain gateway, wherein the instruction is used for indicating the cross-chain gateway to execute the operation requirement associated with the identification information.

In some embodiments, if the relay chain is a root relay chain in the cross-chain network, the relay chain receives a transaction request sent by the cross-chain gateway, and the relay chain audits attribute information according to the transaction request, including: the root relay chain receives a registration request sent by a cross-chain gateway, wherein the registration request is generated by the cross-chain gateway based on attribute information containing a chain identifier to be registered; the root relay chain audits attribute information containing the chain identifier to be registered.

Correspondingly, if the auditing is passed, the relay chain feeds back an instruction to the cross-chain gateway, which comprises the following steps: if the verification is passed, the root relay chain updates the chain identification table and sends a synchronization instruction to the cross-chain gateway, wherein the synchronization instruction is used for indicating the cross-chain gateway to synchronize the chain identifier to the chain identification table of the relay chain of the sub-network to which the blockchain belongs.

In some embodiments, if the relay chain is a root relay chain in the cross-chain network, the relay chain receives a transaction request sent by the cross-chain gateway, and audits attribute information according to the transaction request, and further includes: the root relay chain receives an update request sent by a cross-chain gateway, wherein the update request is generated by the cross-chain gateway based on update information of a block chain; and the root relay chain audits the updated information.

Correspondingly, if the auditing is passed, the relay chain feeds back an instruction to the cross-chain gateway, which comprises the following steps: if the verification passes, the root relay chain updates the chain identification table and sends an update instruction to the cross-chain gateway, wherein the update instruction is used for indicating the cross-chain gateway to update the stored chain information document of the blockchain according to the update information.

In some embodiments, the method further comprises: the relay chain receives an analysis request sent by a cross-chain gateway, wherein the analysis request is generated by the cross-chain gateway based on a chain identifier to be analyzed sent by a blockchain; if the chain identification table of the relay chain contains the chain identifier to be analyzed, the relay chain analyzes the chain identifier to be analyzed to obtain an analysis result, and the relay chain sends the analysis result to the cross-chain gateway. If the chain identification table of the relay chain contains the chain identifier to be analyzed and the access requests received by the relay chain reach the preset number, the relay chain sends the address of the lower relay chain to the cross-chain gateway, and the address of the lower relay chain is used for indicating the cross-chain gateway to send the analysis request to the lower relay chain. If the chain identification table of the relay chain does not contain the chain identifier to be analyzed, the relay chain sends the address of the upper relay chain to the cross-chain gateway, and the address of the upper relay chain is used for indicating the cross-chain gateway to send the analysis request to the upper relay chain.

In some embodiments, if the relay chain is a root relay chain in a cross-chain network, the method further comprises: a root relay chain in a sub-cross-chain network 1 receives an application request of a preset chain identifier sent by a cross-chain gateway; auditing a preset chain identifier; if the verification is passed, the ownership of the preset chain identifier is recorded in the own chain identifier table, and the information of passing application is sent to the cross-chain gateway.

It should be noted that, the root relay chain B1 has only one in the sub-span chain network 1. The application request, registration request, update request are only authorized to be processed by the root relay chain B1 as long as they are application chains within the sub-cross-chain network 1. The consistency of the identifiers is ensured, and no conflict exists.

As shown in fig. 4, an interactive flow diagram of a blockchain management method according to an embodiment of the present application includes an application stage, a registration stage, and an update stage of chain information of a chain identifier. As shown in fig. 4, the interaction process of each stage is illustrated, and the application stage includes:

1. the blockchain or user agent node or application sends a preset chain identifier to the cross-chain gateway;

2. the cross-link gateway sends an application request to the root relay link B1;

3. The root relay chain B1 carries out auditing on a preset chain identifier;

4. if the verification passes, recording ownership of the block chain identification obtained by the applicant in a chain identification table of the root relay chain B1;

5. if the verification passes, the root relay link B1 sends verification passing information to the cross-link gateway;

6. and notifying the acquisition of ownership of the preset chain identifier by the cross-chain gateway.

The registration stage comprises the following steps:

1. the blockchain or the user agent node sends attribute information containing a chain identifier to be registered to the cross-chain gateway;

2. the cross-link gateway stores the attribute information in a link and sends a registration request to the root relay link B1;

3. the root relay chain B1 carries out auditing on attribute information containing a chain identifier to be registered;

4. if the verification is passed, updating a chain identifier in a chain identifier table of the root relay chain B1;

5. the root relay chain B1 sends a synchronization instruction to the cross-chain gateway;

6. synchronizing the newly added chain identifier to a relay chain B2 of a sub-network to which the blockchain belongs by the cross-chain gateway;

7. the relay chain B2 updates the chain identification table.

The updating stage comprises the following steps:

1. the blockchain or the user agent node sends attribute information containing update information to the cross-chain gateway;

2. the cross-link gateway stores the attribute information under the link and sends an update request to the root relay link B1;

3. The root relay chain B1 carries out auditing on attribute information containing updated information;

5. the root relay chain B1 sends an update instruction to the cross-chain gateway;

6. the cross-chain gateway updates the chain information updated by the block chain to a relay chain B2 of the sub-network to which the block chain belongs;

7. the relay chain B2 updates the chain identification table.

As shown in fig. 5, an embodiment of the present application provides an interaction flow diagram of the parsing process, and the interaction process is the same as the implementation principle of the above embodiment, and is not described herein again. As shown in fig. 5, the implementation flow of the parsing process includes:

1. the block chain sends a chain identifier to be analyzed to a cross-chain gateway;

2. the cross-link gateway sends an analysis request to a relay link B3 in the cross-link network;

3. if the chain identifier table of the relay chain B3 contains the chain identifier to be analyzed and the received request access number is within a preset number range, the relay chain B3 analyzes the chain identifier to be analyzed to obtain an analysis result;

4. returning the analysis result of the relay chain B3 to the cross-chain gateway;

5. if the chain identifier to be resolved is not contained in the chain identifier table of the relay chain B3, the relay chain B3 sends the address of the upper relay chain B1 to a cross-chain gateway;

6. The cross-link gateway sends an analysis request to the upper relay link B1;

7. the upper relay chain B1 analyzes the chain identifier to be analyzed to obtain an analysis result;

8. returning the analysis result of the upper relay chain B1 to the cross-chain gateway;

9. if the chain identifier table of the relay chain B3 contains the chain identifier to be analyzed and the received request access number exceeds a preset number range, sending the address of the lower relay chain B4 to a cross-chain gateway;

for example, if the chain identifier to be resolved exists in the sub-network corresponding to B4, the relay chain B3 sends the address of the lower relay chain B4 to the inter-chain gateway, and if the chain identifier to be resolved exists in the relay chains of other sub-networks, the relay chain B3 sends the addresses of the relay chains of other sub-networks to the inter-chain gateway.

10. The cross-link gateway sends an analysis request to the lower relay link B4;

for example, if the chain identifier to be parsed exists in the sub-network corresponding to B4, the parsing request is sent to the lower-level relay chain B4 of the relay chain B3, and if the chain identifier to be parsed exists in the relay chains of other sub-networks, the parsing request is sent to the relay chains of the corresponding other sub-networks.

11. The lower relay chain B4 analyzes the chain identifier to be analyzed to obtain an analysis result;

12. Returning the analysis result of the lower relay chain B4 to the cross-chain gateway;

13. after receiving the analysis result, the cross-chain gateway stores the analysis result and sends the analysis result to the blockchain;

14. after receiving the chain identifier to be analyzed, the cross-chain gateway sends corresponding chain information to the blockchain if the chain identifier cache table of the cross-chain gateway contains the chain information of the chain identifier to be analyzed.

In the sub-inter-link network 1, any two inter-link gateways can directly communicate with each other.

It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic of each process, and should not limit the implementation process of the embodiment of the present application in any way.

By the embodiment of the invention, the chain identifier can support self definition (under the premise of acquiring the ownership of the identifier); the chain identifiers are unified and structured; the chain identification expandability can still keep the unique characteristic of the identity identification when a new chain joins the network; the whole identification system is based on each relay chain, so that the centralization risk (such as downtime risk) is greatly reduced; the network structure is flexible, and one cross-link gateway is a single node and is used for transmitting cross-link information between two connected links, so that the cross-link gateway can be flexibly deployed according to requirements; on one hand, the I/O operation of document storage is relatively time consuming, and the workload of user agents and blockchains can be saved after the task is handed to a cross-chain gateway.

In addition, the identity storage is transparent to the relay chain, so that heterogeneous multiple types of identity storage networks can be supported, such as decentralised storage (IPFS, bitXMesh, swarm and the like), a centralized server and cloud storage, and even the whole system is supported to simultaneously and compositely use multiple types of identity storage networks. If the identity storage network is upgraded or a new identity storage network is used, only the interface of the cross-chain gateway for accessing the identity storage network part needs to be upgraded without modifying the interface between the relay chain and the cross-chain gateway, so that no upgrading modification is needed to the blockchain. The caching mechanism of the cross-link gateway can accelerate the response of the request, the cross-link gateway caches the analyzed link identification table entry, and the workload during the request analysis can be reduced, so that the overall response speed of the system is improved.

Corresponding to the blockchain identification management method described in the above embodiments, fig. 6 shows a block diagram of a cross-chain gateway node provided in the embodiment of the present application, and for convenience of explanation, only a portion related to the embodiment of the present application is shown.

Referring to fig. 6, the cross-chain gateway node includes:

a receiving unit 61, configured to receive attribute information sent by a blockchain, where the attribute information includes identification information of the blockchain;

A forwarding unit 62, configured to send a transaction request to a relay chain in a cross-chain network, based on the attribute information, where the transaction request is used to instruct the relay chain to audit the attribute information;

and the processing unit 63 is configured to receive the instruction fed back by the relay chain and execute the operation requirement associated with the identification information if the audit is passed.

Fig. 7 shows a block diagram of a relay chain node provided in an embodiment of the present application, and for convenience of explanation, only a portion relevant to the embodiment of the present application is shown.

Referring to fig. 7, the relay link point includes:

a receiving unit 71, configured to receive a transaction request sent by a cross-chain gateway, where the transaction request is generated by the cross-chain gateway based on attribute information of a blockchain, and the attribute information includes identification information of the blockchain;

a management unit 72, configured to audit the attribute information according to the transaction request;

and the sending unit 73 is configured to feed back an instruction to the cross-link gateway if the audit passes, where the instruction is used to instruct the cross-link gateway to execute the operation requirement associated with the identification information.

According to the embodiment of the application, the terminal equipment of the cross-chain gateway node receives attribute information sent by a blockchain, wherein the attribute information comprises identification information of the blockchain; based on the attribute information, sending a transaction request to a relay chain in a cross-chain network, wherein the transaction request is used for indicating the relay chain to audit the attribute information; if the verification is passed, receiving an instruction fed back by the relay chain, and executing an operation requirement associated with the identification information; the management of the identity of the blockchain in the whole cross-chain network can be realized in the intercommunication scene of the large-scale blockchain, so that the identification information of the blockchain is based on the relay chain, and the centralization risk is reduced; has stronger usability and practicability.

It should be noted that, because the content of information interaction and execution process between the above devices/units is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein again.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.

Embodiments of the present application also provide a computer readable storage medium storing a computer program which, when executed by a processor, implements steps that may implement the various method embodiments described above.

Embodiments of the present application provide a computer program product which, when run on a mobile terminal, causes the mobile terminal to perform steps that may be performed in the various method embodiments described above.

Fig. 8 is a schematic structural diagram of a terminal device 8 according to an embodiment of the present application. As shown in fig. 8, the terminal device 8 of this embodiment includes: at least one processor 80 (only one shown in fig. 8), a memory 81, and a computer program 82 stored in the memory 81 and executable on the at least one processor 80, the processor 80 implementing the steps in any of the various certification method embodiments described above when executing the computer program 82.

The terminal device 8 may be a computing device such as a desktop computer, a notebook computer, a palm computer, a cloud server, etc. The terminal device 8 may include, but is not limited to, a processor 80, a memory 81. It will be appreciated by those skilled in the art that fig. 8 is merely an example of the terminal device 8 and is not limiting of the terminal device 8, and may include more or fewer components than shown, or may combine certain components, or different components, such as may also include input-output devices, network access devices, etc.

The processor 80 may be a central processing unit (Central Processing Unit, CPU), the processor 80 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 81 may in some embodiments be an internal storage unit of the terminal device 8, such as a hard disk or a memory of the terminal device 8. The memory 81 may in other embodiments also be an external storage device of the terminal device 8, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the terminal device 8. Further, the memory 81 may also include both an internal storage unit and an external storage device of the terminal device 8. The memory 81 is used for storing an operating system, application programs, boot loader (BootLoader), data, other programs etc., such as program codes of the computer program etc. The memory 81 may also be used to temporarily store data that has been output or is to be output.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application implements all or part of the flow of the method of the above embodiments, and may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing device/terminal apparatus, recording medium, computer Memory, read-Only Memory (ROM), random access Memory (RAM, random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other manners. For example, the apparatus/network device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims

1. A method for managing blockchain identification, applied to a cross-chain gateway, the method comprising:

receiving attribute information sent by a block chain, wherein the attribute information comprises identification information of the block chain;

Based on the attribute information, sending a transaction request to a relay chain in a cross-chain network, wherein the transaction request is used for indicating the relay chain to audit the attribute information;

if the verification is passed, receiving an instruction fed back by the relay chain, and executing an operation requirement associated with the identification information;

wherein the attribute information comprises a chain identifier to be resolved;

the receiving attribute information sent by the block chain includes: receiving a chain identifier to be analyzed sent by a block chain;

after receiving the parsed chain identifier sent by the blockchain, the method further includes:

based on the chain identifier to be resolved, sending a resolving request to a relay chain in the cross-chain network; if the chain identifier table of the relay chain does not comprise the chain identifier to be analyzed, receiving an address of an upper relay chain fed back by the relay chain; the analysis request is sent to the upper relay chain again according to the address of the upper relay chain; receiving an analysis result fed back by the upper relay chain; caching the analysis result to a chain identification cache table of the cross-chain gateway; and sending the analysis result to the block chain requesting analysis.

2. The method of claim 1, wherein the attribute information includes a chain identifier of the blockchain to be registered;

the sending the transaction request to the relay link in the cross-link network based on the attribute information comprises the following steps:

3. The method of claim 2, wherein the attribute information comprises a chain information document of the blockchain; the method further comprises the steps of:

4. The method of claim 1, wherein the attribute information includes update information;

5. The method of claim 1, wherein after the sending of the resolution request to a relay chain in the cross-chain network based on the chain identifier to be resolved, the method further comprises:

if the chain identifier table of the relay chain contains the chain identifier to be analyzed and the access request received by the relay chain reaches the preset number, receiving the address of the lower relay chain fed back by the relay chain;

the analysis request is sent to the lower relay chain again according to the address of the lower relay chain;

Receiving an analysis result fed back by the relay chain or an analysis result fed back by the lower relay chain; caching the analysis result to a chain identification cache table of the cross-chain gateway;

and sending the analysis result to the block chain requesting analysis.

6. The method of claim 1, wherein the method further comprises:

sending an application request of a preset chain identifier to a root relay chain in the cross-chain network, wherein the application request is used for indicating the root relay chain to audit the preset chain identifier;

and if the root relay chain passes the audit, receiving information of passing application fed back by the relay chain.

7. A method of managing blockchain identification, the method being applied to a relay chain, the method comprising:

receiving a transaction request sent by a cross-chain gateway, wherein the transaction request is generated by the cross-chain gateway based on attribute information of a blockchain, and the attribute information comprises identification information of the blockchain;

auditing the attribute information according to the transaction request;

if the auditing is passed, feeding back an instruction to the cross-link gateway, wherein the instruction is used for indicating the cross-link gateway to execute the operation requirement associated with the identification information;

Wherein the transaction request comprises an resolution request; the receiving a transaction request sent by a cross-chain gateway comprises the following steps:

receiving an analysis request sent by the cross-chain gateway, wherein the analysis request is generated by the cross-chain gateway based on a chain identifier to be analyzed sent by a blockchain;

after the receiving the parsing request sent by the cross-link gateway, the method further includes:

and if the chain identification table of the relay chain does not contain the chain identifier to be analyzed, sending an address of an upper relay chain to the cross-chain gateway, wherein the address of the upper relay chain is used for indicating the cross-chain gateway to send the analysis request to the upper relay chain.

8. The method of claim 7, wherein if the relay chain is a root relay chain in a cross-chain network, the receiving the transaction request sent by the cross-chain gateway, and auditing the attribute information according to the transaction request, comprises:

receiving a registration request sent by the cross-link gateway, wherein the registration request is generated by the cross-link gateway based on attribute information containing a chain identifier to be registered;

auditing attribute information containing the chain identifier to be registered;

if the verification is passed, updating a chain identification table and sending a synchronization instruction to the cross-chain gateway, wherein the synchronization instruction is used for indicating the cross-chain gateway to synchronize the chain identifier to a chain identification table of a relay chain of a sub-network to which the blockchain belongs; and/or;

receiving an update request sent by the cross-chain gateway, wherein the update request is generated by the cross-chain gateway based on the update information of the blockchain;

auditing the updated information;

9. The method of claim 7, wherein after the receiving the resolution request sent by the cross-chain gateway, the method further comprises:

if the chain identification table of the relay chain contains the chain identifier to be analyzed, analyzing the chain identifier to be analyzed to obtain an analysis result, and sending the analysis result to the cross-chain gateway;

And if the chain identification table of the relay chain comprises the chain identifiers to be analyzed and the access requests received by the relay chain reach the preset number, sending the address of a lower relay chain to the inter-chain gateway, wherein the address of the lower relay chain is used for indicating the inter-chain gateway to send the analysis request to the lower relay chain.

10. The method of claim 7, wherein if the relay chain is a root relay chain in a cross-chain network, the method further comprises:

receiving an application request of a preset chain identifier sent by the cross-chain gateway;

auditing the preset chain identifier;

if the verification is passed, the ownership of the preset chain identifier is recorded in a chain identifier table, and information of passing application is sent to the cross-chain gateway.

11. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1 to 6 or claims 7 to 10 when executing the computer program.

12. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the method of any one of claims 1 to 6 or claims 7 to 10.