WO2022140948A1

WO2022140948A1 - Account management method and system, and server and medium

Info

Publication number: WO2022140948A1
Application number: PCT/CN2020/140283
Authority: WO
Inventors: 李伟; 邱炜伟; 汪小益; 匡立中; 蔡亮
Original assignee: 杭州趣链科技有限公司
Priority date: 2020-12-28
Filing date: 2020-12-28
Publication date: 2022-07-07

Abstract

An account management method and system, and a server and a medium. The method comprises: receiving a cross-chain account freezing request sent by a request chain, wherein 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; and in a block chain indicated by the chain identifier of the chain to be frozen, modifying, to be a first preset value, the value of an account state parameter corresponding to the account identifier of the account to be frozen, wherein the account state parameter is used for indicating the account state of an account identified by the account identifier, and the first preset value is used for indicating that the account to be frozen is currently in a frozen state.

Description

Account management method, system, server and medium

technical field

The present application relates to the field of computer technology, and in particular, to an account management method, system, server and medium.

Background technique

Blockchain is a distributed shared ledger and database, which has the characteristics of decentralization, immutability, traceability, traceability, collective maintenance, openness and transparency. The interoperability of identities between blockchains usually means that one of the blockchains can determine whether the accounts on the other blockchains actually exist.

technical problem

One of the purposes of the embodiments of this application is to provide an account management method, system, server and medium, which aims to solve the problem that among multiple blockchains with interoperable identities in the related art, if a certain blockchain exists If the account is operated maliciously, the account may have a bad influence on other blockchains.

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 management method is provided, which includes: receiving a cross-chain account freezing request sent by a request chain, wherein the cross-chain account freezing request includes an account identifier of the account to be frozen and a chain identifier of the chain to be frozen; 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 to the first preset value, wherein the account status parameter is used to indicate that the account identifier identifies The account status of the account, the first preset value is used to indicate that the account to be frozen is currently in the frozen status.

In a second aspect, an account management system is provided, including a request chain and a receiving chain, wherein the request chain is used to send a cross-chain account freezing request to the receiving chain, wherein the cross-chain account freezing request includes the account freezing request of the to-be-frozen account. The account ID and the chain ID of the chain to be frozen; the receiving chain is used to receive the cross-chain account freezing request sent by the request chain; in the blockchain indicated by the chain ID of the chain to be frozen, it will correspond to the account ID of the account to be frozen The value of the account status parameter is modified to a first preset value, wherein the account status parameter is used to indicate the account status of the account identified by the account identifier, and the first preset value is used to indicate that the account to be frozen is currently in a frozen state.

In a third aspect, an account management device is provided, including a request receiving unit for receiving a cross-chain account freezing request sent by a request chain, wherein the cross-chain account freezing request includes an account identifier of the account to be frozen and a chain of the chain to be frozen Identifier; a freeze execution unit, used to modify the value of the account status parameter corresponding to the account identifier of the account to be frozen to a first preset value in the blockchain indicated by the chain identifier of the chain to be frozen, wherein the account The state parameter is used to indicate the account state of the account identified by the account identifier, and the first preset value is used to indicate that the account to be frozen is currently in a frozen state.

In a fourth aspect, a server is provided, including a memory, a processor, and a computer program stored in the memory and running on the processor, where the processor implements the steps of the above account management method when the computer program is executed.

In a fifth aspect, a computer-readable storage medium is provided, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the account management method are implemented.

beneficial effect

The beneficial effect of the present application is that the request chain can send a cross-chain account freezing request to the receiving chain, so as to realize the freezing of 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.

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 application of an account management method provided by an embodiment of the present application;

2 is a schematic flowchart of an account management method provided by an embodiment of the present application;

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

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

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

6 is a schematic structural diagram of an account management apparatus provided by an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a server 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 application of an account management method provided by an embodiment of the present application.

