CN112669036B

CN112669036B - Account management method, system, server and medium

Info

Publication number: CN112669036B
Application number: CN202011584948.8A
Authority: CN
Inventors: 李伟; 邱炜伟; 汪小益; 匡立中; 蔡亮; 楼嵩
Original assignee: Hangzhou Qulian Technology Co Ltd
Current assignee: Hangzhou Qulian Technology Co Ltd
Priority date: 2020-12-28
Filing date: 2020-12-28
Publication date: 2024-03-29
Anticipated expiration: 2040-12-28
Also published as: CN112669036A

Abstract

The application is applicable to the technical field of computers, and provides an account management method, which comprises the following steps: 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; modifying the value of an account state parameter corresponding to the account identifier of the account to be frozen into a first preset value in the blockchain indicated by the chain identifier of the chain to be frozen, wherein the account state parameter is used for indicating the account state of the account identified by the account identifier, and the first preset value is used for indicating that the account to be frozen is currently in the frozen state.

Description

Account management method, system, server and medium

Technical Field

The application belongs to the technical field of computers, and particularly relates to an account management method, an account management system, a server and a medium.

Background

The blockchain is a distributed shared ledger and database, and has the characteristics of decentralization, non-tampering, whole trace, traceability, collective maintenance, disclosure transparency and the like. The identity between blockchains may be interoperable, which generally refers to one of the blockchains being able to determine whether an account on the other blockchain is actually present.

In the related art, if an account of malicious operation exists on a certain blockchain among a plurality of blockchains with mutually-operable identities, the account may have adverse effects on other blockchains.

Disclosure of Invention

The embodiment of the application provides an account management method, an account management system, a server and a medium, which aim to solve the problem that in the related art, among a plurality of blockchains with mutually-operable identities, if an account with malicious operation exists on one blockchain, the account can cause bad influence on other blockchains.

In a first aspect, an embodiment of the present application provides an account management method, including:

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;

modifying the value of an account state parameter corresponding to the account identifier of the account to be frozen into a first preset value in the blockchain indicated by the chain identifier of the chain to be frozen, wherein the account state parameter is used for indicating the account state of the account identified by the account identifier, and the first preset value is used for indicating that the account to be frozen is currently in the frozen state.

In a second aspect, an embodiment of the present application provides an account management system, including: a request chain, a receive chain, wherein,

The request chain is used for sending a cross-chain account freezing request to the receiving chain, wherein the cross-chain account freezing request comprises an account identifier of an account to be frozen and a chain identifier of the chain to be frozen;

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

In a third aspect, an embodiment of the present application provides an account management apparatus, including:

the request receiving unit is used for 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;

the freezing execution unit is used for modifying the value of the account state parameter corresponding to the account identifier of the account to be frozen into a first preset value in the blockchain indicated by the chain identifier of the chain to be frozen, wherein the account state parameter is used for indicating the account state of the account identified by the account identifier, and the first preset value is used for indicating that the account to be frozen is currently in the frozen state.

In a fourth aspect, embodiments of the present application provide a server including a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the account management method described above when executing the computer program.

In a fifth aspect, embodiments of the present application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the account management method described above.

In a sixth aspect, embodiments of the present application provide a computer program product which, when run on a server, causes the server to perform the account management method of any one of the first aspects above.

Compared with the related art, the embodiment of the application has the beneficial effects that: the request chain may send a cross-chain account freeze request to the receive chain to effect cross-blockchain freezing of accounts. The method and the device are beneficial to timely initiating a freezing request aiming at an account when the account with malicious operation on a certain blockchain is found, so that the account is frozen timely, and the safety of other blockchains which can be communicated with the blockchain identity where the account is located is guaranteed.

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

Drawings

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

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

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

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

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

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

FIG. 6 is a schematic diagram of an account management device according to an embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

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

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

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

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

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

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

In order to explain the technical aspects of the present application, the following examples are presented.

Example 1

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

