WO2022140950A1

WO2022140950A1 - Account query system and cross-chain gateway

Info

Publication number: WO2022140950A1
Application number: PCT/CN2020/140286
Authority: WO
Inventors: 李伟; 邱炜伟; 汪小益; 张帅; 匡立中
Original assignee: 杭州趣链科技有限公司
Priority date: 2020-12-28
Filing date: 2020-12-28
Publication date: 2022-07-07
Also published as: JP2024501987A

Abstract

Disclosed in the present application are an account query system and a cross-chain gateway. The system comprises a first blockchain, a second blockchain, a first cross-chain gateway, a second cross-chain gateway, and a relay chain; the first blockchain is communicationally connected to the relay chain by means of the first cross-chain gateway; the second blockchain is communicationally connected to the relay chain by means of the second cross-chain gateway.

Description

Account query system, cross-chain gateway

technical field

The present application relates to the field of computer technology, and in particular to an account query system and a cross-chain gateway.

Background technique

Blockchain is a distributed shared ledger and database, which has the characteristics of decentralization, immutability, traceability, traceability, collective maintenance, openness and transparency.

technical problem

One of the purposes of the embodiments of this application is to provide an account query system and a cross-chain gateway, which aims to solve the problem that the on-chain identities between different blockchains in related technologies are usually not interoperable, and one blockchain cannot obtain The identity information of the account on another blockchain cannot be authenticated across the blockchain, resulting in the problem that the security of the transaction across the blockchain is not high enough.

technical solutions

In order to solve the above-mentioned technical problems, the technical solutions adopted in the embodiments of the present application are:

In a first aspect, an account query system is provided, which includes: a first blockchain, a second blockchain, a first cross-chain gateway, a second cross-chain gateway and a relay chain, and the first blockchain passes The first cross-chain gateway is communicatively connected to the relay chain, and the second blockchain is communicatively connected to the relay chain through the second cross-chain gateway. The relay chain sends a cross-chain account query request, wherein the cross-chain account query request includes the account identifier of the account to be checked on the second blockchain; the relay chain is used to receive the cross-chain account query request, and pre-stores it from the relay chain In the cross-chain identity record information table, look up the identity record information where the account identifier is located, wherein the identity record information in the cross-chain identity record information table includes the account identifier and the account identity description information used to store the account identified by the account identifier. address; in response to finding the identity record information where the account identifier is located, send the found identity record information to the first blockchain through the first cross-chain gateway; the first blockchain is also used to receive the found identity record information, send the storage address in the found identity record information to the first cross-chain gateway; the first cross-chain gateway is used to obtain the account identity of the account to be checked on the second blockchain according to the received storage address description information, and sending the obtained account identity description information to the first blockchain, so that the first blockchain can authenticate the account to be checked on the second blockchain based on the obtained account identity description information.

In a second aspect, a cross-chain gateway is provided, wherein the cross-chain gateway is communicatively connected to the first blockchain and the relay chain, respectively, and the cross-chain gateway includes: an information transmission unit and an information reading unit, wherein the information transmission unit , which is used to forward the cross-chain account query request of the first blockchain to the relay chain, wherein the cross-chain account query request includes the account identifier of the account to be checked on the second blockchain; The identity record information found by the account query request is forwarded to the first blockchain, and the identity record information includes an account identifier and a storage address for storing account identity description information of the account marked by the account identifier; the information reading unit is used to receive the first block chain. The storage address in the found identity record information sent by one blockchain; according to the received storage address, obtain the account identity description information of the account to be checked on the second blockchain, and the account identity description to be obtained The information is sent 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.

beneficial effect

The beneficial effects of the present application are: since it takes a lot of time to read the stored account identity description information, the cross-chain gateway realizes the reading of the stored account identity description information, which can reduce the workload of the blockchain. Helps to improve the data processing efficiency of the entire blockchain network.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the accompanying drawings that are used in the description of the embodiments or exemplary technologies. Obviously, the drawings in the following description are only for the present application. In some embodiments, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without any creative effort.

1 is a system architecture diagram of an account inquiry system provided by an embodiment of the present application;

2 is a schematic structural diagram of an account inquiry system provided by an embodiment of the present application;

3 is a schematic flowchart of a construction step provided by an embodiment of the present application;

4 is a schematic diagram of an identity registration process provided by an embodiment of the present application;

5 is a schematic diagram of an identity verification process provided by an embodiment of the present application;

6 is a schematic structural diagram of an account inquiry system provided by another embodiment of the present application;

7 is a schematic flowchart of an account query method provided by an embodiment of the present application;

8 is a schematic flowchart of an account query method provided by an embodiment of the present application;

FIG. 9 is a structural block diagram of a cross-chain gateway provided by an embodiment of the present application.

Embodiments of the present invention

In order to make the purpose, technical solutions and advantages of the present application more clearly understood, the present application will be described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, but not to limit the present application.

In order to illustrate the technical solutions described in the present application, a detailed description is given below with reference to the specific drawings and embodiments.

Example 1

Referring to FIG. 1 , it is a system architecture diagram of an account query system provided by an embodiment of the present application.

As shown in Figure 1, the system architecture can include blockchains C1, C2, C3, C4, relay chains B1, B2, B3, B4 and cross-chain gateways P1-P7. Among them, the relay chain is usually a special blockchain used to authenticate the connected blockchain and transmit information to the connected blockchain. In practical applications, in order to distinguish the description, the blockchain other than the relay chain can be recorded as the application chain. In addition, unless otherwise specified, the blockchains mentioned in this application (eg, the first blockchain, the second blockchain) are all application chains.

