WO2023093319A1

WO2023093319A1 - Blockchain-based account resetting method, and device

Info

Publication number: WO2023093319A1
Application number: PCT/CN2022/124274
Authority: WO
Inventors: 张龙; 范瑞彬; 张开翔; 毛嘉宇; 储雨知; 王越
Original assignee: 深圳前海微众银行股份有限公司
Priority date: 2021-11-24
Filing date: 2022-10-10
Publication date: 2023-06-01
Also published as: CN114049121B; CN114049121A

Abstract

Provided in the present application are a blockchain-based account resetting method, and a device. The method comprises: acquiring resetting information, and ciphertext of at least one associated account logged in on another authentication device, and generating a resetting notification request according to the resetting information and the ciphertext of the at least one associated account, so as to obtain a resetting notification request corresponding to each authentication device; and sending the corresponding resetting notification request to each authentication device, wherein a resetting transaction request is generated by means of each authentication device and according to the corresponding resetting notification request and ciphertext of an associated account logged in on the authentication device, a verification result of each associated account is obtained by means of a blockchain system performing identity verification according to a resetting transaction request, which is sent by each authentication device, and joint associated account ciphertext stored in a blockchain, and the blockchain system is used for performing account resetting processing according to the resetting information when the verification result of each associated account meets a preset resetting condition. The account security can be improved by encrypting and storing an associated account in a blockchain.

Description

Blockchain-based account reset method and device

This application claims priority to a Chinese patent application filed with the China Patent Office on November 24, 2021, with application number CN202111405515.6, and application title "Blockchain-based account reset method and device", the entire content of which is adopted References are incorporated in this application.

technical field

This application relates to the field of financial technology (Finteh), in particular to a blockchain-based account reset method and device.

Background technique

With the development of computer technology, more and more technologies are applied in the financial field, and the traditional financial industry is gradually transforming into financial technology (Finteh). Blockchain (Block-Chain) technology is no exception, but due to the security and real-time requirements of the financial industry, it also puts forward higher requirements for blockchain technology. Especially when resetting the blockchain account, the security requirements are higher.

Contents of the invention

An embodiment of the present application provides a blockchain-based account reset method, which is applied to a requesting device. The reset system includes a requesting device, a blockchain system, and multiple authentication devices. The method includes:

For each authenticated device, obtain the reset information and the ciphertext of at least one associated account logged in on other authenticated devices, and generate a reset notification request according to the reset information and the ciphertext of at least one associated account, so as to obtain the ciphertext of each authenticated device The corresponding reset notification request;

Send a corresponding reset notification request to each authentication device; wherein, the reset transaction request is generated by each authentication device according to the corresponding reset notification request and the ciphertext of the associated account logged on it;

Among them, the verification results of each associated account are obtained by the blockchain system through identity verification based on the reset transaction request sent by each authentication device and the ciphertext of the joint associated account stored on the blockchain. When the verification result of each associated account meets the preset reset condition, the account reset process is performed according to the reset information.

Another embodiment of the present application provides a blockchain-based account reset method, the method is applied to the blockchain system, and the method includes:

Receive reset transaction requests sent by each authentication device; wherein, each reset transaction request is generated by the corresponding authentication device according to the ciphertext of the associated account logged on the corresponding authentication device and the reset notification request; the corresponding reset transaction request of each authentication device The configuration notification request is generated by the requesting device based on the ciphertext and reset information of the associated account logged on at least one other authentication device;

Verify the identity of each associated account according to the reset transaction request sent by each authentication device and the ciphertext of the joint associated account stored on the blockchain, and obtain the verification result of each associated account;

When the verification result of each associated account satisfies the preset reset condition, the account reset process is performed according to the reset information.

Another embodiment of the present application provides a requesting device, including: a processor, and a memory communicatively connected to the processor;

the memory stores computer-executable instructions;

The processor executes the computer-executed instructions stored in the memory, so as to implement the account reset method provided in the above embodiments.

Another embodiment of the present application provides an authentication device, including: a processor, and a memory communicatively connected to the processor;

the memory stores computer-executable instructions;

Another embodiment of the present application provides a computer-readable storage medium. Computer-executable instructions are stored in the computer-readable storage medium. When the computer-executable instructions are executed by a processor, they are used to implement the account reset method provided in the above-mentioned embodiments.

The blockchain-based account reset method and device provided by this application store multiple associated accounts used to reset private keys and corresponding external accounts in the blockchain in the form of joint ciphertext, and the data security of associated accounts High, it can prevent the authentication device logged in with one of the associated accounts from obtaining other associated accounts on the blockchain to do evil, and cooperate with other associated accounts to initiate a transaction to reset the private key and the corresponding external account, in order to facilitate the reset initiated by the authentication device The transaction request is authenticated. When the requesting device initiates a reset notification request to the authentication device, a notification request is generated based on at least one associated account ciphertext, so that the authentication device can generate a reset transaction request with multiple associated account ciphertexts. Blockchain The system can verify the associated account according to the ciphertext of multiple associated accounts, so as to realize the reset of the private key and the corresponding external account.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description serve to explain the principles of the application.

Figure 1 is a schematic diagram of a model of a blockchain account provided by this application;

FIG. 2 is a schematic flow diagram of establishing a new blockchain account provided by an embodiment of the present application;

Figure 3 is a schematic diagram of an example based on the blockchain account model shown in Figure 1 provided by this application;

Fig. 4 is a schematic diagram of an example after the blockchain account shown in Fig. 3 is reset based on the present application;

FIG. 5 is a schematic structural diagram of the reset system provided by the present application;

FIG. 6 is a schematic flowchart of an account reset method provided in another embodiment of the present application;

FIG. 7 is a schematic flowchart of an account reset method provided by another embodiment of the present application;

Figure 8 is a schematic diagram of another model of the blockchain account provided by this application;

FIG. 9 is a schematic diagram of the principle of generating the ciphertext of joint associated accounts provided by another embodiment of the present application;

Figure 10 is a schematic diagram of an example based on the blockchain account model shown in Figure 8 provided by this application;

Fig. 11 is a schematic diagram of an example after the blockchain account shown in Fig. 10 is reset based on the present application;

Fig. 12 is a schematic structural diagram of an account reset device provided by another embodiment of the present application;

FIG. 13 is a schematic structural diagram of an account reset device provided in yet another embodiment of the present application;

FIG. 14 is a schematic structural diagram of an account reset device provided in another embodiment of the present application;

FIG. 15 is a schematic structural diagram of an electronic device provided by another embodiment of the present application.

