CN110070363A - Account management method and verification method in block chain network and terminal equipment - Google Patents

Abstract

Embodiments of the present invention relate to the field of communication technologies, and disclose an account management method, a verification method and a terminal device in a blockchain network. An account management method in a blockchain network includes: when initiating a transaction to a transaction recipient through a first account, carrying an encrypted code generated based on a code password in the transaction information; The account initiates a verification transaction to the transaction receiver for verifying the second account. The verification transaction includes historical transaction information and a coded password for the transaction receiver to execute on the second account according to the coded password and the encrypted password in the historical transaction information. Verification operation; after the verification is passed, the second account obtains the control right of the first account; the embodiment of the present invention also provides a verification method and a terminal device in a blockchain network; after the user's account private key is lost, it can be retrieved The account-related information in the lost account can avoid the user's asset loss caused by the loss of the account's private key.

Description

Account management method, verification method and terminal device in blockchain network

technical field

The embodiments of the present invention relate to the field of communication technologies, and in particular, to an account management method, a verification method and a terminal device in a blockchain network.

Background technique

Blockchain is a new application mode of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. Its essence is a decentralized database. At the same time, as the underlying technology of digital currency, it is a series of data blocks associated with cryptographic methods. Each data block contains a batch of digital currency network transaction information. Used to verify the validity of its information and generate the next block.

At present, blockchain-based transactions are generally carried out based on wallets, each wallet has a unique address, and users conduct transactions through this unique address. With the rapid development of blockchain technology, blockchain-related applications are becoming more and more extensive, business exchanges between enterprises and individuals through blockchain are increasing, and transaction transfers will become more and more frequent. As a carrier of transactions, the security of blockchain wallets is particularly important.

However, the inventor found that there are at least the following problems in the prior art: in the blockchain-based transaction of the prior art, once the private key of the user's account is lost, the account and the data assets in the account and other account-related information cannot be retrieved, resulting in the loss of the user's assets.

SUMMARY OF THE INVENTION

The purpose of the embodiments of the present invention is to provide an account management method and terminal device in a blockchain network, which can make it possible to retrieve the account-related information in the lost account after the user's private key of the account is lost, so as to prevent the user from Asset loss caused by loss of account private key.

In order to solve the above technical problems, the embodiments of the present invention provide an account management method in a blockchain network, including: when initiating a transaction to the transaction recipient through the first account, carrying a password generated based on a coded password in the transaction information. Encryption code; after the key of the first account is lost, a verification transaction is initiated to the transaction receiver through the second account to verify the second account, and the verification transaction includes historical transaction information and code password for the transaction receiver to use according to The cipher password and the encrypted cipher in the historical transaction information perform a verification operation on the second account; after the verification is passed, the second account obtains the control right of the first account.

Embodiments of the present invention also provide an account verification method in a blockchain network, including: receiving a verification transaction for verifying the account to be verified; the verification transaction includes historical transaction information and a password in coded language; obtaining according to the historical transaction information To the encrypted code in the historical transaction; wherein, the encrypted code is generated based on the code password; according to the encrypted code and the code password in the verification transaction, the verification operation is performed on the account to be verified; the account to be verified is used to obtain the use code after the verification is passed. Control of the first account with the password.

Embodiments of the present invention also provide a terminal device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by at least one processor. A processor executes so that at least one processor can execute the account management method in the blockchain network as described above, or can execute the account verification method in the blockchain network as described above.

Compared with the prior art, the embodiment of the present invention discloses an account management method in a blockchain network. When a user initiates a transaction to a transaction recipient through a first account, the transaction information carries a password generated based on a coded password. Encryption code; after the key of the first account is lost, a verification transaction is initiated to the transaction receiver through the second account to verify the second account, and the verification transaction includes historical transaction information and code password for the transaction receiver to use according to The cipher password and the encrypted cipher in the historical transaction information perform a verification operation on the second account; after the verification is passed, the second account obtains the control right of the first account. By carrying in the transaction information an encrypted cipher based on a coded password known only to the transaction initiator, the second account newly applied for after the key of the first account is lost can initiate a verification transaction based on the coded password and historical transaction information. , Safely verify whether the user who uses the second account is the same user as the user who uses the first account; after the verification is passed, the second account obtains the control right of the first account, so that the user can retrieve the lost account in the account Relevant information, so as to avoid the user's asset loss caused by the loss of the account private key.