The connection relationships between blockchains C1, C2, C3, C4 and relay chains B1, B2, B3, and B4 are usually tree-like structures. Relay chain B2 and relay chain B3 are leaf nodes of relay chain B1. Block chain C1 and block chain C2 are leaf nodes of relay chain B2. Blockchain C3 and relay chain B4 are leaf nodes of relay chain B3. Blockchain C4 is the leaf node of relay chain B4. Relay chain B1 is an upper-level relay chain of relay chain B2 and relay chain B3, and relay chain B3 is an upper-level relay chain of relay chain B4. In practical applications, blockchains C1, C2, C3, and C4 can be application chains for different application scenarios.

For all relay chains in the tree structure, the identity intercommunication between multiple leaf nodes of a relay chain can be realized, for example, the identity intercommunication between blockchain C1 and blockchain C2. Identity interworking between leaf nodes of different relay chains can also be realized, for example, identity interworking between blockchain C1 and blockchain C3. It is also possible to realize intercommunication between relay chains, such as relay chain B2 and relay chain B3, and relay chain B1 and relay chain B2. It is also possible to realize the intercommunication 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, etc.

In practical applications, for the convenience of description, some relation words are usually used to distinguish relative relations among multiple blockchains whose connection relation is in a tree-like structure. For example, words such as direct line, collateral line, peer, junior, and senior can be used to distinguish the relative relationship between multiple blockchains. Generally, chains at the same level are of the same generation, with higher levels being seniors, and lower levels being juniors. For example, for blockchain C1, B2, B1 are its immediate predecessors. For relay chain B2, blockchain C1 is its immediate descendant, and relay chain B1 is its immediate predecessor. In addition, for the blockchain C1, all chains other than B2 and B1 are its side chains.

In practice, the interaction between the two chains can be realized through a cross-chain gateway. As shown in Figure 1, the interaction between chain B1 and chain B2 can be realized through cross-chain gateway P1, the interaction between chain B1 and chain B3 can be realized through cross-chain gateway P2, and the interaction between chain B2 and chain can be realized through cross-chain gateway P3. For the interaction between C1, the interaction between chain B2 and chain C2 is realized through cross-chain gateway P4, the interaction between chain B3 and chain C3 is realized through cross-chain gateway P5, and the interaction between chain B3 and chain B4 is realized through cross-chain gateway P6. The interaction between chain B4 and chain C3 is realized through the cross-chain gateway P7.

In practice, if a relay chain has at least two leaf nodes, each leaf node is a blockchain. In order to facilitate the distinguishing description, one of the blockchains can be called the first blockchain, and the other blockchain can be called the second blockchain. The first blockchain is communicatively connected to the relay chain through the first cross-chain gateway, and the second blockchain is communicatively connected to the relay chain through the second cross-chain gateway. at this time,

The first blockchain can be used to send a cross-chain account query request to the relay chain through the first cross-chain gateway. The relay chain can be used to receive cross-chain account query requests, and find the identity record information where the account identifier is located from the cross-chain identity record information table pre-stored in the relay chain; in response to finding the identity record information where the account identifier is located, The found identity record information is sent to the first blockchain through the first cross-chain gateway. The first blockchain can also be used to receive the found identity record information, and send the storage address in the found identity record information to the first cross-chain gateway. The first cross-chain gateway can be used to obtain the account identity description information of the account to be checked on the second blockchain according to the received storage address, and send the obtained account identity description information to the first blockchain, This enables the first blockchain to authenticate the account to be checked on the second blockchain based on the acquired account identity description information.

Embodiment 2

Continue to refer to FIG. 2 , which is a schematic structural diagram of an account inquiry system provided by an embodiment of the present application. The account inquiry 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 , and the first blockchain 201 The first cross-chain gateway 203 is communicatively connected to the relay chain 205 , and the second blockchain 202 is communicatively connected to the relay chain 205 through the second cross-chain gateway 204 . in,

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

The cross-chain account query request includes the account identifier of the account to be checked on the second blockchain. The above account to be checked is usually the account to be checked.

In practice, each blockchain usually has many blockchain accounts, and each blockchain account has a corresponding blockchain account address. For the convenience of description, this application may refer to the blockchain account as an account for short.

Wherein, the above account identifier is usually information used to identify the account. In practical applications, the account identifier can usually indicate the account and the blockchain where the account is located. For example, the account identifier can be: 001:0x1234567, where 001 can be the identifier of the blockchain, and 0x1234567 is the code of the account on the blockchain identified as 001.

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

The relay chain 205 is configured to receive a cross-chain account query request, and search for the identity record information where the account identifier is located from the cross-chain identity record information table pre-stored in the relay chain. In response to finding the identity record information where the account identifier is located, the found identity record information is sent to the first blockchain through the first cross-chain gateway.

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

The above account identity description information is usually information used to describe the account identity. For example, account identity description information may include, but is not limited to, account address, account public key, account encryption algorithm, account registration time, and the like. Account address usually refers to the address of a blockchain account. Account public key usually refers to the public key used by the blockchain account. Account encryption algorithm usually refers to the encryption algorithm used by blockchain accounts. In this application, the specific format of the account identity description information may be the object notation format (JavaScript Object Notation, JSON), or the extensible markup language format (eXtensible Markup Language format). Language, XML), can also be another markup language format (Yet Another Markup Language, YAML) etc.

In practice, each blockchain may be pre-stored with a local chain identity record information table for recording relevant information of accounts on this chain. The identity record information table of this chain stored in each blockchain has multiple pieces of identity record information. In the relay chain type blockchain, a cross-chain identity record information table is usually stored, and the stored cross-chain identity record information table usually has the identity corresponding to the account on the leaf node blockchain of the relay chain. record information. In the upper-level relay chain of any relay chain, the cross-chain identity record information table stored by the relay chain can be backed up. In this way, identity interoperability between blockchains can be realized. For example, with reference to FIG. 1, the relay chain B1 may simultaneously have the cross-chain identity record information table stored by the relay chain B2, the cross-chain identity record information table stored by the relay chain B3, and the cross-chain identity record information table stored by B4. Record information sheet. For further example, if blockchain C1 sends a request to query an account on blockchain C3 to relay chain B2, the cross-chain identity record information table in relay chain B2 usually does not have an account on blockchain C3. Corresponding identity record information. At this time, the relay chain B2 can send a continuation query request to the upper-level relay chain B1, so as to query the identity record information corresponding to the account on the blockchain C3 through the relay chain B1.