By means of the above drawings, specific embodiments of the present application have been shown, which will be described in more detail hereinafter. These drawings and text descriptions are not intended to limit the scope of the concept of the application in any way, but to illustrate the concept of the application for those skilled in the art by referring to specific embodiments.

Detailed ways

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present application as recited in the appended claims.

In the blockchain system, the public key system is usually used to operate and manage the blockchain account. The user saves the private key and saves the account generated based on the public key on the blockchain. When a transaction request is initiated, the transaction request is signed by the private key, and the blockchain system verifies the transaction signature through the account on the blockchain. In other words, the private key is the only certificate for identity verification of the blockchain account. Once the private key is lost, it means that the user will lose all assets and rights under the current blockchain account.

In order to solve this problem, as one of the technical solutions, the user needs to save the mnemonic, usually through the mnemonic. When the user loses the private key, the lost private key can be obtained through the mnemonic. As another technical solution, the encrypted private key will also be saved through the password escrow system. Since the encrypted private key is escrowed by the password escrow system, the user is required to save the password used for private key encryption. Although mnemonic words and passwords can improve user experience, users do not need to memorize complex private keys. However, mnemonic words and passwords still have the risk of being lost or stolen, which essentially does not solve the problem of private key loss.

In order to essentially solve the problem of private key loss, a blockchain account model based on a two-tier account system is proposed, which facilitates obtaining a new private key and a new external account by resetting the private key and external account when the private key is lost. account. In addition, all the assets and rights of the user are bound to the internal account, and the external account is only used to verify the transaction signature. When the external account is reset, the user's assets and rights will not be affected in any way.

As shown in Figure 1, the blockchain account model of the proposed two-tier account system includes external accounts and internal accounts. The external account is implemented based on the public key, that is, the device is requested to randomly generate an asymmetric key, and the external account generated based on the public key is saved on the blockchain, and the user saves the private key. When the requesting device initiates a transaction request, the transaction request is signed by the private key, and the blockchain system verifies the transaction signature through the external account on the blockchain.

Internal accounts are used to reset private keys and external accounts. Internal accounts include internal contract account information, a list of associated accounts, and reset thresholds. Among them, the internal contract account information is randomly generated by the blockchain system in response to the registration request initiated by the requesting device, and forms a mapping relationship between the internal contract account information and the external account. The associated account list contains multiple associated accounts, and each associated account is an external account of a blockchain account, which is used to reset the private key saved by the user and the external account saved in the blockchain. The reset threshold is the minimum number of signatures associated with an account when private keys and external accounts are reset.

As shown in Figure 2, the process of creating a new blockchain account in the blockchain system specifically includes:

S101. The requesting device randomly generates an asymmetric key, and generates an external account according to the public key in the asymmetric key.

In this step, requesting the device to randomly generate an asymmetric key is recorded as:

<privateKey, publicKey>

Among them, privateKey represents the private key, and the private key is used to sign the transaction to the blockchain system. publicKey represents the public key, and the private key is used to generate an external account in the blockchain account, and the external account is recorded as publicKeyAddress.

S102. The requesting device generates a registration request according to the external account, and signs the registration request with a private key.

S103. The requesting device sends a registration request to the blockchain system.

S104. The blockchain system creates a new blockchain account according to the registration request.

Among them, after the blockchain system receives the registration request, the blockchain system first randomly generates internal contract account information, which is recorded as: randomAddress. Then obtain the external account according to the signature, record it as: publicKeyAddress, and finally establish the mapping relationship between the external account and the internal contract account information, and record the mapping relationship on the blockchain. The mapping relationship is recorded as: (publicKeyAddress, randomAddress).

After completing the registration of the blockchain by executing S101 to S104, it is also necessary to add the associated account of the newly created blockchain account to the internal account and reset the threshold.

The essence of setting up linked accounts is to provide a redundant multi-factor authentication. When the private key saved by the user is lost or stolen, the account reset transaction can be initiated through the device logged in with the associated account, and the external account generated by the blockchain system using the public key corresponding to the new private key will replace the public key corresponding to the old private key. The external account generated by the key will form a new mapping relationship, and the security of account reset will be ensured by means of multi-party signatures.

When adding an associated account and resetting the threshold, the requesting device obtains the associated account and resetting the threshold, and initiates an adding transaction request based on the associated account and resetting the threshold, and the requesting device signs the adding transaction request and sends it to the blockchain system . That is, the request device is sent to the blockchain system in plain text. After the blockchain system receives the request to add a transaction, it is also stored on the blockchain in plain text.

For example: After creating a new blockchain account in the blockchain system, set the reset threshold to 3, and the associated account list of the added blockchain account is:

{ publicKeyAddress _A ;

publicKeyAddress _B ;

publicKeyAddress _C ;

publicKeyAddress _D }

Among them, publicKeyAddress _A represents the external account of blockchain account A, publicKeyAddress _B represents the external account of blockchain account B, publicKeyAddress _C represents the external account of blockchain account C, and publicKeyAddress _D represents the external account of blockchain account D.

The reset threshold is the minimum number of blockchain accounts that agree to reset during the private key and external account reset process. That is to say, when resetting the private key and external account, at least 3 signatures of blockchain accounts in blockchain account A to blockchain account D are required to complete the reset operation. At this time, the user's blockchain account model is shown in Figure 3.

When the private key saved by the user is leaked or lost, the requesting device can initiate a reset notification request to the authentication device logged in with the associated account, so that the authentication device initiates an account reset transaction request to the blockchain, and the blockchain system The reset of the account and private key is completed by means of multi-party signatures. Specific steps are as follows:

S201. The requesting device randomly generates an asymmetric key, and generates a new external account according to the public key in the asymmetric key.

Among them, after the private key is lost, the requesting device randomly generates an asymmetric key, which is recorded as:

(privateKey', publicKey')

Among them, privateKey' is the new private key, and publicKey' is the new public key.

A new external account is calculated according to the new public key publicKey', and the new external account is recorded as publicKeyAddress'.

S202. The requesting device generates an account reset notification request according to the new external account and the old external account.

S203. The requesting device sends a reset notification request to the authentication device logged in with the associated account.

In this step, the associated account list includes blockchain account A to blockchain account D, then a reset notification request is sent to the authentication device logged in from blockchain account A to blockchain account D, and the new external account The publicKeyAddress' and the old external account publicKeyAddress are sent to the authentication devices logged in from blockchain account A to blockchain account D.

S204. Each authentication device generates a private key reset transaction request according to the new external address and the old external address.