As shown in Figure 1, the system architecture can include blockchains C1, C2, C3, C4 and relay chains B1, B2, B3, B4. Among them, the relay chain is usually a special blockchain used to authenticate the connected blockchain and transmit information to the connected blockchain. The connection relationship between blockchains C1, C2, C3, C4 and relay chains B1, B2, B3, and B4 is in a tree-like structure. 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 the upper-level relay chain of relay chain B2 and relay chain B3, and relay chain B3 is the upper-level relay chain of relay chain B4. In practical applications, blockchains C1, C2, C3, C4 It can be the application chain of 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. It is also possible to realize identity intercommunication between leaf nodes of different relay chains, for example, identity intercommunication between blockchain C1 and blockchain C3, and intercommunication between relay chains and relay chains, such as, Relay chain B2 and relay chain B3, relay chain B1 and relay chain B2 can also realize the intercommunication between leaf nodes and relay chain nodes, such as blockchain C1 and relay chain B2, block chain C1 and relay chain B2. Chain 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, for any two blockchains in the system, one blockchain can send a request to freeze an account to the other blockchain. In order to facilitate the distinguishing description, one of the blockchains can be called the request chain, and the other blockchain is called the receiving chain. In practice, the request chain can include any one or more of the following: application chain, relay chain. And the receiving chain can also include any one or more of the following: application chain, relay chain. In practical applications, the receiving chain can receive the cross-chain account freezing request sent by the requesting chain; in the blockchain indicated by the chain ID of the chain to be frozen, the value of the account status parameter corresponding to the account ID of the account to be frozen is modified. is a first preset value, and the first preset value is used to indicate that the account to be frozen is currently in a frozen state.

Embodiment 2

Continuing to refer to FIG. 2, an embodiment of the present application provides an account management method, including:

Step 201: Receive a cross-chain account freezing request sent by the request 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. 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.

In practice, each blockchain usually has many blockchain accounts, and each blockchain account corresponds to a 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 execution subject of the above account management method may be a receiving chain. The receiving chain can be a general blockchain or a relay chain. The above execution subject can receive the cross-chain account freezing request sent by the request chain through the network.

Step 202 , in the blockchain indicated by the chain identifier of the chain to be frozen, modify the value of the account status parameter corresponding to the account identifier of the account to be frozen to a first preset value.

The account state parameter is used to indicate the account state of the account identified by the account identifier, and the first preset value is used to indicate that the account to be frozen is currently in a frozen state.

Here, the receiving chain may preset corresponding account status parameters for accounts belonging to the receiving chain or not belonging to the receiving chain to record the account status of the corresponding account, and the account status parameters usually correspond to account identifiers.

In this embodiment, when receiving the cross-chain account freezing request sent by the requesting chain, the receiving chain may start to execute the request in the blockchain indicated by the chain identifier of the chain to be frozen, and store the account identifier corresponding to the account to be frozen. The value of the account status parameter is modified to the first preset value. In this way, the account to be frozen is frozen.

In the method provided in this embodiment, the requesting chain can send a cross-chain account freezing request to the receiving chain, so as to realize the freezing of 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 to the first preset value values, including:

First, in response to determining that the chain identifier indicates that the receiving chain is the chain to be frozen and that the blockchain where the account to be frozen is located is the receiving chain, find the identity of the account identifier of the account to be frozen from the identity record information table of this chain pre-stored in the receiving chain record information.

Among them, the identity record information in the identity record information table of this chain includes account identification and account status parameters.

Here, each block chain may be pre-stored with a local chain identity record information table for recording the relevant information of the accounts on this chain. There are multiple pieces of identity record information in the identity record information table of this chain, and each piece of identity record information includes an account ID and account status parameters corresponding to the account ID.

In this implementation manner, if the chain ID in the cross-chain account freezing request is the same as the ID of the receiving chain, it is determined that the receiving chain is the chain to be frozen. In addition, since the account identifier can usually indicate the account and the blockchain where the account is located, the receiving chain can determine whether the blockchain where the account to be frozen is located is the receiving chain through the account identifier. When it is determined 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, the receiving chain can use the account identifier of the account to be frozen, and find the location where the account identifier is located from the identity record information table of this chain of the receiving chain. identity record information, so as to obtain account status parameters in the identity record information.

Then, the value of the account status parameter in the found identity record information is modified to the first preset value.

In this implementation manner, the above-mentioned execution body may directly modify the value of the account status parameter in the found identity record information to the first preset value. Realize the freezing of accounts on the receiving chain.

In this implementation manner, the request chain can send a cross-chain account freezing request to the receiving chain to freeze the account on the receiving chain.

Embodiment 3

Continue to refer to FIG. 3 , which is a schematic structural diagram of an account management system provided by an embodiment of the present application. The account management system shown in FIG. 3 includes a request chain 301 and a receiving chain 302, wherein,

