CN112669038B

CN112669038B - Account inquiry system and cross-link gateway

Info

Publication number: CN112669038B
Application number: CN202011584892.6A
Authority: CN
Inventors: 李伟; 邱炜伟; 汪小益; 张帅; 匡立中; 楼嵩
Original assignee: Hangzhou Qulian Technology Co Ltd
Current assignee: Hangzhou Qulian Technology Co Ltd
Priority date: 2020-12-28
Filing date: 2020-12-28
Publication date: 2024-03-15
Anticipated expiration: 2040-12-28
Also published as: CN112669038A

Abstract

The application is applicable to the technical field of computers, and provides an account inquiry system, which comprises: the system comprises a first blockchain, a second blockchain, a first cross-chain gateway, a second cross-chain gateway and a relay chain, wherein the first blockchain is in communication connection with the relay chain through the first cross-chain gateway, and the second blockchain is in communication connection with the relay chain through the second cross-chain gateway. In the method, identity intercommunication among different blockchains is realized through the relay chain and the cross-chain gateway, and the method is beneficial to improving the safety of transaction among different blockchains.

Description

Account inquiry system and cross-link gateway

Technical Field

The application belongs to the technical field of computers, and particularly relates to an account query system and a cross-chain gateway.

Background

The blockchain is a distributed shared ledger and database, and has the characteristics of decentralization, non-tampering, whole trace, traceability, collective maintenance, disclosure transparency and the like. In the related art, a plurality of blockchains are usually provided, the identities on the chains of different blockchains are not communicated, and one blockchain cannot acquire the identity information of an account on the other blockchain, so that the identity authentication of the blockchains cannot be realized, and the safety of the transaction of the blockchains is problematic.

Accordingly, there is a need in the related art to enable on-chain identity interworking between different blockchains to improve the security of transactions across blockchains.

Disclosure of Invention

The embodiment of the application provides an account inquiry system and a cross-chain gateway, and aims to solve the problem that the identity on chains among different blockchains in the related technology is not always communicated, and one blockchain cannot acquire the identity information of an account on the other blockchain, so that the identity authentication of the cross-block chain cannot be realized, and the safety of the transaction of the cross-block chain is not high enough.

In a first aspect, an embodiment of the present application provides an account query system, including: the first blockchain is in communication connection with the relay chain through the first cross-chain gateway, the second blockchain is in communication connection with the relay chain through the second cross-chain gateway,

the first blockchain is used for sending a cross-chain account query request to the relay chain through the first cross-chain gateway, wherein the cross-chain account query request comprises an account identifier of an account to be checked on the second blockchain;

the relay chain is used for receiving a cross-chain account query request, and searching identity record information where the account identifier is located in a cross-chain identity record information table stored in advance in the relay chain, wherein the identity record information in the cross-chain identity record information table comprises the account identifier and a storage address for storing account identity description information of an account marked by the account identifier; responding to the found identity record information of the account identifier, and sending the found identity record information to a first blockchain through a first cross-chain gateway;

The first blockchain is also used for receiving the searched identity record information and sending the storage address in the searched identity record information to the first cross-chain gateway;

the first cross-link gateway is used for acquiring account identity description information of the account to be checked on the second blockchain according to the received storage address, and sending the acquired account identity description information to the first blockchain, so that the first blockchain performs identity authentication on the account to be checked on the second blockchain based on the acquired account identity description information.

In a second aspect, embodiments of the present application provide a cross-chain gateway, where the cross-chain gateway is communicatively connected to a first blockchain and a trunk chain, respectively, and the cross-chain gateway includes: an information transfer unit, and an information reading unit, wherein,

the information transfer unit is used for forwarding a cross-chain account query request of the first blockchain to the relay chain, wherein the cross-chain account query request comprises an account identifier of an account to be checked on the second blockchain; forwarding identity record information searched by a relay chain aiming at a cross-chain account query request to a first blockchain, wherein the identity record information comprises an account identifier and a storage address for storing account identity description information of an account marked by the account identifier;

The information reading unit is used for receiving the storage address in the searched identity record information sent by the first block chain; according to the received storage address, acquiring account identity description information of the account to be checked on the second blockchain, and sending the acquired account identity description information to the first blockchain, so that the first blockchain performs identity authentication on the account to be checked on the second blockchain based on the acquired account identity description information.

Compared with the related art, the embodiment of the application has the beneficial effects that: the identity intercommunication between different blockchains is realized through the relay chain and the cross-chain gateway, so that the safety of transaction between different blockchains is improved. Secondly, by looking up a table, the account identity description information corresponding to the account identifier of the account to be checked is looked up from the cross-chain identity record information table, so that the method is technically easy to realize and is beneficial to improving the account query efficiency. Then, the storage address of the account identity description information is stored in the cross-link identity record information table of the relay link, instead of storing the account identity description information, so that the storage space of the relay link can be saved, and the cross-link identity record information table can be simplified. And then, the account identity description information of the accounts on each blockchain is only required to be stored once, and each blockchain can access the account identity description information of the accounts on all blockchains in a storage address access mode, so that the storage space of the whole blockchain network is saved. In addition, because the stored account identity description information needs to consume more time, the stored account identity description information is read by the cross-chain gateway, so that the workload of the blockchain can be reduced, and the data processing efficiency of the whole blockchain network can be improved.

It will be appreciated that the advantages of the second aspect may be found in the relevant description of the first aspect, and will not be described in detail herein.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following description will briefly introduce the drawings that are needed in the embodiments or the related technical descriptions, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person of ordinary skill in the art.

FIG. 1 is a system architecture diagram of an account query system provided in an embodiment of the present application;

FIG. 2 is a schematic diagram of an account query system according to an embodiment of the present application;

FIG. 3 is a flow chart of the construction steps provided in an embodiment of the present application;

FIG. 4 is a schematic diagram of an identity registration process according to an embodiment of the present application;

FIG. 5 is a schematic diagram of an identity verification process according to an embodiment of the present application;

FIG. 6 is a schematic diagram of an account query system according to another embodiment of the present application;

FIG. 7 is a flow chart of an account query method according to an embodiment of the present application;

FIG. 8 is a flow chart of an account query method according to an embodiment of the present application;

fig. 9 is a block diagram of a cross-link gateway according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.

Example 1

Referring to fig. 1, a system architecture diagram of an account query system according to an embodiment of the present application is provided.

As shown in fig. 1, the system architecture may include blockchains C1, C2, C3, C4, relay chains B1, B2, B3, B4, and cross-chain gateways P1-P7. Where the relay chain is typically a special blockchain used to authenticate and transmit information to the connected blockchain. In practice, for the purpose of distinguishing descriptions, blockchains other than relay chains may be referred to as application chains. In addition, unless specifically stated otherwise, the blockchains referred to herein (e.g., first blockchain, second blockchain) are application chains.