In addition, the encrypted code is specifically: the encrypted code obtained by encrypting the hash value of the first information with the public key of the transaction recipient; the first information specifically includes: the transaction flow used to uniquely identify the transaction, the first account information , the account information of the transaction recipient, the asset transfer information and the hash value of the coded password; the coded password included in the verification transaction is specifically: the hash value of the coded password. Provides a specific data structure for encrypted ciphers. Among them, since the encrypted code includes the hash value of the code password, users other than the transaction initiator cannot know the specific content of the code code, so that the code code to the transaction initiator can not be leaked.

In addition, before initiating a verification transaction for verifying the second account to the transaction recipient through the second account, the method further includes: selecting a transaction recipient that satisfies a preset condition as a target transaction recipient; receiving the transaction through the second account The party initiates a verification transaction for verifying the second account, specifically: initiating a verification transaction for verifying the second account to the target transaction recipient through the second account. By selecting a target transaction recipient and performing a verification operation on the second account, different needs of users in practical applications can be better met.

In addition, the number of transaction recipients is multiple; a verification transaction for verifying the second account is initiated to the transaction recipient through the second account, specifically: initiating a verification transaction to the transaction recipients through the second account to verify the second account respectively. The second account performs a verification transaction for verification; the verification is passed, specifically: the sum of the number of verification transactions passed by multiple transaction recipients reaches a preset threshold. The user can obtain the control right of the first account in the second account only after the preset number of verification transactions are passed, and the security is higher.

Description of drawings

FIG. 1 is a flowchart of an account management method in a blockchain network provided according to a first embodiment of the present invention;

2 is a flowchart of an account management method in a blockchain network provided according to a second embodiment of the present invention;

3 is a flowchart of an account management method in a blockchain network provided according to a third embodiment of the present invention;

4 is a flowchart of an account verification method in a blockchain network provided according to a fourth embodiment of the present invention;

5 is a flowchart of sub-steps of step 403 in an account verification method in a blockchain network provided according to the fourth embodiment of the present invention;

FIG. 6 is a schematic diagram of structural connection of a terminal device according to a fifth embodiment of the present invention.

Detailed ways

In order to make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the various embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, those of ordinary skill in the art can appreciate that, in the various embodiments of the present invention, many technical details are set forth in order for the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical solutions claimed in the present application can be realized. The following divisions of the various embodiments are for the convenience of description, and should not constitute any limitation on the specific implementation of the present invention, and the various embodiments may be combined with each other and referred to each other on the premise of not contradicting each other.

The first embodiment of the present invention relates to an account management method in a blockchain network. In this embodiment, when a transaction is initiated to the transaction recipient through the first account, the encrypted cipher generated based on the cipher password is carried in the transaction information; after the secret key of the first account is lost, the transaction recipient is sent to the transaction recipient through the second account Initiate a verification transaction for verifying the second account, and the verification transaction includes historical transaction information and a coded password for the transaction recipient to perform a verification operation on the second account according to the coded password and the encrypted password in the historical transaction information; After that, the second account obtains the control right of the first account.

In this embodiment, an encrypted code is generated by carrying a code based on a code known only to the transaction initiator in the transaction information. After the secret key of the first account is lost, the newly applied for the second account initiates an encrypted code based on the code password and historical transaction information. The verification transaction can effectively and safely verify whether the user using the second account is the same user as the user using the first account; after the verification is passed, the second account obtains the control right of the first account, so that the user can retrieve the lost The account-related information in the account, so as to avoid the user's asset loss caused by the loss of the account's private key.

The implementation details of the account management method in the blockchain network of the present embodiment will be described in detail below. The following contents are only provided for the convenience of understanding, and are not necessary to implement this solution.

The flowchart of the account management method in the blockchain network in this embodiment is shown in Figure 1, including:

Step 101, when initiating a transaction to the transaction recipient through the first account, carry the encrypted code generated based on the code password in the transaction information.

Specifically, the encrypted code in this embodiment may be an encrypted code obtained by encrypting the hash value of the first information with the public key of the transaction recipient. Wherein, the first information mentioned here may include: transaction flow used to uniquely identify the transaction, first account information, transaction recipient account information, asset transfer information, and a hash value of a password in cipher language. In this embodiment, the specific content of the coded password may be related to the transaction or not related to the transaction, similar to the password prompt information, which is equivalent to generating a transaction mark that cannot be known by a third party except the transaction initiator.