In this embodiment, the relay chain 205 may receive a cross-chain account query request. Then, using the account identifier of the account to be checked, the identity record information where the account identifier is located is searched from the cross-chain identity record information table pre-stored in the relay chain 205 . Afterwards, the found identity record information is sent to the first cross-chain gateway 203 , so 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 the storage address in the found identity record information to the first cross-chain gateway.

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

The first cross-chain gateway 203 is configured to obtain the account identity description information of the account to be checked on the second blockchain according to the received storage address, and send the obtained account identity description information to the first blockchain, Make the first blockchain perform identity authentication on the account to be checked on the second blockchain based on the acquired account identity description information.

In this embodiment, the first cross-chain gateway 203 may use the received storage address to obtain account identity description information from the location indicated by the storage address. Because the storage address is the description information of the address used to store the account identity description information of the account to be checked on the second blockchain. Therefore, at this time, the first cross-chain gateway 203 can obtain the account identity description information of the account to be checked on the second blockchain. After that, the first cross-chain gateway 203 may send the acquired account identity description information to the first blockchain 201 . In this way, the first blockchain 201 can receive the account identity description information, so as to perform identity authentication on the account to be checked on the second blockchain.

In the system provided by this embodiment, the relay chain and the cross-chain gateway can realize identity intercommunication between different blockchains, which helps to improve the security of transactions between different blockchains. Secondly, by looking up the table, the account identity description information corresponding to the account identifier of the account to be checked is searched from the cross-chain identity record information table, which is technically easy to implement and helps to improve the efficiency of account query. Then, the storage address of the account identity description information is stored in the cross-chain identity record information table of the relay chain, instead of storing the account identity description information itself, which can save the storage space of the relay chain and simplify the cross-chain identity record information table. After that, the account identity description information of the accounts on each blockchain only needs to be stored once, and each blockchain can access the account identity description information of the accounts on all blockchains by accessing the storage address, which helps to save the entire The storage space of the blockchain network. In addition, since it takes a lot of time to read the stored account identity description information, the cross-chain gateway realizes the reading of the stored account identity description information, which can reduce the workload of the blockchain and help improve the entire blockchain. The data processing efficiency of the blockchain network.

In some optional implementations of this embodiment, in the above account query system, the relay chain is further configured to: in response to not finding the identity record information where the account identifier is located, send a communication link including the account identifier to the upper-level relay chain of the communication connection the continuation query request. Receive the identity record information where the account identifier is located and send the received identity record information to the first blockchain through the first cross-chain gateway.

Wherein, the continuing query request may include the account identifier of the account to be queried on the second blockchain.

Here, if the above-mentioned execution body does not find the identity record information where the account identifier is located, in the case that the above-mentioned execution body has an upper-level relay chain, the above-mentioned execution body can send a continuation query request to the upper-level relay chain. In this way, after receiving the continuation query request, the upper-level relay chain can generally use the account identifier in the continuation query request to continue the query from one or more cross-chain identity record information tables stored in the upper-level relay chain. If the identity record information where the account identifier is located is found, the found identity record information is sent to the relay chain. In this way, the above-mentioned relay chain can receive the identity record information of the account identifier returned by the upper-level relay chain, and send the received identity record information of the account identifier to the first blockchain.

In this implementation manner, by sending a continuation query request to the upper-level relay chain, so that the upper-level relay chain continues to query the account identifier of the account to be queried, the identity exchange between leaf nodes of different relay chains can be realized. It helps to further improve the security of transactions between different blockchains.

In some optional implementations of this embodiment, in the first blockchain, sending a cross-chain account query request to the relay chain through the first cross-chain gateway includes: in response to receiving the user terminal where the account of this chain is located, sending The cross-chain account query request is sent to the relay chain through the first cross-chain gateway.

The cross-chain account query request includes the account identifier of the account to be checked on the second blockchain. The local chain account here usually refers to the account on the first blockchain. Users can log in to the account on the blockchain through the user terminal.

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

In some optional implementations of this embodiment, in the above account inquiry system,

The first blockchain can also be used to retrieve the local-chain account query request sent by the user terminal where the local-chain account is located and used to query the account to be checked on the first blockchain. In the pre-stored identity record information table of this chain, look up the identity record information where the account identifier of the account to be checked is located, and send the storage address in the found identity record information to the first cross-chain gateway.

The on-chain account query request includes the account identifier of the account to be checked, and the identity record information in the on-chain identity record information table includes the account identifier and the storage address for storing the account identity description information of the account indicated by the account identifier.

Here, the account to be checked is an account on the first blockchain. The first blockchain can receive the query request of the account of the chain sent by the user terminal where the account of the chain is located. The local chain account query request is used to query the account identity description information of the account on the 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 for the local chain identity record information table pre-stored in the first blockchain. The identity record information where the account ID is located. Then, the storage address in the found identity record information is sent to the first cross-chain gateway.

The first cross-chain gateway is further configured to obtain account identity description information of the 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 can receive the storage address sent by the first blockchain. After receiving the storage address, the first cross-chain gateway can directly read the account identity description information from the location indicated by the storage address. Because the storage address is the description information of the address used to store the account identity description information of the account to be checked on the first blockchain. Therefore, at this time, the first cross-chain gateway can obtain the account identity description information of the account to be checked on the first blockchain. Then, the acquired account identity description information is sent to the first blockchain.

The first blockchain is further configured to receive the account identity description information of the account to be checked on the first blockchain returned by the first cross-chain gateway, and send the received account identity description information to the user terminal.

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