The connection relationship between the blockchains C1, C2, C3, C4 and the relay chains B1, B2, B3, B4 is generally in a tree structure, and the relay chain B2 and the relay chain B3 are leaf nodes of the relay chain B1. Blockchain C1 and blockchain C2 are leaf nodes of the relay chain B2. Blockchain C3 and relay chain B4 are leaf nodes of relay chain B3. Blockchain C4 is a leaf node of the relay chain B4. The relay chain B1 is an upper relay chain of the relay chains B2 and B3, and the relay chain B3 is an upper relay chain of the relay chain B4. In practical applications, the blockchains C1, C2, C3, and C4 may be application chains of different application scenarios.

For all relay chains in the tree structure, identity intercommunication among a plurality of leaf nodes of one relay chain, such as identity intercommunication among a blockchain C1 and a blockchain C2, can be realized. The identity intercommunication between the leaf nodes of different relay chains can also be realized, for example, the identity intercommunication between the blockchain C1 and the blockchain C3. Interworking between relay links, such as relay link B2 and relay link B3, relay link B1 and relay link B2, may also be achieved. Interworking between leaf nodes and relay chain nodes, such as blockchain C1 and relay chain B2, blockchain C1 and relay chain B3, blockchain C1 and relay chain B1, and the like, may also be achieved.

In practical applications, for convenience of description, a plurality of blockchains with tree-like connection relationships are generally distinguished by adopting a plurality of relationship words. For example, the relative relationships between the blockchains may be distinguished using words such as ancestors, paralogues, siblings, descendants, ancestors, and the like. Generally, chains at the same level are siblings, higher-level being ancestors and lower-level being offspring. For example, for blockchain C1, B2, B1 are their ancestor. While for relay chain B2, blockchain C1 is its ancestor and relay chain B1 is its ancestor. In addition, for blockchain C1, the chains other than B2, B1 are both its side chains.

In practice, interaction between the two chains may be achieved through a cross-chain gateway. As shown in fig. 1, the interaction between the chain B1 and the chain B2 may be implemented through the cross-chain gateway P1, the interaction between the chain B1 and the chain B3 may be implemented through the cross-chain gateway P2, the interaction between the chain B2 and the chain C1 may be implemented through the cross-chain gateway P3, the interaction between the chain B2 and the chain C2 may be implemented through the cross-chain gateway P4, the interaction between the chain B3 and the chain C3 may be implemented through the cross-chain gateway P5, the interaction between the chain B3 and the chain B4 may be implemented through the cross-chain gateway P6, and the interaction between the chain B4 and the chain C3 may be implemented through the cross-chain gateway P7.

In practice, if a relay chain has at least two leaf nodes, each leaf node is a blockchain. For ease of description, one of the blockchains may be referred to as a first blockchain and the other blockchain may be referred to as a second blockchain. The first blockchain is communicatively coupled to the relay chain through a first cross-chain gateway and the second blockchain is communicatively coupled to the relay chain through a second cross-chain gateway. At this time, the liquid crystal display device,

the first blockchain may be configured to send a cross-chain account query request to the relay chain through the first cross-chain gateway, wherein the cross-chain account query request includes an account identification of an account to be checked on the second blockchain.

The relay chain can be used for receiving a cross-chain account query request, and searching identity record information of an account identifier from a cross-chain identity record information table stored in advance in the relay chain, wherein the identity record information in the cross-chain identity record information table comprises the account identifier and a storage address for storing account identity description information of an account marked by the account identifier; and in response to the found identity record information of the account identifier, sending the found identity record information to the first blockchain through the first cross-chain gateway.

The first blockchain can also be used for receiving the searched identity record information and sending the storage address in the searched identity record information to the first cross-chain gateway.

The first cross-link gateway can be used for acquiring account identity description information of an account to be checked on the second blockchain according to the received storage address, and sending the acquired account identity description information to the first blockchain, so that the first blockchain can confirm identity authentication of the account to be checked on the second blockchain based on the acquired account identity description information.

In the method, identity intercommunication among different blockchains is realized through the relay chain and the cross-chain gateway, and the method is beneficial to improving the safety of transaction among different blockchains. Secondly, by looking up a table, the account identity description information corresponding to the account identifier of the account to be checked is looked up from the cross-chain identity record information table, so that the method is technically easy to realize and is beneficial to improving the account query efficiency. Then, the storage address of the account identity description information is stored in the cross-link identity record information table of the relay link, instead of storing the account identity description information, so that the storage space of the relay link can be saved, and the cross-link identity record information table can be simplified. And then, the account identity description information of the accounts on each blockchain is only required to be stored once, and each blockchain can access the account identity description information of the accounts on all blockchains in a storage address access mode, so that the storage space of the whole blockchain network is saved. In addition, because the stored account identity description information needs to consume more time, the stored account identity description information is read by the cross-chain gateway, so that the workload of the blockchain can be reduced, and the data processing efficiency of the whole blockchain network can be improved.

Example two

With continued reference to fig. 2, a schematic structural diagram of an account query system according to an embodiment of the present application is provided. The account query system shown in FIG. 3 includes a first blockchain 201, a second blockchain 202, a first cross-chain gateway 203, a second cross-chain gateway 204, and a relay chain 205, the first blockchain 201 being communicatively coupled to the relay chain 205 through the first cross-chain gateway 203, the second blockchain 202 being communicatively coupled to the relay chain 205 through the second cross-chain gateway 204. Wherein,

the first blockchain 201 is configured to send a cross-chain account query request to the relay chain through the first cross-chain gateway.

The cross-chain account query request comprises account identification of an account to be checked on the second blockchain. The account to be checked is usually an account to be queried.

In practice, there are typically a large number of blockchain accounts on each blockchain, with each blockchain account having a blockchain account address corresponding thereto. For ease of description, the blockchain account may be referred to herein simply as an account.

Wherein the account identification is generally information for identifying an account. In practice, account identification may generally indicate the account and the blockchain in which the account is located. For example, the account identification may be: 001:0x1234567, where 001 may be the identity of a blockchain, 0x1234567 is the encoding of an account on the blockchain identified as 001.

In this embodiment, the first blockchain 201 may send a cross-chain account query request to the relay chain 205 through the first cross-chain gateway 203.

And the relay chain 205 is configured to receive a cross-chain account query request, and search identity record information where the account identifier is located from a cross-chain identity record information table stored in advance in the relay chain. And in response to the found identity record information of the account identifier, sending the found identity record information to the first blockchain through the first cross-chain gateway.