It should be noted that the transaction flow in this embodiment is to uniquely identify the transaction, and through the identification, the relevant transaction information under the identification can be found.

For example, if the cipher password of the first account is: "Oriental Pearl", then the data structure of the encrypted cipher generated by the user's terminal device based on the cipher password may be: the public key of the transaction recipient (SHA256 (transaction flow + first account) information + transaction recipient account information + asset transfer information + SHA256 (Oriental Pearl))), based on this, it is not difficult to find that anyone can verify whether the transaction information initiated by the transaction initiator carries encrypted codes, but except the transaction initiator , almost no one knows the specific content of the coded password, which ensures the privacy of the coded password.

In the above example, the hash value of the coded password and the hash value of the first information are both: 256-bit hash values, which are respectively used to represent the unique value of the coded password and the unique value of the first information, and are unique. Of course, the specific hash value algorithm is not specifically limited in this embodiment.

In addition, the transaction information when a transaction is initiated to the transaction recipient through the first account may also include, but is not limited to, the following information: transaction flow used to uniquely identify the transaction, first account information, transaction recipient account information, asset transfer information and the private key signature of the first account. Among them, since the transaction information includes the signature of the private key of the first account, the security and legitimacy of the transaction can be ensured.

Step 102, after the secret key of the first account is lost, a verification transaction for verifying the second account is initiated to the transaction recipient through the second account.

Specifically, if the secret key of the first account is lost, the user can apply for a new second account, and the user's terminal device obtains the transaction flow of the first account from the blockchain through the second account, and obtains the transaction flow including the code word Password transactions, generate verification transactions. The verification transaction includes historical transaction information and a coded password, for the transaction recipient to perform a verification operation on the second account according to the coded password and the encrypted password in the historical transaction information. Wherein, the historical transaction information mentioned here is the transaction information in step 101 .

It can be understood that the reason why the terminal device of the transaction recipient can perform the verification operation on the second account according to the cipher password and the encrypted cipher in the historical transaction information is because: the terminal device of the transaction recipient can verify the data in the historical transaction information. The encrypted cipher is decrypted, so as to obtain the information based on the cipher password carried in the transaction information that the user conducts the transaction with the transaction recipient through the first account before the key of the first account is lost; The transaction also includes the information of the coded password. Since the coded password is only known to the transaction initiator, if the user conducts a transaction with the transaction recipient through the first account, the information based on the coded password carried in the transaction information will be communicated with the user through the first account. If the information of the coded password also included in the verification transaction sent by the second account is consistent, it can be verified that: the user who currently initiates the verification transaction through the second account is the user of the first account.

Further, the coded password included in the verification transaction can be the hash value of the coded password. Specifically, the verification transaction can include the second information obtained by encrypting the hash value of the coded password with the public key of the transaction recipient. , and the data structure of the second information may be: the public key of the transaction recipient (SHA256 (cryptographic password)). Wherein, the verification transaction may include but is not limited to: the first asset recovery transaction flow, historical transaction flow, historical transaction signature, first account information, transaction receiver account information, second information, third The second account information, the private key signature of the second account. Among them, since the encrypted code includes the hash value of the code password, users other than the transaction initiator cannot know the specific content of the code code, so that the code code to the transaction initiator can not be leaked.

It should be noted that, in this embodiment, after the secret key of the first account is lost, the number of retrieving transactions for retrieving the first account by initiating a verification transaction to the transaction recipient through the second account can be limited to N, where N is a natural number greater than or equal to 1. Among them, the specific value of N is determined by the protocol set in the blockchain. Under the limitation of the number of retrieved transactions, the abnormal users who frequently initiate verification transactions to the transaction recipient through the second account to retrieve the first account can be restricted.

Step 103: After the verification is passed, the second account acquires the control right of the first account.

Specifically, after the transaction recipient performs a verification operation on the second account according to the coded password and the encrypted coded language in the historical transaction information, the waiting period is entered. If the verification result is obtained, after the verification is passed, the second account obtains the control right of the first account, which can avoid the user's asset loss caused by the loss of the account's private key.