Among them, the associated accounts are blockchain account A to blockchain account D, and the authentication device logged in from blockchain account A to blockchain account C sends a signed reset transaction request.

The signed reset transaction requests initiated by blockchain account A to blockchain account C are recorded as TX _A , TX _B and TX _C , specifically:

TX _A ＝(publicKeyAddress', publicKeyAddress, signature _A )

TX _B ＝(publicKeyAddress', publicKeyAddress, signature _B )

TX _C ＝(publicKeyAddress', publicKeyAddress, signature _C )

Among them, publicKeyAddress′ is the new external account, publicKeyAddress is the external account corresponding to the lost private key, that is, the old external account, signature _A is the signature of blockchain account A, signature _B is the signature of blockchain account B, signature _c It is the signature of blockchain account C.

S205. The blockchain system performs signature verification according to the reset transaction request sent by each authentication device and the associated account list on the blockchain, and resets the account according to the signature verification result.

In this step, after receiving the reset transaction request sent by the authentication device logged in by blockchain account A, the blockchain system parses out the external address according to the transaction signature _{A of blockchain account A.} If the external address is in In the list of associated accounts on the blockchain, if the verification is passed, the number of signatures that pass the verification is accumulated. The reset transaction requests sent by the authentication devices logged in by blockchain account B and blockchain account C are authenticated in turn, and the number of signatures that pass the verification is accumulated.

Determine whether the accumulation result is greater than or equal to the reset threshold. If the accumulation result is less than the reset threshold, the reset transaction request will not be responded and the transaction will fail. If the accumulated result is equal to or greater than the reset threshold, the reset transaction request is responded and the transaction is successful.

Since blockchain account A to blockchain account C are associated accounts, and the cumulative number of signatures is 3, the accumulated result is equal to the reset threshold, and the blockchain system will update the external account to a new external account. The update model is:

(publicKeyAddress, randomAddress) → (publicKeyAddress′, randomAddress)

The reset blockchain account is shown in Figure 4. Since the internal account remains unchanged, the user's assets and rights and interests are not lost, and the external account is reset to the external account publicKeyAddress' corresponding to the new private key privateKey', so The user signs the transaction initiated by the new private key, the signature can be verified, and the assets and rights of the account corresponding to the old private key can be inherited, and the old private key will become invalid.

The above-mentioned private key and external account reset solution based on the two-tier account system can reset the private key and external account through the associated account in case the private key is leaked or lost, so as to ensure that the assets and rights of the account are not lost .

But security is multi-dimensional. This algorithm for resetting the private key and external account is based on the assumption that the associated account does not do evil or the private key of the associated account is not stolen. Since the associated account list of the blockchain account is stored on the blockchain in plain text. When the associated account does evil, it will also collude with other associated accounts to initiate a reset transaction request, and reset the external account corresponding to the blockchain account to obtain the assets and related rights of the blockchain account. Or, the attacking device attacks the device logged in by the associated account until the private key of the most associated account is obtained, and then it can initiate a reset transaction request for the private key of the corresponding blockchain account, thereby obtaining the assets and related information of the blockchain account. rights and interests.

In summary, the root cause of the above-mentioned malicious risks or attack methods is that the associated accounts are stored in plain text on the blockchain. Based on the above analysis, this application provides a more secure account reset solution. Save the associated account in ciphertext on the upper blockchain, and jointly encrypt the associated account, so that the attacking device cannot determine the associated account of the blockchain account based on the associated account after joint encryption, and reset the account if necessary At this time, the identity verification of the associated account can still be performed through joint encryption, so as to realize account reset.

As shown in FIG. 5 , an embodiment of the present application provides an account reset system, which includes a blockchain system 300 , a requesting device 100 and an authentication device 200 . The blockchain system 300 and the authentication device 200 are connected in communication, so that the authentication device 200 initiates a reset transaction request to the blockchain system 300 . The blockchain system 300 and the requesting device 100 are also connected in communication, so that the requesting device 100 can also initiate a registration request and an initialization transaction request to the blockchain system 300 .

A blockchain account is stored in the blockchain running on the blockchain system 300, and the communication connection between the requesting device 100 and the authentication device 200, so that the requesting device 100 can initiate a reset notification request to the authentication device, and the authentication device 200 After receiving the reset notification request, send an account reset transaction request to the blockchain system, so that the blockchain system resets the blockchain account.

As shown in Figure 6, an embodiment of the present application provides a blockchain-based account reset method, which is applied to an account reset system, and the method includes the following steps:

S301. For each authentication device, request the device to obtain the reset information and the ciphertext of at least one associated account logged in on other authentication devices, and generate a reset notification request according to the reset information and the ciphertext of at least one associated account, to obtain Reset notification request for each authenticated device.

In this step, the reset information includes an external account in the blockchain account corresponding to the private key to be reset, which is also called an old external account. It also includes a new external account generated based on the public key corresponding to the new private key.

For each authenticated device, the requesting device generates a reset notification request. When a reset notification request is generated for a certain authentication device, obtain the associated account logged on other authentication devices except the authentication device, the associated account is the associated account in the blockchain account corresponding to the private key to be reset, and Encrypting associated accounts logged in on other authentication devices to obtain at least one associated account ciphertext.

After obtaining the reset information and the ciphertext of at least one associated account, first generate the certification information of the authentication device according to the ciphertext of the at least one associated account, and then generate a reset notification request according to the certification information of the authentication device and the reset information.

When generating the certification information of the authentication device, the ciphertexts of at least one associated account may be grouped, and the ciphertexts in each group are encrypted, so as to generate the certification information of the certification device. Among them, the grouping method is the same as the grouping method when generating the joint associated account ciphertext stored on the blockchain. It is also possible to directly use the obtained ciphertext of at least one associated account as the certification information of the authentication device.

After generating the certification information of the authentication device by group, and then further generating the reset notification request method, it is more difficult to obtain the associated account after it is maliciously attacked, which can improve the security of account reset.

S302. The requesting device sends a corresponding reset notification request to each authentication device.

In this step, the requesting device will generate a corresponding reset notification request for each authentication device. For a certain authentication device, only the ciphertext of the associated account logged in on other authentication devices is used to generate a reset notification request. Therefore, each authentication Device reset notification requests are different.

S303. Each authentication device generates a reset transaction request according to the corresponding reset notification request and the ciphertext of the associated account logged on the authentication device.

In this step, for any authentication device, the authentication device receives the reset notification request, and parses out the reset information and the certification information of the authentication device from the reset notification request, and obtains the ciphertext of the associated account logged in on its own device. , and then generate a reset transaction request based on the ciphertext of the associated account logged in on the own device, the certification information of the authentication device, and the reset information. That is, the reset transaction request needs to be based on the ciphertext of all associated accounts. The authentication device also uses the private key corresponding to the associated account logged on it to sign the reset transaction request.

S304. Each authentication device sends a reset transaction request to the blockchain system.

In this step, after each authentication device receives the reset notification request, it will generate a signed reset transaction request and send the reset transaction request to the blockchain system under the condition of not doing evil.

S305. The blockchain system verifies the identity of the associated account according to the reset transaction request sent by each authentication device and the ciphertext of the associated account stored on the blockchain, and obtains the verification result of the associated account.

In this step, the blockchain system performs identity verification on the reset transaction request sent by each authentication device, and obtains the verification result of the associated account logged on each authentication device.

For the reset transaction request sent by each authentication device, any node in the blockchain system parses the reset transaction request to obtain the certification information of the authentication device, the ciphertext of the associated account logged on the authentication device, and the reset information. The certification information of the authentication device and the ciphertext of the associated account logged on the authentication device are encrypted to generate a composite ciphertext, and then the composite ciphertext is compared with the ciphertext of the joint associated account stored on the blockchain, and if they are consistent, a verification is generated If the verification result is passed, if it is inconsistent, a verification result of verification failure will be generated.

S306. The blockchain system resets the account according to the reset information when the verification result of the associated account satisfies the preset reset condition.

In this step, satisfying the preset reset condition includes that the verification result is that the number of linked accounts that pass the verification is greater than or equal to the reset threshold. Failure to meet the preset reset condition includes that the verification result is that the number of associated accounts that pass the verification is less than the reset threshold.

The blockchain system counts the verification results of the associated accounts, obtains the number of associated accounts that have passed the verification, and judges whether the number of associated accounts that have passed the verification is greater than or equal to the reset threshold. If so, use the new external account to update the old external account, and form The mapping relationship between the new external account and the corresponding internal account of the old external account.

In the above technical solution, the multiple associated accounts used to reset the private key and the corresponding external accounts are stored in the block chain in the form of joint ciphertext. The authentication device obtains other associated accounts on the blockchain to do evil, and cooperates with other associated accounts to initiate a transaction to reset the private key and the corresponding external account, which can also resist the attack of the attacking device. In order to facilitate the authentication of the reset transaction request initiated by the authentication device, when the requesting device initiates a reset notification request to the authentication device, a notification request is generated based on at least one associated account ciphertext, so that the authentication device can use multiple associated account ciphertexts Generate a reset transaction request, and the blockchain system can verify the associated account according to the ciphertext of multiple associated accounts, so as to realize the reset of the private key and the corresponding external account.

As shown in Figure 7, an embodiment of the present application provides a blockchain-based account reset method, which is applied to an account reset system, and the method includes the following steps:

S401. Request the device to encrypt all associated accounts associated with the old external account, and generate a joint associated account ciphertext.

Wherein, the old external account is generated by the requesting device according to the public key in the randomly generated second asymmetric key. The way in which the requesting device generates the certification information of each authentication account is the same as the way in which the requesting device generates the ciphertext of the joint associated account.

If the ciphertext of the associated account is not grouped and then encrypted when the ciphertext of the joint associated account is generated, the certification information of the authentication account only includes the ciphertext of the associated account logged in on each other authentication device.

If the ciphertext of the joint associated account is obtained by grouping the ciphertexts of each associated account and then encrypting them separately, when generating the certification information of the authentication account, it is also necessary to group the ciphertexts of the associated accounts logged in on other authentication devices.

More specifically, a hash calculation is performed on each associated account associated with the old external account to obtain the ciphertext of each associated account associated with the old external account. Group the ciphertexts of each associated account associated with the old external account, and perform hash calculation on the ciphertexts in each group to obtain the hash value of each group, perform cyclic execution to group the hash values of each group and then hash the hash values in the group Perform hash calculation on the values to obtain the hash values of multiple groups until the number of groups satisfies the second loop stop condition. And hash calculation is performed on the hash values of the multiple groups obtained at last to obtain the ciphertext of the joint associated account.

In an embodiment, when grouping each associated account ciphertext and regrouping each group, it is guaranteed that there are two hash values or two associated account ciphertexts in each group after grouping.

Satisfying the second loop stop condition includes that the number of packets is equal to 2, and not satisfying the second loop stop condition includes that the number of packets is not equal to 2.

S402. The requesting device generates an initialization transaction request according to the ciphertext of the associated account and the reset threshold, and signs the initialization transaction request using the private key in the second asymmetric key.

Among them, the initialization request is used to increase the associated account information and reset the threshold in the blockchain account, and the associated account information is stored in the form of joint associated account ciphertext. The private key in the second asymmetric key is used to sign the initial transaction request, so that the blockchain system can authenticate the requesting device.

S403. The requesting device sends an initialization transaction request to the blockchain system.

S404. The blockchain system responds to the initialization transaction request.

In this step, use the external account of the blockchain account to verify the signature in the initial transaction request, establish the corresponding relationship between the ciphertext of the joint associated account and the internal account after the verification is passed, and establish the relationship between the reset threshold and the internal account. The corresponding relationship between the old external accounts and internal accounts is stored on the blockchain, as shown in Figure 8.

In the above technical solution, when generating the ciphertext of the joint associated account, the group hash value is calculated again by cyclically grouping each hash value, and the ciphertext of the joint associated account is obtained in a tree-shaped encryption method, and the ciphertext of the associated account is increased in the area. The data security stored in the block chain does not need to decrypt the ciphertext of the joint associated account when resetting the account. It is directly based on the certification information of the authentication device and the hash value of the associated account logged in on the authentication device. After rehashing , and then compared with the ciphertext of the joint associated account stored in the blockchain to complete the identity verification, which can further resist the attack of the attacking device and the malicious authentication device will jointly perform the account reset transaction after cracking the associated account.

An embodiment of the present application provides a blockchain-based account reset method, which is applied to an account reset system, and the method includes the following steps:

S501. For each authentication device, request the device to obtain the reset information and the ciphertext of at least one associated account logged in on other authentication devices, and generate a reset notification request according to the reset information and the ciphertext of at least one associated account, so as to obtain Reset notification request for each authenticated device.

In this step, the reset information includes an external account in the blockchain account corresponding to the private key to be reset, which is also called an old external account. Reset information also includes new external accounts. In order to obtain a new external account, a first asymmetric key is randomly generated, and a new external account is generated according to the public key in the first asymmetric key.

In order to obtain the ciphertext of each associated account, take one of the authentication devices as an example, obtain the associated account logged in on the authentication device, perform hash processing on the associated account logged in on the authentication device, and obtain the password of the associated account logged in on the authentication device Text, so as to obtain the ciphertext of multiple associated accounts.

In order to obtain the certification information of each authentication device, the ciphertext of at least one associated account is grouped, and hash calculation is performed on the ciphertext in each group to obtain the hash value of each group. That is, for each group, calculate the hash value between all ciphertexts in the group, and use it as the hash value of the group. For example, if the group includes 2 ciphertexts, calculate the hash value between the 2 ciphertexts, and if the group includes 3 ciphertexts, then calculate the hash value between the 3 ciphertexts.

After the hash value of each group is obtained, the hash value of each group is cyclically grouped and then the hash value in the group is calculated to obtain the hash value of multiple groups until the number of groups satisfies the first loop stop condition. That is, after obtaining the hash values of multiple groups, further group the hash values of multiple groups to obtain a new group, and then calculate the hash value between the hash values in the new group for each new group, Use it as the hash value of the new group, so as to obtain the hash values of multiple new groups, and complete a cycle. The hash value of each group is obtained through multiple loops. And the hash value of multiple groups is used as the certification information of the authenticated device.

Among them, satisfying the first cycle stop condition includes that the number of groups is equal to the first threshold, and the first threshold is determined according to the method of obtaining the ciphertext of the joint associated account, so as to ensure that when the blockchain system receives the reset transaction request sent by the authentication device, Based on the hash value of each group and the hash value of the associated account registered on the authentication device, the ciphertext of the joint associated account can be obtained, and then compared with the ciphertext of the associated account stored on the blockchain to realize the verification of the authentication device.

After the certification information of each certified device is obtained, a reset notification request for each certified device is generated according to each certified device, the certified information and the reset information.

S502. The requesting device sends a corresponding reset notification request to each authentication device.

S503. For each authentication device, the authentication device performs hash processing on the associated account logged in to obtain the ciphertext of the associated account logged in on the authentication device, so as to obtain the ciphertext of the associated account logged in on each authentication device.

S504. For each authentication device, the authentication device generates a reset transaction request according to the received reset notification request and the ciphertext of the associated account logged on it, so as to obtain the reset transaction request generated by each authentication device.

S505. Each authentication device sends a reset transaction request to the blockchain system.

S506. The blockchain system performs identity verification on each associated account according to the reset transaction request sent by each authentication device and the joint associated account ciphertext stored on the blockchain, and obtains a verification result of each associated account.

In this step, for any reset transaction request, analyze the reset transaction request to obtain the certification information of the authentication device and the ciphertext of the associated account logged on the authentication device, and encrypt the certification information and the ciphertext of the associated account to generate Synthetic ciphertext, compare the synthetic ciphertext with the ciphertext of the joint associated account to obtain the verification result of the associated account, and obtain the verification result of an associated account.

Repeat the above steps to obtain the verification results of the associated accounts corresponding to all reset transaction requests.

S507. The blockchain system performs account reset processing according to the reset information when the verification result of each associated account meets the preset reset condition.

In this step, the verification results of the obtained associated accounts are counted to obtain the number of associated accounts that have passed the verification. Use the new external account to update the old external account, and associate the new external account with the internal account corresponding to the old external account. The internal account includes the ciphertext of the joint associated account and resets the threshold.

In the above technical solution, in order to realize the identity verification of the authentication device, the requesting device generates an identity certificate for each authentication device, so that the block chain can be based on the ciphertext of the identity certificate and the associated account of the authentication device in the reset transaction request. Identity verification, while ensuring the security of associated accounts stored on the block chain, it can also facilitate the block chain system to perform identity verification.

Another embodiment of the present application provides a blockchain-based account reset method, which is applied to an account reset system, and the method includes the following steps:

S601. Request the device to encrypt all associated accounts associated with the old external account, and generate a joint associated account ciphertext.

In this step, the blockchain account to be reset has been created in the blockchain, the external account of the blockchain account is recorded as publicKeyAddress, the randomly generated internal contract account information is recorded as randomAddress, and the internal contract account information As an internal account address, and make the external account and internal contract account information form a mapping relationship, and record it on the blockchain, the mapping relationship model is:

(publicKeyAddress, randomAddress)

The external account is generated based on the public key in the asymmetric key, and the asymmetric key is recorded as <privateKey, publicKey> privateKey is the private key, and publicKey is the public key.

The associated accounts of the external account are blockchain account A, blockchain account B, blockchain account C and blockchain account D. Obtain the external accounts of the four accounts, also known as public key address information, as follows:

_{publicKeyAddressA}

publicKeyAddress _B

publicKeyAddress _C

publicKeyAddress _D

Perform hash calculation on the external account to obtain the hash value of the associated account:

H(A)＝Hash(publicKeyAddress _A )

H(B)＝Hash(publicKeyAddress _B )

H(C)＝Hash(publicKeyAddress _C )

H(D)＝Hash(publicKeyAddress _D )

As shown in Figure 9, the joint associated account ciphertext is obtained through tree hash operation, which is marked as H(ABCD). Group the four hash values, the first group is H(A) and H(B), and the second group is H(C) and H(D).

The hash value of the first group is marked as H(AB):

H(AB)=H(H(A)+H(B))

The hash value of the second group is marked as H(CD):

H(CD)=H(H(C)+H(D))

Hash the hash values of the two groups to obtain the joint account ciphertext H(ABCD

H(ABCD)＝H(H(AB)+H(CD))

S602. The requesting device generates an initialization transaction request according to the ciphertext of the associated account and the reset threshold, and signs the initialization transaction request using the private key in the second asymmetric key.

In this step, the associated associated account ciphertext H (ABCD) is used to set the associated account information and set the reset threshold, for example: the reset threshold is 3.

S603. The requesting device sends an initialization transaction request to the blockchain system.

S604. The blockchain system responds to the initialization transaction request.

In this step, after the signature verification of the initial transaction request, the joint associated account ciphertext H (ABCD) and the reset threshold are stored in the blockchain, as shown in Figure 10.

In the above technical solution, due to the anti-collision feature of the hash function, the possibility of obtaining each associated account from the joint associated account ciphertext H (ABCD) is extremely low, and the authentication device or other attacking device cannot cooperate with other associated accounts to maliciously reset Blockchain accounts ensure the privacy and security of associated accounts.

S701. For each authentication device, request the device to obtain the reset information and the ciphertext of at least one associated account logged in on other authentication devices, and generate a reset notification request according to the reset information and the ciphertext of at least one associated account, so as to obtain Reset notification request for each authenticated device.

In this step, when the private key is lost or there is a risk of leakage, the device is requested to regenerate a public-private key pair (privateKey', publicKey'), and calculate a new external account publicKeyAddress' based on the new public key publicKey'.

Each authentication device has an associated account logged in, and the requesting device generates certification information for each authentication device based on the associated account, so as to construct a joint associated account ciphertext based on the ciphertext and authentication information of the associated account logged in on the authentication device. Since only the root hash value H(ABCD) of the tree encryption method is stored on the blockchain, it is necessary to prove whether the blockchain account logged in on the requesting device that sends a private key reset transaction request is an associated account. The root hash value needs to be constructed based on the proof information, and it is equal to the root hash value H(ABCD) stored on the blockchain, which proves that the login account on the authentication device is an associated account, otherwise the login account on the authentication device is not associated account.

Taking blockchain account A as the associated account as an example, to calculate H(ABCD), you only need to know the hash value H(B) of blockchain account B, the hash value of blockchain account C, and the blockchain account The hash value H(CD) between the hash values of D is enough. The authentication device then calculates the hash value H(A) of blockchain account A, calculates H(AB) based on H(A) and H(B), and then calculates H(AB) based on H(AB) and H(CD) (ABCD), so the proof information Proof _A of the associated account A is: Proof _A = {H(B), H(CD)}.

After obtaining the certification information of each authentication device, a reset notification request is generated according to the reset information and the certification information of the certification device. The reset information includes the new external account publicKeyAddress' and the old external account publicKeyAddress.

S702. The requesting device sends a corresponding reset notification request to each authentication device.

S703. For each authentication device, the authentication device performs hash processing on the associated account logged in to obtain the ciphertext of the associated account logged in on the authentication device, so as to obtain the ciphertext of the associated account logged in on each authentication device.

In this step, each authentication device has an associated account logged in, and each authentication device performs hash calculation on the associated account logged in to obtain the ciphertext of the associated account.

For example, if a blockchain account A is registered on the first authentication device, the first authentication device 200 encrypts the external account of the blockchain account A to obtain the ciphertext of the associated account. The second authentication device 200 has a blockchain account B logged in, and the second authentication device encrypts the external account of the blockchain account B to obtain the ciphertext of the associated account.

S704. For each authentication device, the authentication device generates a reset transaction request according to the received reset notification request and the ciphertext of the associated account logged on it, so as to obtain the reset transaction request generated by each authentication device.

In this step, after receiving the reset notification request, each authentication device initiates a reset transaction request and signs it.

For example: the reset transaction request initiated by the device where the blockchain account A is located is recorded as TX _A :

TX _A ＝(publicKeyAddress′, publicKeyAddress, signature _A , Proof _A )

Among them, publicKeyAddress' is the new external account, publicKeyAddress is the nine external accounts, signature _A is the signature of blockchain account A, and Proof _A is the certification information of blockchain account A.

Correspondingly, the reset transaction request initiated by the device of blockchain account A is recorded as TX _A , and the reset transaction request initiated by the device of blockchain account B is recorded as TX _B :

TX _B ＝(publicKeyAddress′, publicKeyAddress, signature _B , Proof _B )

TX _C ＝(publicKeyAddress′, publicKeyAddress, signature _C , Proof _C )

signature _B is the signature of blockchain account B, Proof _B is the certification information of blockchain account B, signature _C is the signature of blockchain account C, and Proof _C is the certification information of blockchain account C.

S705. Each authentication device sends a reset transaction request to the blockchain system.

S706. The blockchain system performs identity verification on each associated account according to the reset transaction request sent by each authentication device and the joint associated account ciphertext stored on the blockchain, and obtains a verification result of each associated account.

In this step, the blockchain network authenticates the blockchain account on the transaction initiator device according to the transaction signature. The blockchain system analyzes the associated account that initiates the reset transaction request based on the transaction signature, and constructs the root hash value based on the associated account and the corresponding certification information. If the root hash value and the ciphertext of the joint associated account stored on the blockchain If they are the same, the originating account of the reset transaction request is an associated account, and the verification is passed, and the transaction is successful; if not, it is not an associated account, and the verification fails, and the transaction fails. And accumulate the number of associated accounts that pass the verification, and judge whether the reset threshold is reached.

S707. The blockchain system performs account reset processing according to the reset information when the verification result of each associated account meets the preset reset condition.

In this step, for the reset transaction request TX _A , it is verified that the blockchain account A logged in on the initiating device of the transaction TX _A is an associated account, and the cumulative number of signatures is 1, but the threshold for the number of signatures has not yet been reached required, so no account reset will be performed.

Since the blockchain account B logged in on the authentication device and the blockchain account C logged in on the authentication device are associated accounts, the blockchain account logged in on the device that initiates the reset transaction request TX _B and reset transaction request TX _C Verify that both are verified, and add up the number of signatures to 3. At this time, the number of signatures is equal to the reset threshold, and the blockchain system updates the old external account to a new external account. The model is as follows:

(publicKeyAddress, randomAddress) → (publicKeyAddress′, randomAddress)

The updated blockchain model is shown in Figure 11. Since the internal account remains unchanged, the user's assets and rights and interests are not lost, and the external account is reset to the external account publicKeyAddress' generated based on the public key corresponding to the new private key privateKey', so the authentication device initiates through the new private key pair After the transaction request is signed, it can be verified, and the assets and rights of the account corresponding to the original private key will be inherited, and the original private key will become invalid.

In the above technical solution, when adding an associated account, the associated account is not added in plain text, but the associated account is encrypted and added, and at the same time, the verification information is used to verify whether the account that initiated the reset transaction request is one of the multiple associated accounts, which can reduce the number of associated accounts. Even if the account is attacked, other associated account information cannot be obtained from the blockchain, which can prevent the associated accounts from colluding.

As shown in Figure 12, an embodiment of the present application provides a blockchain-based account reset device 800, which includes:

The first processing module 801 is configured to, for each authentication device, obtain reset information and the ciphertext of at least one associated account logged on other authentication devices, and generate a reset notification according to the reset information and the ciphertext of at least one associated account request to obtain the reset notification request corresponding to each authenticated device;

The first sending module 802 is configured to send a corresponding reset notification request to each authentication device; wherein, the reset transaction request is generated by each authentication device according to the corresponding reset notification request and the ciphertext of the associated account logged on it of;

In an embodiment, the first processing module 801 is specifically configured to:

Generating certification information of the authentication device according to the ciphertext of at least one associated account;

Generate a reset notification request based on the attestation information and reset information of the authenticated device.

Group the ciphertext of at least one associated account, and perform hash calculation on the ciphertext in each group to obtain the hash value of each group;

Carry out cyclic execution to group the hash values of each group and then perform hash calculation on the hash values in the group to obtain the hash values of multiple groups until the number of groups satisfies the first loop stop condition;

The hash values of multiple groups are used as proof information for authenticating the device.

For each authentication device, the associated account logged on the authentication device is obtained, and hash processing is performed on the associated account to generate the ciphertext of the associated account, so as to obtain the ciphertext of multiple associated accounts.

The first asymmetric key is randomly generated, and a new external account is generated according to the public key in the first asymmetric key.

In an embodiment, the first sending module 802 is specifically used for:

Encrypt all associated accounts associated with the old external account to generate a joint associated account ciphertext; wherein, the old external account is generated according to the public key in the second asymmetric key;

Generate an initial transaction request according to the ciphertext of the joint associated account and the reset threshold, and use the private key in the second asymmetric key to sign the initial transaction request;

Send a signed initial transaction request to the blockchain system;

Among them, the initialization transaction request is used to make the blockchain system store the mapping relationship between the old external account and the internal account on the blockchain, and the internal account includes the ciphertext of the joint associated account and the reset threshold.

Perform hash calculation on each associated account associated with the old external account to obtain the ciphertext of each associated account associated with the old external account;

Group the ciphertext of each associated account associated with the old external account, and perform hash calculation on the ciphertext in each group to obtain the hash value of each group;

Carry out cyclic execution to group the hash values of each group and then perform hash calculation on the hash values in the group to obtain the hash values of multiple groups until the number of groups satisfies the second loop stop condition;

Perform hash calculation on the hash values of multiple groups to obtain the ciphertext of the joint associated account.

As shown in Figure 13, an embodiment of the present application provides a blockchain-based account reset device 900, which includes:

The first receiving module 901 is configured to receive a reset notification request sent by the requesting device; wherein, the reset notification request is generated according to the reset information and the ciphertext of the associated account logged in on other authentication devices;

The second processing module 902 is configured to generate a reset transaction request according to the reset notification request and the ciphertext of the associated account logged on the authentication device;

The second sending module 903 is used to send a reset transaction request to the block chain system; wherein, the verification result of each associated account is the combination of the reset transaction request sent by the block chain system according to each authentication device and the block chain. The blockchain system is also used to perform account reset processing according to the reset information when the verification results of each associated account meet the preset reset conditions.

In an embodiment, the second processing module 902 is specifically used to:

Perform hash processing on the associated account logged in on the authentication device to obtain the ciphertext of the associated account logged in on the authentication device.

As shown in Figure 14, an embodiment of the present application provides a blockchain-based account reset device 110, which includes:

The second receiving module 111 is configured to receive reset transaction requests sent by each authentication device; wherein, each reset transaction request is generated by the corresponding authentication device according to the ciphertext of the associated account logged on the corresponding authentication device and the reset notification request The reset notification request corresponding to each authentication device is generated by the requesting device based on the ciphertext and reset information of the associated account logged on at least one other authentication device;

The third processing module 112 is used to perform identity verification on each associated account according to the reset transaction request sent by each authentication device and the joint associated account ciphertext stored on the block chain, and obtain the verification result of each associated account;

In an embodiment, the third processing module 112 is specifically used for:

For each reset transaction request, analyze the reset transaction request to obtain the certification information of the authentication device and the ciphertext of the associated account logged in on the authentication device, and encrypt the certification information and the ciphertext of the associated account to generate a composite ciphertext to Obtain multiple synthetic ciphertexts;

For each synthesized ciphertext, compare the synthesized ciphertext with the ciphertext of the joint associated account to obtain the verification result of the associated account, so as to obtain the verification results of multiple associated accounts.

In an embodiment, the third processing module 112 is specifically used for:

When the verification result is that the number of associated accounts that have passed the verification exceeds the reset threshold, the new external account is used to update the old external account in the blockchain, and the mapping relationship between the new external account and the internal account corresponding to the old external account is established;

Among them, the internal account includes the joint associated account ciphertext and reset threshold.

In an embodiment, the third processing module 112 is specifically used for:

Receive the initial transaction request sent by the requesting device;

Store the mapping relationship between old external accounts and internal accounts on the blockchain;

Among them, the old external account includes federated associated account ciphertext and reset threshold.

As shown in FIG. 15 , an embodiment of the present application provides an electronic device 120 , and the electronic device 120 includes a memory 121 and a processor 122 .

Wherein, the memory 121 is used to store computer instructions executable by the processor;

The processor 122 implements each step in the methods in the above-mentioned embodiments when executing computer instructions. For details, refer to the related descriptions in the foregoing method embodiments.

Optionally, the above-mentioned memory 121 can be independent or integrated with the processor 122 . When the memory 121 is set independently, the electronic device further includes a bus for connecting the memory 121 and the processor 122 .

The embodiment of the present application also provides a computer-readable storage medium, in which computer instructions are stored, and when the processor executes the computer instructions, each step in the method in the foregoing embodiments is implemented.

An embodiment of the present application further provides a computer program product, including computer instructions, and when the computer instructions are executed by a processor, each step in the method in the foregoing embodiments is implemented.

Other embodiments of the present application will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the application, these modifications, uses or adaptations follow the general principles of the application and include common knowledge or conventional technical means in the technical field not disclosed in the application . The specification and examples are to be considered exemplary only, with a true scope and spirit of the application indicated by the following claims.

It should be understood that the present application is not limited to the precise constructions which have been described above and shown in the accompanying drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

A blockchain-based account reset method, characterized in that the method is applied to a requesting device, and the reset system includes a requesting device, a blockchain system and multiple authentication devices, and the method includes:

For each authentication device, obtain the reset information and the ciphertext of the associated account logged in at least one other authentication device, and generate a reset notification request according to the reset information and the ciphertext of the at least one associated account, to obtain A reset notification request corresponding to each authentication device; the reset information includes a new external account and an old external account;

Send a corresponding reset notification request to each authentication device; wherein, the reset transaction request is generated by each authentication device according to the corresponding reset notification request and the ciphertext of the associated account logged on it;

Wherein, the verification result of each associated account is obtained by the block chain system through identity verification according to the reset transaction request sent by each authentication device and the joint associated account ciphertext stored on the block chain, The block chain system is also used to perform account reset processing according to the reset information when the verification result of each associated account satisfies the preset reset condition; the preset reset condition includes an association whose verification result is verified The number of accounts is greater than or equal to the reset threshold.
The method according to claim 1, wherein generating a reset notification request according to the reset information and the ciphertext of the at least one associated account specifically includes:

generating certification information of the authentication device according to the ciphertext of the at least one associated account;

generating the reset notification request according to the certification information of the authentication device and the reset information.
The method according to claim 2, characterized in that generating the certification information of the authentication device according to the ciphertext of the at least one associated account, specifically comprising:

grouping the ciphertexts of the at least one associated account, and performing hash calculation on the ciphertexts in each group to obtain the hash value of each group;

Carry out the hash calculation of the hash values in the group to obtain the hash values of multiple groups after grouping the hash values of each group until the number of groups satisfies the first loop stop condition;

The hash values of multiple groups are used as the certification information of the authentication device.
The method according to any one of claims 1 to 3, wherein obtaining the ciphertext of the associated account logged in at least one other authentication device specifically includes:

For each authentication device, the associated account logged in on the authentication device is obtained, and hash processing is performed on the associated account to generate the ciphertext of the associated account, so as to obtain the ciphertext of multiple associated accounts.
The method according to any one of claims 1 to 3, wherein the reset information includes a new external account, and the obtaining reset information specifically includes:

A first asymmetric key is randomly generated, and a new external account is generated according to the public key in the first asymmetric key.
The method according to any one of claims 1 to 3, wherein the reset information includes the old external account, and before obtaining the reset information and the ciphertext of the associated account logged on at least one other authentication device, The methods include:

Encrypt all associated accounts associated with the old external account to generate a joint associated account ciphertext; wherein, the old external account is generated according to the public key in the second asymmetric key;

Generate an initialization transaction request according to the ciphertext of the joint associated account and the reset threshold, and use the private key in the second asymmetric key to sign the initialization transaction request;

Send a signed initial transaction request to the blockchain system;

Wherein, the initialization transaction request is used to make the block chain system store the mapping relationship between the old external account and the internal account on the block chain, and the internal account includes the ciphertext of the joint associated account and the reset threshold.
The method according to claim 6, characterized in that, encrypting all associated accounts associated with the old external account to generate a joint associated account ciphertext, specifically comprising:

Perform hash calculation on each associated account associated with the old external account to obtain the ciphertext of each associated account associated with the old external account;

grouping the ciphertexts of each associated account associated with the old external account, and performing hash calculation on the ciphertexts in each group to obtain the hash value of each group;

Carry out cyclic execution to group the hash values of each group and then perform hash calculation on the hash values in the group to obtain the hash values of multiple groups until the number of groups satisfies the second loop stop condition;

Perform hash calculation on the hash values of the multiple groups to obtain the ciphertext of the joint associated account.
A blockchain-based account reset method, characterized in that the method is applied to authentication equipment, and the method includes:

Receive a reset notification request sent by the requesting device; wherein, the reset notification request is generated based on the reset information and the ciphertext of the associated account logged in on other authentication devices; the reset information includes the new external account and the old external account account;

generating a reset transaction request according to the reset notification request and the ciphertext of the associated account logged in on the authentication device;

Send the reset transaction request to the block chain system; wherein, the verification result of each associated account is that the block chain system sends the reset transaction request according to each authentication device and the joint associated account stored on the block chain The ciphertext is obtained through identity verification, and the blockchain system is also used to perform account reset processing according to the reset information when the verification results of each associated account meet the preset reset conditions; the preset reset conditions Include the number of associated accounts whose verification result is verified to be greater than or equal to the reset threshold.
The method according to claim 8, characterized in that, based on the ciphertext of the associated account logged in on the authentication device, the ciphertext of the associated account logged in on the other authentication device, and the re-encrypted account logged in on the requesting device Before the configuration information generates a reset transaction request, the method further includes:

Perform hash processing on the associated account logged in on the authentication device to obtain the ciphertext of the associated account logged in on the authentication device.
A blockchain-based account reset method, characterized in that the method is applied to a blockchain system, and the method includes:

Receive reset transaction requests sent by each authentication device; wherein, each of the reset transaction requests is generated by the corresponding authentication device according to the ciphertext of the associated account logged on the corresponding authentication device and the reset notification request; each authentication The reset notification request corresponding to the device is generated by the requesting device according to the ciphertext and reset information of the associated account logged on at least one other authentication device; the reset information includes the new external account and the old external account;

Perform identity verification on each associated account according to the reset transaction request sent by each authentication device and the joint associated account ciphertext stored on the block chain, and obtain the verification result of each associated account;

When the verification result of each associated account satisfies the preset reset condition, the account reset process is performed according to the reset information; the preset reset condition includes that the number of associated accounts whose verification result is verified is greater than or equal to the reset threshold .
The method according to claim 10, characterized in that, performing identity verification on each associated account according to the reset transaction request sent by each authentication device and the joint associated account ciphertext stored on the block chain, to obtain The verification results of each associated account specifically include:

For each reset transaction request, analyze the reset transaction request to obtain the certification information of the authentication device and the ciphertext of the associated account logged on the authentication device, and encrypt the certification information and the ciphertext of the associated account Generate composite ciphertexts to obtain multiple composite ciphertexts;

For each synthesized ciphertext, compare the synthesized ciphertext with the joint associated account ciphertext to obtain the verification result of the associated account, so as to obtain the verification results of multiple associated accounts.
The method according to claim 10 or 11, wherein when the verification result of each associated account satisfies a preset reset condition, the account reset process is performed according to the reset information, specifically comprising:

When the verification result is that the number of associated accounts that have passed the verification exceeds the reset threshold, update the old external account with the new external account in the blockchain, and establish a relationship between the new external account and the old external account Mapping relationship between internal accounts;

Wherein, the internal account includes the cipher text of the joint associated account and the reset threshold.
The method according to claim 10 or 11, wherein before receiving the transaction reset request sent by each authentication device, the method further comprises:

receiving an initialization transaction request sent by the requesting device;

storing the mapping relationship between the old external account and the internal account on the blockchain;

Wherein, the old external account includes the joint associated account ciphertext and a reset threshold.
An electronic device, comprising: a processor, and a memory communicatively connected to the processor;

the memory stores computer-executable instructions;

The processor executes the computer-executed instructions stored in the memory, so as to realize the account reset method described in any one of claims 1-7, or 8 or 9.
A computer-readable storage medium, characterized in that computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to implement any one of claims 1 to 7, 8 Or 9, or, the account reset method described in any one of 10 to 13.