The identity record information in the cross-chain identity record information table comprises an account identifier and a storage address for storing account identity description information of an account marked by the account identifier.

The account identity description information is generally information for describing an account identity. As an example, the account identity description information may include, but is not limited to: account address, account public key, account encryption algorithm, account registration time, etc. Account addresses are typically referred to as addresses of blockchain accounts. The account public key generally refers to the public key employed by the blockchain account. Account encryption algorithms generally refer to encryption algorithms employed by blockchain accounts. In the application, the specific format of the account identity description information may be an object numbered format (JavaScript Object Notation, JSON), an extensible markup language format (eXtensible Markup Language, XML), or another markup language format (Yet Another Markup Language, YAML). The specific format of the account identity description information is not limited in the application.

In practice, a local chain identity record information table for recording information about accounts on the local chain may be pre-stored on each blockchain. The identity record information table of the present chain stored in each block chain is provided with a plurality of pieces of identity record information. In the blockchain of the relay chain type, a cross-chain identity record information table is also stored, and the stored cross-chain identity record information table is provided with identity record information corresponding to an account on a leaf node blockchain of the relay chain. In the upper relay chain of any relay chain, the cross-chain identity record information table stored in the relay chain can be backed up. In this way, identity interworking between blockchains can be achieved. For example, in connection with fig. 1, the relay chain B1 may have both a cross-chain identity record information table stored in the relay chain B2, a cross-chain identity record information table stored in the relay chain B3, and a cross-chain identity record information table stored in the relay chain B4. For further example, if blockchain C1 sends a request to relay chain B2 to query an account on blockchain C3, the cross-chain identity record information table in relay chain B2 typically does not have identity record information corresponding to the account on blockchain C3. At this time, the relay chain B2 may send a continuous query request to the relay chain B1 at the previous stage, so that the identity record information corresponding to the account on the blockchain C3 is queried through the relay chain B1.

In this embodiment, the relay chain 205 may receive a cross-chain account query request. Then, the account identifier of the account to be checked is adopted, and the identity record information where the account identifier is located is searched from a pre-stored cross-link identity record information table in the relay link 205. The found identity record information is then sent to the first cross-chain gateway 203, such that the first cross-chain gateway 203 forwards the found identity record information to the first blockchain 201.

The first blockchain 201 is further configured to receive the found identity record information, and send a storage address in the found identity record information to the first cross-chain gateway.

In this embodiment, first blockchain 201 may receive identity record information forwarded by first cross-chain gateway 203. The storage address in the identity record information is then sent to the first cross-chain gateway 203.

The first cross-link gateway 203 is configured to obtain, according to the received storage address, account identity description information of an account to be checked on the second blockchain, and send the obtained account identity description information to the first blockchain, so that the first blockchain performs identity authentication on the account to be checked on the second blockchain based on the obtained account identity description information.

In this embodiment, the first cross-chain gateway 203 may employ the received storage address to obtain account identity description information from the location indicated by the storage address. Since the storage address is the description information of the address for storing the account identity description information of the account to be checked on the second blockchain. Therefore, at this time, the first cross-link gateway 203 may obtain the account identity description information of the account to be checked on the second blockchain. Thereafter, first cross-chain gateway 203 may send the obtained account identity description information to first blockchain 201. In this way, the first blockchain 201 may receive the account identity description information, thereby authenticating the account to be checked on the second blockchain.

The system provided by the embodiment can realize the identity intercommunication between different blockchains through the relay chain and the cross-chain gateway, and is beneficial to improving the security of transaction between different blockchains. Secondly, by looking up a table, the account identity description information corresponding to the account identifier of the account to be checked is looked up from the cross-chain identity record information table, so that the method is technically easy to realize and is beneficial to improving the account query efficiency. Then, the storage address of the account identity description information is stored in the cross-link identity record information table of the relay link, instead of storing the account identity description information, so that the storage space of the relay link can be saved, and the cross-link identity record information table can be simplified. And then, the account identity description information of the accounts on each blockchain is only required to be stored once, and each blockchain can access the account identity description information of the accounts on all blockchains in a storage address access mode, so that the storage space of the whole blockchain network is saved. In addition, because the stored account identity description information needs to consume more time, the stored account identity description information is read by the cross-chain gateway, so that the workload of the blockchain can be reduced, and the data processing efficiency of the whole blockchain network can be improved.

In some optional implementations of this embodiment, in the account query system described above, the relay chain is further configured to: and sending a continuous query request comprising the account identifier to an upper relay chain of the communication connection in response to the fact that the identity record information of the account identifier is not found. And receiving the identity record information of the account identifier returned by the upper relay chain aiming at the continuous query request, and sending the received identity record information to the first blockchain through the first cross-chain gateway.

Wherein the continue query request may include an account identification of the account under investigation on the second blockchain.

Here, if the executing body does not find the identity record information of the account identifier, the executing body may send a continuous query request to the upper relay chain when the executing body has the upper relay chain. Thus, upon receipt of a continue query request, the upper relay chain may typically employ account identification in the continue query request to continue the query from one or more cross-chain identity record information tables stored by the upper relay chain. If the identity record information of the account identifier is found, the found identity record information is sent to a relay chain. Thus, the relay chain can receive the identity record information of the account identifier returned by the upper relay chain and send the received identity record information of the account identifier to the first blockchain.

In the implementation manner, the continuous query request is sent to the upper relay chain, so that the account identification of the account to be checked is continuously queried through the upper relay chain, and the identity intercommunication among the leaf nodes of different relay chains can be realized. The method is beneficial to further improving the security of transactions between different blockchains.

In some optional implementations of the present embodiment, in the first blockchain, sending, by the first cross-chain gateway, a cross-chain account query request to the relay chain includes: and responding to the received cross-link account query request sent by the user terminal where the local link account is located, and sending the cross-link account query request to the relay link through the first cross-link gateway.

The cross-chain account query request comprises account identification of an account to be checked on the second blockchain.

The present chain account herein generally refers to an account on the first blockchain. A user may log into an account on the blockchain through a user terminal.

Here, the first blockchain may receive a cross-chain account query request sent by a user terminal where the local chain account is located. And then, the received cross-link account query request is sent to the relay link through the cross-link gateway. Thus, when the relay chain returns the identity record information of the account identifier, the first blockchain can feed back the corresponding account identity description information to the user terminal based on the identity record information.

In some alternative implementations of this embodiment, in the account query system described above,

the first blockchain can also be used for responding to a local chain account query request which is sent by a user terminal where the local chain account is located and used for querying an account to be queried on the first blockchain, searching identity record information where an account identifier of the account to be queried is located from a local chain identity record information table stored in the first blockchain in advance, and sending a storage address in the searched identity record information to the first cross-chain gateway.

