Account management method, device, equipment and storage medium based on blockchain

Abstract

The present application provides a blockchain-based account management method, device, equipment and storage medium, which relates to the field of blockchain technology. The method includes: receiving a confirmation operation for a target sub-control group sent by a target management user account of a target contract account; wherein the target management user account is different from the original administrator user account of the target contract account; sending a recovery request to each user in the target sub-control group; the recovery request is used to apply for the recovery of the management authority of the target management user account over the target contract account; receiving the consent signature returned by each user in the target sub-control group, and verifying the consent signature; if the verification is passed, the management authority of the target management user account over the target contract account is determined. Compared with the prior art, it avoids the problem that the scale of the authority management group is difficult to determine, and there is a risk of authority recovery for the contract account.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and specifically, to a blockchain-based account management method, device, equipment and storage medium. Background Art

[0002] The contract account manages qualifications and identities through a contract, and users can use an administrator account to manage it. If the administrator account is lost, the administrator account of the contract account can be replaced by a certain method. After modifying the administrator account, the modified administrator account can be restored to control the contract account.

[0003] In the prior art, the method for restoring the administrator account of a contract account is: select a group of accounts as the authority management group corresponding to the administrator account, and when the number of signatures returned by each account in the authority management group to restore the administrator account is a certain proportion a of the signatures of the agreed signature, the administrator account of the account can be modified.

[0004] However, with this setting method, it is difficult to determine the size of the permission management group. If there are too many groups, there will be a risk of account loss and it will be difficult to manage. If there are too few groups, the risk cannot be dispersed. Summary of the invention

[0005] The purpose of this application is to provide a blockchain-based account management method, device, equipment and storage medium to address the deficiencies in the above-mentioned prior art, so as to solve the problem that the size of the authority management group is difficult to determine and there is a risk in the authority recovery of the contract account in the prior art.

[0006] To achieve the above purpose, the technical solution adopted in the embodiment of the present application is as follows:

[0007] In a first aspect, an embodiment of the present application provides a blockchain-based account management method, which is applied to any blockchain node of the blockchain, and the method includes:

[0008] Receive the confirmation operation for the target sub-control group sent by the management user of the target contract account;

[0009] Sending a restoration request to each user in the target sub-control group; the restoration request is used to apply for restoration of the management user's management authority over the target contract account;

[0010] Receiving consent signatures returned by each user in the target sub-control group, and verifying the consent signatures;

[0011] If the verification is successful, the management user's management rights over the target contract account are determined.

[0012] In a second aspect, another embodiment of the present application provides a blockchain-based account management device, the device comprising: a receiving module, a sending module and a recovery module, wherein:

[0013] The receiving module is used to receive a confirmation operation for the target sub-control group sent by the management user of the target contract account;

[0014] The sending module is used to send a recovery request to each user in the target sub-control group; the recovery request is used to apply for restoring the management authority of the management user to the target contract account;

[0015] The receiving module is specifically used to receive the consent signature returned by each user in the target sub-control group and verify the consent signature;

[0016] The recovery module is used to restore the management user's management rights over the target contract account if the verification is successful.

[0017] In the third aspect, another embodiment of the present application provides a blockchain-based account management device, comprising: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, when the blockchain-based account management device is running, the processor and the storage medium communicate through the bus, and the processor executes the machine-readable instructions to perform the steps of any method described in the first aspect above.

[0018] In a fourth aspect, another embodiment of the present application provides a storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of any method described in the first aspect are executed.

[0019] The beneficial effect of the present application is: by adopting the blockchain-based account management method provided by the present application, after the original administrator user account that manages the target contract account is lost or stolen, the target sub-control group can be determined through a new target management user account by a determination operation in the sub-control group, and a recovery request is sent to each user in the target sub-control group to restore the target management user account's management authority over the target contract account. After receiving the consent signature returned by each target user and verifying the consent signature, the target management user account's management authority over the target contract account is determined. This method of restoring the management authority of the target contract account is not only highly efficient, but also safe and convenient because the recovery decision is jointly determined based on multiple target users. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0021] Figure 1 A flowchart of a blockchain-based account management method provided in one embodiment of the present application;

[0022] Figure 2 A flowchart of a blockchain-based account management method provided in another embodiment of the present application;

[0023] Figure 3 A flowchart of a blockchain-based account management method provided in another embodiment of the present application;

[0024] Figure 4 A schematic diagram of the structure of a blockchain-based account management device provided in one embodiment of the present application;

