A method and device for resetting an account private key

Abstract

The present invention discloses a method and device for resetting an account's private key, which is applied to a blockchain system. The method comprises the following steps: a blockchain node receives a private key reset transaction; the private key reset transaction is used to reset a first address account to a second address account; the first address account is bound to a random account; the random account has transaction rights to trade assets of the first address account; the blockchain node executes the private key reset transaction to obtain a transaction result; and after determining, based on the transaction result, that a preset reset condition is satisfied, the first address account bound to the random account is reset to the second address account. When applied to fintech, the above method can reset an account's private key.

Description

Technical Field

[0001] The present invention relates to the fields of financial technology (Fintech) and blockchain (blockchain), and in particular to a method and device for resetting an account private key. Background Art

[0002] With the development of computer technology, more and more technologies are being applied in the financial sector. Traditional finance is gradually shifting towards financial technology (Fintech). However, due to the security and real-time requirements of the financial industry, higher requirements are also placed on technology. For example, when Fintech is combined with the blockchain field, the security requirements for data storage in the blockchain are even higher.

[0003] Most current blockchain platforms utilize a public-private key system to operate and manage accounts. Users maintain their own private keys, which serve as the sole proof of account verification. Consequently, if a private key is lost or leaked, existing technologies cannot reset it, resulting in the loss of all rights and interests associated with the account. Therefore, current methods hinder the ability to reset the account's private key and recover all rights and interests associated with the account after loss or leakage, creating an urgent problem that needs to be addressed. Summary of the Invention

[0004] The present invention provides a method and device for resetting an account private key, which solves the problem in the prior art that the private key of an account cannot be reset after the private key is lost or leaked.

[0005] In a first aspect, the present invention provides a method for resetting an account private key, comprising: a blockchain node receiving a private key reset transaction; the private key reset transaction is used to reset a first address account to a second address account; the first address account is generated based on a first private key; the second address account is generated based on a second private key; the first address account is bound to a random account; the random account has transaction rights to trade assets of the first address account; the blockchain node executes the private key reset transaction to obtain a transaction result, and after determining that a preset reset condition is met based on the transaction result, the first address account bound to the random account is reset to the second address account.

[0006] Under the above method, the first address account is bound to the random account; the random account has the transaction authority to trade the assets of the first address account. Therefore, in the actual transaction process, the transaction operation is not directly performed through the first address account, but the transaction operation on the assets under the first address account is performed through the random account. Therefore, after the blockchain node receives the private key reset transaction, it can reset the first address account bound to the random account to the second address account after determining that the preset reset conditions are met based on the transaction results, and transfer the assets under the first address account to the second address account. Since the second address account can be obtained through the second private key, and the assets under the first address account can be traded through the random account, the private key reset is realized through the second address account, and all rights and interests under the address account of the first private key are recovered.

[0007] In an optional embodiment, the blockchain node executes the private key reset transaction to obtain a transaction result, including: the blockchain node determines that the initiating account of the private key reset transaction is the reset initiating account pre-set by the first address account, and uses the fragment information obtained by executing the private key reset transaction as the transaction result; determining that the preset reset condition is satisfied based on the transaction result includes: determining that the preset reset condition is satisfied based on the fragment information.

[0008] In the above method, the blockchain node determines that the initiating account of the private key reset transaction is the reset initiating account pre-set by the first address account, that is, the first address account can be pre-set as an account for resetting the first address account. After determining that it is the reset initiating account, the private key reset transaction can be executed to obtain fragment information as the transaction result, and determine whether the preset reset condition is met based on the fragment information, thereby providing a method for determining whether the preset reset condition is met based on the reset initiating account.

[0009] In an optional embodiment, determining that the preset reset condition is satisfied based on the fragment information includes: the blockchain node determining that the transaction result of the private key reset transaction is the first fragment information; the blockchain node determining that multiple second fragment information and the first fragment information satisfy the preset reset condition; the multiple second fragment information are fragment information of multiple private key reset transactions accumulated in the blockchain node for the second address account.

[0010] In the above method, the blockchain node determines that the transaction result of the private key reset transaction is the first fragment information; the blockchain node determines that the preset reset condition is met based on multiple second fragment information and the first fragment information; that is, the fragment information of multiple private key reset transactions is required to meet the preset reset condition, thereby increasing the security of private key reset.

[0011] In an optional implementation, the reset initiating account is the platform's governance account and / or a user account associated with the first address account.