As shown in fig. 1, the system architecture may include blockchains C1, C2, C3, C4 and relay chains B1, B2, B3, B4. Where the relay chain is typically a special blockchain used to authenticate and transmit information to the connected blockchain. The connection relation between the block chains C1, C2, C3 and C4 and the relay chains B1, B2, B3 and B4 is in a tree structure, and the relay chain B2 and the relay chain B3 are leaf nodes of the relay chain B1. Blockchain C1 and blockchain C2 are leaf nodes of the relay chain B2. Blockchain C3 and relay chain B4 are leaf nodes of relay chain B3. Blockchain C4 is a leaf node of the relay chain B4. The relay chain B1 is an upper relay chain of the relay chains B2 and B3, and the relay chain B3 is an upper relay chain of the relay chain B4, and in practical application, the blockchains C1, C2, C3, and C4 may be application chains of different application scenarios.

For all relay chains in the tree structure, identity intercommunication among a plurality of leaf nodes of one relay chain, such as identity intercommunication among a blockchain C1 and a blockchain C2, can be realized. Identity intercommunication between leaf nodes of different relay chains can be achieved, for example, identity intercommunication between a block chain C1 and a block chain C3 can be achieved, intercommunication between a relay chain and a relay chain can be achieved, for example, a relay chain B2 and a relay chain B3, intercommunication between a leaf node and each relay chain node can be achieved, for example, a block chain C1 and a relay chain B2, a block chain C1 and a relay chain B3, a block chain C1 and a relay chain B1 and the like can be achieved.

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

In practice, for any two blockchains in a system, one blockchain may send a request to the other blockchain to freeze an account. For ease of description, one of the blockchains may be referred to as the request chain and the other blockchain as the receive chain. In practice, the request chain may include any one or more of the following: application chain, relay chain. And the receive chain may also include any one or more of: application chain, relay chain.

In practical application, the receiving chain may receive a cross-chain account freeze request sent by the request chain, where the cross-chain account freeze request includes an account identifier of an account to be frozen and a chain identifier of the chain to be frozen; modifying the value of an account state parameter corresponding to the account identifier of the account to be frozen into a first preset value in the blockchain indicated by the chain identifier of the chain to be frozen, wherein the account state parameter is used for indicating the account state of the account identified by the account identifier, and the first preset value is used for indicating that the account to be frozen is currently in the frozen state.

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

Example two

With continued reference to fig. 2, an embodiment of the present application provides an account management method, including:

step 201, a cross-chain account freeze request sent by a request chain is received.

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. Cross-chain account freeze requests are typically used to request that accounts on blockchains other than the subject blockchain be frozen. The chain to be frozen is typically a blockchain that needs to perform operations related to account freezing. Chain identification is typically information used to identify blockchains. As an example, the chain identity may be 001.

In practice, there are typically many blockchain accounts on each blockchain, with each blockchain account having a blockchain account address for that pair. For ease of description, the blockchain account may be referred to herein simply as an account.

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

In this embodiment, the execution subject of the account management method may be a receiving chain. The receive chain may be a general block chain or a relay chain. Where the relay chain is typically a special blockchain used to authenticate and transmit information to the connected blockchain. The execution body can receive a cross-chain account freezing request sent by a request chain through a network.

Step 202, modifying 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.

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

Here, the receiving chain may preset, for an account belonging to the receiving chain or not belonging to the receiving chain, a corresponding account status parameter for recording an account status of the corresponding account, where the account status parameter generally corresponds to an account identifier.

In this embodiment, when receiving a cross-link account freeze request sent by a request chain, a receiving chain may start to execute in a blockchain indicated by a chain identifier of a chain to be frozen, and modify a value of an account state parameter corresponding to the account identifier of the account to be frozen to a first preset value. Thus realizing freezing of the account to be frozen.

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

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

firstly, in response to determining that the chain identification indicates that the receiving chain is a chain to be frozen and the blockchain where the account to be frozen is located is the receiving chain, searching identity record information where the account identification of the account to be frozen is located from a chain identity record information table stored in the receiving chain in advance.

The identity record information in the identity record information table of the chain comprises an account identifier and account state parameters;

here, a home chain identity record information table for recording information about an account on the home chain may be stored in advance on each blockchain. The chain identity record information table is provided with a plurality of pieces of identity record information, and each piece of identity record information comprises an account identifier and account state parameters corresponding to the account identifier.