In this implementation manner, the identity record information table of this chain is stored in the blockchain, so that when the user terminal where an account on the blockchain is located needs to query the relevant information of another account on the blockchain, the block The chain can send the account identity description information of the above-mentioned another account to the user terminal. Helps to increase the speed of data processing and thus the speed of transactions between the same blockchains. In addition, not all query requests are implemented through the relay chain, which can save the processing resources of the relay chain.

The relay chain is also used to, in response to receiving the 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, from the pre-stored account in the relay chain. In the identity record information table of this chain, look up the identity record information of the account identifier of the account to be checked on the relay chain; in response to finding the identity record information of the account identifier of the account to be checked on the relay chain, through the first The cross-chain gateway sends the found identity record information to the first blockchain.

Here, the account to be checked is the account on the relay chain. The relay chain can receive the account query request sent by the first blockchain through the first cross-chain gateway. The local chain account query request is used to query the account identity description information of the account on the relay chain. After the Relay Chain receives the local chain account query request, it can use the account identifier included in the local chain account inquiry request to find the identity of the account identifier from the local chain identity record information table pre-stored in the Relay Chain record information. Then, the found identity record information is forwarded to the first blockchain through the first cross-chain gateway.

The first blockchain is further configured to receive the found identity record information, and send the storage address in the found 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-chain gateway is used to obtain the account identity description information of the account to be checked on the relay chain according to the received storage address, and send the obtained account identity description information to the first blockchain, so that the first The blockchain authenticates the account to be checked on the relay chain based on the obtained account identity description information.

Here, the first cross-chain gateway may use the received storage address to obtain account identity description information from the location indicated by the storage address. Because the storage address is the description information of the address used to store the account identity description information of the account to be checked on the relay chain. Therefore, at this time, the first cross-chain gateway can obtain the account identity description information of the account to be checked on the relay chain. After that, the first cross-chain gateway can send the acquired account identity description information to the first blockchain. In this way, the first blockchain can receive the account identity description information, so as to authenticate the account to be checked on the relay chain.

In this implementation manner, the account on the relay chain can be queried, so as to perform identity authentication 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 realizes pre-storing the identity record information table of this chain by executing the construction steps.

FIG. 3 is a schematic flowchart of construction steps provided in an embodiment of the present application. As shown in Figure 3, the building step may include steps 301-303. It should be pointed out that the execution subject of steps 301-303 is the first blockchain.

Step 301, in response to receiving the identity registration request sent by the user terminal where the account of this chain is located, including the account identification and account identity description information of the account of this chain, the data storage type of the first blockchain and the account identity of the account of this chain are stored. The description information is sent to the first cross-chain gateway, so that the first cross-chain gateway stores the account identity description information of the account in this chain to a storage server that matches the data storage type.

The identity registration request described above is generally information for requesting registration. The above-mentioned storage server may be a preset server for storing data. There can 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 support one data storage type respectively. The data storage type usually refers to the type of data storage. As an example, the above data storage types may include, but are not limited to, support for structured query language (Structured Query Language, SQL), interplanetary file system (Inter Planetary File) System, IPFS), remote dictionary service (REmote DIctionary Server, Redis), etc.

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

Step 302: Receive the storage address returned by the first cross-chain gateway for the account identity description information of the account on this chain.

Here, after the first cross-chain gateway stores the account identity description information of the account on this chain into the storage server, it usually returns the storage address to the first blockchain. In this way, the first blockchain can receive the storage address.

Step 303: Store the entirety of the account identifier, storage address, account identity description information of the account of this chain, and the account status parameter whose value is the first preset value as the identity record information into the identity of this chain. Record information sheet.

Among them, the first preset value is used to indicate that the account of this chain is currently in the state of registration pending review.

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

FIG. 4 is a schematic diagram of an identity registration process provided by an embodiment of the present application.

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

Here, the application chain may be the above-mentioned first blockchain, the above-mentioned second blockchain, or other blockchains.

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 matching 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.

Step 406, the application chain stores the account identifier, storage address and the hash value of the account identity description information as a piece of identity record information into the identity record information table of this chain.

In practice, each piece of identity record information in the identity record information table of this chain may also have an account state parameter used to indicate the account state. Different values of the account state parameter may indicate different account states. When performing identity registration on an account, the value of the account status parameter may be a first preset value, which is used to indicate that the account status is a registration pending status.

In some optional implementations of this embodiment, the above construction step may further include: performing a preset audit operation on the identity record information whose value of the corresponding account status parameter in the identity record information table of the local chain is the first preset value, Obtaining audit result information, and modifying the value of the account status parameter in the corresponding identity record information to a second preset value when the audit result information indicates that the audit is passed.

The second preset value is used to indicate that the account is currently in an approved state.

Wherein, the above-mentioned preset audit operation may be an operation of auditing account identity description information. For example, the above-mentioned preset audit operation may be: the blockchain controls all or part of the blockchain nodes of the blockchain to perform the following steps: using the storage address in the identity record information to download the account identity description information. Then, the hash value of the downloaded identity description information is calculated. Finally, the calculated hash value is compared with the hash value in the identity record information, and if the two are the same, the approval information for indicating approval is returned to the blockchain. On the contrary, if the two are different, the verification failure indication information for indicating failure of the verification will be returned to the blockchain. In this way, the blockchain can determine whether the account identity description information of the account has passed the review by counting the number of approval indications. In practice, if the audit result is approved, the blockchain can modify the value of the account status parameter in the corresponding identity record information to the second preset value. The second preset value is used to indicate that the account is currently in an approved state. If the audit result is that the audit fails, the blockchain can modify the value of the account status parameter in the corresponding identity record information to the fifth preset value. Wherein, the fifth preset value is used to indicate that the account is currently in a state of review and rejection.