The chain account inquiry request comprises an account identifier of an account to be checked, and the identity record information in the chain identity record information table comprises the account identifier and a storage address for storing account identity description information of the account marked by the account identifier.

Here, the account under investigation is an account on the first blockchain. The first blockchain can receive a local chain account query request sent by a user terminal where the local chain account is located. The local chain account query request is used for querying account identity description information of an account on a first blockchain. After receiving the local chain account query request, the first blockchain can use the account identifier included in the local chain account query request to search the identity record information of the account identifier from a local chain identity record information table stored in the first blockchain in advance. And then, the storage address in the searched identity record information is sent to the first cross-link gateway.

The first cross-link gateway is further configured to obtain account identity description information of an account to be checked on the first blockchain according to the received storage address, and send the obtained account identity description information to the first blockchain.

Here, the first cross-chain gateway may receive the memory address sent by the first blockchain. After receiving the storage address, the first cross-link gateway can directly read the account identity description information from the position indicated by the storage address. Because the storage address is descriptive information of an address for storing account identity descriptive information of the account under investigation on the first blockchain. Therefore, at this time, the first cross-link gateway can acquire account identity description information of the account to be checked on the first blockchain. The obtained account identity description information is then sent to the first blockchain.

The first blockchain is further used for receiving account identity description information of the account to be checked on the first blockchain returned by the first cross-chain gateway and sending the received account identity description information to the user terminal.

Here, the first blockchain may receive account identity description information of the account to be checked on the first blockchain returned by the first cross-chain gateway, and may send the account identity description information to the user terminal.

In this implementation manner, the blockchain is stored with the local chain identity record information table, so that when the user terminal where one account on the blockchain is located needs to query the related information of another account on the blockchain, the blockchain can send the account identity description information of the other account to the user terminal. Which helps to increase the speed of data processing and thus the speed of transactions between the same blockchains. In addition, not all the inquiry requests are realized through the relay chain, so that the processing resources of the relay chain can be saved.

the relay chain is also used for responding to a local chain account query request which is sent by the first blockchain through the first cross-chain gateway and used for querying an account to be queried on the relay chain, and searching identity record information of an account identifier of the account to be queried on the relay chain from a local chain identity record information table stored in advance in the relay chain; and responding to the found identity record information of the account identifier of the account to be found on the relay chain, and sending the found identity record information to the first blockchain through the first cross-chain gateway.

Here, the account to be checked is an account on the relay chain. The relay chain may receive a local chain account query request sent by the first blockchain through the first cross-chain gateway. The local chain account query request is used for querying account identity description information of an account on the relay chain. After receiving the local link account query request, the relay link can use the account identifier included in the local link account query request to search the identity record information where the account identifier is located from the local link identity record information table stored in advance in the relay link. And then, forwarding the searched identity record information to the first blockchain through the first cross-chain gateway.

The first blockchain is also used for receiving the searched identity record information and sending the storage address in the searched identity record information to the first cross-chain gateway.

Here, the first blockchain may receive the identity record information forwarded by the first cross-chain gateway, and send the storage address in the identity record information to the first cross-chain gateway.

The first cross-link gateway is used for acquiring account identity description information of an account to be checked on the relay link according to the received storage address, and sending the acquired account identity description information to the first blockchain, so that the first blockchain performs identity authentication on the account to be checked on the relay link based on the acquired account identity description information.

Here, the first cross-chain gateway may employ the received storage address to obtain account identity description information from the location indicated by the storage address. Since the storage address is the description information of the address for storing the account identity description information of the account to be checked on the relay chain. Therefore, at this time, the first cross-link gateway can acquire account identity description information of the account to be checked on the relay link. The first cross-chain gateway may then send the obtained account identity description information to the first blockchain. Thus, the first blockchain can receive the account identity description information, so that identity authentication is performed on the accounts to be checked on the relay chain.

According to the implementation mode, the account on the relay chain can be queried, so that identity authentication can be performed on the account to be checked on the relay chain.

In some optional implementations of this embodiment, the system further includes at least one storage server, and the first blockchain is configured to pre-store the local chain identity record information table by performing the constructing step.

Fig. 3 is a schematic flow chart of a construction step provided in an embodiment of the present application. As shown in FIG. 3, the build step may include steps 301-303. It should be noted that the execution subject of steps 301-303 is the first blockchain.

Step 301, in response to receiving an identity registration request including an account identifier and account identity description information of a local chain account sent by a user terminal where the local chain account is located, sending a data storage type of a first blockchain and the account identity description information of the local chain account to a first cross-chain gateway, so that the first cross-chain gateway stores the account identity description information of the local chain account to a storage server matched with the data storage type.

The above-mentioned identity registration request is typically information for requesting registration. The storage server may be a preset server for storing data. There may be one or more storage servers. If there is one storage server, the storage server can support multiple data storage types at the same time. If there are multiple storage servers, the multiple storage servers may each support a data storage type. The data storage type generally refers to a type of storing data. By way of example, the data storage types described above may include, but are not limited to, support structured query language (Structured Query Language, SQL), interplanetary file system (Inter Planetary File System, IPFS), remote dictionary service (REmote DIctionary Server, redis), and the like.

Here, when the first blockchain receives the identity registration request, the first blockchain may send the data storage type adopted by the first blockchain and the account identity description information of the local chain account to the first cross-chain gateway together. In this way, the first cross-chain gateway may store the account identity description information in a storage server corresponding to the data storage type.

Step 302, receiving a storage address returned by the first cross-link gateway for the account identity description information of the local link account.

Here, after the first cross-link gateway stores the account identity description information of the local link account in the storage server, the storage address is generally returned to the first blockchain. Thus, the first blockchain may receive the memory address.

And 303, storing the account identifier and the storage address of the chain account, the hash value of the account identity description information of the chain account and the whole account state parameter with the value of the first preset value into the chain identity record information table as identity record information.

The first preset value is used for indicating that the chain account is currently in a registered pending state.

Here, the first blockchain may store the account identifier, the storage address, the hash value of the account identity description information, and the account status parameter as one piece of identity record information in the local chain identity record information table.

Fig. 4 is a schematic diagram of an identity registration procedure according to an embodiment of the present application.

Step 401, a user terminal where an account is located sends an identity registration request to an application chain, wherein the identity registration request comprises an account identifier and account identity description information.

Here, the application chain may be the first blockchain, the second blockchain, or another blockchain.

In step 402, the application chain sends the data storage type and account identity description information of the application chain to the cross-chain gateway.

Step 403, the cross-chain gateway stores the account identity description information to a storage server matched with the data storage type.

Step 404, the storage server stores the account identity description information and returns the storage address to the cross-chain gateway.