In this implementation manner, if the chain identifier in the cross-chain account freeze request is the same as the identifier of the receiving chain, it is determined that the receiving chain is the chain to be frozen. In addition, since account identification may generally indicate an account and the blockchain in which the account is located, the receive chain may determine, through the account identification, whether the blockchain in which the account is to be frozen is the receive chain. When the receiving chain is determined to be the chain to be frozen and the blockchain where the account to be frozen is located is determined to be the receiving chain, the receiving chain can adopt the account identifier of the account to be frozen, and the identity record information where the account identifier is located is found from the identity record information table of the receiving chain, so that the account state parameter in the identity record information is obtained.

And then, modifying the value of the account state parameter in the searched identity record information into a first preset value.

In this implementation manner, the executing body may directly modify the value of the account status parameter in the searched identity record information to a first preset value. Freezing the account on the receiving chain is achieved.

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

Example III

With continued reference to fig. 3, a schematic structural diagram of an account management system according to an embodiment of the present application is provided. The account management system shown in fig. 3, includes a request chain 301 and a receive chain 302, wherein,

a request chain 301 for sending a cross-chain account freeze request to a receiving chain. The cross-chain account freezing request comprises an account identifier of an account to be frozen and a chain identifier of a chain to be frozen.

A receiving chain 302, configured to receive a cross-chain account freeze request sent by the request chain; modifying the value of an account state parameter corresponding to the account identifier of the account to be frozen into a first preset value in the blockchain indicated by the chain identifier of the chain to be frozen, wherein the account state parameter is used for indicating the account state of the account identified by the account identifier, and the first preset value is used for indicating that the account to be frozen is currently in the frozen state.

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

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

It should be noted that, because the content of information interaction and execution process between the request chain and the receiving chain is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and details are not repeated herein.

In some alternative implementations of the present embodiment, the system further includes a direct-line sub-chain of the receive chain. At this time, in the blockchain indicated by the chain identifier of the chain to be frozen, modifying the value of the account status parameter corresponding to the account identifier of the account to be frozen to the first preset value may include:

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

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

Here, if the receiving chain is not the chain to be frozen and the blockchain in which the account to be frozen is the direct-chain of the receiving chain, the receiving chain may send the cross-chain account freeze request to the direct-chain subchain. In this way, the direct link sub-link can adopt the account identifier of the account to be frozen, find the identity record information of the account identifier from the identity record information table of the local link in the direct link sub-link, and modify the value of the account state parameter in the found identity record information to a first preset value. Freezing the account on the direct link of the receiving chain is realized.

It should be noted that, a local chain identity record information table for recording information about an account on the local chain may be stored in advance on each blockchain. The identity record information table of the present chain stored by each blockchain is provided with a plurality of pieces of identity record information, and each piece of identity record information comprises an account identifier and an account state parameter corresponding to the account identifier.

In the implementation manner, the request chain can send a cross-chain account freezing request to the receiving chain, so that the account on the direct-system subchain of the receiving chain is frozen, and the account can be frozen in a cross-block chain manner. The method and the device are beneficial to timely initiating a freezing request aiming at an account when the account with malicious operation on a certain blockchain is found, so that the account is frozen timely, and the safety of other blockchains which can be communicated with the blockchain identity where the account is located is further guaranteed.

In practice, if the receiving chain has a multi-stage direct-link sub-chain, the receiving chain can send a cross-chain account freezing request to the direct-link sub-chain where the account to be frozen is located in a step-by-step issuing mode. For example, in connection with fig. 1, if the receive chain is the relay chain B3, B3 there are two levels of direct-link subchains, where the first level of direct-link subchains is B4 and the second level of direct-link subchains is C4. At this time, if the account to be frozen is the account with the ID6 identified on the C4, the receiving chain may first send the cross-chain account freezing request to the primary direct-link sub-chain B4 of the receiving chain, then the B4 sends the cross-chain account freezing request to the secondary direct-link sub-chain C4 of the receiving chain, and finally the C4 freezes the account to be frozen. At this time, the C4 may use the account identifier ID6, find the identity record information where the account identifier ID6 is located from the local chain identity record information table of the C4, and modify the value of the account status parameter in the found identity record information to a first preset value. Freezing the account to be frozen is achieved.

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