In the above implementation manner, after modifying the value of the account status parameter in the corresponding identity record information, the first blockchain is further configured to: respond to the modified value of the account status parameter in the corresponding identity record information As the second preset value, the modified corresponding identity record information is sent 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 an approved status, it is considered that the identity record information is valid. At this point, the blockchain can send this identity record information to the relay chain. In this way, the relay chain can use the identity record information to update the cross-chain identity record information table. Specifically, the relay chain can add the identity record information to the 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 audits the identity record information of the account. If the audit fails, steps 501-504 are performed. When the verification is passed, steps 505-509 are performed.

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

Step 502, the cross-chain 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 completion of deletion through the cross-chain gateway.

Step 504, the application chain modifies the value of the account status parameter in the reviewed identity record information to a fifth preset value, and deletes the storage address in the identity record information. Wherein, the fifth preset value is used to indicate that the account is currently in a state of review and rejection.

Step 505, the application chain updates the identity record information table of this chain.

Here, the value of the account status parameter of the identity record information that has passed the audit in the identity record information of this chain can be modified to the second preset value. The second preset value is used to indicate that the account is currently in an approved state.

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

Step 507: The cross-chain gateway sends the verified identity record information to the relay chain.

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

Here, the relay chain can add the verified identity record information to the cross-chain identity record information table.

Step 509: The relay chain sends the verified identity record information to the upper-level relay chain of the relay chain. In this way, the upper-level relay chain of the relay chain can add the verified identity record information to the corresponding cross-chain identity record information table.

In some optional implementations of this embodiment, the foregoing construction step may further include the following steps 1 to 3. It should be pointed out that the execution subject of steps 1 to 3 is the first blockchain.

Step 1, in response to receiving the identity update request sent by the user terminal where the account of this chain is located, including the account identification of the account of this chain and the description information of the new account identity, the data storage type of the first blockchain and the new account of the account of this chain are stored. The account identity description information is sent to the first cross-chain gateway, so that the first cross-chain gateway stores the new account identity description information of the account on this chain to a storage server that matches the data storage type.

Here, the identity update request may be information for requesting to update the account identity description information of the account. After receiving the identity update request, the first blockchain can 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 can store the new account identity description information to the storage server matching the data storage type.

Step 2: Receive the new storage address returned by the first cross-chain gateway for the new account identity description information of the account on this chain.

Here, after the first cross-chain gateway stores the new account identity description information of the account on this chain into the storage server, it usually returns the storage address for storing the new account identity description information, which is recorded as the new storage address here.

Step 3: Modify the storage address in the identity record information corresponding to the account on this chain to the new storage address, change the hash value of the account identity description information to the hash value of the new account identity description information, and change the value of the account status parameter Modified to the third preset value.

Among them, the third preset value is used to indicate that the account of this chain is currently in the state of update pending review. Here, after receiving the new storage address, the first blockchain can modify the storage address in the identity record information of the account to the new storage address, and modify the hash value of the account identity description information to the new account identity description information The hash value of the account status parameter is modified to the third preset value.

It should be pointed out that the blockchain can audit the updated identity record information. Here, the operation of auditing the updated identity record information is basically the same as the foregoing operation of auditing the identity record information, and details are not described here. In practice, when auditing the new identity record information whose account status parameter is the third preset value, if the audit fails, the blockchain can delete the new storage address and send the new identity record to the cross-chain gateway. The storage address realizes that the new account identity description information stored by the new storage address is deleted by the cross-chain gateway. After deleting the new storage address, the blockchain can modify the identity record information where the new storage address is located to be the same as before the update.

Embodiment 3

Continue to refer to FIG. 6 , which is a schematic structural diagram of an account inquiry system provided by an embodiment of the present application. The account inquiry system 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 The first cross-chain gateway 603 is communicatively connected to the relay chain 605 , and the second blockchain 602 is communicatively connected to the relay chain 605 through the second cross-chain gateway 604 .

In addition, the system may further include a third blockchain 606, and the third blockchain 606 may be an application chain or a relay chain. And any one or more blockchains included in the system are pre-stored with the identity record information table of this chain, and the identity record information in the identity record information table of this chain includes the account ID and the account used to store the account marked by the account ID. The storage address of the identity description information, and the account status parameter used to indicate the account status of the account identified by the account identifier. at this time,

The third blockchain 606 can be used to send a cross-chain account freezing request to the receiving chain.

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

Here, the third blockchain 606 may be a blockchain that has 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 a direct predecessor chain, a collateral sibling chain, or the like of the relay chain 605 .

In this embodiment, the third blockchain 606 may send a cross-chain account freezing 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 to receive the cross-chain account freezing request sent by the third blockchain; in the blockchain indicated by the chain ID of the chain to be frozen, the account ID corresponding to the account ID of the account to be frozen is The value of the account status parameter is modified to the fourth preset value.

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

In the system provided by this embodiment, the third blockchain can send a cross-chain account freezing request to the receiving chain, so as to freeze the account across the blockchain. It is helpful to realize that when an account with malicious operations is found on a certain blockchain, a freezing request is initiated for the account in time, so as to realize the timely freezing of the account, which helps to ensure that the identity of the blockchain where the account is located can be communicated with each other. Security of other blockchains.

In some optional implementations of this embodiment, 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 is modified is the fourth preset value, which may include: in response to the determination of the chain identifier, the receiving chain indicates that the receiving chain is the chain to be frozen and the blockchain where the account to be frozen is located is the receiving chain, from the identity record information table of this chain pre-stored in the receiving chain , look up the identity record information where the account identifier of the account to be frozen is located; and modify the value of the account status parameter in the found identity record information to a fourth preset value.

At this time, the chain to be frozen is the receiving chain. This implementation method can realize the freezing of the account on the receiving chain, so as to realize the freezing of the account across the blockchain.