The request chain 301 is 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 302 is used for receiving the cross-chain account freezing request sent by the request chain; 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 as The first preset value, wherein the account status parameter is used to indicate the account status of the account identified by the account identifier, and the first 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 requesting chain can send a cross-chain account freezing request to the receiving chain, so as to realize the freezing of 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 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, the receiving chain searches for the identity of the account identifier of the account to be frozen from the identity record information table of the chain pre-stored in the receiving chain record information, wherein the identity record information in the identity record information table of this chain includes account identification and account status parameters; modify the value of the account status parameter in the found identity record information to a first preset value.

It should be noted that the information exchange, execution process and other contents between the above request chain and the above receiving chain are based on the same concept as the method embodiments of the present application, and the specific functions and technical effects brought by them can be found in the method implementation for details. The example part will not be repeated here.

In some optional implementations of this embodiment, the system further includes a direct sub-chain of the receiving chain. At this time, 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 to the first preset value, which may include:

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 account to be frozen is located is a direct sub-chain of the receiving chain, sends the cross-chain account freezing request to the direct sub-chain.

The direct sub-chain searches the identity record information of the account ID of the account to be frozen from the identity record information table of the chain pre-stored in the direct sub-chain; modifies the value of the account status parameter in the found identity record information to the first default value.

Here, if the receiving chain is not 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, the receiving chain can send the cross-chain account freezing request to the direct sub-chain. In this way, the direct sub-chain can use the account identifier of the account to be frozen, look up the identity record information where the account identifier is located from the identity record information table of this chain in the direct sub-chain, and find the account status parameter in the found identity record information. The value of is modified to the first preset value. Realize the freezing of accounts on the direct sub-chain of the receiving chain.

In this implementation manner, the request chain can send a cross-chain account freezing request to the receiving chain, so as to freeze the account on the direct sub-chain of the receiving chain.

In practice, if there are multi-level direct sub-chains in the above receiving chain, the receiving chain can send the cross-chain account freezing request to the direct sub-chain where the account to be frozen is located by delivering it step by step.

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 a direct sub-chain of the receiving chain, the receiving chain searches the cross-chain identity record information table pre-stored in the receiving chain to find the account of the to-be-frozen account. For the identity record information where the account identifier is located, the value of the account status parameter in the found identity record information is modified to the first preset value; the cross-chain account freezing request is sent to the immediate sub-chain.

Here, if the receiving chain is the chain to be frozen, and the direct child chain of the receiving chain is the blockchain where the account to be frozen is located. At this time, the chain to be frozen is the receiving chain and the direct child chain of the receiving chain. And at this time, the number of chain IDs in the cross-chain account freeze request is two. In practice, there can be multiple chain identifiers in the cross-chain account freezing request.

In this implementation, the receiving chain can use the account identifier of the account to be frozen, and find the identity record information where the account identifier is located from the cross-chain identity record information table in the receiving chain, and the account status in the identity record information to be found. The parameter is modified to the first preset value. In addition, the receiving chain can also send the cross-chain account freezing request to the immediate sub-chain. In this way, the direct sub-chain can use the account identifier of the account to be frozen, look up the identity record information where the account identifier is located from the identity record information table of this chain in the direct sub-chain, and find the account status parameter in the found identity record information. The value of is modified to the first preset value. 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 addition, it should be pointed out that each block chain may be pre-stored with a local chain identity record information table used to record relevant information of accounts on this chain. 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 practice, for the same blockchain, if the blockchain has both a local-chain identity record information table and a cross-chain identity record information table, the two tables can usually be combined into one large table.

In this implementation, the request chain can send a cross-chain account freezing request to the receiving chain, so that for a certain account to be frozen, the account authority can be frozen in the scope of the receiving chain and the direct sub-chain of the receiving chain, so as to control the account to be frozen. The freezing range of the account will help to better ensure the security of other blockchains that can communicate with the identity of the blockchain where the account is located.