Here, if the receiving chain is the chain to be frozen and the direct-link sub-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-chain of the receiving chain. And at this point there are two of the number of chain identifications in the cross-chain account freeze request. In practice, there may be multiple numbers of chain identifications in a cross-chain account freeze request.

In this implementation manner, the receiving chain may use the account identifier of the account to be frozen, find the identity record information where the account identifier is located from the cross-chain identity record information table in the receiving chain, and modify the account status parameter in the found identity record information to a first preset value. In addition, the receive chain may also send the cross-chain account freeze request to the immediate child chain. In this way, the direct link sub-link can adopt the account identifier of the account to be frozen, find the identity record information of the account identifier from the identity record information table of the local link in the direct link sub-link, and modify the value of the account state parameter in the found identity record information to a first preset value. The account to be frozen is frozen in the range of the receiving chain and the direct-connection subchain of the receiving chain.

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

In practice, for the same blockchain, if there is both a local chain identity record information table and a cross-chain identity record information table in the blockchain, the two tables can be combined into one large table.

In the implementation manner, the request chain can send a cross-chain account freezing request to the receiving chain, so that the account authority is frozen in the direct-system subchain range of the receiving chain and the receiving chain aiming at a certain account to be frozen, the freezing range of the account to be frozen can be controlled, and the safety of other blockchains which can be communicated with the blockchain identity where the account is located can be better guaranteed.

In practice, if the receiving chain has a multi-stage direct-link sub-chain, the receiving chain can send a cross-chain account freezing request to the direct-link sub-chain where the account to be frozen is located in a step-by-step issuing mode. For example, in connection with fig. 1, if the receive chain is the relay chain B3, B3 there are two levels of direct-link subchains, where the first level of direct-link subchains is B4 and the second level of direct-link subchains is C4. At this time, if the chains to be frozen are B3, B4, and C4, and the account to be frozen is the account on C4 identified as the account of ID 6. At this time, the receiving chain may find the identity record information corresponding to the 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 a first preset value. The receive chain then sends a cross-chain account freeze request to the receive chain's primary immediate child chain B4. Thus, B4 may 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 a cross-chain account freeze request to the secondary direct child chain C4 of the receive chain. In this way, the C4 may use the account identifier ID6, find the identity record information where the account identifier ID6 is located from the local chain identity record information table of the C4, and modify the value of the account status parameter in the found identity record information to a first preset value. Freezing the account to be frozen in the range of B3, B4 and C4 is achieved. In addition, it should be noted that, B3 sends the cross-chain account freeze request to C4 through B4, and compared with B3 sending the cross-chain account freeze request to B4 and C4 respectively, the number of times of sending the request by B3 can be reduced, which is helpful to save the computing resources of the high-level blockchain, thereby improving the overall data processing efficiency of the system.

It should be noted that if an account needs to be frozen in all the blockchain ranges included in the system, the request chain may send a cross-chain account freezing request to the blockchain with the highest hierarchy, where the request includes the chain identifiers of all the blockchains included in the system, i.e., all the blockchains included in the system are to-be-frozen chains.

In some alternative implementations of the present 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, modifying the value of the account status parameter corresponding to the account identifier of the account to be frozen to the first preset value may include:

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

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

Here, since there is typically no identity record information for the account in the synchronized side chain in the receive chain. In order to freeze the account to be frozen, the receiving chain can generate identity record information aiming at the identity identification of the account to be frozen, so that the account to be frozen is frozen in the range of the receiving chain. Here, the generated identity record information may include an account identifier and an account status parameter having a value of a 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 is usually null, and the hash value is usually null.

According to the implementation mode, the account on the side chain of the receiving chain can be frozen in the range of the receiving chain, and the account can be frozen in a cross-blockchain manner. The method and the device are beneficial to timely initiating a freezing request aiming at an account when the account with malicious operation on a certain blockchain is found, so that the account is frozen timely, and the safety of other blockchains which can be communicated with the blockchain identity where the account is located is further guaranteed.