[0012] In an optional implementation, the first fragment information is a first weight value; the multiple second fragment information is multiple second weight values; and the preset reset condition includes: the sum of the first weight value and the multiple second weight values is greater than a first threshold.

[0013] In the above method, by setting weight values, the impact of the private key reset transactions of each initiating account on the success of the private key reset is quantified, thereby providing a method for determining the preset reset conditions based on the weight values.

[0014] In an optional implementation, if the reset initiating account is the platform's governance account and / or the user account associated with the first address account, the preset reset condition also includes: the sum of the weight values of successful private key reset transactions initiated by the platform's governance account is greater than a second threshold, and the sum of the weight information of successful private key reset transactions initiated by the user account associated with the first address account is greater than a third threshold.

[0015] Under the above method, by setting the sum of the weight values of successful private key reset transactions initiated by the platform governance account to be greater than the second threshold, and setting the sum of the weight information of successful private key reset transactions initiated by user accounts associated with the first address account to be greater than the third threshold, it can be ensured that the initiating account requesting the reset of the first address account must exceed a certain threshold in the platform governance account and the associated user account, thereby preventing the platform governance account or the associated user account from committing malicious acts and resetting the first address account without authorization.

[0016] In an optional implementation, before the blockchain node executes the private key reset transaction to obtain a transaction result, it also includes: the blockchain node determines that the private key reset transaction is a private key reset transaction newly added for the first address account.

[0017] Under the above method, the blockchain node first determines that the private key reset transaction is a new private key reset transaction for the second address account, and then executes the private key reset transaction, thereby preventing the private key reset transaction of a certain initiating account from repeating the transaction result and preventing the transaction result from being counted into the preset reset condition multiple times.

[0018] In an optional implementation, after resetting the first address account bound to the random account to the second address account, it also includes: the blockchain node receiving a transaction request from the second address account; the transaction request includes the second address account and a transaction signature obtained using the second private key; after the blockchain node determines that the transaction signature verification is successful, it determines the random account bound to the second address account; the blockchain node completes the transaction request through the random account.

[0019] In the above method, after the first address account bound to the random account is reset to the second address account, the blockchain node determines that the transaction signature verification is passed, and then determines the random account bound to the second address account; the blockchain node completes the transaction request through the random account, thereby providing a transaction processing method after the binding relationship of the address account is reset.

[0020] In a second aspect, the present invention provides a device for resetting an account private key, which is applied to a blockchain system, and the device includes: a receiving module for receiving a private key reset transaction; the private key reset transaction is used to reset a first address account to a second address account; the first address account is generated based on a first private key; the second address account is generated based on a second private key; the first address account is bound to a random account; the random account has the transaction authority to trade the assets of the first address account; a processing module for executing the private key reset transaction to obtain a transaction result, and after determining that a preset reset condition is met based on the transaction result, resetting the first address account bound to the random account to the second address account.

[0021] In an optional embodiment, the processing module is specifically used to: determine that the initiating account of the private key reset transaction is the reset initiating account pre-set by the first address account, and use the fragment information obtained by executing the private key reset transaction as the transaction result; and determine that the preset reset condition is met based on the fragment information.

[0022] In an optional embodiment, the processing module is specifically used to: determine that multiple second fragment information and the first fragment information meet the preset reset condition; the multiple second fragment information are fragment information of multiple private key reset transactions accumulated in the device for the second address account.

[0023] In an optional implementation, the reset initiating account is the platform's governance account and / or a user account associated with the first address account.

[0024] In an optional implementation, the first fragment information is a first weight value; the multiple second fragment information is multiple second weight values; and the preset reset condition includes: the sum of the first weight value and the multiple second weight values is greater than a first threshold.

[0025] In an optional implementation, if the reset initiating account is the platform's governance account and / or the user account associated with the first address account, the preset reset condition also includes: the sum of the weight values of successful private key reset transactions initiated by the platform's governance account is greater than a second threshold, and the sum of the weight information of successful private key reset transactions initiated by the user account associated with the first address account is greater than a third threshold.

[0026] In an optional implementation, the processing module is further configured to determine that the private key reset transaction is a new private key reset transaction for the second address account.

[0027] In an optional embodiment, the receiving module is further used to: receive a transaction request from the second address account; the transaction request includes the second address account and a transaction signature obtained using the second private key; the processing module is further used to: after determining that the transaction signature is verified, determine the random account bound to the second address account; the blockchain node completes the transaction request through the random account.