In practice, if there are multi-level direct sub-chains in the above receiving chain, the receiving chain can send the cross-chain account freezing request to the direct sub-chain where the account to be frozen is located by delivering it step by step. For example, referring to FIG. 1 , if the receiving chain is the relay chain B3, B3 has two levels of straight sub-chains, wherein the first-level straight sub-chain is B4, and the second-level straight sub-chain is C4. At this time, if the chain to be frozen is B3, B4 and C4, and the account to be frozen is the account with ID6 on C4. At this time, the receiving chain can first find the identity record information corresponding to ID6 in the cross-chain identity record information table in B3, and modify the value of the account status parameter in the found identity record information to the first preset value. Then, the receiving chain sends the cross-chain account freezing request to the first-level direct sub-chain B4 of the receiving chain. In this way, B4 can find the identity record information corresponding to ID6 from the cross-chain identity record information table in B4, and modify the value of the account status parameter in the found identity record information to the first preset value. Finally, B4 sends the cross-chain account freeze request to the second-level direct sub-chain C4 of the receiving chain. In this way, C4 can use the account identifier ID6 to find the identity record information where the account identifier ID6 is located from the identity record information table of the chain of C4, and modify the value of the account status parameter in the found identity record information to be The first preset value. Realize the freezing of accounts to be frozen within the scope of B3, B4, and C4. In addition, it should be pointed out that B3 sends the cross-chain account freeze request to C4 through B4. Compared with B3 sending the cross-chain account freeze request to B4 and C4 respectively, it can reduce the number of requests sent by B3 and help save high-level The computing resources of the high-level blockchain can be improved, thereby improving the overall data processing efficiency of the system.

It should be pointed out that if an account needs to be frozen within the scope of all the blockchains included in the system, the request chain can send a cross-chain account freezing request to the blockchain with the highest level, and the request includes the system Chain identifiers of all included blockchains, that is, all blockchains included in the system are chains to be frozen.

In some optional implementations of this embodiment, the system further includes a side chain of the receive chain. At this time, 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 to the first preset value, which may include:

The receiving chain generates identity record information corresponding to the account to be frozen, and adds the generated identity record information 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 side chain of the receiving chain. 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 the first preset value.

Here, the identity record information of the accounts in the synchronization sidechain is usually not synchronized in the receiving 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 first 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.

In some optional implementations of this embodiment, searching for 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 receiving chain includes: in response to determining the request chain and the receiving chain The relationship type between them is the first type. From the identity record information table of this chain in the receiving chain, find the identity record information of the account identifier of the account to be frozen. Among them, the first type is used to indicate that the request chain is the immediate predecessor chain of the receiving chain. In response to the relationship type being other than the first type, perform the request review operation on the cross-chain account freezing request, obtain the request review result information, and when the request review result information indicates that the review is passed, the identity of the chain in the receiving chain is obtained. In the record information table, find the identity record information of the account ID of the account to be frozen.

Among them, the request audit operation is usually an operation used to audit the cross-chain account freezing request. The request audit result information is usually information used to indicate whether the audit is passed or not. In practice, the cross-chain account freezing request usually also includes the freezing reason and freezing evidence. The request review operation can be: the blockchain as the receiving chain controls all or part of the blockchain nodes of the blockchain to perform the following steps: analyze the freezing reason and freezing evidence, and if the freezing evidence matches the freezing reason, report to the district The blockchain returns information that indicates approval. Conversely, if the freezing evidence does not match the freezing reason, the information indicating the failure of the audit will be returned to the blockchain. In this way, the blockchain can count the number of information indicating that the audit has passed, and if the number is greater than the first preset number threshold, the requested audit result information is the information used to indicate that the audit has passed. If the data is less than or equal to the first preset number threshold, the request audit result information is information used to indicate that the audit fails. It should be noted that the first preset number threshold is usually a preset value. The first preset number threshold is usually a positive integer.

Here, if the request chain is the immediate predecessor chain of the receiving chain, at this time, it is generally considered that the security of the request chain is high, and the receiving chain can directly perform the search for the account of the account to be frozen from the identity record information table of this chain in the receiving chain. An action that identifies the information on the identity record in which it resides. Conversely, if the request chain is not a direct predecessor chain of the receiving chain, at this time, it is generally considered that the security of the request chain is not high enough, and the receiving chain usually needs to review the cross-chain account freezing request sent by the request chain first. Execute the operation of finding the identity record information of the account ID of the account to be frozen from the identity record information table of this chain in the receiving chain.

In practical applications, the relationship types between the request chain and the receive chain may include but are not limited to any one or more of the following: the first type used to indicate that the request chain is the immediate predecessor chain of the receive chain. The second type used to indicate that the requesting chain is the immediate descendant of the receiving chain. A third type of collateral predecessor chain used to indicate that the requesting chain is the receiving chain. A fourth type of collateral sibling chain used to indicate that the requesting chain is the receiving chain. A fifth type used to indicate that the requesting chain is a collateral descendant of the receiving chain.