[0025] Figure 5 A schematic diagram of the structure of a blockchain-based account management device provided in another embodiment of the present application;

[0026] Figure 6 A schematic diagram of the structure of a blockchain-based account management device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in combination with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments.

[0028] The components of the embodiments of the present application generally described and shown in the drawings herein may be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0029] In addition, the flowchart used in this application shows the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowchart can be implemented out of order, and the steps without logical context can be reversed in order or implemented simultaneously. In addition, those skilled in the art can add one or more other operations to the flowchart under the guidance of the content of this application, and can also remove one or more operations from the flowchart.

[0030] To facilitate understanding of this application, some terms involved in this application are explained as follows:

[0031] Address account: The address and private key are bound one by one, and the private key cannot be changed. Once lost, the user completely loses control of the address account and cannot recover.

[0032] Contract account (abstract account): also known as an abstract account, which manages qualifications and identities through a contract. Users can use an administrator account for management. An administrator account is an address account. If the administrator account is lost, the lost administrator account completely restores the control of the account and cannot be restored. However, in order to restore the control of the contract account, the administrator account of the contract account can be replaced by a certain method. After modifying the administrator account, the control and management of the contract account can be restored through the modified administrator account.

[0033] The following is an explanation of a blockchain-based account management method provided in an embodiment of the present application in combination with a number of specific application examples. Figure 1 A flowchart of a blockchain-based account management method provided in one embodiment of the present application is applied to any blockchain node of the blockchain, such as Figure 1 As shown, the method includes:

[0034] S101: Receive a confirmation operation for a target sub-control group sent by a target management user account of a target contract account.

[0035] Among them, the target management user account is a user who is different from the original administrator user of the target contract account; the application scenario of the present application is: after the original management user account of the target contract account loses the original management user account, if the management user still needs to restore the control authority over the target contract account, at this time, the management user is required to use a new target management user account that is different from the original management user account to rebind the relationship between the target management user account and the target contract account, and restore and determine the management authority of the target management user account over the target contract account, so as to realize the management and control of the target contract account by the management user.

[0036] In an embodiment of the present application, the target contract account may correspond to multiple sub-control groups, each sub-control group may include multiple users, and the multiple users are users who have social relationships with the management user; then, the management user can select a sub-control group as the target sub-control group from the multiple sub-control groups through the target management user account.

[0037] Such a target contract account can give the control of the management user account to as many users as possible by setting up multiple sub-control groups, thereby increasing the security when restoring the management rights of the target contract account; when it is necessary to restore the control rights of the target contract account, by selecting a target sub-control group from multiple sub-control groups, it can be achieved that only fewer users are involved when restoring the management rights of the target contract account, thereby enhancing the practicality of the recovery management process.

[0038] S102: Send a recovery request to each user in the target sub-control group.

[0039] The recovery request is used to apply for the restoration of the target management user account's management authority over the target contract account.

[0040] In an embodiment of the present application, a recovery request is, for example, jointly determined based on a target management user account and a current confirmation operation, and the content included in the recovery request may be, for example: identification information of the current recovery operation, and address information of the target management user account; wherein, the identification information of the recovery operation may be, for example, information on the number of times the target contract account is currently restored, or random unique identification information. It should be understood that the above embodiment is only an exemplary description, and the specific setting method of the identification information can be flexibly adjusted according to user needs, as long as it can uniquely indicate the current recovery operation.

[0041] S103: receiving consent signatures returned by each user in the target sub-control group, and verifying the consent signatures.

[0042] Among them, after receiving the signatures returned by all users in the target sub-control group, a common signature will be generated based on the signatures returned by all users; if the signatures returned by each user are all consent signatures, then the common signature is a consent signature; if there is at least one disagreement signature among the signatures returned by each user, then the common signature is determined to be a disagreement signature.

[0043] Therefore, after obtaining the joint signature, this application also needs to verify whether the joint signature is an approval signature. If the joint signature is an approval signature, the signature content in the approval signature and the signing user are further verified to determine whether the approval signature is verified.

[0044] S104: If the verification is successful, the management rights of the target management user account over the target contract account are determined.

[0045] If the verification is successful, the current target management user account is determined to be the management user account of the target contract account, and its management rights over the target contract account are restored. The restored management user account has management rights and control rights over the target contract account.