[0028] The above-mentioned second aspect and its respective beneficial effects can refer to the above-mentioned first aspect and its respective beneficial effects, which will not be repeated here.

[0029] In a third aspect, the present invention provides a computer device, comprising a program or instructions, which, when executed, is used to execute the above-mentioned first aspect and each optional method of the first aspect.

[0030] In a fourth aspect, the present invention provides a storage medium comprising a program or an instruction, which, when executed, is used to execute the above-mentioned first aspect and each optional method of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 A flowchart illustrating the steps of a method for resetting an account private key provided in an embodiment of the present application;

[0032] Figure 2 A schematic diagram of the account registration process in a method for resetting an account private key provided in an embodiment of the present application;

[0033] Figure 3 A schematic diagram of the structure of a device for resetting an account private key provided in an embodiment of the present application. DETAILED DESCRIPTION

[0034] In order to better understand the above technical solution, the above technical solution will be described in detail below in combination with the accompanying drawings and specific implementation methods. It should be understood that the embodiments of the present application and the specific features in the embodiments are detailed descriptions of the technical solution of the present application, rather than limitations on the technical solution of the present application. In the absence of conflict, the embodiments of the present application and the technical features in the embodiments can be combined with each other.

[0035] The following first lists the nouns that appear in this application.

[0036] Blockchain: A new distributed infrastructure and computing method that uses a block chain data structure to verify and store data, a distributed node consensus algorithm to generate and update data, cryptography to ensure the security of data transmission and access, and smart contracts composed of automated script code to program and operate data.

[0037] Public key system: Keys are generated in pairs, each consisting of a public key and a private key. In practical applications, the private key is kept by the owner, while the public key needs to be made public.

[0038] Private key: The private key is the only credential of a blockchain account and is used to sign transactions.

[0039] Blockchain account: Blockchain accounts include external accounts and contract accounts. External accounts are based on the public key system. First, the public key is generated by the private key, and the address account is generated by the public key. The address account serves as the external account of the blockchain.

[0040] Transaction signature: The transaction signature is similar to a stamp, which is used to ensure the ownership verification of the transaction. After receiving the transaction broadcast, the node will verify the transaction. If it passes, it will be included in the memory and packaged into the block. Otherwise, it will be discarded.

[0041] Transaction signature generation process: Generally, a summary is generated based on the transaction content, and then encrypted with the private key to obtain a signature.

[0042] Signature verification is when the receiving end generates a comparison summary based on the transaction content, then decrypts the signature using the public key corresponding to the address in the transaction to obtain the signature summary; the two summaries are compared to see if they are consistent, and verification is successful if they are consistent.

[0043] Financial institutions (banks, insurance companies, or securities firms) use a public-private key system to operate and manage accounts during operations (such as bank loans and deposits). Users maintain their own private keys, which serve as the sole proof of account verification. Lost or leaked private keys cannot be reset. Once a private key is lost or leaked, the user cannot change it and will lose all rights and interests in the current account. This situation does not meet the needs of banks and other financial institutions and cannot ensure the efficient operation of their various businesses.

[0044] Additionally, current methods offer some measures to help users recover their private keys. For example, mnemonics can be used to recover a user's private key if lost, though this requires the user to back up their mnemonics. Alternatively, platforms can host encrypted private keys, requiring the user to remember the password used to encrypt the private key. Essentially, the private key is hosted on the platform, leaving the possibility of malicious activity on the platform unavoidable. Both mnemonics and passwords can be lost, forgotten, or stolen, ultimately failing to address the issue of private key loss.

[0045] For this reason, Figure 1 As shown, this application provides a method for resetting an account private key.

[0046] Step 101: The blockchain node receives the private key reset transaction.

[0047] Step 102: The blockchain node executes the private key reset transaction to obtain a transaction result. After determining that a preset reset condition is met based on the transaction result, the first address account bound to the random account is reset to the second address account.

[0048] It should be noted that reset means changing the first address account to the second address account.

[0049] In step 101, the private key reset transaction is used to reset the first address account to the second address account; the first address account is generated based on the first private key; the second address account is generated based on the second private key; the first address account is bound to the random account; and the random account has the trading authority to trade the assets of the first address account.

[0050] Therefore, the method described in steps 101-102 decouples private keys from address accounts. If a user's private key is lost or leaked, the private key can be reset, ensuring the security of personal assets and rights. The core of this solution lies in designing a new account system that makes blockchain accounts independent of private keys, or in other words, not strictly bound to private keys. Private keys serve only as a tool to verify the current account's operational permissions, not transaction permissions, which are strictly bound to random accounts. If the private key is lost, the random account remains unchanged, and assets can still be operated through the original random account.