In this implementation, when the request chain is not a direct predecessor chain of the receiving chain, the cross-chain account freezing request sent by the request chain is reviewed, which can prevent the account from being maliciously frozen, thereby ensuring the security of freezing the account to be frozen.

In some optional implementations of this embodiment, in the request chain, sending a cross-chain account freezing request to the receiving chain includes: in response to receiving the cross-chain account freezing request sent by the user terminal where the account of this chain is located, sending a request to the receiving chain to freeze the cross-chain account. Send a cross-chain account freeze request.

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 local chain account in this implementation usually refers to the account on the request chain. Users can log in to the account on the blockchain through the user terminal. Here, the request chain can receive the cross-chain account freezing request sent by the user terminal where the account of this chain is located. Then, send the received cross-chain account freezing request to the receiving chain. Realize the freezing of the account to be frozen through the receiving chain.

In some optional implementation manners of this embodiment, any one or more blockchains included in the system are pre-stored with an identity record information table of this chain. Any one or more blockchains included in the system are also used for: in response to receiving a request to freeze the account of this chain sent by the user terminal where the account of this chain is located, including the account identifier of the account to be frozen, from the local chain of the blockchain. Find the identity record information of the account identifier of the account to be frozen in the chain identity record information table, and modify the value of the account status parameter in the found identity record information to the first preset value.

Among them, the account freezing request of this chain includes the account identifier of the account to be frozen. This chain account freezing request is usually used to request to freeze an account on this blockchain. Here, any blockchain can receive the request to freeze the account of this chain sent by the user terminal where the account of this chain is located. Then, using the account identifier in the account freezing request of this chain, find the identity record information where the account identifier is located from the identity record information table of this chain stored in the blockchain. Finally, the account status parameter in the found identity record information is modified to the first preset value to freeze the account on the chain.

In an optional implementation manner of each embodiment of the present application, the system further includes a storage server. Any one or more blockchains included in the system are pre-stored with the identity record information table of this chain. The identity record information table of this chain in any one or more blockchains included in the system is obtained through the following construction steps.

FIG. 4 is a schematic flowchart of construction steps provided in an embodiment of the present application. As shown in Figure 4, the building steps may include steps 401-403.

Step 401, in response to receiving the identity registration request sent by the user terminal where the account of this chain is located, including the account identifier of the account of this chain and the description information of the account identity, send the account identity description information of the account of this chain to the storage server, and receive the storage server. The storage address returned by the server for the account identity description information of the account in this chain.

Wherein, the above-mentioned identity registration request is usually information for requesting registration. The above-mentioned storage server is generally a server for storing data. The above account identity description information is usually information used to describe the 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, 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.

Here, if the blockchain receives the identity registration request sent by the account of this chain, the blockchain can send the account identity description information in the identity registration request to the storage server. In this way, the storage server can store the account identity description information in the identity registration request, and can return the storage address of the account identity description information to the blockchain.

It should be pointed out that storing the storage address of the account identity description information in the identity record information table of this chain, rather than storing the account identity description information itself, can save the storage space of the blockchain and simplify the identity record information table of the chain. It should be pointed out that the account identity description information of accounts on each blockchain is stored in the same storage server, and the account identity description information of each account only needs to be stored once, and each blockchain can be accessed by accessing the storage address. The account identity description information of accounts in all blockchains helps to save the storage space of the entire blockchain network.

Step 402, 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 second preset value as the identity record information into the identity of this chain. Record information sheet.

Among them, the second preset value is used to indicate that the account of this chain is currently in the state of registration pending review. Here, the blockchain can store account identification, storage address, hash value of account identity description information, and account status parameters as a piece of identity record information in the identity record information table of the blockchain.

Step 403: Perform an identity audit operation on the identity record information whose value of the corresponding account status parameter in the identity record information table of the current chain is the second preset value to obtain the identity audit result information, and when the identity audit result information indicates that the audit is passed, The value of the account status parameter in the corresponding identity record information is modified to a third preset value.

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