Step 405, the cross-chain gateway returns the storage address of the account identity description information to the application chain.

In step 406, the application chain stores the account identifier, the storage address and the hash value of the account identity description information as an identity record information in the chain identity record information table.

In practice, each piece of identity record information in the chain identity record information table may also have an account status parameter for indicating the status of the account. Different values of the account status parameter may indicate different account status. When the account is registered for identity, the value of the account state parameter may be a first preset value, which is used to indicate that the account state is a registered to-be-checked state.

In some optional implementations of this embodiment, the foregoing constructing step may further include: and executing preset auditing operation on the identity record information with the value of the corresponding account state parameter in the identity record information table of the chain as a first preset value to obtain auditing result information, and modifying the value of the account state parameter in the corresponding identity record information into a second preset value when the auditing result information indicates that auditing is passed.

The second preset value is used for indicating that the account is currently in an audit passing state.

The preset auditing operation may be an operation of auditing the account identity description information. For example, the preset auditing operation may be: the blockchain controls all or part of the blockchain link points of the blockchain to perform the following steps: and downloading the account identity description information by adopting a storage address in the identity record information. Then, a hash value of the downloaded identity description information is calculated. And finally, comparing the calculated hash value with the hash value in the identity record information, and if the calculated hash value is the same as the hash value in the identity record information, returning audit passing indication information for indicating that the audit passes to the block chain. Otherwise, if the two types of information are different, audit non-passing indication information for indicating that the audit is not passed is returned to the blockchain. In this way, the blockchain can determine whether the account identity description information of the account passes the audit by counting the number of audit passing indication information. In practice, if the auditing result is that the auditing is passed, the blockchain can modify the value of the account state parameter in the corresponding identity record information into a second preset value. The second preset value is used for indicating that the account is currently in an audit passing state. If the auditing result is that the auditing is not passed, the blockchain can modify the value of the account state parameter in the corresponding identity record information into a fifth preset value. The fifth preset value is used for indicating that the account is currently in an audit reject state.

In the above implementation, after modifying the value of the account status parameter in the corresponding identity record information, the first blockchain is further configured to: and responding to the value of the account state parameter in the modified corresponding identity record information as a second preset value, and sending the modified corresponding identity record information to the relay chain, so that the relay chain updates the cross-chain identity record information table based on the modified corresponding identity record information.

Here, if the account status is the audit passing status, the identity record information is considered valid. At this point, the blockchain may send the identity record information to the relay chain. In this way, the relay chain can update the cross-chain identity record information table by using the identity record information. Specifically, the relay chain may add the identity record information to a cross-chain identity record information table.

Fig. 5 is a schematic diagram of an identity verification process provided in an embodiment of the present application.

The application chain performs an audit on the identity record information of the account, and when the audit is not passed, steps 501-504 are executed. Upon passing the audit, steps 505-509 are performed.

In step 501, the application chain sends the storage address of the account identity description information in the identity record information to be audited to the cross-chain gateway.

Step 502, the cross-link gateway sends the storage address to the storage server, so that the storage server deletes the account identity description information corresponding to the storage address.

In step 503, the storage server returns information for prompting deletion completion through the cross-link gateway.

In step 504, the application chain modifies the value of the account status parameter in the checked identity record information to a fifth preset value, and deletes the storage address in the identity record information. The fifth preset value is used for indicating that the account is currently in an audit reject state.

In step 505, the application chain updates the present chain identity record information table.

Here, the value of the account status parameter of the identity record information passing the audit in the identity record information of the present chain may be modified to a second preset value. The second preset value is used for indicating that the account is currently in an audit passing state.

In step 506, the application chain sends the identity record information passing the audit to the cross-chain gateway.

And step 507, the cross-link gateway sends the identity record information passing the verification to the relay link.

Step 508, the relay chain updates the cross-chain identity record information table.

Here, the relay chain may add the identity record information that passes the audit to the cross-chain identity record information table.

In step 509, the relay chain transmits the identity record information passing the audit to the upper relay chain of the relay chain. In this way, the upper relay chain of the relay chain can add the identity record information passing the audit to the corresponding cross-chain identity record information table.

In some optional implementations of this embodiment, the above-mentioned constructing step may further include the following steps one to three. It should be noted that, the execution subject of the first to third steps is the first blockchain.

Step one, in response to receiving an identity update request which is sent by a user terminal where a local chain account is located and comprises an account identifier of the local chain account and new account identity description information, a data storage type of a first blockchain and the new account identity description information of the local chain account are sent to a first cross-chain gateway, so that the first cross-chain gateway stores the new account identity description information of the local chain account to a storage server matched with the data storage type.

Here, the identity update request may be information for requesting updating of account identity description information of an account. After receiving the identity update request, the first blockchain may send the new account identity description information in the identity update request and the data storage type of the first blockchain to the first cross-chain gateway. In this way, the first cross-chain gateway may store the new account identity description information to a storage server that matches the data storage type.

And step two, receiving a new storage address returned by the first cross-link gateway aiming at the new account identity description information of the local link account.

Here, after storing the new account identity description information of the present chain account in the storage server, the first cross-chain gateway generally returns a storage address for storing the new account identity description information, which is referred to herein as a new storage address.

Step three, the storage address in the identity record information corresponding to the chain account is modified to be a new storage address, the hash value of the account identity description information is modified to be the hash value of the new account identity description information, and the value of the account state parameter is modified to be a third preset value.

The third preset value is used for indicating that the chain account is currently in an update pending state.

Here, after receiving the new storage address, the first blockchain may modify the storage address in the identity record information of the account to the new storage address, modify the hash value of the account identity description information to the hash value of the new account identity description information, and modify the value of the account status parameter to the third preset value.

It should be noted that the blockchain may audit the updated identity record information. Here, the operation of auditing the updated identity record information is substantially the same as the operation of auditing the identity record information described above, and will not be described here. In practice, when checking the new identity record information with the value of the account state parameter being the third preset value, if the checking is not passed, the blockchain can delete the new storage address, and the new account identity description information stored by the new storage address is deleted by the cross-chain gateway by sending the new storage address to the cross-chain gateway. After deleting the new storage address, the blockchain may modify the identity record information where the new storage address is located to be the same as before the update.

Example III

With continued reference to fig. 6, a schematic structural diagram of an account query system according to an embodiment of the present application is provided. The account query system as shown in FIG. 6 includes a first blockchain 601, a second blockchain 602, a first cross-chain gateway 603, a second cross-chain gateway 604, and a relay chain 605, the first blockchain 601 being communicatively coupled to the relay chain 605 through the first cross-chain gateway 603, the second blockchain 602 being communicatively coupled to the relay chain 605 through the second cross-chain gateway 604.