It is not difficult to find that an account management method in a blockchain network provided by this embodiment generates an encrypted cipher by carrying a cipher password known only to the transaction initiator in the transaction information. After the secret key of the first account is lost, The newly applied second account initiates a verification transaction based on the coded password and historical transaction information, which can effectively and safely verify whether the user using the second account is the same user as the user using the first account; The second account obtains the control right of the first account, so that the user can retrieve the account-related information in the lost account, thereby avoiding the user's asset loss caused by the loss of the account's private key.

The second embodiment of the present invention relates to an account management method in a blockchain network. The second embodiment is an improvement made on the basis of the first embodiment, and the specific improvement lies in that: in this embodiment, a verification transaction for verifying the second account is initiated to the transaction recipient through the second account Previously, a transaction recipient that satisfies a preset condition is also selected as a target transaction recipient, and a verification transaction for verifying the second account is initiated to the target transaction recipient through the second account. In this embodiment, it is disclosed that the verification operation can be performed on the second account by selecting the target transaction recipient, which can better meet the different needs of users in practical applications.

The flowchart of the account management method in the blockchain network in this embodiment is shown in Figure 2, including:

Step 201, when initiating a transaction to the transaction recipient through the first account, carry the encrypted code generated based on the code password in the transaction information.

Since this step is substantially the same as step 101 in the first embodiment, in order to avoid repetition, it will not be repeated here.

Step 202, after the secret key of the first account is lost, select a transaction recipient that satisfies a preset condition as a target transaction recipient.

Specifically, through the blockchain network, according to the transaction information of the user's first account, a specific transaction recipient can be selected as the target transaction recipient according to a certain algorithm. For example, the earliest transaction information may be selected from the transaction information of the first account, the information of the transaction recipient may be obtained according to the earliest transaction information, and the transaction recipient may be regarded as the target transaction recipient. For another example, the latest transaction information from the current time may be selected from the transaction information of the first account, the transaction recipient information is obtained according to the latest transaction information, and the transaction recipient is used as the target transaction recipient. In addition, according to a certain algorithm, the transaction recipient may be randomly selected as the target transaction recipient in the transaction information of the first account, which is not specifically limited in this embodiment.

In addition, in this embodiment, a specific transaction recipient can also be selected as the target transaction recipient according to the provisions of the smart contract. Among them, the smart contract mentioned here can be understood as the digital network version of the traditional contract, which is a computer program running on the blockchain, which can be executed by itself when the conditions written in the source code are satisfied. Since a smart contract can be trusted by users once written, the terms of the contract cannot be changed. That is to say, no one can modify the smart contract, which is immutable. This makes it impossible to change to select the transaction recipient that satisfies the condition B as the target transaction recipient if the regulation of the written smart contract is to select the transaction recipient that satisfies the A condition as the target transaction recipient.

Step 203 , initiate a verification transaction for verifying the second account to the target transaction recipient through the second account.

The verification transaction includes historical transaction information and a coded password, for the transaction recipient to perform a verification operation on the second account according to the coded password and the encrypted password in the historical transaction information.

In this embodiment, a verification transaction for verifying the second account is only initiated to the target transaction recipient through the second account.

Step 204, after the verification is passed, the second account acquires the control right of the first account.

Since this step is substantially the same as step 103 in the first embodiment, in order to avoid repetition, it will not be repeated here.

It is not difficult to find that, in an account management method in a blockchain network provided by this embodiment, before initiating a verification transaction for verifying the second account to the transaction recipient through the second account, it also selects a method that satisfies a preset condition. The transaction receiver is used as the target transaction receiver, and a verification transaction for verifying the second account is initiated to the target transaction receiver through the second account. In this embodiment, it is disclosed that the verification operation can be performed on the second account by selecting the target transaction recipient, which can better meet the different needs of users in practical applications.

The third embodiment of the present invention relates to an account management method in a blockchain network. The third embodiment is an improvement made on the basis of the first embodiment. The specific improvement lies in that: in this embodiment, the number of transaction recipients is multiple; A verification transaction for verifying the second account; the verification is passed only when the sum of the number of verification transactions passed by multiple transaction recipients reaches a preset threshold. In this embodiment, the user can obtain the control right of the first account in the second account only after the preset number of verification transactions are passed, and the security is higher.

The flowchart of the account management method in the blockchain network in this embodiment is shown in FIG. 3 , including:

Step 301, when initiating a transaction to the transaction recipient through the first account, carry the encrypted code generated based on the code password in the transaction information.