Wherein, the above-mentioned identity auditing operation may be an operation of auditing account identity description information. The identity audit result information is usually information used to indicate whether the audit is passed or not. In practice, the above-mentioned identity verification 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, compare the calculated hash value with the hash value in the identity record information. If the two are the same, return the approval information indicating the approval to the blockchain. If the two are different, send it to the blockchain. The blockchain returns the audit failure indication information used to indicate the failure of the audit. In this way, the blockchain can count the number of information indicating that the verification has passed, and if the number is greater than the second preset number threshold, the identity verification result information is information used to indicate that the verification has passed. If the data is less than or equal to the second preset number threshold, the identity verification result information is information used to indicate that the verification fails. It should be noted that the second preset number threshold is usually a preset value. The second preset number threshold is usually a positive integer. In practice, the first preset number threshold and the second preset number threshold may be the same or different.

In this implementation manner, if the audit result is approved, the blockchain can modify the value of the account status parameter in the corresponding identity record information to a third preset value. The third 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.

Here, if the account status is an approved status, it is considered that the identity record information is valid.

It should be pointed out that if the blockchain has an upper-level relay chain, the blockchain can send the valid identity record information to the upper-level relay chain. In this way, the upper relay chain can use the identity record information to update the cross-chain identity record information table. Specifically, the upper relay chain can add the identity record information to the cross-chain identity record information table.

Embodiment 4

Continue to refer to FIG. 5 , which is a schematic structural diagram of an account management system according to an embodiment of the present application. The account management system shown in FIG. 5 includes a request chain 501 and a receiving chain 502 . in,

The request chain 501 is also used to send a cross-chain account unfreezing request to the receiving chain.

The cross-chain account unfreezing request includes the account identifier of the account to be unfrozen and the chain identifier of the chain to be unfrozen. Here, the cross-chain account unfreeze request is usually used to request to unfreeze accounts on blockchains other than this blockchain. The unfreeze chain is usually the blockchain that needs to perform operations related to account unfreezing.

In this embodiment, the request chain 501 may be a general blockchain or a relay chain.

The receiving chain 502 is further configured to receive the cross-chain account unfreezing request sent by the request chain; in the blockchain indicated by the chain identifier of the chain to be unfrozen, modify the value of the account status parameter corresponding to the account identifier of the account to be unfrozen is the fourth preset value.

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

Here, the receiving chain 502 may be a general blockchain or a relay chain. In this embodiment, the receiving chain may receive the cross-chain account unfreezing request sent by the requesting chain through the network. When receiving a cross-chain account unfreezing request, the receiving chain starts executing in the blockchain indicated by the chain identifier of the chain to be unfrozen, and modifies the value of the account status parameter corresponding to the account identifier of the account to be unfrozen to the fourth preset set value. Realize the unfreezing of frozen accounts.

In the system provided by this embodiment, the request chain can send a cross-chain account unfreezing request to the receiving chain, so as to unfreeze the account across the blockchain. It can realize the unfreezing of the frozen account in time, which helps to further ensure the security of other blockchains that can communicate with the blockchain identity where the account is located.

It should be noted that the method of unfreezing an account is generally similar to the method of freezing the account. Therefore, this application does not make too many statements on how to unfreeze the account.

Embodiment 5

Corresponding to the account management method of the above embodiment, FIG. 6 shows a structural block diagram of the account management apparatus 600 provided by the embodiment of the present application. For convenience of description, only the part related to the embodiment of the present application is shown.

6 , the device includes: a request receiving unit 601 for receiving a cross-chain account freeze request sent by the request chain, wherein the cross-chain account freeze request includes the account identifier of the account to be frozen and the chain identifier of the chain to be frozen; freeze execution Unit 602, configured to modify, 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 a first preset value, wherein the account status parameter is a In order to indicate the account status of the account identified by the account identifier, the first preset value is used to indicate that the account to be frozen is currently in the frozen status.

In the device provided in this embodiment, the requesting chain can send a cross-chain account freezing request to the receiving chain, so as to freeze the account across the blockchain.

It should be noted that the information exchange, execution process and other contents between the above-mentioned devices/units are based on the same concept as the method embodiments of the present application. For specific functions and technical effects, please refer to the method embodiments section. It is not repeated here.

Embodiment 6

FIG. 7 is a schematic structural diagram of a server 700 according to an embodiment of the present application. As shown in FIG. 7 , the server 700 of this embodiment includes: at least one processor 701 , a memory 702 , and a computer program 703 , such as an account management program, stored in the memory 702 and executable on the at least one processor 701 . When the processor 701 executes the computer program 703, the steps in the above-mentioned embodiments of the various account management methods are implemented. When the processor 701 executes the computer program 703, the functions of the modules/units in the above device embodiments, for example, the functions of the units 601 to 602 shown in FIG. 6 are realized.