In some optional implementations of this embodiment, 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 is modified is the fourth preset value, which may include: first, the receiving chain sends a cross-chain account freezing request in response to determining that the chain identifier indicates that the receiving chain is a non-to-be-frozen chain and the blockchain where the account to be frozen is located is a direct sub-chain of the receiving chain to the immediate subchain. Then, the direct sub-chain searches the identity record information where the account identifier of the account to be frozen is located from the identity record information table of this chain pre-stored in the direct sub-chain; and modifies the value of the account status parameter in the found identity record information to Fourth preset value.

At this time, the receiving chain is not the chain to be frozen, and the chain to be frozen is a direct child chain of the receiving chain. This implementation can realize the freezing of the accounts on the direct sub-chain of the receiving chain.

In some optional implementations of this embodiment, 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 is modified The fourth preset value may include: first, the receiving chain, in response to determining the chain identifier indicating that the receiving chain is the chain to be frozen and the blockchain where the account to be frozen is located is a direct sub-chain of the receiving chain, from the cross-chain pre-stored in the receiving chain; In the chain identity record information table, look up the identity record information of the account identifier of the account to be frozen, and modify the value of the account status parameter in the found identity record information to the fourth preset value; send the cross-chain account freezing request to Immediate child chain. Then, the direct sub-chain searches the identity record information where the account identifier of the account to be frozen is located from the identity record information table of this chain pre-stored in the direct sub-chain; and modifies the value of the account status parameter in the found identity record information to Fourth preset value.

Here, the chain to be frozen is the receiving chain and the direct child chain of the receiving chain. At this time, the number of chain IDs in the cross-chain account freezing request is two. In practice, there can be multiple chain identifiers in the cross-chain account freezing request. This implementation mode can realize the freezing of the account to be frozen within the scope of the receiving chain and the direct sub-chain of the receiving chain.

In some optional implementations of this embodiment, 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 is modified is the fourth preset value, which may include: the receiving chain generates an identity record corresponding to the to-be-frozen account in response to determining that the chain identifier indicates that the receiving chain is a non-to-be-frozen chain and the blockchain where the to-be-frozen account is located is a side-chain of the receiving chain information, and add the generated identity record information to the cross-chain identity record information table of the receiving chain.

The value of the account status parameter in the generated identity record information is a fourth preset value. Here, since the receiving chain usually does not synchronize the identity record information of the accounts in the sidechain chain. In order to freeze the account to be frozen, the receiving chain can generate an identity record information for the identity of the account to be frozen, so as to freeze the account to be frozen within the scope of the receiving chain. Here, the generated identity record information may include an account identifier and an account status parameter whose value is 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 Usually empty, and the hash value is usually empty.

In this implementation manner, the account on the sidechain chain of the receiving chain can be frozen within the scope of the receiving chain, and the account can be frozen across the blockchain.

It should be pointed out that controlling the freezing range of the account to be frozen helps to better ensure the security of other blockchains that can communicate with the identity of the blockchain where the account is located.

Also, unfreezing an account is typically done in a similar way to freezing the account. Therefore, this application does not make too many statements on how to unfreeze the account.

The first cross-chain gateway is also used to cache the found identity record information returned by the relay chain for the cross-chain account query request; in response to receiving the second cross-chain account query request sent by the first blockchain, according to the cached identity The storage address included in the record information is obtained, the account identity description information of the account to be checked on the second blockchain is obtained, and the obtained account identity description information is sent to the first blockchain.

The first cross-chain gateway is further configured to cache the account status parameter when the block chain 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 value is the identity record information of the fourth preset value.

In this implementation manner, when the relay chain returns the found identity record information for the first blockchain, the first cross-chain gateway can cache the returned identity record information. In this way, when the first blockchain queries the same account next time, the cached identity record information can be directly sent to the first blockchain, thereby speeding up the query efficiency.

In addition, after the first blockchain freezes an 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-chain gateway, the first cross-chain gateway can 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-chain gateway, the first cross-chain gateway may cache the identity record information of the other frozen account to the first cross-chain gateway.

Embodiment 4

Continuing to refer to FIG. 7 , FIG. 7 is a schematic flowchart of an account inquiry method corresponding to an account inquiry system provided by an embodiment of the present application. As shown in Figure 7, the account inquiry method includes:

Step 701: The first blockchain sends a cross-chain account query request to the relay chain through the first cross-chain gateway.

The cross-chain account query request includes the account identifier of the account to be checked on the second blockchain.

Step 702, the relay chain receives the cross-chain account query request, and searches for the identity record information where the account identifier is located from the cross-chain identity record information table pre-stored in the relay chain; in response to finding the identity record information where the account identifier is located, by The first cross-chain gateway sends the found identity record information to the first blockchain.

Step 703: The first blockchain receives the found identity record information, and sends the storage address in the found identity record information to the first cross-chain gateway.

Step 704, the first cross-chain gateway obtains the 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 authenticates the account to be checked on the second blockchain based on the obtained account identity description information.

It should be noted that the information exchange and execution process among the above-mentioned first blockchain, the above-mentioned first cross-chain gateway, the above-mentioned second blockchain, the above-mentioned second cross-chain gateway and the above-mentioned relay chain, due to the The system embodiments of the present application are based on the same concept, and the specific functions and technical effects brought about by the system embodiments can be found in the system embodiments section for details, which will not be repeated here.

FIG. 8 is a schematic flowchart of an account query method provided by an embodiment of the present application.

Step 801, the user terminal where the account is located sends an account query request of the local chain to the blockchain, and the account query request of the local chain includes the account identifier.

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

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

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

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

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

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

Here, the verification of the received account identity description information usually involves calculating a hash value of the received account identity description information. If the calculated hash value is the same as the hash value in the identity record information, the verification is passed. Conversely, if they are inconsistent, the verification fails.

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

In step 809, the application chain sends the continuation query request including the account identifier to the cross-chain gateway.