In some optional implementations of this embodiment, searching identity record information of an account identifier of an account to be frozen from a local chain identity record information table stored in advance in a receiving chain includes: and in response to determining that the relation type between the request chain and the receiving chain is the first type, searching identity record information of an account identifier of the account to be frozen from a local chain identity record information table in the receiving chain. Wherein the first type is used to indicate that the request chain is an ancestor chain of the receive chain. And responding to the relationship types as other types except the first type, executing request auditing operation on the cross-chain account freezing request to obtain request auditing result information, and searching identity record information of an account identifier of the account to be frozen from a local chain identity record information table in a receiving chain when the request auditing result information indicates that auditing passes.

Where the request auditing operation is typically an operation for auditing a cross-chain account freeze request. The request audit result information is typically information indicating whether the audit is passed. In practice, the cross-chain account freeze request also typically includes a reason for freeze and evidence of freeze. The request audit operation may be: the blockchain as the receive chain controls all or part of the blockchain link points of the blockchain to perform the following steps: and analyzing the freezing reason and the freezing evidence, and if the freezing evidence is matched with the freezing reason, returning information for indicating that the audit passes to the blockchain. Otherwise, if the freezing evidence is not matched with the freezing reason, information for indicating that the audit is not passed is returned to the blockchain. Thus, the blockchain can count the number of the information indicating the passing of the audit, and if the number is larger than a first preset number threshold, the audit result information is requested to be the information for indicating the passing of the audit. And if the data is smaller than or equal to the first preset number threshold, requesting the auditing result information to be information for indicating that the auditing is not passed. It should be noted that the first preset number threshold is typically a preset value. The first preset number threshold is typically a positive integer.

Here, if the request chain is an ancestor chain of the receiving chain, the security of the request chain is generally considered to be high, and the receiving chain may directly perform the operation of searching the identity record information of the account identifier of the account to be frozen from the identity record information table of the receiving chain. Otherwise, if the request chain is not an ancestor chain of the receiving chain, at this time, the security of the request chain is generally considered to be not high enough, the receiving chain generally needs to audit the cross-chain account freezing request sent by the request chain, and if the audit is passed, the operation of searching the identity record information of the account identifier of the account to be frozen from the identity record information table of the receiving chain is executed.

In practice, the type of relationship between the request chain and the receive chain may include, but is not limited to, any one or more of the following: a first type of ancestor chain that indicates the request chain is the receive chain. A second type of ancestor chain that indicates the request chain as the receive chain. A third type of bystander chain that indicates that the request chain is a receive chain. A fourth type of paralog chain that indicates that the request chain is the receive chain. A fifth type for indicating that the request chain is a paralytic descendant chain of the receive chain.

In the implementation manner, when the request chain is not the ancestor chain of the receiving chain, the cross-chain account freezing request sent by the request chain is audited, so that the account can be prevented from being maliciously frozen, and the security of freezing the account to be frozen is ensured.

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

The cross-chain account freezing request comprises an account identifier of an account to be frozen and a chain identifier of a chain to be frozen.

The present chain account in this implementation is generally referred to as an account on the request chain. A user may log into an account on the blockchain through a user terminal.

Here, the request chain may receive a cross-chain account freeze request sent by a user terminal where the local chain account is located. The received cross-chain account freeze request is then sent to the receive chain. Freezing the account to be frozen through the receiving chain is achieved.

In some optional implementations of this embodiment, the system includes any one or more blockchains in which the local chain identity record information table is pre-stored. Any one or more blockchains included in the system are also used to:

And responding to a local chain account freezing request which is sent by a user terminal where the local chain account is located and comprises an account identifier of an account to be frozen, searching identity record information where the account identifier of the account to be frozen is located from a local chain identity record information table of the blockchain, and modifying the value of an account state parameter in the searched identity record information into a first preset value.

The chain account freezing request comprises an account identifier of an account to be frozen. The local chain account freeze request is typically used to request that accounts on the local blockchain be frozen.

Here, any blockchain may receive a local chain account freeze request sent by a user terminal where the local chain account is located. Then, the account identifier in the local chain account freezing request is adopted, and the identity record information where the account identifier is located is found in the local chain identity record information table stored in the block chain. And finally, modifying the account state parameter in the found identity record information into a first preset value to freeze the account on the chain.

In an alternative implementation of the various embodiments of the present application, the system further includes a storage server. The system includes one or several block chains with pre-stored identity record information list. The identity record information table of the chain in any one or more blockchains included in the system is obtained through the following construction steps.