Exemplarily, the computer program 703 may be divided into one or more modules/units, and the one or more modules/units are stored in the memory 702 and executed by the processor 701 to complete the present application. One or more modules/units may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program 703 in the server 700 . For example, the computer program 703 may be divided into a request receiving unit and a freezing execution unit. The specific functions of each unit have been described in the above embodiments, and will not be repeated here.

The server 700 may be a computing device such as a server, a desktop computer, a tablet computer, a cloud server, and a mobile terminal. The server 700 may include, but is not limited to, a processor 701 and a memory 702 . Those skilled in the art can understand that FIG. 7 is only an example of the server 700, and does not constitute a limitation to the server 700. It may include more or less components than the one shown, or combine some components, or different components, such as The server may also include input and output devices, network access devices, buses, and the like.

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

The memory 702 may be an internal storage unit of the server 700 , such as a hard disk or a memory of the server 700 . The memory 702 may also be an external storage device of the server 700 , such as a pluggable hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, and a flash memory card (Flash Card) equipped on the server 700 . Wait. Further, the memory 702 may also include both an internal storage unit of the server 700 and an external storage device. The memory 702 is used to store computer programs and other programs and data required by the server. The memory 702 may also be used to temporarily store data that has been or will be output.

Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. Module completion means dividing the internal structure of the device into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment may be integrated in one processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit, and the above-mentioned integrated units may adopt hardware. It can also be realized in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing from each other, and are not used to limit the protection scope of the present application. For the specific working processes of the units and modules in the above-mentioned system, reference may be made to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the foregoing embodiments, the description of each embodiment has its own emphasis. For parts that are not described or described in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

In the embodiments provided in this application, it should be understood that the disclosed apparatus/server and method may be implemented in other manners. For example, the device/server embodiments described above are only illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be Incorporation may either be integrated into another system, or some features may be omitted, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated modules, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer-readable storage medium. Based on this understanding, this application can implement all or part of the processes in the methods of the above embodiments, and it can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can be When executed by the processor, the steps of the foregoing method embodiments may be implemented. Wherein, the computer program includes computer program code, and the computer program code may be in the form of source code, object code, executable file or some intermediate forms, and the like. Computer-readable media may include: any entity or device capable of carrying computer program code, recording media, USB flash drives, removable hard disks, magnetic disks, optical discs, computer memory, read-only memory (ROM, Read-Only Memory), random access Memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in computer-readable media may be appropriately increased or decreased in accordance with the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media does not include Electrical carrier signals and telecommunication signals.

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 management method, wherein the method comprises:

Receive a cross-chain account freezing request sent by the request chain, wherein 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;

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 to a first preset value, wherein the account status parameter is used for Indicates the account status of the account identified by the account identifier, and the first preset value is used to indicate that the account to be frozen is currently in a frozen status.
The method according to claim 1, wherein, in the blockchain indicated by the chain identifier of the to-be-frozen chain, the value of the account status parameter corresponding to the account identifier of the to-be-frozen account is modified to be The first preset value, including:

In response to determining that the chain identifier indicates that the receiving chain is the chain to be frozen and that the blockchain where the account to be frozen is located is the receiving chain, search for the identity record information table of this chain pre-stored in the receiving chain. The identity record information where the account identifier of the account to be frozen is located, wherein the identity record information in the identity record information table of this chain includes the account identifier and the account status parameter;

Modify the value of the account status parameter in the found identity record information to the first preset value.
An account management system, wherein the system includes: a request chain and a receiving chain, wherein,

The request chain 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;