[0051] Before step 101, the user must first register an account on the platform. The registration process is as follows: Figure 2As shown in the figure, the user first generates a pair of public and private keys, and then generates a corresponding address account based on the public key. The user submits the address account to initiate the account registration process. The blockchain system automatically generates a random account, binds it to the address account corresponding to the public key, and stores it on the blockchain. During the account registration process, the private key is generated off-chain and kept by the user. Only the public key is uploaded to the blockchain during the registration process, ensuring the security of the private key.

[0052] It should be noted that registered accounts can be divided into three categories: platform governance accounts, associated accounts, and ordinary accounts. The details are as follows:

[0053] The registration process for platform governance accounts is the same as for regular accounts. The platform owner of a governance account can be either an individual or a legal entity, elected by blockchain participants and possessing a certain degree of credibility. The platform governance account's responsibility is to assist regular accounts in replacing their private keys. If a regular account's private key is lost, the platform governance account can initiate a private key reset transaction to reset the private key for the regular account.

[0054] Linked accounts are at the same level as regular accounts. Linked accounts are for independent regular accounts and can be thought of as a friend list. Users can manage their own linked accounts (only accounts they have authorized). Linked accounts are responsible for helping regular users replace their private keys. If a user's private key is lost, they can initiate a reset request through a linked account to have it reset.

[0055] A regular account is an independent account that can send transactions on the blockchain. When a user registers an account, the account generated is a regular account. Users can add other regular accounts as their associated accounts. Users can also set their own private key reset method.

[0056] After step 101, an optional implementation after step 102 may be as follows:

[0057] The blockchain node determines that the private key reset transaction is a private key reset transaction newly added for the first address account.

[0058] This method can prevent the private key reset transaction of a certain initiating account from repeating the transaction results and prevent the transaction results from being counted into the preset reset conditions multiple times.

[0059] An optional implementation of step 102 may be as follows:

[0060] Implementation method (1): The blockchain node determines that the initiating account of the private key reset transaction is the reset initiating account pre-set by the first address account, and uses the fragment information obtained by executing the private key reset transaction as the transaction result; and determines that the preset reset condition is met based on the fragment information.

[0061] That is, the process of the above implementation method (1) is to verify whether the initiating account of the private key reset transaction is the pre-set reset initiating account. If it is, the private key reset transaction is processed, the fragment information is obtained, and the preset reset condition is determined to be met based on the fragment information.

[0062] It's worth noting that in the aforementioned implementation (1), a single account can initiate a private key reset transaction, or multiple accounts can initiate a private key reset transaction. When a single account can initiate a private key reset, there's no decentralization, which greatly increases the risk of a single account committing malicious acts.

[0063] A specific optional implementation of implementation mode (1) may be:

[0064] Implementation method (1): The blockchain node determines that the transaction result of the private key reset transaction is the first fragment information; the blockchain node determines that multiple second fragment information and the first fragment information meet the preset reset condition; the multiple second fragment information are fragment information of multiple private key reset transactions accumulated in the blockchain node for the second address account.

[0065] For example, the first and second information segments consist of a single letter, and the preset reset condition is that the information composed of the first and multiple second information segments includes multiple consecutive letters, such as four letters. For example, if the first information segment is a, and the accumulated second information segments are b, c, d, and f, then the combination of a will include four consecutive letters from a to d, meeting the preset reset condition. The specific information segments and preset reset condition can be flexibly set according to the scenario.

[0066] It should be noted that the reset initiating account in implementation (1) and implementation (1) can be the platform's governance account and / or the user account associated with the first address account. When the reset initiating account includes both the platform's governance account and the user account associated with the first address account, it can prevent one party from acting maliciously.

[0067] Since linked accounts are generally authenticated or endorsed by users, and governance accounts are platform-owned accounts, users are required to submit relevant identification to the platform when registering. For security reasons, resetting private keys solely through linked accounts could lead to the possibility of key hijacking; similar issues exist if resetting private keys solely through governance accounts. Private key resets can be achieved through the decentralization of governance and linked accounts. While governance accounts maintain their own credibility, linked accounts are set up and managed by users themselves, eliminating the possibility of collusion between governance and linked accounts.