[0046] By adopting the blockchain-based account management method provided by the present application, after the original administrator user account that manages the target contract account is lost or stolen, a new target management user account can be used to determine the target sub-control group through a determination operation in the sub-control group, and a recovery request can be sent to each user in the target sub-control group to restore the management authority of the target management user account over the target contract account. After receiving the consent signature returned by each target user and verifying the consent signature, the management authority of the target management user account over the target contract account is determined. Since the recovery decision is determined based on multiple target users, this method of restoring the management authority of the target contract account not only has a high recovery efficiency, but also has a safe and convenient effect.

[0047] In an embodiment of the present application, in order to further ensure the security of use of the target contract account, after the target management user account successfully restores the management rights of the target contract account, the target sub-control group is deleted.

[0048] This setting method avoids the risk of collusion in which the same target sub-control group repeatedly restores or resets the management and control rights of the target contract account. Therefore, after the target sub-control group restores the management rights of the target contract account, the target sub-control group is deleted.

[0049] Optionally, based on the above embodiment, the embodiment of the present application may also provide a blockchain-based account management method. The implementation process of the above method is illustrated below in conjunction with the accompanying drawings. Figure 2 A flowchart of a blockchain-based account management method provided in another embodiment of the present application is shown in FIG. Figure 2 As shown, before S101, the method may further include:

[0050] S111: In response to an adding operation of a sub-control group triggered by a target management user account, a sub-control group is determined according to hash information of multiple users corresponding to the adding operation.

[0051] The information of the sub-control group includes: hash information of multiple users.

[0052] For example, in one embodiment of the present application, for example, the target management user account selects 9 users as the users corresponding to the sub-control group. At this time, the address information of each user in the sub-control group is hashed to obtain a group of hash values ​​H1, H2...H9. According to the group of hash values, the users corresponding to a group of sub-control groups can be uniquely determined. After selecting each user in the sub-control group and generating the hash value of the sub-control group, the group of hash values ​​is uploaded to the target contract account.

[0053] In an embodiment of the present application, a method for determining a sub-control group may be, for example: determining address information of multiple users corresponding to the selection operation according to a selection operation of an add operation in a social circle corresponding to at least two target management user accounts, and determining hash information corresponding to the multiple users respectively according to the address information of the multiple users; determining hash information corresponding to the sub-control group according to the hash information of the multiple users.

[0054] With this setting, since the users in the sub-control group are selected by the management user from different social circles, the possibility of intersection between the users is small. Therefore, the risk of collusion between the users in the sub-control group can be reduced, the security of the target contract account can be improved, and the security of the management and control rights of the target contract account can be restored.

[0055] Among them, the selection of each sub-control group is selected by the management user and kept confidential. Different social circles are divided according to the social relationships of the management user. In some possible embodiments, the social circles may include the following social circles: friends, classmates, relatives and friends, colleagues, partners, etc. It should be understood that the above embodiments are only exemplary descriptions, and the content included in the specific social circles can be flexibly adjusted according to user needs and is not limited to the above embodiments.

[0056] Taking a sub-control group including 6 users as an example, the users in a sub-control group may be composed of users in two social circles. When determining the sub-control group, the management user needs to select 3 users from the two social circles respectively to form a sub-control group; or, the management user may select 2 users from the three social circles respectively to form a sub-control group. It should be understood that the above embodiments are only exemplary descriptions, and the user only needs to select the users of the sub-control group in different social circles. The specific selection method and the number of people included in each sub-control group can be flexibly adjusted according to user needs and are not limited to the above embodiments.

[0057] In an embodiment of the present application, the number of users included in a sub-control group may be, for example, a preset number, that is, the number of users included in each sub-control group is the same, which is a preset number, wherein the preset number may be, for example, 6, or 8 or any integer; or it may be any number within a preset number range, that is, the number of users included in each sub-control group may be different, and the number of users is within a preset number range of users, wherein the preset range may be, for example, 3-9; it should be understood that the above embodiment is only an exemplary description, and the setting of the specific preset number and the setting of the preset number range may be flexibly adjusted according to user needs, and is not limited to the above embodiment; the target management user can control the size of each sub-user group by presetting a certain range of sub-control group user numbers, so that each sub-user group can avoid the difficult management caused by too many users in the sub-user group while achieving the purpose of dispersing risks, thereby improving the security and recoverability of the target contract account.