Fig. 4 is a schematic flow chart of the construction steps provided in the embodiment of the present application. As shown in fig. 4, the build steps may include steps 401-403.

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

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

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

It should be noted that, the storage address of the account identity description information is stored in the present chain identity record information table, instead of storing the account identity description information itself, so that the storage space of the blockchain can be saved, and the present chain identity record information table can be simplified. It should be noted that the account identity description information of the accounts on each blockchain is stored in the same storage server, the account identity description information of each account is only stored once, and each blockchain can access the account identity description information of the accounts of all blockchains by accessing the storage address, so that the storage space of the whole blockchain network is saved.

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

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

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

And step 403, performing an identity verification operation on the identity record information with the value of the corresponding account state parameter in the identity record information table of the present chain as a second preset value to obtain identity verification result information, and modifying the value of the account state parameter in the corresponding identity record information to a third preset value when the identity verification result information indicates verification pass.

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

The identity verification operation may be an operation of verifying the account identity description information. Identity verification result information is typically information indicating whether verification is passed. In practice, the identity verification operation may be: the blockchain controls all or part of the blockchain link points of the blockchain to perform the following steps: and downloading the account identity description information by adopting a storage address in the identity record information. Then, a hash value of the downloaded identity description information is calculated. And finally, comparing the calculated hash value with the hash value in the identity record information, and if the hash value and the hash value are the same, returning audit passing indication information for indicating that the audit passes to the block chain, and if the hash value and the hash value are different, returning audit failing indication information for indicating that the audit fails to pass to the block chain. Thus, the blockchain can count the number of the auditing passing indication information, and if the number is larger than a second preset number threshold, the identity auditing result information is information for indicating that the auditing passes. If the data is smaller than or equal to the second preset number threshold, the identity verification result information is information for indicating that verification is not passed. It should be noted that the second preset number threshold is typically a preset value. The second preset number threshold is typically a positive integer. In practice, the first preset number threshold may be the same as or different from the second preset number threshold.

In this implementation, if the auditing result is that the auditing is passed, the blockchain may 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 for indicating that the account is currently in an audit passing state. If the auditing result is that the auditing is not passed, the blockchain can modify the value of the account state parameter in the corresponding identity record information into a fifth preset value. The fifth preset value is used for indicating that the account is currently in an audit reject state.

Here, if the account status is the audit passing status, the identity record information is considered valid.

It should be noted that if the blockchain has an upper relay chain, the blockchain may send the valid identity record information to the upper relay chain. In this way, the upper relay chain can update the cross-chain identity record information table by adopting the identity record information. Specifically, the upper relay chain may add the identity record information to the cross-chain identity record information table.

Example IV

With continued reference to fig. 5, a schematic structural diagram of an account management system according to an embodiment of the present application is provided. The account management system shown in fig. 5 includes a request chain 501 and a receive chain 502. Wherein,

The request chain 501 is further configured to send a cross-chain account thawing request to the receiving chain.

The cross-chain account thawing request comprises an account identifier of an account to be thawed and a chain identifier of a chain to be thawed.

Here, a cross-chain account defrost request is typically used to request that accounts on blockchains other than the present blockchain be defrosted. The chain to be thawed is typically a blockchain that needs to perform operations related to account thawing. Chain identification is typically information used to identify blockchains. As an example, the chain identity may be 001.

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 a cross-chain account thawing request sent by the request chain; and modifying the value of the account state parameter corresponding to the account identifier of the account to be defrosted into a fourth preset value in the blockchain indicated by the chain identifier of the chain to be defrosted.

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

Here, the receive chain 502 may be a general blockchain or a relay chain.

In this embodiment, the receiving chain may receive, through the network, a cross-chain account defrost request sent by the request chain. When a cross-chain account defrosting request is received, the receiving chain starts to execute in the blockchain indicated by the chain identification of the chain to be defrosted, and the value of the account state parameter corresponding to the account identification of the account to be defrosted is modified to a fourth preset value. And thawing the frozen account is realized.

According to the method provided by the embodiment, the request chain can send the cross-chain account defrosting request to the receiving chain, so that the account can be defrosted in a cross-block chain manner. The frozen account can be timely thawed, and the safety of other blockchains which can be communicated with the blockchain identity of the account can be further guaranteed.