The receiving chain is used to receive the cross-chain account freezing request sent by the request chain; in the blockchain indicated by the chain identifier of the chain to be frozen, the account corresponding to the account identifier of the account to be frozen is stored The value of the state parameter is modified to a first preset value, wherein the account state parameter is used to indicate the account state of the account identified by the account identifier, and the first preset value is used to indicate that the account to be frozen is currently frozen state.
The system according to claim 3, 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 modified as The first 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 of the account identifier of the account to be frozen, wherein the identity record information in the identity record information table of this chain includes the account identifier and account status parameters; The value of is modified to the first preset value.
The system according to claim 3, wherein the system further comprises a direct sub-chain of the receiving chain; The value of the account status parameter corresponding to the account identifier of the frozen account is modified to the first 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 first preset value.
The system according to claim 3, wherein the system further comprises a direct sub-chain of the receiving chain; The value of the account status parameter corresponding to the account identifier of the frozen account is modified to the first 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 the first preset value; change the cross-chain account A freeze request is sent to the immediate 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 first preset value.
The system according to claim 3, wherein the system further comprises a side chain of the receiving chain; The value of the account status parameter corresponding to the account identifier of the frozen account is modified to the first 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 first preset value.
The system according to claim 4, wherein, searching for the identity record information where the account identifier of the account to be frozen is located in the identity record information table of the current chain pre-stored in the receiving chain includes:

In response to determining that the relationship type between the request chain and the receiving chain is the first type, look up 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 in the receiving chain , wherein the first type is used to indicate that the request chain is a direct predecessor chain of the receive chain;

In response to the relationship type being a type other than the first type, perform a request review operation on the cross-chain account freezing request to obtain request review result information, and when the request review result information indicates that the review is passed, From the identity record information table of this chain in the receiving chain, look up the identity record information where the account identifier of the account to be frozen is located.
The system according to claim 3, wherein any one or more blockchains included in the system are pre-stored with an identity record information table of this chain, and any one or more blockchains included in the system Also used for:

In response to receiving the request to freeze the account of the chain that is sent by the user terminal where the account of the chain is located and includes the account identifier of the account to be frozen, find the account identifier of the account to be frozen from the identity record information table of the chain of the chain. identity record information, and modify the value of the account status parameter in the found identity record information to a first preset value.
The system of claim 3, wherein,

The request chain is further configured to send a cross-chain account unfreezing request to the receiving chain, wherein the cross-chain account unfreezing request includes the account identifier of the account to be unfrozen and the chain identifier of the chain to be unfrozen;

The receiving chain is also used to receive the cross-chain account unfreezing request sent by the request chain; in the blockchain indicated by the chain identifier of the chain to be unfrozen, the account identifier corresponding to the account to be unfrozen will be The value of the account status parameter is modified to a fourth preset value, wherein the fourth preset value is used to indicate that the account to be unfrozen is currently in the unfrozen state.
The system according to any one of claims 3-10, wherein the system further comprises a storage server, and any one or more blockchains included in the system are pre-stored with an identity record information table of this chain, The identity record information table of this chain in any one or more blockchains included in the system is obtained through the following construction steps:

In response to receiving the identity registration request including the account identification and account identity description information of the local chain account sent by the user terminal where the local chain account is located, sending the account identity description information of the local chain account to the storage server, and receiving the storage address returned by the storage server for the account identity description information of the account on this chain;

Store the entirety of the account identifier of the on-chain account, the storage address, the hash value of the account identity description information of the on-chain account, and the account status parameter whose value is the second preset value as the identity record information. On-chain identity record information table, wherein the second preset value is used to indicate that the on-chain account is currently in a registration pending state;

Perform the identity audit operation on the identity record information whose value of the corresponding account status parameter in the identity record information table of the chain is the second preset value, and obtain the identity audit result information, and when the identity audit result information indicates that the audit is passed, the corresponding The value of the account status parameter in the identity record information is modified to a third preset value, wherein the third preset value is used to indicate that the account is currently in a state of approval.
A server, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:

Receive a cross-chain account freezing request sent by the request chain, wherein 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;

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 to a first preset value, wherein the account status parameter is used for Indicates the account status of the account identified by the account identifier, and the first preset value is used to indicate that the account to be frozen is currently in a frozen status.
A computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, the following steps are implemented:

Receive a cross-chain account freezing request sent by the request chain, wherein 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;

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 to a first preset value, wherein the account status parameter is used for Indicates the account status of the account identified by the account identifier, and the first preset value is used to indicate that the account to be frozen is currently in a frozen status.
The computer-readable storage medium according to claim 13, wherein the computer program further implements the following steps when executed by the processor:

In response to determining that the chain identifier indicates that the receiving chain is the chain to be frozen and that the blockchain where the account to be frozen is located is the receiving chain, search for the identity record information table of this chain pre-stored in the receiving chain. The identity record information where the account identifier of the account to be frozen is located, wherein the identity record information in the identity record information table of this chain includes the account identifier and the account status parameter;

Modify the value of the account status parameter in the found identity record information to the first preset value.