Since this step is substantially the same as step 101 in the first embodiment, in order to avoid repetition, it will not be repeated here.

Step 302: After the secret key of the first account is lost, a verification transaction for verifying the second account is respectively initiated to multiple transaction recipients through the second account.

In this embodiment, the number of transaction recipients is plural.

Generally speaking, from the registration of the first account to the loss of the secret key of the first account, transactions have been conducted with many transaction recipients through the first account respectively. Therefore, when a verification transaction for verifying the second account is initiated to the transaction recipient through the second account, verification transactions for verifying the second account may be initiated to multiple transaction recipients through the second account. The verification transaction includes historical transaction information and a coded password, for multiple transaction recipients to perform verification operations on the second account according to the coded password and the encrypted password in the historical transaction information, respectively.

For example, it is possible to randomly select 5 transaction recipients from among 20 transaction recipients, and initiate verification transactions to the 5 transaction recipients through the second account for verifying the second account, for the 5 transaction recipients. The receiver performs a verification operation on the second account according to the encrypted cipher and the cipher password of the historical transaction information included in the verification transaction, respectively. Of course, the above is only an example, and the practical application should not be limited by the above. For example, 10 transaction recipients or 20 transaction recipients may also be selected to perform the verification operation on the second account respectively.

Step 303 , in the verification transaction for verification, when the sum of the number of verified items reaches a preset threshold, the second account acquires the control right of the first account.

In one embodiment, if a verification transaction for verifying the second account is respectively initiated to 20 transaction recipients through the second account, the preset threshold is set to 80% of the total number of transaction recipients, that is, 16. If the total number of verification transactions passed by 20 transaction receivers is 5, and the preset threshold of 16 is not reached, the verification fails and the process ends; if the number of verification transactions passed by 20 transaction receivers is verified The total number is 19, and if the preset threshold of 16 is reached, the verification is passed. The setting of the preset threshold may be a fixed value, or may be set according to the total number of transaction recipients who perform the verification operation on the second account, which is not specifically limited here.

It should be noted that this embodiment may also be an improvement made on the basis of the second embodiment.

It is not difficult to find that, in an account management method in a blockchain network provided by this embodiment, the number of transaction recipients is multiple; the second account is used to respectively initiate multiple transaction recipients to verify the second account. The verification transaction; the verification is passed only when the total number of verification transactions passed by multiple transaction recipients reaches the preset threshold. In this embodiment, the user can obtain the control right of the first account in the second account only after the preset number of verification transactions are passed, and the security is higher.

The fourth embodiment of the present invention relates to an account verification method in a blockchain network. In this embodiment, a verification transaction for verifying the account to be verified is received; the verification transaction includes historical transaction information and a password; the encrypted password in the historical transaction is obtained according to the historical transaction information; wherein, the encrypted password is generated based on the password password; According to the encrypted code and the code password in the verification transaction, the verification operation is performed on the account to be verified; the account to be verified is used to obtain the control right of the first account using the code password after the verification is passed.

In this embodiment, after receiving the verification transaction for verifying the account to be verified, according to the historical transaction information included in the verification transaction, the encrypted code in the historical transaction is obtained; The encrypted code received, and the verification operation is performed on the account to be verified. If the verification is passed, it means that the account to be verified and the first account using the password password use the same password. Since the password password is only known to the transaction initiator, after the verification is passed, the account to be verified can obtain the password using the password password. The control right of the first account enables the user to retrieve the account-related information in the lost account, thereby avoiding the user's asset loss caused by the loss of the account private key.

The implementation details of the account verification method in the blockchain network of the present embodiment will be described in detail below. The following contents are only provided for the convenience of understanding, and are not necessary to implement this solution.

The flowchart of the account verification method in the blockchain network in this embodiment is shown in Figure 4, including:

Step 401: Receive a verification transaction for verifying the account to be verified.

Among them, the verification transaction includes historical transaction information and coded password. The account to be verified here specifically refers to the newly applied account after the private key of the user's first account is lost.