It should be noted that the manner in which an account is defrosted is generally similar to the manner in which the account is frozen. Therefore, the present application does not make any further statement as to how to defrost the account.

Example five

Corresponding to the account management method of the above embodiments, fig. 6 shows a block diagram of an account management apparatus 600 provided in the embodiment of the present application, and for convenience of explanation, only a portion related to the embodiment of the present application is shown.

Referring to fig. 6, the apparatus includes:

a request receiving unit 601, configured to receive a cross-link account freeze request sent by a request chain, where the cross-link account freeze request includes an account identifier of an account to be frozen and a chain identifier of a chain to be frozen;

the freeze execution unit 602 is configured to modify, in a blockchain indicated by a chain identifier of a chain to be frozen, a value of an account status parameter corresponding to an account identifier of an account to be frozen to a first preset value, where the account status parameter is used to indicate an 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.

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

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

Example six

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 (only one processor is shown in fig. 7), 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. The steps of any of the various method embodiments described above are implemented by the processor 701 when executing the computer program 703. The processor 701, when executing the computer program 703, implements the steps of the embodiments of the various account management methods described above. The processor 701, when executing the computer program 703, implements the functions of the modules/units in the above-described device embodiments, such as the functions of the units 601 to 602 shown in fig. 6.

By way of example, the computer program 703 may be partitioned into one or more modules/units, which are stored in the memory 702 and executed by the processor 701 to complete the present application. One or more of the modules/units may be a series of computer program instruction segments capable of performing a specific function, which instruction segments describe the execution of the computer program 703 in the server 700. For example, the computer program 703 may be divided into a request receiving unit, a freeze execution unit, and specific functions of each unit are described in the above embodiments, which are not described herein.

The server 700 may be a computing device such as a server, desktop computer, tablet computer, cloud server, mobile terminal, and the like. The server 700 may include, but is not limited to, a processor 701, a memory 702. It will be appreciated by those skilled in the art that fig. 7 is merely an example of a server 700 and is not limiting of the server 700, and may include more or fewer components than shown, or may combine certain components, or different components, e.g., a server may also include input and output devices, network access devices, buses, etc.

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

The memory 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 plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the server 700. Further, the memory 702 may also include both internal storage units and external storage devices of the server 700. 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 output or is to be output.

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

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

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

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

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

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

The integrated modules, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, executable files or in some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the content of the computer readable medium can be appropriately increased or decreased according to the requirements of the jurisdiction's jurisdiction and the patent practice, for example, in some jurisdictions, the computer readable medium does not include electrical carrier signals and telecommunication signals according to the jurisdiction and the patent practice.

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

Claims

1. A method of account management applied to a receive chain, the method comprising:

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 the chain to be frozen comprises at least one of the following: the receiving chain, a direct-chain sub-chain of the receiving chain, and a side chain of the receiving chain;

modifying the value of an account state parameter corresponding to the account identifier of the account to be frozen into a first preset value in the blockchain indicated by the chain identifier of the chain to be frozen, wherein the account state parameter is used for indicating the account state of the 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.

2. The method of claim 1, wherein modifying, in the blockchain indicated by the chain identifier of the chain to be frozen, the value of the account status parameter corresponding to the account identifier of the account to be frozen to a first preset value, comprises:

in response to determining that the chain identification indicates that the receiving chain is a chain to be frozen and the blockchain where the account to be frozen is, searching identity record information where the account identification of the account to be frozen is located from a local chain identity record information table stored in the receiving chain in advance, wherein the identity record information in the local chain identity record information table comprises an account identification and account state parameters;

and modifying the value of the account state parameter in the searched identity record information into a first preset value.

3. An account management system, the system comprising: a request chain, a receive chain, wherein,

the request chain is configured to send a cross-chain account freeze request to the receiving chain, where the cross-chain account freeze request includes an account identifier of an account to be frozen and a chain identifier of a chain to be frozen, and the chain to be frozen includes at least one of the following: the receiving chain, a direct-chain sub-chain of the receiving chain, and a side chain of the receiving chain;