[0068] In an optional implementation of implementation (1), the first fragment information is a first weight value; the multiple second fragment information is multiple second weight values; the preset reset condition includes: the sum of the first weight value and the multiple second weight values is greater than a first threshold.

[0069] In other words, the user of the first address account can pre-set the weight and threshold for each associated account and governance account for the first address account. The weight can be in any form, such as an arbitrary value or a normalized ratio. For example, if the sum of the weights is set to 100%, the preset reset condition is met when the sum of the first weight and the multiple second weights is greater than or equal to the first threshold of 70%.

[0070] It should be noted that when the weight values of all accounts that can reset the first address account are the same, the private key reset method of the first address account is actually a multi-signature method, that is, the accounts that initiate the private key reset transaction are counted, and the reset is allowed when the count reaches the preset threshold.

[0071] Based on the above solution, a preferred method is:

[0072] If the reset initiating account is the platform's governance account and / or the user account associated with the first address account, the preset reset condition also includes: the sum of the weight values of successful private key reset transactions initiated by the platform's governance account is greater than a second threshold, and the sum of the weight information of successful private key reset transactions initiated by user accounts associated with the first address account is greater than a third threshold.

[0073] In other words, the above method requires that both the platform governance account and the user accounts associated with the first address account meet a certain threshold. Otherwise, even if the sum of the first weight value and the multiple second weight values is greater than or equal to the first threshold, it cannot be reset. In addition, the first threshold can also be set to be greater than the sum of the weight values of all platform governance accounts and greater than the sum of the weight values of all associated user accounts. In other words, whether all platform governance accounts or all associated user accounts jointly commit malicious acts, there is no guarantee that the sum of the first weight value and the multiple second weight values is greater than or equal to the first threshold.

[0074] For scenarios where all weights are the same, the system will accumulate the number of signatures in the current transaction and determine whether the number of signatures from the governance account and the number of signatures from the associated accounts simultaneously reaches the value set for the current ordinary account. If so, the address will be reset, completing the private key reset. If not, other governance accounts or associated accounts will initiate a private key reset transaction, and the cycle will continue.

[0075] An alternative implementation after step 102 is as follows:

[0076] The blockchain node receives a transaction request from the second address account; the transaction request includes the second address account and a transaction signature obtained using the second private key; after the blockchain node determines that the transaction signature is verified, it determines the random account bound to the second address account; the blockchain node completes the transaction request through the random account.

[0077] It can be seen that after step 102 is executed, the account bound to the random account is the second address account. Then, after receiving the transaction request from the second address account, the transaction request can also be completed through the random account bound to the second address account, that is, all the rights and interests of the first address account are restored, but the operation authority is transferred to the second address account.

[0078] like Figure 3 As shown, the present invention provides a device for resetting an account private key, which is applied to a blockchain system, and the device includes: a receiving module 301, which is used to receive a private key reset transaction; the private key reset transaction is used to reset a first address account to a second address account; the first address account is generated based on a first private key; the second address account is generated based on a second private key; the first address account is bound to a random account; the random account has the transaction authority to trade the assets of the first address account; a processing module 302, which is used to execute the private key reset transaction to obtain a transaction result, and after determining that a preset reset condition is met according to the transaction result, reset the first address account bound to the random account to the second address account.

[0079] In an optional embodiment, the processing module 302 is specifically used to: determine that the initiating account of the private key reset transaction is the reset initiating account pre-set by the first address account, and use the fragment information obtained by executing the private key reset transaction as the transaction result; and determine that the preset reset condition is met based on the fragment information.

[0080] In an optional embodiment, the processing module 302 is specifically used to: determine that multiple second fragment information and the first fragment information meet the preset reset condition; the multiple second fragment information are fragment information of multiple private key reset transactions accumulated in the device for the second address account.

[0081] In an optional implementation, the reset initiating account is the platform's governance account and / or a user account associated with the first address account.

[0082] In an optional implementation, the first fragment information is a first weight value; the multiple second fragment information is multiple second weight values; and the preset reset condition includes: the sum of the first weight value and the multiple second weight values is greater than a first threshold.

[0083] In an optional implementation, if the reset initiating account is the platform's governance account and / or the user account associated with the first address account, the preset reset condition also includes: the sum of the weight values of successful private key reset transactions initiated by the platform's governance account is greater than a second threshold, and the sum of the weight information of successful private key reset transactions initiated by the user account associated with the first address account is greater than a third threshold.