[0058] In one embodiment of the present application, for example, the social circles of the management user are divided into S1, S2, ..., Sn, and several users are selected from at least two social circles as sub-control group members U1, U2, ... Un, which are all sub-control groups corresponding to the target contract account preset by the user, wherein the members of the sub-control group may be distributed in different social circles. When setting up each sub-control group, the management user can select several accounts in different social circles, for example, 6 accounts can be selected as a sub-control group, and several sub-control groups (T1, T2, ..., Tm) can be obtained, and the hash groups corresponding to the several sub-control groups can be obtained respectively, (H1, H2, ..., Hm), and the user transfers the sub-control groups corresponding to each group of hash groups to the smart contract wallet of the target contract account for storage, and the storage format is as follows:

[0059] 1: hash1

[0060] 2: hash2

[0061] …

[0062] N:hashn

[0063] Among them, 1 corresponds to sub-control group T1, 2 corresponds to sub-control group T2, and so on. It should be understood that the above embodiments are only exemplary, and the specific way of storing each sub-control group can be flexibly adjusted according to user needs and is not limited to the above embodiments.

[0064] For example, H1=hash(U1, U2, ..., U6), where U1, U2, ..., U6 are users belonging to sub-control group T1. This setting method makes it possible to directly determine the users corresponding to each sub-control group based on the hash value of each sub-control group.

[0065] Optionally, based on the above embodiment, the embodiment of the present application can also provide a blockchain-based account management method. The implementation process of verifying the consent signature in the above method is illustrated as follows in combination with the accompanying drawings. Figure 3 A flowchart of a blockchain-based account management method provided in another embodiment of the present application is shown in FIG. Figure 3 As shown, S103 may include:

[0066] S121: Determine whether the number of signatures agreeing to sign is equal to the number of users corresponding to the target sub-control group.

[0067] That is, in the embodiment of the present application, it is necessary for each user in the target sub-control group to return a consent signature before it is determined that the number of consent signatures is equal to the number of users corresponding to the target sub-control group.

[0068] S122: Determine whether the users corresponding to the consent signature are users in the target sub-control group.

[0069] In the embodiments of the present application, the communication between blockchain nodes is explained by way of preset contract communication as an example. That is, in the embodiments of the present application, when the target management user account needs to restore the management authority over the target contract account, it needs to select a target sub-control group and send a recovery request to each user in the sub-control group. After receiving the recovery request, each user in the sub-control group signs separately, and generates a common signature based on the signature result, and sends it to the contract, so that the contract verifies the recovery request based on the common signature.

[0070] For example, take the target sub-control group k selected by the target management user account as an example. S1, ..., S6 are the signatures of the recovery request returned by each user in the target sub-control group k. At this time, the contract will verify the following information in the joint signature: verify whether the number of S1, ..., S6 in the returned joint signature is equal to the number of users corresponding to U1, ...U6 in the target sub-control group k; restore U1, ..., U6 through S1, ...S6, and take the hash of U1, ..., U6 to obtain hash(U1, U2, ..., U6) = hashv; if hashv = hashk, then it can be concluded that each user in the joint signature is the user selected by the user in the target sub-control group k, that is, if the number of users and the user identity in the joint signature are verified, it is determined that the management rights of the target contract account can be reset, and the management rights of the target management user account over the target contract account are determined.

[0071] In one embodiment of the present application, in order to further ensure the security of the target contract account, before restoring the target account's management rights over the target contract account, it is also necessary to receive the password information entered by the target management user account; determine whether the password information is the preset password of the target management user account; if so, determine that the verification is successful.

[0072] Among them, the preset password is a preset password set in advance by the management user, which can be stored in each sub-control group. When verifying the target management user account, in addition to verifying the number of signatures in the consent signature, it is also necessary to verify whether each user in the consent signature is a user in the target sub-control group, and it is also necessary to accept the password information entered by the target management account, and compare the received password information with the preset password set in advance by the management user and stored in the target sub-control group.

[0073] Only when all the above three verifications are passed, it is determined that the verification of the target management user account has passed; if at least one of the above three verifications fails, it is determined that the verification of the target management user account has failed, and a recovery failure instruction is returned to the target management user account. The target management user account can re-try to recover the management rights of the target contract account by reselecting the target sub-control group or re-sending the recovery request and password information to the target sub-control area; it should be understood that the above embodiment is only an exemplary description, and the specific operation when the management rights of the target contract account fail to be recovered can be flexibly adjusted according to user needs, and is not limited to the above embodiment.

[0074] In an embodiment of the present application, in order to further ensure the security of the target contract account's recovery authority, before restoring the target management user account's management rights over the target contract account, it is also necessary to determine whether the recovery identification information in the consent signature is consistent with the recovery identification information in the recovery request; if they are consistent, the verification is determined to be successful.