The receiving chain is used for receiving a cross-chain account freezing request sent by the request chain; modifying the value of an account state parameter corresponding to the account identifier of the account to be frozen into a first preset value in the blockchain indicated by the chain identifier of the chain to be frozen, wherein the account state parameter is used for indicating the account state of the 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.

4. The system of claim 3, wherein modifying 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 comprises:

the receiving chain searches identity record information of account identification of the account to be frozen from a pre-stored identity record information table of the chain, wherein the identity record information in the identity record information table of the chain comprises account identification and account state parameters; and modifying the value of the account state parameter in the searched identity record information into a first preset value.

5. A system according to claim 3, further comprising an immediate sub-chain of the receive chain; and modifying, in the blockchain indicated by the chain identifier of the chain to be frozen, a value of an account state parameter corresponding to the account identifier of the account to be frozen to a first preset value, where the modifying includes:

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

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

6. A system according to claim 3, further comprising an immediate sub-chain of the receive chain; and modifying, in the blockchain indicated by the chain identifier of the chain to be frozen, a value of an account state parameter corresponding to the account identifier of the account to be frozen to a first preset value, where the modifying includes:

The receiving chain searches identity record information of the account identifier of the account to be frozen from a pre-stored cross-chain identity record information table in the receiving chain in response to determining that the chain identifier indicates that the receiving chain is a chain to be frozen and that a blockchain where the account to be frozen is located is a direct-series sub-chain of the receiving chain, and modifies the value of an account state parameter in the searched identity record information into a first preset value; sending the cross-chain account freeze request to the direct-line child chain;

7. The system of claim 3, further comprising a side chain of the receive chain; and modifying, in the blockchain indicated by the chain identifier of the chain to be frozen, a value of an account state parameter corresponding to the account identifier of the account to be frozen to a first preset value, where the modifying includes:

the receiving chain generates identity record information corresponding to the account to be frozen in response to determining that the chain identification indicates that the receiving chain is a non-chain to be frozen and the blockchain where the account to be frozen is located is a side chain of the receiving chain, and adds the generated identity record information to a cross-chain identity record information table of the receiving chain, wherein the value of an account state parameter in the generated identity record information is a first preset value.

8. The system of claim 4, wherein the searching the identity record information of the account identifier of the account to be frozen from the local chain identity record information table stored in advance in the receiving chain includes:

in response to determining that the relationship type between the request chain and the receiving chain is a first type, searching identity record information of an account identifier of the account to be frozen from a local chain identity record information table in the receiving chain, wherein the first type is used for indicating that the request chain is an ancestor chain of the receiving chain;

and responding to the relationship type as other types except the first type, executing request auditing operation on the cross-chain account freezing request to obtain request auditing result information, and searching identity record information of the account identifier of the account to be frozen from a chain identity record information table in the receiving chain when the request auditing result information indicates that auditing is passed.

9. The system of claim 3, wherein the system includes any one or more blockchains having a table of local chain identity record information pre-stored therein, the system further including any one or more blockchains for:

10. The system of claim 3, wherein the system further comprises a controller configured to control the controller,

the request chain is further used for sending a cross-chain account defrosting request to the receiving chain, wherein the cross-chain account defrosting request comprises an account identifier of an account to be defrosted and a chain identifier of the chain to be defrosted;

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

11. The system according to any one of claims 3-10, further comprising a storage server, wherein the system includes any one or more blockchains in which a local chain identity record information table is pre-stored, and the system includes any one or more blockchains in which a local chain identity record information table is obtained through the following construction steps:

Responding to an identity registration request which is sent by a user terminal where a local chain account is located and comprises an account identifier and account identity description information of the local chain account, sending the account identity description information of the local chain account to a storage server, and receiving a storage address returned by the storage server for the account identity description information of the local chain account;

storing the account identifier of the present chain account, the storage address, the hash value of the account identity description information of the present chain account and the whole account state parameter with the value of a second preset value as identity record information into a present chain identity record information table, wherein the second preset value is used for indicating that the present chain account is in a registered to-be-checked state;

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

12. 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 method according to any of claims 1-2 when executing the computer program.

13. A computer readable storage medium storing a computer program, which when executed by a processor implements the method according to any one of claims 1-2.