In addition, the system may further include a third blockchain 606, where the third blockchain 606 may be an application chain or a relay chain. The system comprises any one or more blockchains, wherein a local chain identity record information table is prestored in the blockchain, and the identity record information in the local chain identity record information table comprises an account identifier, a storage address for storing account identity description information of an account marked by the account identifier, and account state parameters for indicating the account state of the account marked by the account identifier. At this time, the liquid crystal display device,

a third blockchain 606 may be used to send a cross-chain account freeze request to the receive chain.

The cross-chain account freezing request comprises an account identifier of an account to be frozen and a chain identifier of a chain to be frozen. The receive chain may include any one or more of the following: first blockchain 601, second blockchain 602, and relay chain 605. Cross-chain account freeze requests are typically used to request that accounts on blockchains other than the subject blockchain be frozen. The chain to be frozen is typically a blockchain that needs to perform operations related to account freezing. Chain identification is typically information used to identify blockchains. As an example, the chain identity may be 001.

Here, the third blockchain 606 may be a blockchain having any relationship with the first blockchain 601, the second blockchain 602, and the relay chain 605 in the system. For example, the third blockchain 606 may be an ancestor chain, a paralogue chain, or the like of the relay chain 605.

In this embodiment, the third blockchain 606 may send a cross-chain account freeze request to any one or more of the first blockchain 601, the second blockchain 602, and the relay chain 605.

The receiving chain is used for receiving a cross-chain account freezing request sent by the third blockchain; and modifying the value of the account state parameter corresponding to the account identifier of the account to be frozen into a fourth preset value in the blockchain indicated by the chain identifier of the chain to be frozen.

The fourth preset value is used for indicating that the account to be frozen is currently in a frozen state.

According to the system provided by the embodiment, the third blockchain can send the cross-chain account freezing request to the receiving chain, so that the cross-blockchain account freezing is realized. The method and the device are beneficial to timely initiating a freezing request aiming at an account when the account with malicious operation on a certain blockchain is found, so that the account is frozen timely, and the safety of other blockchains which can be communicated with the blockchain identity where the account is located is guaranteed.

In some optional implementations of this embodiment, modifying, in the blockchain indicated by the chain identifier of the chain to be frozen, the value of the account status parameter corresponding to the account identifier of the account to be frozen to the fourth preset value may include:

the receiving chain responds to the fact that the chain identification indicates that the receiving chain is a chain to be frozen and the blockchain where the account to be frozen is located is the receiving chain, and identity record information where the account identification of the account to be frozen is located is searched from a chain identity record information table stored in the receiving chain in advance; and modifying the value of the account state parameter in the searched identity record information into a fourth preset value.

At this time, the chain to be frozen is the receiving chain. The implementation can freeze the account on the receiving chain, so that the account is frozen in a cross-blockchain manner.

and the receiving chain sends the cross-chain account freezing request to the direct-line sub-chain in response to determining that the chain identification indicates that the receiving chain is a non-freezing chain and that the blockchain where the account to be frozen is located is the direct-line sub-chain of the receiving chain.

The direct-connection sub-chain searches identity record information of an account identifier of an account to be frozen from a local chain identity record information table stored in the direct-connection sub-chain in advance; and modifying the value of the account state parameter in the searched identity record information into a fourth preset value.

At this time, the receiving chain is not the chain to be frozen, and the chain to be frozen is an orthonormal child of the receiving chain. The implementation can freeze the account on the direct link sub-chain of the receiving chain.

the receiving chain responds to the fact that the chain identification indicates that the receiving chain is a to-be-frozen chain and the blockchain where the account to be frozen is located is a direct-series subchain of the receiving chain, identity record information where the account identification of the account to be frozen is located is searched from a cross-chain identity record information table stored in the receiving chain in advance, and the value of the account state parameter in the searched identity record information is modified to be a fourth preset value; a cross-chain account freeze request is sent to the direct child chain.

Here, the chain to be frozen is the receive chain and the direct-chain of the receive chain. At this point, there are two numbers of chain identifications in the cross-chain account freeze request. In practice, there may be multiple numbers of chain identifications in a cross-chain account freeze request. The implementation method can freeze the account to be frozen in the range of the receiving chain and the direct-system subchain of the receiving chain.

and the receiving chain responds to the fact that the chain identification indicates that the receiving chain is not a chain to be frozen and the blockchain where the account to be frozen is located is a side chain of the receiving chain, identity record information corresponding to the account to be frozen is generated, and the generated identity record information is added into a cross-chain identity record information table of the receiving chain.

The value of the account state parameter in the generated identity record information is a fourth preset value.

Here, since there is typically no identity record information for the account in the synchronized side chain in the receive chain. In order to freeze the account to be frozen, the receiving chain can generate identity record information aiming at the identity identification of the account to be frozen, so that the account to be frozen is frozen in the range of the receiving chain. Here, the generated identity record information may include an account identifier and an account status parameter having a value of a fourth preset value. In practice, when the format of the identity record information needs to include the account identifier, the storage address of the account identity description information, the hash value of the account identity description information and the account status parameter, in the generated identity record information, the storage address is usually null, and the hash value is usually null.

According to the implementation mode, the account on the side chain of the receiving chain can be frozen in the range of the receiving chain, and the account can be frozen in a cross-blockchain manner.

It should be noted that controlling the freezing range of an account to be frozen helps to better ensure the security of other blockchains that can be interworked with the blockchain identity in which the account is located.

In addition, the manner in which an account is defrosted is generally similar to the manner in which the account is frozen. Therefore, the present application does not make any further statement as to how to defrost the account.

the first cross-link gateway is further used for caching the searched identity record information returned by the relay link aiming at the cross-link account query request; and responding to the received request of secondarily sending the cross-chain account inquiry by the first blockchain, acquiring account identity description information of the account to be checked on the second blockchain according to the storage address included in the cached identity record information, and sending the acquired account identity description information to the first blockchain.

The first cross-link gateway is further configured to cache identity record information with an account status parameter value of a to-be-frozen account as a fourth preset value when the blockchain connected in communication modifies the account status parameter value of the identity record information with the account identifier of the to-be-frozen account as the fourth preset value.

In this implementation, when the relay chain returns the searched identity record information for the first blockchain, the first cross-chain gateway may cache the returned identity record information. Therefore, when the first blockchain queries the same account again next time, the cached identity record information can be directly sent to the first blockchain, so that the query efficiency is improved.