[0075] In some possible embodiments, the recovery identification information may be, for example, the number of times the management authority of the target contract account is currently restored. For example, if the management authority of the target contract account is currently restored for the sixth time, the recovery identification information may be set to 6; or, it may be random identification information, wherein each random identification information will not be randomly obtained in a subsequent random process when in use, that is, the random identification information will only be randomly obtained once. Such a setting method ensures that each consent signature can only be used once to restore the management authority of the target contract account, thereby avoiding the repeated use of the consent signature, which may cause security problems for the target contract account. It should be understood that the above embodiments are only exemplary descriptions, and the specific setting of the recovery identification information may be flexibly adjusted according to user needs, as long as it can uniquely identify the recovery operation, and is not limited to the above embodiments.

[0076] By adopting the blockchain-based account management method provided by the present application, since the target sub-control group is pre-configured for the management user and determined based on multiple social circles corresponding to the management user, the possibility of collusion among the users in the target sub-control group is relatively small; and during the verification process, not only the identification information of the recovery request will be verified, but also whether the number of signatures in the consent signature is equal to the number of users in the target sub-control group, and whether each signing user in the consent signature is a user in the target sub-control group, and the password information entered by the target administrator user account will be obtained and compared with the preset password. Only when the above verifications are passed, will it be determined that the verification of the current target management user account has passed, and the control and management rights of the target management user account over the target contract account will be restored. This setting method greatly improves the security of the target contract account and ensures the safety of users during use.

[0077] The following is an explanation of the blockchain-based account management device provided by the present application in conjunction with the accompanying drawings. The blockchain-based account management device can perform the above Figure 1-Figure 3 The specific implementation and beneficial effects of any blockchain-based account management method are as mentioned above and will not be repeated below.

[0078] Figure 4 A schematic diagram of the structure of a blockchain-based account management device provided in one embodiment of the present application, such as Figure 4 As shown, the device includes: a receiving module 201, a sending module 202 and a recovery module 203, wherein:

[0079] Receiving module 201, used to receive a confirmation operation for a target sub-control group sent by a target management user account of a target contract account;

[0080] The sending module 202 is used to send a recovery request to each user in the target sub-control group; the recovery request is used to apply for restoring the management authority of the target management user account to the target contract account;

[0081] The receiving module 201 is specifically used to receive the consent signature returned by each user in the target sub-control group and verify the consent signature;

[0082] The restoration module 203 is used to restore the management rights of the target management user account to the target contract account if the verification is successful.

[0083] Optionally, based on the above embodiment, the present application embodiment may also provide an account management device based on blockchain, as shown below in conjunction with the accompanying drawings. Figure 4 The implementation process of the given device is described by way of example. Figure 5 A schematic diagram of a blockchain-based account management device provided in another embodiment of the present application is shown in FIG. Figure 5 As shown, the device also includes: a determination module 204, which is used to respond to the sub-control group adding operation triggered by the target management user account, and determine the sub-control group according to the hash information of multiple users corresponding to the adding operation; wherein the sub-control group information includes: hash information of multiple users.

[0084] like Figure 5 As shown, the device further includes: a deleting module 205, which deletes the target sub-control group after the target management user account successfully recovers the management right of the target contract account.

[0085] Optionally, the determination module 204 is specifically used to determine whether the number of signatures of the consent signature is equal to the number of users corresponding to the target sub-control group; determine whether each user corresponding to the consent signature is each user in the target sub-control group.

[0086] Optionally, the receiving module 201 is specifically configured to receive password information input by a target management user account;

[0087] The determination module 204 is specifically used to determine whether the password information is the preset password of the target management user account; if so, it is determined that the verification is passed.

[0088] Optionally, the determination module 204 is specifically used to determine whether the recovery identification information in the consent signature is consistent with the recovery identification information in the recovery request; if they are consistent, it is determined that the verification is successful.

[0089] Optionally, the determination module 204 is specifically used to determine hash information of multiple users corresponding to the selection operation of the add operation in the social circles corresponding to at least two target management user accounts; and determine the sub-control group based on the hash information of the multiple users.

[0090] The above-mentioned device is used to execute the method provided by the aforementioned embodiment, and its implementation principle and technical effect are similar, which will not be repeated here.

[0091] The above modules may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASICs), or one or more microprocessors, or one or more field programmable gate arrays (FPGAs). For another example, when a module is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0092] Figure 6 A schematic diagram of the structure of a blockchain-based account management device provided in one embodiment of the present application. The blockchain-based account management device can be integrated into a terminal device or a chip of a terminal device.