Step 810, the cross-chain gateway sends a continuation query request including the account identifier to the relay chain.

Step 811, the relay chain searches the identity record information where the account identifier is located from the cross-chain identity record information table. If the search fails, step 812 is executed. If the search is successful, the found identity record information will be sent to the AppChain through the cross-chain gateway. In this way, the application chain returns the successful search result to the user terminal by executing steps 803-808.

Step 812: Send a continuation query request to the upper-level relay chain to implement the search in the upper-level relay chain. If the upper-level relay chain, the upper-level relay chain of each layer of the upper-level relay chain, and even the top-most relay chain are all unsuccessfully searched, step 813 is executed.

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

Step 814, the cross-chain gateway returns the unsuccessful search result to the application chain.

Step 815, the application chain returns the unsuccessful search result to the user terminal.

Embodiment 5

Continuing to refer to FIG. 9 , FIG. 9 shows a structural 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 transmission unit 901 and an information reading unit 902 , wherein the cross-chain gateway is connected in communication with the first blockchain and the relay chain, respectively.

The information transfer unit 901 is used to forward the cross-chain account query request of the first blockchain to the relay chain, wherein the cross-chain account query request includes the account identifier of the account to be checked on the second blockchain; The chain forwards the identity record information found by the cross-chain account query request to the first blockchain, and the identity record information includes the account identifier and the storage address for storing the account identity description information of the account marked by the account identifier;

The information reading unit 902 is configured to receive the storage address in the found identity record information sent by the first blockchain; obtain the account identity description of the account to be checked on the second blockchain according to the received storage address information, and send the obtained account identity description information to the first blockchain, so that the first blockchain can authenticate the account to be checked on the second blockchain based on the obtained account identity description information.

In the cross-chain gateway provided in this embodiment, since it takes a lot of time to read the stored account identity description information, the cross-chain gateway realizes the reading of the stored account identity description information, which can reduce the workload of the blockchain , which helps to improve the data processing efficiency of the entire blockchain network.

In some optional implementations of this embodiment, the cross-chain gateway further includes an information storage unit, wherein the information storage unit is used for receiving the data storage type and account identity description information sent by the first blockchain, The received account identity description information is stored to a storage server matching the data storage type, and the storage address for the received account identity description information is returned to the blockchain.

The above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The recorded technical solutions are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the application, and should be included in the application. within the scope of protection.

Claims

An account inquiry system, wherein the system includes: a first blockchain, a second blockchain, a first cross-chain gateway, a second cross-chain gateway and a relay chain, the first blockchain is The first cross-chain gateway is communicatively connected to the relay chain, and the second blockchain is communicatively connected to the relay chain through the second cross-chain gateway, wherein,

The first blockchain is used 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 the query request on the second blockchain. Account ID of the account to be checked;

The relay chain is used to receive the cross-chain account query request, and search for the identity record information where the account identifier is located from the cross-chain identity record information table pre-stored in the relay chain, wherein the The identity record information in the cross-chain identity record information table includes an account identifier and a storage address for storing account identity description information of the account marked by the account identifier; in response to finding the identity record information where the account identifier is located, the A cross-chain gateway sends the found identity record information to the first blockchain;

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

The first cross-chain gateway is used to obtain the account identity description information of the account to be checked on the second blockchain according to the received storage address, and send the obtained account identity description information to the first blockchain. The block chain is sent, so that the first block chain performs identity authentication on the account to be checked on the second block chain based on the acquired account identity description information.
The account inquiry system according to claim 1, wherein,

The first blockchain is further configured to, in response to receiving a local-chain account query request sent by the user terminal where the local-chain account is located, for querying the account to be checked on the first blockchain, from the first blockchain. In an identity record information table of this chain pre-stored in the blockchain, look up the identity record information where the account identifier of the account to be checked is located, and send the storage address in the found identity record information to the first cross-chain gateway, Wherein, the on-chain account query request includes the account identifier of the account to be checked, and the identity record information in the on-chain identity record information table includes the account identifier and the storage address for storing the account identity description information of the account marked by the account identifier;

The first cross-chain gateway is further configured to obtain the account identity description information of the 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. a blockchain send;

The first blockchain is further configured to receive the account identity description information of the account to be checked on the first blockchain returned by the first cross-chain gateway, and send the received account identity description information to the sent by the user terminal.
The account inquiry system according to claim 1, wherein,

The relay chain is further configured to respond to a local chain account query request sent by the first blockchain through the first cross-chain gateway and used to query the account to be checked on the relay chain , from the identity record information table of this chain pre-stored in the relay chain, look up the identity record information where the account identifier of the account to be checked on the relay chain is located; in response to finding the identity record information on the relay chain The identity record information where the account identifier of the account to be checked is located, and the found identity record information is sent to the first blockchain through the first cross-chain gateway;

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

The first cross-chain gateway is used to obtain the account identity description information of the account to be checked on the relay chain according to the received storage address, and send the obtained account identity description information to the first block. Chain transmission, so that the first block chain performs identity authentication on the account to be checked on the relay chain based on the acquired account identity description information.
The account inquiry system according to claim 2, wherein the system further comprises at least one storage server, and the first blockchain realizes pre-storing the identity record information table of this chain by executing a construction step, and the construction step includes:

In response to receiving the identity registration request sent by the user terminal where the account of this chain is located, including the account identification and account identity description information of the account of this chain, describe the data storage type of the first blockchain and the account identity of the account of this chain. Sending the information to the first cross-chain gateway, so that the first cross-chain gateway stores the account identity description information of the account on this chain to a storage server that matches the data storage type;

Receive the storage address returned by the first cross-chain gateway for the account identity description information of the account on this chain;

Store the entirety of the account identifier of the account on this chain, the storage address, the hash value of the account identity description information of the account in this chain, and the account status parameter whose value is the first preset value as the identity record information in the identity record of this chain The information table, wherein the first preset value is used to indicate that the account of this chain is currently in a registration pending state.
The account inquiry system according to claim 4, wherein the constructing step further comprises:

Perform a preset audit operation on the identity record information whose value of the corresponding account status parameter in the identity record information table of this chain is the first preset value to obtain audit result information, and when the audit result information indicates that the audit is passed, the corresponding identity The value of the account status parameter in the record information is modified to a second preset value, wherein the second preset value is used to indicate that the account is currently in an approved state.
The account inquiry system according to claim 4, wherein the constructing step further comprises:

In response to receiving the identity update request sent by the user terminal where the account of this chain is located, including the account identification of the account of this chain and the description information of the new account identity, the data storage type of the first blockchain and the new account of the account of this chain are stored. The identity description information is sent to the first cross-chain gateway, so that the first cross-chain gateway stores the new account identity description information of the account on this chain to a storage server that matches the data storage type;

Receive the new storage address returned by the first cross-chain gateway for the new account identity description information of the account on this chain;

Modify the storage address in the identity record information corresponding to this chain 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 change the value of the account status parameter. The value is modified to a third preset value, wherein the third preset value is used to indicate that the account of this chain is currently in a state of update pending review.
The account inquiry system according to any one of claims 1-6, wherein the system further includes a third blockchain, and any one or more blockchains included in the system are pre-stored with this Chain identity record information table, the identity record information in this chain identity record information table includes the account identifier, the storage address used to store the account identity description information of the account marked by the account identifier, and the address used to indicate the account status of the account marked by the account identifier. account status parameters; and

The third blockchain is used to send a cross-chain account freezing request to the receiving chain, wherein the cross-chain account freezing request includes the account identifier of the account to be frozen and the chain identifier of the chain to be frozen, and the receiving chain includes the following: Any one or more of: the first blockchain, the second blockchain, the relay chain;

The receiving chain is used to receive the cross-chain account freezing request sent by the third blockchain; in the blockchain indicated by the chain ID of the chain to be frozen, the account ID of the account to be frozen is compared with the account ID of the account to be frozen The value of the corresponding account state parameter is modified to a fourth preset value, where the fourth preset value is used to indicate that the account to be frozen is currently in a frozen state.
The account inquiry system according to claim 7, wherein, 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 is set Modified to the fourth preset value, including:

The receiving chain, in response to determining that the chain identifier indicates that the receiving chain is the chain to be frozen and the blockchain where the account to be frozen is located is the receiving chain, obtains the identity record information of this chain pre-stored in the receiving chain In the table, look up the identity record information where the account identifier of the account to be frozen is located; and modify the value of the account status parameter in the found identity record information to a fourth preset value.
The account inquiry system according to claim 7, wherein, 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 is set Modified to the fourth preset value, including:

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

The direct sub-chain searches the identity record information where the account identifier of the account to be frozen is located from the identity record information table of the chain pre-stored in the direct sub-chain; The value is modified to the fourth preset value.
The account inquiry system according to claim 7, wherein, 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 is set Modified to the fourth preset value, including:

In response to determining that the chain identifier indicates that the receiving chain is a chain to be frozen and the blockchain where the account to be frozen is located is a direct sub-chain of the receiving chain, the receiving chain retrieves the cross-chain data pre-stored in the receiving chain. In the chain identity record information table, look up the identity record information where the account identifier of the account to be frozen is located, and modify the value of the account status parameter in the found identity record information to a fourth preset value; change the cross-chain account A freeze request is sent to the direct child chain;

The direct sub-chain searches the identity record information where the account identifier of the account to be frozen is located from the identity record information table of the chain pre-stored in the direct sub-chain; The value is modified to the fourth preset value.
The account inquiry system according to claim 7, wherein, 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 is set Modified to the fourth preset value, including:

The receiving chain, in response to determining that the chain identifier indicates that the receiving chain is a non-to-be-frozen chain and that the blockchain where the to-be-frozen account is located is a sidechain of the receiving chain, generates a chain corresponding to the to-be-frozen account. Identity record information, the generated identity record information is added to the cross-chain identity record information table of the receiving chain, wherein the value of the account status parameter in the generated identity record information is a fourth preset value.
The account inquiry system according to claim 7, wherein,

The first cross-chain gateway is further configured to cache the found identity record information returned by the relay chain for the cross-chain account query request; in response to receiving the first blockchain, send the For a cross-chain account query request, according to the storage address included in the cached identity record information, obtain the account identity description information of the account to be checked on the second blockchain, and send the obtained account identity description information to the first block chain. a blockchain send;

The first cross-chain gateway is further configured to cache the account status when the block chain 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 value of the parameter is the identity record information of the fourth preset value.
A cross-chain gateway, wherein the cross-chain gateway is respectively connected to a first blockchain and a relay chain in communication, the cross-chain gateway comprises: an information transmission unit and an information reading unit, wherein,

The information transfer unit is configured to forward the cross-chain account query request of the first blockchain to the relay chain, wherein the cross-chain account query request includes the account to be checked on the second blockchain forwarding the identity record information found by the relay chain for the cross-chain account query request to the first blockchain, where the identity record information includes the account identifier and the account identifier used to store the account marked by the account identifier. The storage address of account identity description information;

The information reading unit is configured to receive the storage address in the found identity record information sent by the first blockchain; obtain the storage address on the second blockchain according to the received storage address. The account identity description information of the account to be checked, and the obtained account identity description information is sent to the first blockchain, so that the first blockchain based on the obtained account identity description The account to be checked on the blockchain is authenticated.
The cross-chain gateway according to claim 13, wherein the cross-chain gateway further comprises an information storage unit, wherein,

The information storage unit is configured to, in response to receiving the data storage type and account identity description information sent by the first blockchain, store the received account identity description information to a storage server matching the data storage type, and Return the storage address for the received account identity description information to the blockchain.