Specifically, the cipher password included in the verification transaction may be a hash value of the cipher password. Specifically, the cipher password included in the verification transaction may be a second hash value obtained by encrypting the hash value of the cipher password with the public key of the transaction recipient. information, and the data structure of the second information may be: the public key of the transaction recipient (SHA256 (cryptographic password)). Wherein, the verification transaction may include but is not limited to: the first asset recovery transaction flow, historical transaction flow, historical transaction signature, first account information, transaction receiver account information, second information, third Second account information, the private key signature of the second account; the second account mentioned here is the account to be verified. Among them, since the encrypted code includes the hash value of the code password, users other than the transaction initiator cannot know the specific content of the code code, so that the code code to the transaction initiator can not be leaked.

In step 402, the encrypted code words in the historical transaction are acquired according to the historical transaction information. Among them, the encrypted code is generated based on the code password.

Specifically, the encrypted code in this embodiment may be an encrypted code obtained by encrypting the hash value of the first information with the public key of the transaction recipient. Wherein, the first information mentioned here may include: transaction flow used to uniquely identify the transaction, first account information, transaction recipient account information, asset transfer information, and a hash value of a password in cipher language. In this embodiment, the specific content of the coded password may be related to the transaction or not related to the transaction, similar to the password prompt information, which is equivalent to generating a transaction mark that cannot be known by a third party except the transaction initiator.

In addition, the historical transaction information in this embodiment may also include, but is not limited to, the following information: transaction flow for uniquely identifying transactions, the first account information, the transaction recipient account information, asset transfer information, and the first The account's private key signature. Among them, since the historical transaction information includes the private key signature of the first account, the security and legality of the transaction can be ensured.

Step 403: Perform a verification operation on the account to be verified according to the encrypted cipher and the cipher password in the verification transaction.

The account to be verified is used to obtain the control right of the first account using the coded password after the verification is passed.

Specifically, this step 403 may include the following sub-steps, and the specific flowchart is shown in FIG. 5 :

Sub-step 4031, decrypt the encrypted code in the historical transaction information with the private key of the transaction recipient, and obtain the hash value of the first information after decryption.

Specifically, if the encrypted code in the historical transaction information is: the public key of the transaction recipient (SHA256 (transaction flow + first account information + transaction recipient account information + asset transfer information + SHA256 (Oriental Pearl))), then the transaction After the recipient's private key decrypts the encrypted code, the obtained hash value of the first information is: SHA256 (transaction flow + first account information + transaction recipient account information + asset transfer information + SHA256 (Oriental Pearl)).

Wherein, the first information may include: transaction flow used to uniquely identify the transaction, first account information, transaction recipient account information, asset transfer information, and a hash value of a coded password.

Sub-step 4032, decrypt the second information with the private key of the transaction recipient to obtain the hash value of the cipher password.

If the second information is obtained by encrypting the hash value of the cipher password with the public key of the transaction receiver, the data structure of the second information is: the public key of the transaction receiver (SHA256 (crypto password)). Then, decrypt the second information with the private key of the transaction recipient, and the obtained hash value of the cipher password is: (SHA256 (cipher password)).

It should be noted that the order of execution of sub-step 4031 and sub-step 4032 is not limited in this embodiment.

Sub-step 4033, acquiring the third information in the historical transaction information.

The third information may include: historical transaction flow, first account information, transaction recipient account information, and asset transfer information.

Sub-step 4034: Calculate the hash value of the combination of the hash value of the third message and the cipher password.