[0093] like Figure 6 As shown, the blockchain-based account management device includes: a processor 501, a bus 502 and a storage medium 503.

[0094] The processor 501 is used to store programs. The processor 501 calls the program stored in the storage medium 503 to execute the above Figure 1-Figure 3 The corresponding method embodiment has similar specific implementation methods and technical effects, which will not be described here.

[0095] Optionally, the present application also provides a program product, such as a storage medium, on which a computer program is stored, including a program that, when executed by a processor, executes an embodiment corresponding to the above method.

[0096] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0097] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple 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.

[0098] 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 separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0099] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (English: processor) to perform some steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (English: Read-Only Memory, abbreviated: ROM), random access memory (English: Random Access Memory, abbreviated: RAM), disk or optical disk and other media that can store program codes.

Claims

1. A blockchain-based account management method, characterized in that: Applied to any blockchain node of a blockchain, the method comprises: Receiving a confirmation operation for a target sub-control group sent by a target management user account of a target contract account; wherein the target management user account is different from an original administrator user account of the target contract account; Sending a restoration request to each user in the target sub-control group; the restoration request is used to apply for restoration of the management authority of the target management user account over the target contract account; Receiving consent signatures returned by each user in the target sub-control group, and verifying the consent signatures; If the verification is successful, the management rights of the target management user account over the target contract account are determined; Before receiving the confirmation operation for the target sub-control group sent by the target management user account of the target contract account, the method further includes: In response to the adding operation of the sub-control group triggered by the target management user account, the sub-control group is determined according to the hash information of multiple users corresponding to the adding operation; wherein the information of the sub-control group includes: the hash information of the multiple users, and the multiple users in the sub-control group are users in different social circles of the target management user account; Before restoring the management rights of the target management user account to the target contract account, the method further includes: Determine whether the recovery identification information in the consent signature is consistent with the recovery identification information in the recovery request, wherein the recovery identification information is the number of times the management authority of the target contract account is currently restored, or random identification information; If they are consistent, the verification is confirmed to be successful.

2. The method according to claim 1, characterized in that The method further comprises: After the target management user account successfully recovers the management rights of the target contract account, the target sub-control group is deleted.

3. The method according to claim 1, characterized in that The verifying the consent signature includes: Determine whether the number of signatures of the agreed signatures is equal to the number of users corresponding to the target sub-control group; Determine whether each user corresponding to the consent signature is a user in the target sub-control group.

4. The method according to claim 3, characterized in that Before restoring the management rights of the target management user account to the target contract account, the method further includes: Receiving password information input by the target management user account; Determining whether the password information is a preset password of the target management user account; If so, the verification is confirmed to be successful.

5. The method according to claim 1, characterized in that The determining the sub-control group according to the hash information of the plurality of users corresponding to the adding operation includes: Determine hash information of multiple users corresponding to the selection operation according to the selection operation of the adding operation in the social circles corresponding to at least two of the target management user accounts; The sub-control group is determined according to the hash information of the multiple users.

6. An account management device based on blockchain, characterized in that: The device comprises: a receiving module, a sending module and a recovery module, wherein: The receiving module is used to receive a confirmation operation for a target sub-control group sent by a target management user account of a target contract account; The sending module is used to send a recovery request to each user in the target sub-control group; the recovery request is used to apply for restoring the management authority of the target management user account to the target contract account; The receiving module is specifically used to receive the consent signature returned by each user in the target sub-control group and verify the consent signature; The recovery module is used to restore the management rights of the target management user account to the target contract account if the verification is successful; The device further comprises: a determination module; configured to determine the sub-control group in response to the adding operation of the sub-control group triggered by the target management user account according to the hash information of multiple users corresponding to the adding operation; wherein the information of the sub-control group comprises: the hash information of the multiple users, and the multiple users in the sub-control group are users of the target management user account in different social circles; The determination module is specifically used to determine whether the recovery identification information in the consent signature is consistent with the recovery identification information in the recovery request, wherein the recovery identification information is the number of times the management authority of the current target contract account is restored, or random identification information; if they are consistent, it is determined that the verification is passed.

7. A blockchain-based account management device, characterized in that: The device includes: a processor, a storage medium and a bus, the storage medium stores machine-readable instructions executable by the processor, and when the blockchain-based account management device is running, the processor communicates with the storage medium through the bus, and the processor executes the machine-readable instructions to execute the method described in any one of claims 1 to 5.

8. A storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 is executed.

Images