[0084] In an optional implementation, the processing module 302 is further configured to: determine that the private key reset transaction is a private key reset transaction newly added for the second address account.

[0085] In an optional implementation, the receiving module 301 is further used to: receive a transaction request from the second address account; the transaction request includes the second address account and a transaction signature obtained using the second private key; the processing module 302 is further used to: determine the random account bound to the second address account after determining that the transaction signature is verified; and the blockchain node completes the transaction request through the random account.

[0086] An embodiment of the present application provides a computer device, including a program or instruction, which, when executed, is used to execute a method for resetting an account private key and any optional method provided in an embodiment of the present application.

[0087] An embodiment of the present application provides a storage medium including a program or instruction. When the program or instruction is executed, it is used to execute a method for resetting an account private key and any optional method provided in an embodiment of the present application.

[0088] Finally, it should be noted that those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, optical storage, etc.) containing computer-usable program code.

[0089] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0090] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0091] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.

Claims

1. A method for resetting an account private key, characterized in that: Applied to a blockchain system, the method includes: The blockchain node receives a private key reset transaction; the private key reset transaction is used to reset a first address account to a second address account; the first address account is generated based on a first private key; the second address account is generated based on a second private key; the first address account is bound to a random account; the random account has transaction rights for the assets of the first address account; The blockchain node executes the private key reset transaction to obtain a transaction result, and after determining that a preset reset condition is satisfied based on the transaction result, resets the first address account bound to the random account to the second address account; Among them, the determination that the preset reset condition is met based on the transaction result includes: the blockchain node determines that the transaction result of the private key reset transaction is the first fragment information; the blockchain node determines that multiple second fragment information and the first fragment information meet the preset reset condition; the multiple second fragment information are fragment information of multiple private key reset transactions accumulated in the blockchain node for the second address account; wherein, the first fragment information is a first weight value; the multiple second fragment information is a multiple second weight values; the preset reset condition includes: the sum of the first weight value and the multiple second weight values is greater than a first threshold.

2. The method according to claim 1, wherein The blockchain node executes the private key reset transaction to obtain a transaction result, including: The blockchain node determines that the initiating account of the private key reset transaction is the reset initiating account preset by the first address account, and uses the fragment information obtained by executing the private key reset transaction as the transaction result.

3. The method according to claim 2, wherein The reset initiating account is the platform's governance account and / or the user account associated with the first address account.

4. The method according to claim 2 or 3, wherein: If the reset initiating account is the platform's governance account and / or the user account associated with the first address account, the preset reset condition also includes: the sum of the weight values of successful private key reset transactions initiated by the platform's governance account is greater than a second threshold, and the sum of the weight information of successful private key reset transactions initiated by user accounts associated with the first address account is greater than a third threshold.

5. The method according to any one of claims 2 to 3, characterized in that Before the blockchain node executes the private key reset transaction to obtain a transaction result, the process further includes: The blockchain node determines that the private key reset transaction is a private key reset transaction newly added for the first address account.

6. The method according to claim 1, wherein After resetting the first address account bound to the random account to the second address account, the method further includes: The blockchain node receives a transaction request from the second address account; the transaction request includes the second address account and a transaction signature obtained using the second private key; After the blockchain node determines that the transaction signature verification is successful, it determines a random account bound to the second address account; The blockchain node completes the transaction request through the random account.

7. A device for resetting an account private key, characterized in that: Applied to a blockchain system, the device includes: A receiving module, configured to receive a private key reset transaction; the private key reset transaction is used to reset a first address account to a second address account; the first address account is generated based on a first private key; the second address account is generated based on a second private key; the first address account is bound to a random account; the random account has transaction rights for the assets of the first address account; A processing module is used to execute the private key reset transaction to obtain a transaction result, and after determining that a preset reset condition is satisfied according to the transaction result, the first address account bound to the random account is reset to the second address account; wherein, determining that the preset reset condition is satisfied according to the transaction result includes: determining that the transaction result of the private key reset transaction is a first fragment information; determining that multiple second fragment information and the first fragment information satisfy the preset reset condition; the multiple second fragment information are fragment information of multiple private key reset transactions accumulated in the blockchain node for the second address account; wherein, the first fragment information is a first weight value; the multiple second fragment information is a multiple second weight values; the preset reset condition includes: the sum of the first weight value and the multiple second weight values is greater than a first threshold.

8. A computer device, characterized in that: The method comprises a program or an instruction, and when the program or the instruction is executed, the method according to any one of claims 1 to 6 is performed.

Images