The third information obtained by sub-step 4033 and the coded password obtained by sub-step 4032 can obtain the hash value of the combination of the third information and the hash value of the coded password in this step, and the calculated hash value can be It is expressed as: SHA256 (historical transaction flow + first account information + transaction recipient account information + asset transfer information + (SHA256 (password)).

Sub-step 4035, if the calculated hash value is consistent with the hash value of the first information obtained after decryption, it is determined that the verification is passed.

Specifically, the hash value of the first information obtained in sub-step 4031 is: SHA256 (transaction flow + first account information + transaction recipient account information + asset transfer information + SHA256 (Oriental Pearl)); in sub-step 4034 The hash value calculated in: SHA256 (historical transaction flow + first account information + transaction recipient account information + asset transfer information + (SHA256 (password)); if the calculated hash value is the same as the one obtained after decryption If the hash values of the first information are consistent, it indicates that the code password in the verification transaction is also the "Oriental Pearl". Since the specific content of the code password is only known to the transaction initiator, it can be determined that the first account belongs to the user and the verification is passed; otherwise , the verification fails and the process ends.

In a specific embodiment, after it is determined that the verification is passed, the result of the verification can also be released to the blockchain network, so that the blockchain network can determine the account to be verified when the sum of the number of verified items reaches a preset threshold. Verification passed. Wherein, the result of passing the verification may specifically be the second asset retrieval transaction. The second asset recovery transaction mentioned here may include but is not limited to: second asset recovery transaction flow, first asset recovery transaction flow, first account information, second account information, transaction asset information, transaction weight, The transaction recipient's signature. By sending the data package of the second asset recovery transaction to the second account, the second account obtains the control right of the first account.

Compared with the prior art, an account verification method in a blockchain network provided by this embodiment is obtained by, after receiving a verification transaction for verifying the account to be verified, according to the historical transaction information included in the verification transaction. To the encrypted code in the historical transaction; then according to the code password included in the verification transaction and the obtained encrypted code, the verification operation is performed on the account to be verified. If the verification is passed, it means that the account to be verified and the first account using the password password use the same password. Since the password password is only known to the transaction initiator, after the verification is passed, the account to be verified can obtain the password using the password password. The control right of the first account enables the user to retrieve the account-related information in the lost account, thereby avoiding the user's asset loss caused by the loss of the account private key.

It is not difficult to find that this embodiment is a method example corresponding to any one of the first to third embodiments, and this embodiment can be implemented in cooperation with any one of the first to third embodiments. The relevant technical details mentioned in the first embodiment are still valid in this embodiment, and are not repeated here in order to reduce repetition. Correspondingly, the related technical details mentioned in this embodiment can also be applied to the first embodiment.

The steps of the above various methods are divided only for the purpose of describing clearly. During implementation, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as the same logical relationship is included, they are all within the protection scope of this patent. ;Adding insignificant modifications to the algorithm or process or introducing insignificant designs, but not changing the core design of the algorithm and process are all within the scope of protection of this patent.

The fifth embodiment of the present invention relates to a terminal device, as shown in FIG. 6 , comprising: at least one processor 501; and a memory 502 connected in communication with the at least one processor 501; Instructions executed by the processor 501, the instructions are executed by at least one processor 501 to enable the at least one processor 501 to execute the account management method in the blockchain network as in any one of the first to third embodiments, or The account verification method in the blockchain network as the fourth embodiment can be performed.

The memory 502 and the processor 501 are connected by a bus, and the bus may include any number of interconnected buses and bridges, and the bus connects one or more processors 501 and various circuits of the memory 502 together. The bus may also connect together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface between the bus and the transceiver. A transceiver may be a single element or multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other devices over a transmission medium. The data processed by the processor 501 is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor 501 .

Processor 501 is responsible for managing the bus and general processing, and may also provide various functions including timing, peripheral interface, voltage regulation, power management, and other control functions. The memory 502 may be used to store data used by the processor 501 in performing operations.

That is, those skilled in the art can understand that all or part of the steps in the method of implementing the above embodiments can be completed by instructing relevant hardware through a program, and the program is stored in a storage medium and includes several instructions to make a device ( It may be a single chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, removable hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes.

Those skilled in the art can understand that the above-mentioned embodiments are specific examples for realizing the present invention, and in practical applications, various changes in form and details can be made without departing from the spirit and the spirit of the present invention. scope.

Claims (16)

1. A method for account management in a blockchain network, comprising:

when a transaction is initiated to a transaction receiver through a first account, carrying an encrypted secret generated based on a secret password in transaction information;

after the secret key of the first account is lost, initiating a verification transaction for verifying the second account to the transaction receiver through the second account, wherein the verification transaction comprises historical transaction information and the secret language password, and the transaction receiver executes verification operation on the second account according to the secret language password and the encrypted secret language in the historical transaction information;

and after the verification is passed, the second account acquires the control right of the first account.

2. The method of claim 1, wherein the encryption linger is specifically: the encrypted secret words are obtained by encrypting the hash value of the first information through the public key of the transaction receiver;

the first information specifically includes:

a hash value of the transaction pipeline, the first account information, transaction recipient account information, asset transfer information, and the secret password for uniquely identifying a transaction;

the secret password included in the verification transaction is specifically: a hash value of the lingo password.

3. The method of claim 2, wherein the hash value of the whisper password included in the validation transaction is specifically: and the second information is obtained by encrypting the hash value of the secret password by the public key of the transaction receiver.

4. The account management method in a blockchain network according to claim 3, wherein the verifying the transaction specifically includes:

the first asset retrieval transaction flow, the historical transaction signature, the first account information, the transaction receiver account information, the second account information and the private key signature of the second account are used for uniquely identifying the verification transaction.

5. The method of account management in a blockchain network of claim 1, wherein the transaction information further comprises:

a transaction pipeline for uniquely identifying a transaction, the first account information, transaction recipient account information, asset transfer information, and a private key signature of the first account.

6. The method for account management in a blockchain network according to any one of claims 1 to 5, wherein before the initiating a verification transaction for verifying the second account to the transaction receiver through the second account, the method further comprises:

selecting a transaction receiver meeting preset conditions as a target transaction receiver;

the initiating a verification transaction for verifying the second account to the transaction receiver through the second account specifically includes: and initiating a verification transaction for verifying the second account to the target transaction receiver through the second account.

7. The account management method in a blockchain network according to any one of claims 1 to 5, wherein the number of the transaction recipients is plural;

the initiating a verification transaction for verifying the second account to the transaction receiver through the second account specifically includes:

respectively initiating verification transactions for verifying the second account to the plurality of transaction receivers through the second account;

the verification is passed, and specifically comprises the following steps: the sum of the number of the transaction receivers passing the verification of the verification transaction reaches a preset threshold.

8. A method of account verification in a blockchain network, comprising:

receiving a verification transaction for verifying an account to be verified; the verification transaction comprises historical transaction information and a secret password;

acquiring an encryption secret phrase in the historical transaction according to the historical transaction information; wherein the encrypted secret is generated based on a secret password;

according to the encrypted secret words and the secret word password in the verification transaction, performing verification operation on the account to be verified; and the account to be verified is used for acquiring the control right of the first account using the secret password after verification passes.

9. The account verification method in a blockchain network according to claim 8, wherein the encryption lingo is specifically: the encrypted secret words are obtained by encrypting the hash value of the first information through the public key of the transaction receiver;

the first information specifically includes:

a hash value of the transaction pipeline, the first account information, transaction recipient account information, asset transfer information, and the secret password for uniquely identifying a transaction;

the secret password included in the verification transaction is specifically: a hash value of the lingo password.

10. The method of claim 9, wherein the hash value of the whisper password included in the validation transaction is specifically: and the second information is obtained by encrypting the hash value of the secret password by the public key of the transaction receiver.

11. The method of claim 10, wherein the validating the transaction comprises:

a first asset retrieval transaction pipeline, a historical transaction signature, the first account information, transaction receiver account information, the second information, second account information, a private key signature of the second account for uniquely identifying the verification transaction; and the second account is the account to be verified.

12. The method of account validation in a blockchain network of claim 8, wherein the historical transaction information further includes: a transaction pipeline for uniquely identifying a transaction, the first account information, transaction recipient account information, asset transfer information, and a private key signature of the first account.

13. The method according to claim 10, wherein the performing a verification operation on the account to be verified according to the encrypted secret and the secret password in the verification transaction comprises:

decrypting the encrypted secret words in the historical transaction information by using a private key of a transaction receiver to obtain a hash value of the first information after decryption; decrypting the second information by using a private key of a transaction receiver to obtain a hash value of the secret language password;

acquiring third information in the historical transaction information; the third information specifically includes: historical transaction pipelining, the first account information, transaction receiver account information and asset transfer information;

calculating a hash value of a combination of the third information and the hash value of the whisper password;

and if the hash value obtained by calculation is consistent with the hash value of the first information obtained after decryption, judging that the verification is passed.

14. The method of account validation in a blockchain network of claim 13, further comprising, after said determining that validation passed:

and issuing the verification passing result to the block chain network, so that the block chain network judges that the account to be verified passes the verification when the sum of the verification passing numbers reaches a preset threshold.

15. The method of account validation in a blockchain network of claim 14, wherein the result of the validation is specifically a second asset retrieval transaction; the second asset recovery transaction specifically comprises:

the second asset retrieval transaction pipeline, the first account information, the second account information, the transaction asset information, the transaction weight, and the transaction receiver signature.

16. A terminal device, comprising:

at least one processor; and the number of the first and second groups,

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a method of account management in a blockchain network as claimed in any one of claims 1 to 7 or to perform a method of account verification in a blockchain network as claimed in any one of claims 8 to 15.