In addition, after the first blockchain freezes a certain account on the first blockchain, the first cross-chain gateway can update the currently cached identity record information. Specifically, if the identity record information of the frozen account is cached in the first cross-link gateway, the first cross-link gateway may modify the value of the account status parameter in the cached identity record information to a fourth preset value. If the identity record information of the frozen account is not cached in the first cross-link gateway, the first cross-link gateway can cache the identity record information of the other frozen account to the first cross-link gateway.

Example IV

With continued reference to fig. 7, fig. 7 is a flowchart of an account query method corresponding to the account query system provided in the embodiment of the present application. As shown in fig. 7, the account query method includes:

in step 701, a first blockchain sends a cross-chain account query request to a relay chain through a first cross-chain gateway.

Step 702, a relay chain receives a cross-chain account query request, and searches identity record information where an account identifier is located in a cross-chain identity record information table stored in advance in the relay chain; and in response to the found identity record information of the account identifier, sending the found identity record information to the first blockchain through the first cross-chain gateway.

In step 703, the first block links the found identity record information, and sends the storage address in the found identity record information to the first cross-link gateway.

Step 704, the first cross-link gateway obtains account identity description information of the account to be checked on the second blockchain according to the received storage address, and sends the obtained account identity description information to the first blockchain, so that the first blockchain performs identity authentication on the account to be checked on the second blockchain based on the obtained account identity description information.

According to the method provided by the embodiment, the identity intercommunication among different blockchains is realized through the relay chain and the cross-chain gateway, so that the safety of transaction among different blockchains is improved. Secondly, by looking up a table, the account identity description information corresponding to the account identifier of the account to be checked is looked up from the cross-chain identity record information table, so that the method is technically easy to realize and is beneficial to improving the account query efficiency. Then, the storage address of the account identity description information is stored in the cross-link identity record information table of the relay link, instead of storing the account identity description information, so that the storage space of the relay link can be saved, and the cross-link identity record information table can be simplified. And then, the account identity description information of the accounts on each blockchain is only required to be stored once, and each blockchain can access the account identity description information of the accounts on all blockchains in a storage address access mode, so that the storage space of the whole blockchain network is saved. In addition, because the stored account identity description information needs to consume more time, the stored account identity description information is read by the cross-chain gateway, so that the workload of the blockchain can be reduced, and the data processing efficiency of the whole blockchain network can be improved.

It should be noted that, because the content of information interaction and execution process between the first blockchain, the first cross-chain gateway, the second blockchain, the second cross-chain gateway, and the relay chain is based on the same conception as the system embodiment of the present application, specific functions and technical effects thereof may be referred to the system embodiment section, and will not be repeated here.

Fig. 8 is a flowchart of an account query method provided in an embodiment of the present application.

Step 801, a user terminal where an account is located sends a local chain account query request to a blockchain, wherein the local chain account query request comprises an account identifier.

Step 802, the application chain searches the identity record information of the account identifier from the identity record information table of the application chain. If the search is successful, steps 803-808 are performed. If the lookup is unsuccessful, step 809 is performed.

Step 803, the application chain sends the storage address in the searched identity record information to the cross-chain gateway.

Step 804, the cross-link gateway uses the storage address to obtain data from the location corresponding to the storage address.

The storage server returns the account identity description information at the storage address to the cross-chain gateway, step 805.

Step 806, the cross-chain gateway sends the account identity description information to the application chain.

The application chain verifies the received account identity description information, step 807.

Here, the received account identity description information is verified, typically, a hash value of the received account identity description information is calculated, and if the calculated hash value is the same as the hash value in the identity record information, the verification is passed. Otherwise, if the verification is inconsistent, the verification is not passed.

In step 808, the application chain sends the verification result and the account identity description information to the user terminal.

In step 809, the application chain sends a continue query request including the account identification to the cross-chain gateway.

Step 810, the cross-chain gateway sends a continue query request including an account identification to the relay chain.

In step 811, the relay chain searches the identity record information in which the account identifier is located from the cross-chain identity record information table. If the lookup fails, step 812 is performed. If the searching is successful, the searched identity record information is sent to the application chain through the cross-chain gateway. Thus, the application chain returns the search result of the successful search to the user terminal by performing steps 803-808.

Step 812, a continue query request is sent to the upper relay chain to perform a lookup in the upper relay chain. If the search of the upper relay chain and the upper relay chain of each layer of the upper relay chain or even the top relay chain is unsuccessful, step 813 is performed.

Step 813, the relay chain returns the unsuccessful lookup result to the cross-chain gateway.

Step 814, the cross-chain gateway returns the unsuccessful lookup results to the application chain.

In step 815, the application chain returns the search result of unsuccessful search to the user terminal.

Example five

With continued reference to fig. 9, fig. 9 shows a block diagram of a cross-chain gateway 900 provided by an embodiment of the present application. As shown in fig. 9, the cross-chain gateway 900 includes: an information transfer unit 901 and an information reading unit 902, wherein the cross-chain gateway is respectively in communication connection with the first blockchain and the relay chain.

The information transfer unit 901 is configured to forward a cross-chain account query request of a first blockchain to a relay chain, where the cross-chain account query request includes an account identifier of an account to be checked on a second blockchain; forwarding identity record information searched by a relay chain aiming at a cross-chain account query request to a first blockchain, wherein the identity record information comprises an account identifier and a storage address for storing account identity description information of an account marked by the account identifier;

an information reading unit 902, configured to receive a storage address in the found identity record information sent by the first blockchain; according to the received storage address, acquiring account identity description information of the account to be checked on the second blockchain, and sending the acquired account identity description information to the first blockchain, so that the first blockchain performs identity authentication on the account to be checked on the second blockchain based on the acquired account identity description information.

According to the cross-chain gateway provided by the embodiment, more time is required for reading the stored account identity description information, and the cross-chain gateway is used for reading the stored account identity description information, so that the workload of a blockchain can be reduced, and the data processing efficiency of the whole blockchain network can be improved.

In some optional implementations of this embodiment, the cross-chain gateway further includes an information storage unit, where the information storage unit is configured to store the received account identity description information to a storage server that matches the data storage type in response to receiving the data storage type and the account identity description information sent by the first blockchain, and return a storage address for the received account identity description information to the blockchain.

The above embodiments are only for illustrating the technical solution of the present application, and are not limiting thereof; 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. An account query system, the system comprising: a first blockchain, a second blockchain, a first cross-chain gateway, a second cross-chain gateway, and a relay chain, the first blockchain communicatively coupled to the relay chain through the first cross-chain gateway, the second blockchain communicatively coupled to the relay chain through the second cross-chain gateway, wherein,

The relay chain is used for receiving the cross-chain account query request, and searching the identity record information of the account identifier from a cross-chain identity record information table stored in the relay chain in advance, wherein the identity record information in the cross-chain identity record information table comprises the account identifier and a storage address for storing account identity description information of an account marked by the account identifier; responding to the found identity record information of the account identifier, and sending the found identity record information to the first blockchain through the first cross-chain gateway;

the first blockchain is further used for receiving the searched identity record information and sending a storage address in the searched identity record information to the first cross-chain gateway;

the first cross-link gateway is configured to obtain, according to the received storage address, account identity description information of an account to be checked on the second blockchain, and send the obtained account identity description information to the first blockchain, so that the first blockchain performs identity authentication on the account to be checked on the second blockchain based on the obtained account identity description information.

2. The account query system of claim 1, wherein the account query system is configured to,

the first blockchain is further configured to, in response to receiving a local chain account query request sent by a user terminal where a local chain account is located and used for querying an account to be queried on the first blockchain, search identity record information where an account identifier of the account to be queried is located from a local chain identity record information table stored in advance in the first blockchain, and send a storage address in the searched identity record information to the first cross-chain gateway, where the local chain account query request includes the account identifier of the account to be queried, and the identity record information in the local chain identity record information table includes the account identifier and a storage address used for storing account identity description information of the account indicated by the account identifier;

the first cross-link gateway is further configured to obtain account identity description information of an account to be checked on the first blockchain according to the received storage address, and send the obtained account identity description information to the first blockchain;

3. The account query system of claim 1, wherein the account query system is configured to,

the relay chain is further configured to search identity record information of an account identifier of an account to be checked on the relay chain from a local chain identity record information table stored in advance in the relay chain, where the identity record information is located, in response to receiving a local chain account query request sent by the first blockchain through the first cross-chain gateway and used for querying the account to be checked on the relay chain; responding to the identity record information of the account identifier of the account to be checked on the relay chain, and transmitting the searched identity record information to the first blockchain through the first cross-chain gateway;

the first cross-link gateway is configured to obtain, according to the received storage address, account identity description information of an account to be checked on the relay chain, and send the obtained account identity description information to the first blockchain, so that the first blockchain performs identity authentication on the account to be checked on the relay chain based on the obtained account identity description information.

4. The account query system of claim 2, further comprising at least one storage server, the first blockchain implementing the pre-storing of the local chain identity record information table by performing a building step comprising:

responding to an identity registration request which is sent by a user terminal where a local chain account is located and comprises an account identifier and account identity description information of the local chain account, and sending the data storage type of the first blockchain and the account identity description information of the local chain account to the first cross-chain gateway so that the first cross-chain gateway stores the account identity description information of the local chain account to a storage server matched with the data storage type;

receiving a storage address returned by the first cross-link gateway aiming at account identity description information of a local link account;

and storing the account identifier of the chain account, the storage address, the hash value of the account identity description information of the chain account and the whole account state parameter with the value of a first preset value into the chain identity record information table as identity record information, wherein the first preset value is used for indicating that the chain account is in a registered pending state currently.

5. The account query system of claim 4, wherein the constructing step further comprises:

and when the auditing result information indicates that the auditing is passed, modifying the value of the account state parameter in the corresponding identity record information into a second preset value, wherein the second preset value is used for indicating that the account is currently in an auditing passing state.

6. The account query system of claim 4, wherein the constructing step further comprises:

responding to an identity updating request which is sent by a user terminal where a local chain account is located and comprises an account identifier of the local chain account and new account identity description information, and sending the data storage type of the first blockchain and the new account identity description information of the local chain account to the first cross-chain gateway so that the first cross-chain gateway stores the new account identity description information of the local chain account to a storage server matched with the data storage type;

receiving a new storage address returned by the first cross-link gateway aiming at new account identity description information of the local link account;

And modifying a storage address in the identity record information corresponding to the chain account into the new storage address, modifying the hash value of the account identity description information into the hash value of the new account identity description information, and modifying the value of the account state parameter into a third preset value, wherein the third preset value is used for indicating that the chain account is in an update pending state currently.

7. The account query system of any one of claims 1-6, further comprising a third blockchain, and wherein a local chain identity record information table is pre-stored in any one or more blockchains included in the system, the identity record information in the local chain identity record information table comprising an account identification, a storage address for storing account identity description information for the account identified by the account identification, and an account status parameter for indicating an account status of the account identified by the account identification; and

the third blockchain is configured to send a cross-chain account freeze request to a receiving chain, where the cross-chain account freeze request includes an account identifier of an account to be frozen and a chain identifier of a chain to be frozen, and the receiving chain includes any one or more of the following: the first blockchain, the second blockchain, the relay chain;

The receiving chain is used for receiving a cross-chain account freezing request sent by the third blockchain; modifying the value of the account state parameter corresponding to the account identifier of the account to be frozen into a fourth preset value in the blockchain indicated by the chain identifier of the chain to be frozen, wherein the fourth preset value is used for indicating that the account to be frozen is currently in a frozen state.

8. The account query system of claim 7, wherein the account query system is configured to,

the first cross-link gateway is further configured to cache the searched identity record information returned by the relay link for the cross-link account query request; in response to receiving the request for querying the cross-chain account sent by the first blockchain for the second time, acquiring account identity description information of an account to be queried on the second blockchain according to a storage address included in the cached identity record information, and sending the acquired account identity description information to the first blockchain;

the first cross-link gateway is further configured to cache, when the blockchain of the communication connection modifies the value of the account status parameter in the identity record information where the account identifier of the account to be frozen is located to a fourth preset value, the identity record information where the value of the account status parameter is the fourth preset value.

9. A cross-chain gateway for use in an account query system as claimed in any one of claims 1 to 8, the cross-chain gateway being communicatively coupled to a first blockchain and a trunk chain respectively, the cross-chain gateway comprising: an information transfer unit, and an information reading unit, wherein,

the information transfer unit is used for forwarding a cross-chain account query request of the first blockchain to the relay chain, wherein the cross-chain account query request comprises an account identifier of an account to be checked on a second blockchain; forwarding identity record information searched by the relay chain aiming at the cross-chain account inquiry request to the first blockchain, wherein the identity record information comprises an account identifier and a storage address for storing account identity description information of an account marked by the account identifier;

the information reading unit is used for receiving a storage address in the searched identity record information sent by the first blockchain; according to the received storage address, acquiring account identity description information of the account to be checked on the second blockchain, and sending the acquired account identity description information to the first blockchain, so that the first blockchain performs identity authentication on the account to be checked on the second blockchain based on the acquired account identity description information.

10. The cross-chain gateway of claim 9, further comprising an information storage unit, wherein,

the information storage unit is used for responding to the received data storage type and account identity description information sent by the first blockchain, storing the received account identity description information to a storage server matched with the data storage type, and returning a storage address aiming at the received account identity description information to the blockchain.