Method and device for resetting blockchain account key based on biometrics

Abstract

The embodiments of this specification provide a method and device for storing user biometrics in a blockchain and a method and device for resetting an account key. The method for storing user biometrics includes: obtaining the biometrics of the first user; obtaining a trusted user list, the trusted user list including the account identifier of at least one second user, the at least one second user being a preset trusted user of the first user; and sending a transaction to a blockchain node, so that each node in the blockchain respectively sets the biometrics and the trusted user list corresponding to the first account in the account database.

Description

[0001] This application is a divisional application of the invention patent application with application number 201910250773.8 filed on March 29, 2019, and entitled “Method and device for resetting blockchain account keys based on biometrics”. Technical Field

[0002] The embodiments of this specification relate to the field of blockchain technology, and more specifically, to a method and device for storing user biometrics in a blockchain, and a method and device for resetting a blockchain account key. Background Art

[0003] In the new generation of blockchains, such as Ethereum, the concept of accounts is added, where the accounts created by users are external accounts in Ethereum. Typically, each external account has a pair of public and private keys, where the private key is used for digital signatures and the public key is used to verify signatures. In addition, in each node, a data table of all accounts in the blockchain is maintained in the form of a state tree in the local database of the node. The state tree is a mapping between the account address and the account content, and the account content includes account balance, account key information (hash value), etc. Before making a transaction, the user can obtain the other party's balance and verify the other party's key information by querying the state tree. However, in Ethereum, the user must save the private key after creating the account. If the private key is lost or forgotten, the user will not be able to access his account, that is, the user does not have the function of resetting the private key or retrieving the private key. In the EOS blockchain of the prior art, two private keys are used to reset the key, where one private key is used for digital signatures and the other private key is used for key reset. However, the increase in keys increases the management and use costs of keys.

[0004] Therefore, a more efficient solution for resetting account keys in blockchain is needed. Summary of the invention

[0005] The embodiments of this specification aim to provide a more effective method and device for resetting blockchain account keys to address the deficiencies in the prior art.

[0006] To achieve the above-mentioned purpose, in one aspect, the present specification provides a method for storing a user's biometric features in a blockchain, wherein the blockchain is a consortium chain, and each full node in the blockchain is a consensus node of the blockchain, and the method is executed by a blockchain client corresponding to a first account of a first user, comprising:

[0007] Acquiring a biometric feature of the first user;

[0008] Acquire a trusted user list, wherein the trusted user list includes an account identifier of at least one second user, wherein the at least one second user is a preset trusted user of the first user; and

[0009] A first transaction for setting a biometric feature is sent to any full node in the blockchain, so that each full node in the blockchain sets the biometric feature and the trusted user list corresponding to the first account in its local account database, wherein the data field of the first transaction includes the biometric feature and the trusted user list.

[0010] In one embodiment, acquiring the biometric characteristic of the first user includes receiving the biometric characteristic of the first user from a biometric characteristic acquisition device.

[0011] In one embodiment, the biometric feature includes at least one of the following features: face, fingerprint, and iris.

[0012] In one embodiment, the data field includes a biometric ciphertext, and the biometric ciphertext is obtained by encrypting the biometric by the client using a pre-acquired first encryption key jointly negotiated by the full nodes.

[0013] Another aspect of the present specification provides a method for storing a user's biometric features in a blockchain, wherein the blockchain is a consortium blockchain, and each full node in the blockchain is a consensus node of the blockchain, and the method is performed by a first node in the blockchain as a full node, comprising:

[0014] Receiving a first transaction for setting a biometric feature issued by a first account from a blockchain, wherein a data field of the first transaction includes at least a biometric feature corresponding to the first account and a trusted user list;

[0015] After the digital signature of the first transaction is verified, adding the biometrics and the trusted user list corresponding to the first account to the local account database; and

[0016] The first transaction is packaged into a block and sent to at least one full node in the blockchain.

[0017] In one embodiment, adding the biometric and the trusted user list corresponding to the first account in the local account database includes adding the biometric ciphertext and the trusted user list corresponding to the first account in the local account database, wherein the biometric ciphertext is obtained by encrypting the biometric by the first node with the second encryption key jointly negotiated by the full nodes.

[0018] In one embodiment, the account database is a state tree with an MPT tree structure, wherein adding the biometric and trusted user list corresponding to the first account in the local account database includes adding the biometric and trusted user list to the value of the leaf node corresponding to the first account in the local state tree, and updating the value of the existing node related to the leaf node in the state tree accordingly.

[0019] On the other hand, the present specification provides a method for resetting a blockchain account key, wherein the blockchain is a consortium chain, and each full node in the blockchain is a consensus node of the blockchain, and each full node stores a first biometric corresponding to a first account of a first user and a trusted user list in its local account database, wherein the trusted user list includes an account identifier of a second account of a second user, and the method is executed by a blockchain client corresponding to the second account, and includes:

[0020] Acquiring a second biometric feature of the first user;

[0021] Obtaining a second public key of the first account, where the second public key will be used to replace the first public key already existing in the first account; and

[0022] A second transaction for resetting the public key of the first account is sent to any full node in the blockchain, wherein a data field of the second transaction includes the second biometric and the second public key, so that each full node in the blockchain replaces the first public key of the first account stored locally with the second public key.

[0023] In one embodiment, the data field of the second transaction includes a second biometric ciphertext, and the second biometric ciphertext is obtained by the client encrypting the second biometric with a third encryption key pre-acquired and jointly negotiated by the full nodes.

[0024] On the other hand, the present specification provides a method for resetting a blockchain account key, wherein the blockchain is a consortium chain, and each full node in the blockchain is a consensus node of the blockchain, and each full node stores a first biometric corresponding to a first account of a first user and a trusted user list in its local account database, wherein the trusted user list includes an account identifier of a second account of a second user, and the method is executed by a second node in the blockchain as a full node, and includes:

[0025] Receiving from the blockchain a second transaction issued by the second account for resetting the public key of the first account, wherein the data field of the second transaction includes a second biometric feature and a second public key corresponding to the first account, and the second public key will be used to replace the first public key already existing in the first account;

[0026] After the digital signature of the second transaction is verified, determining whether the account identifier of the second account is in the trusted user list, and determining whether the second biometric feature is consistent with the first biometric feature;

[0027] In a case where it is determined that the account identifier of the second account is in the trusted user list and the second biometric feature is consistent with the first biometric feature, replacing the locally stored first public key of the first account with the second public key; and

[0028] The second transaction is packaged into a block and sent to at least one full node in the blockchain.

[0029] In one embodiment, each of the full nodes stores a first biometric ciphertext corresponding to the first account in its local account database, wherein the first biometric ciphertext is encrypted with a second encryption key jointly agreed upon by the full nodes, and the method further includes, before determining whether the second biometric is consistent with the first biometric, decrypting the first biometric ciphertext using a second decryption key jointly agreed upon by the full nodes to obtain the first biometric.

[0030] In one embodiment, the data field of the second transaction includes a second biometric ciphertext, and the second biometric ciphertext is encrypted with a third encryption key jointly agreed upon by the full nodes. The method also includes, before determining whether the second biometric is consistent with the first biometric, decrypting the first biometric ciphertext using the third decryption key jointly agreed upon by the full nodes to obtain the first biometric.

[0031] In one embodiment, the account database also stores a public key hash value of the first account, and the method further includes updating the public key hash value of the first account in the local account database after replacing the first public key of the first account stored locally with the second public key.

[0032] On the other hand, the present specification provides a device for storing a user's biometric features in a blockchain, wherein the blockchain is a consortium blockchain, and each full node in the blockchain is a consensus node of the blockchain, and the device is deployed in a blockchain client corresponding to a first account of a first user, including:

[0033] A first acquisition unit, configured to acquire a biometric feature of the first user;

[0034] A second acquisition unit is configured to acquire a trusted user list, wherein the trusted user list includes an account identifier of at least one second user, and the at least one second user is a preset trusted user of the first user; and

[0035] The sending unit is configured to send a first transaction for setting a biometric feature to any full node in the blockchain, so that each full node in the blockchain sets the biometric feature and the trusted user list corresponding to the first account in its local account database, wherein the data field of the first transaction includes the biometric feature and the trusted user list.

[0036] In one embodiment, the first acquisition unit is further configured to receive the biometrics of the first user from a biometrics collection device.

[0037] On the other hand, the present specification provides a device for storing a user's biometric features in a blockchain, wherein the blockchain is a consortium blockchain, and each full node in the blockchain is a consensus node of the blockchain, and the device is deployed in the blockchain as a first node of the full node, including:

[0038] A receiving unit is configured to receive, from a blockchain, a first transaction for setting a biometric feature issued by a first account, wherein a data field of the first transaction includes at least a biometric feature corresponding to the first account and a trusted user list;

[0039] an adding unit configured to, after the digital signature of the first transaction is verified, add the biometric feature and the trusted user list corresponding to the first account to a local account database; and

[0040] The packaging unit is configured to package the first transaction into a block and send it to at least one full node in the blockchain.

[0041] In one embodiment, the adding unit is further configured to add a biometric ciphertext and a trusted user list corresponding to the first account in a local account database, wherein the biometric ciphertext is obtained by encrypting the biometric by the first node with a second encryption key jointly negotiated by the full nodes.

[0042] In one embodiment, the account database is a status tree having an MPT tree structure, wherein the adding unit is further configured to add the biometric and trusted user list to the value of a leaf node corresponding to the first account in the local status tree, and to update the value of an existing node related to the leaf node in the status tree accordingly.

[0043] On the other hand, the present specification provides a device for resetting a blockchain account key, wherein the blockchain is a consortium chain, and each full node in the blockchain is a consensus node of the blockchain, and each full node stores a first biometric feature and a trusted user list corresponding to a first account of a first user in its local account database, wherein the trusted user list includes an account identifier of a second account of a second user, and the device is deployed on a blockchain client corresponding to the second account, and includes:

[0044] A first acquiring unit, configured to acquire a second biometric feature of the first user;

[0045] A second obtaining unit is configured to obtain a second public key of the first account, where the second public key will be used to replace the first public key already existing in the first account; and

[0046] The sending unit is configured to send a second transaction for resetting the public key of the first account to any full node in the blockchain, wherein the data field of the second transaction includes the second biometric and the second public key, so that each full node in the blockchain replaces the first public key of the first account stored locally with the second public key.

[0047] In one embodiment, the data field of the second transaction includes a second biometric ciphertext, and the second biometric ciphertext is obtained by the client encrypting the second biometric with a third encryption key pre-acquired and jointly negotiated by the full nodes.

[0048] On the other hand, the present specification provides a device for resetting a blockchain account key, wherein the blockchain is a consortium chain, and each full node in the blockchain is a consensus node of the blockchain, and each full node stores a first biometric corresponding to a first account of a first user and a trusted user list in its local account database, wherein the trusted user list includes an account identifier of a second account of a second user, and the device is deployed in the blockchain as a second node of the full node, and includes:

[0049] A receiving unit is configured to receive, from the blockchain, a second transaction issued by the second account for resetting the public key of the first account, wherein the data field of the second transaction includes a second biometric feature and a second public key corresponding to the first account, and the second public key will be used to replace the first public key already in the first account;

[0050] a determining unit configured to, after the digital signature of the second transaction is verified, determine whether the account identifier of the second account is in the trusted user list, and determine whether the second biometric feature is consistent with the first biometric feature;

[0051] a replacing unit configured to, when it is determined that the account identifier of the second account is in the trusted user list and the second biometric feature is consistent with the first biometric feature, replace the locally stored first public key of the first account with the second public key; and

[0052] The packaging unit is configured to package the second transaction into a block and send it to at least one full node in the blockchain.

[0053] In one embodiment, each of the full nodes stores a first biometric ciphertext corresponding to the first account in its local account database, wherein the first biometric ciphertext is encrypted with a second encryption key jointly agreed upon by the full nodes, and the device also includes a first decryption unit configured to decrypt the first biometric ciphertext using the second decryption key jointly agreed upon by the full nodes before determining whether the second biometric is consistent with the first biometric to obtain the first biometric.

[0054] In one embodiment, the data field of the second transaction includes a second biometric ciphertext, and the second biometric ciphertext is encrypted with a third encryption key jointly agreed upon by the full nodes. The device also includes a second decryption unit configured to decrypt the first biometric ciphertext using the third decryption key jointly agreed upon by the full nodes before determining whether the second biometric is consistent with the first biometric to obtain the first biometric.

[0055] In one embodiment, the account database also stores a public key hash value of the first account, and the device also includes an updating unit configured to update the public key hash value of the first account in the local account database after replacing the first public key of the first account stored locally with the second public key.

[0056] On the other hand, the present specification provides a computer-readable storage medium having a computer program stored thereon, which, when executed in a computer, causes the computer to execute any one of the above methods.

[0057] On the other hand, the present specification provides a computing device, including a memory and a processor, wherein executable code is stored in the memory, and when the processor executes the executable code, any of the above methods is implemented.

[0058] In the scheme according to the embodiment of this specification, the function of resetting the account key in the blockchain is realized by combining the user's biometric features and the configuration of the account content in the corresponding account database. Compared with the scheme of using two private keys for key resetting in the prior art, it saves the key management cost and facilitates the user's operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] The embodiments of this specification are described in conjunction with the accompanying drawings to make the embodiments of this specification clearer:

[0060] Figure 1 A blockchain account maintenance system according to an embodiment of this specification is shown;

[0061] Figure 2 A method for storing user biometrics in a blockchain according to an embodiment of this specification is shown;

[0062] Figure 3 A method for resetting a blockchain account key according to an embodiment of this specification is shown;

[0063] Figure 4 The embodiment of the present specification is shown in FIG. Figure 2 and Figure 3 Interaction diagram of the method shown;

[0064] Figure 5 An apparatus 500 for storing user biometrics in a blockchain according to an embodiment of this specification is shown;

[0065] Figure 6 An apparatus 600 for storing user biometrics in a blockchain according to an embodiment of this specification is shown;

[0066] Figure 7 A device 700 for resetting a blockchain account key according to an embodiment of this specification is shown;

[0067] Figure 8 A device 800 for resetting a blockchain account key according to an embodiment of this specification is shown. DETAILED DESCRIPTION

[0068] The embodiments of this specification will be described below with reference to the accompanying drawings.

[0069] Figure 1 The blockchain account maintenance system according to the embodiment of this specification is shown. Figure 1As shown, the system includes multiple full nodes constituting a blockchain (six full nodes are schematically shown in the figure), these nodes are connected in pairs, including, for example, node 11, node 12 and node 13, the blockchain is a consortium chain, each full node in which is a node that can participate in consensus in the consortium chain, which is equivalent to each server of the blockchain platform, and each full node is a trusted node, which corresponds to at least one trusted institution. The system also includes a client 14 and a client 15 of the blockchain, the client is, for example, a light wallet node in the blockchain, which relies on the above-mentioned full nodes for transactions. Among them, client 14 is, for example, a client of the first account of the first user, and client 15 is, for example, a client of the second account of the second user.

[0070] In this blockchain, each full node maintains an account database locally, which is, for example, the state tree shown in the lower right part of the figure, and the state tree is, for example, an MPT tree. The leaf nodes of the MPT tree are the account contents of each account (such as account balance, account biometric information, trusted account list, account key information, etc.), and each parent node of the MPT tree above the leaf node includes at least one address character of the account and a hash value corresponding to all its child nodes, wherein the value of the root node of the MPT tree is the state root of the tree. Through this state tree, the node can obtain the user's biometric features locally through the account address for resetting the user's key. It can be understood that the account database is not limited to the form of an MPT state tree, and can also be in other database forms, such as a Merkle tree, a Trie tree, etc.

[0071] For example, the first user may send a transaction for setting biometrics to any full node through the client 14, so that each full node in the blockchain sets the biometrics and trusted user list corresponding to the first account in its local account database.

[0072] The lower left part of the figure schematically shows the transaction Tx sent by the client 14. It is assumed that the client 14 is the client of the first user Bob, (0xf5e...) is the newly generated account address of Bob, and the client 14 sends the transaction to the node 11. The account address of the node 11 is (0x6f8...), where "Data" is the data field in the transaction, which is, for example, the biometrics and trusted user list corresponding to the first account of the first user. The digital signature "0x93a" in the figure is the encrypted data obtained by encrypting the data field in the transaction by the private key of the first account.

[0073] After receiving the transaction, node 11 verifies the digital signature of the transaction with the public key of the first account obtained in advance to verify that the transaction data has not been tampered with, and sends the transaction to other full nodes in the blockchain (such as node 12), thereby spreading to each full node in the blockchain. Node 13 is determined as the accounting node of the transaction, for example, after verifying the digital signature of the transaction, it updates its local account state tree, that is, updates the value of the leaf node corresponding to the account address in the state tree, that is, adds the biometric feature and the trusted user list in the leaf node, and updates the values ​​of other related nodes of the state tree, including the state root of the root node, and packages the transaction into a block to be stored in the blockchain, wherein the block header of the block includes the updated state root. After node 13 sends the newly generated block to at least one full node in the blockchain, a consensus is reached after verification by a predetermined number of full nodes, thereby generating a new block in the blockchain, and each node updates its local account state tree according to the newly generated block, thereby achieving consistency across the entire network.

[0074] The trusted user list includes, for example, the account identifier of the second account of the second user. When the first user loses the private key and wishes to reset the key (i.e., the public key), the first user can reset the first account key through the second user. After collecting the biometrics of the first user, the second user can send a second transaction for resetting the public key of the first account to any full node (e.g., node 11) in the blockchain through the client 15 corresponding to the second account, so that each full node in the blockchain replaces the previously used public key of the first user stored locally with the new public key of the first user.

[0075] The above blockchain account key reset process is described in detail below.

[0076] Figure 2 A method for storing a user's biometric features in a blockchain according to an embodiment of the present specification is shown, wherein the blockchain is a consortium blockchain, and each full node in the blockchain is a consensus node of the blockchain, and the method is executed by a blockchain client corresponding to a first account of a first user, including:

[0077] In step S202, the biometric characteristics of the first user are obtained;

[0078] In step S204, a trusted user list is obtained, wherein the trusted user list includes an account identifier of at least one second user, and the at least one second user is a preset trusted user of the first user; and

[0079] In step S206, a first transaction for setting a biometric feature is sent to any full node in the blockchain, so that each full node in the blockchain sets the biometric feature and the trusted user list corresponding to the first account in its local account database, wherein the data field of the first transaction includes the biometric feature and the trusted user list.

[0080] As mentioned above, the blockchain is a consortium chain, and each full node of the blockchain corresponds to at least one trust institution, which is equivalent to each server of the blockchain platform, and is used to provide storage and computing functions in the blockchain, such as storing account status trees, storing blocks, verifying transactions, bookkeeping, consensus, etc. Users deposit their biometrics into the blockchain by sending transactions from their clients (i.e., blockchain light nodes) to these full nodes, that is, their biometrics are respectively stored in the account status trees of each full node, so that when the user needs to reset the key, the key can be reset through each full node based on the local biometrics of the user. And each full node ensures the immutability of the data in its respective database based on the blockchain architecture, which increases security compared to ordinary servers.

[0081] The implementation process of each step of the method is described in detail below.

[0082] First, in step S202, the biometric features of the first user are obtained.

[0083] The biometric feature may be one or more features of biometric features such as face, fingerprint, iris, etc. The corresponding biometric feature may be collected by a corresponding feature collection device. For example, features such as face and iris may be collected by a camera, and fingerprints may be collected by a fingerprint collection device. The client may refer to a user's terminal or an APP on the user's terminal. In the case where the client is a user terminal, the client may be equipped with the above-mentioned various feature collection devices to collect features and obtain corresponding features, or the client may be connected to a corresponding feature collection device and receive corresponding features from the feature collection device.

[0084] In step S204, a trusted user list is obtained, wherein the trusted user list includes an account identifier of at least one second user, and the at least one second user is a preset trusted user of the first user.

[0085] When the first user stores the biometrics in the blockchain, the trusted user list will also be stored for biometric-based key reset through the second user. In other words, the second user is a trusted user of the first user. For example, the first user and the second user may be a husband and wife, and the first user's privacy information does not need to be retained by the second user, so that when the first user loses the key, the key can be reset through the second user. The account identifier of each of the at least one second user is, for example, the blockchain account address of each second user. It can be understood that the account identifier is not limited to the account address, as long as it is uniquely corresponding to the second user. For example, the user's blockchain account address is real-name authenticated, so the account identifier can be the identity identifier of the second user, etc.

[0086] In step S206, a first transaction for setting a biometric feature is sent to any full node in the blockchain, so that each full node in the blockchain sets the biometric feature and the trusted user list corresponding to the first account in its local account database, wherein the data field of the first transaction includes the biometric feature and the trusted user list.

[0087] like Figure 1 As shown in , the first transaction includes, for example, the following three fields: "From", "To" and "Data". The "From" field can be filled with the sender's account address, that is, the account address of the first account, which is, for example, Figure 1 The "To" field can be filled with the account address of the node to be sent, for example Figure 1 The account address of node 11 in the blockchain. It can be understood that the first user is not limited to sending the transaction to node 11, but can send it to any full node in the blockchain. The "Data" field is the data field in the transaction. For the first transaction, its data field includes the above-obtained biometrics and the trusted user list.

[0088] In order to ensure that the transaction is not tampered with, the first user will use the private key of the first account to digitally sign the transaction. After the client 14 sends the first transaction with the digital signature to the node 11, the node 11 uses the pre-acquired public key of the first account to decrypt the digital signature to verify that the data field has not been tampered with. After the node 11 verifies the digital signature of the first transaction, it sends the first transaction to at least one full node to which it is connected, thereby broadcasting the first transaction to the blockchain. Figure 1As shown in , node 13 is, for example, a bookkeeping node for storing the first transaction. After receiving the first transaction issued by the first account from the blockchain, node 13 first verifies the digital signature of the transaction in the same way as node 11, and updates the local account database after the verification. The account database is, for example, an MPT tree structure, which can be called a state tree. Specifically, node 13 updates the leaf node corresponding to the account address in the state tree, that is, adds the biometric feature and trusted user list field information corresponding to the account in the leaf node corresponding to the account address, and updates the value of the existing node related to the leaf node in the state tree accordingly, the related nodes include the root node of the state tree, the value of the root node is the state root of the state tree, and the value of the leaf node is the account content corresponding to the account address.

[0089] After updating the account content of the first account, the account content includes at least the following fields: the account identifier, the balance of the account, user biometrics, and a trusted user list. The account content is not limited to including the above fields. For example, the account content may also include field information such as the hash value of the first public key.

[0090] After updating the state tree, if the first transaction is the last transaction in the block to be packaged, node 13 writes the state root of the state tree into the state root field in the block header of the block, and also fills in the transaction root, receipt root, etc. in the block header as known in the art, thereby generating a new block, storing the block in the local block data block, and broadcasting the newly generated block to the blockchain for storage in the blockchain.

[0091] After receiving the newly generated block, a predetermined number of other full nodes in the blockchain verify the block through the state root, transaction root, receipt root, etc. in the block header, and after the verification is passed, update the local state tree similar to node 13, store the block in the local block data block, and reach a consensus on the generation of the block. Other full nodes in the blockchain can then directly download the block and update the local state tree based on the block.

[0092] In one embodiment, the data field of the first transaction includes a biometric ciphertext, which is obtained by encrypting the biometric with the first encryption key jointly negotiated by the full nodes obtained in advance by the client 14. Accordingly, the node 13 can store the biometric ciphertext in the local account state tree, and also include the biometric ciphertext in the block stored in the blockchain, so as to further protect the privacy security of the user.

[0093] In one embodiment, before setting the biometric feature of the first user into the corresponding account content in the state tree, the node 13 encrypts the biometric feature using the second encryption key jointly agreed upon by all full nodes, and sets the encrypted biometric feature into the state tree. In one embodiment, as described above, the data field of the first transaction includes a biometric feature ciphertext, which is obtained by the client 14 encrypting the biometric feature with the first encryption key jointly agreed upon by all full nodes in advance. For security reasons, the node 13 first decrypts the biometric feature ciphertext using the first decryption key jointly agreed upon by all full nodes to obtain the plaintext of the biometric feature, and then encrypts the biometric feature using the second encryption key jointly agreed upon by all full nodes to obtain a new biometric feature ciphertext and store it in the state tree.

[0094] Figure 3 A method for resetting a blockchain account key according to an embodiment of the present specification is shown, wherein the blockchain is a consortium chain, and each full node in the blockchain is a consensus node of the blockchain, and each full node stores a first biometric corresponding to a first account of a first user and a trusted user list in its local account database, wherein the trusted user list includes an account identifier of a second account of a second user, and the method is executed by a blockchain client corresponding to the second account, including:

[0095] In step S302, a second biometric feature of the first user is obtained;

[0096] In step S304, a second public key of the first account is obtained, where the second public key will be used to replace the first public key already existing in the first account; and

[0097] In step S306, a second transaction for resetting the public key of the first account is sent to any full node in the blockchain, wherein the data field of the second transaction includes the second biometric and the second public key, so that each full node in the blockchain replaces the first public key of the first account stored locally with the second public key.

[0098] For example Figure 1 As shown in FIG. 1 , the client 14 is performing Figure 2 After the method shown, each full node in the blockchain stores the biometrics corresponding to the first account and the trusted user list in its account database, wherein the trusted user list includes the second account of the second user. Therefore, when the first user loses the private key, he or she can reset the key through the client of the second user.

[0099] Specifically, first, in step S302, the second biometric feature of the first user is obtained. Figure 1As shown, the first user can come to the location of the client 15 to collect biometrics, or the first user can collect biometrics by himself and then send the biometrics to the second user's client 15 in a secure manner. Here, the second biometric refers to the biometric of the first user obtained through the client 15 to distinguish it from the biometric of the first user obtained through the client 14 and stored in the state tree (herein referred to as the first biometric).

[0100] In step S304, a second public key of the first account is obtained, and the second public key will be used to replace the existing first public key of the first account.

[0101] For example, the client 15 may receive the regenerated second public key of the first account from the client 14. Alternatively, the second user may obtain the second public key from the first user, and the second user may input the second public key into the client 15, and so on.

[0102] In step S306, a second transaction for resetting the public key of the first account is sent to any full node in the blockchain, wherein the data field of the second transaction includes the second biometric and the second public key, so that each full node in the blockchain replaces the first public key of the first account stored locally with the second public key.

[0103] Similar to the first transaction above, the "From" field of the second transaction can be filled with, for example Figure 1 The account address of the second account corresponding to the client 15 in the "To" field can be filled with the account address of the node to be sent, for example Figure 1 The account address of the intermediate node 11, the "Data" field includes the second biometric feature and the second public key obtained above.

[0104] Similarly, in order to ensure the immutability of the transaction, the second user will use the private key of the second account to digitally sign the second transaction. After the client 15 sends the second transaction with the above digital signature to the node 11, the node 11 uses the pre-acquired public key of the second account to decrypt the digital signature to verify that the data field has not been tampered with. After the node 11 verifies the digital signature of the second transaction, it sends the second transaction to at least one full node connected to it, thereby broadcasting the first transaction to the blockchain.

[0105] like Figure 1As shown in , node 13 is, for example, a bookkeeping node for storing the second transaction. After receiving the second transaction issued by the second account from the blockchain, node 13 first verifies the digital signature of the transaction in the same way as node 11, and after the verification is passed, determines whether the account identifier of the second account (the account corresponding to the client 15) is in the trusted user list of the first account, and determines whether the second biometric is consistent with the first biometric. Specifically, node 13 can obtain the trusted user list and the first biometric corresponding to the first account from the local account status tree, thereby determining whether the account identifier of the second account is in the trusted user list based on the trusted user list, and by comparing the second biometric in the second transaction with the first biometric, it is determined whether the second biometric is consistent with the first biometric. In the case where it is determined that the account identifier of the second account is in the trusted user list and the second biometric is consistent with the first biometric, node 13 replaces the first public key of the first account stored locally with the second public key, and packages the second transaction into a block and sends it to at least one full node in the blockchain. In the case where the public key hash value is included in the account status tree, node 13 can also update the public key hash value in the local status tree accordingly.

[0106] After receiving the newly generated block, a predetermined number of other full nodes in the blockchain store the block locally after verifying the block, update the local public key of the first user similarly to node 13, and reach a consensus on the generation of the block. The other full nodes in the blockchain can then directly download the block and update the local public key of the first user based on the block.

[0107] In one embodiment, each of the full nodes stores a first biometric ciphertext corresponding to the first account in its local account database, wherein the first biometric ciphertext is encrypted with a second encryption key jointly agreed upon by the full nodes. Thus, before determining whether the second biometric is consistent with the first biometric, node 13 uses the second decryption key jointly agreed upon by the full nodes to decrypt the first biometric ciphertext to obtain the first biometric.

[0108] In one embodiment, the data field of the second transaction includes a second biometric ciphertext, and the second biometric ciphertext is obtained by encrypting the second biometric by the client of the second user with a pre-acquired third encryption key jointly agreed upon by the various full nodes. Therefore, before determining whether the second biometric is consistent with the first biometric, node 13 uses the third decryption key jointly agreed upon by the various full nodes to decrypt the first biometric ciphertext to obtain the first biometric.

[0109] Figure 4 The embodiment of the present specification is shown in FIG. Figure 2 and Figure 3 An interactive diagram of the method shown. Figure 4 As shown in FIG. , the first client (eg Figure 1 The client 14 in step S402 obtains the biometrics of the first user, and obtains the trusted user list of the first user in step S404. In step S406, the first client sends a first transaction including the biometrics and the trusted user list to the blockchain platform. Here, the blockchain platform can be specifically any full node in the blockchain. In step S408, the blockchain platform adds the biometrics and the trusted user list of the first user to the account status tree of the platform according to the first transaction. Here, the account status tree of the platform can be specifically the local account status tree of each full node. The second client (e.g. Figure 1 The client 15 in step S410 obtains the biometrics of the first user, and obtains the new public key in step S412 for resetting the key of the first user. In step S414, the second client sends the second transaction including the biometrics and the new public key to the blockchain platform. Here, similarly, the blockchain platform can be specifically any full node in the blockchain. In step S416, the blockchain platform verifies whether the account identifier of the second user corresponding to the second client is in the trusted user list of the first user, and whether the biometrics in the second transaction are consistent with the biometrics of the first user stored in the state tree. The blockchain platform here can be specifically any full node in the blockchain. In step S418, if the verification is passed, the blockchain platform resets the public key of the first user, that is, replaces the original public key of the first user with the new public key in the second transaction. The blockchain platform here can be specifically each full node in the blockchain.

[0110] Figure 5 A device 500 for storing a user's biometric features in a blockchain according to an embodiment of the present specification is shown, wherein the blockchain is a consortium blockchain, and each full node in the blockchain is a consensus node of the blockchain, and the device is deployed in a blockchain client corresponding to a first account of a first user, including:

[0111] A first acquisition unit 51 is configured to acquire a biometric feature of the first user;

[0112] A second acquisition unit 52 is configured to acquire a trusted user list, wherein the trusted user list includes an account identifier of at least one second user, and the at least one second user is a preset trusted user of the first user; and

[0113] The sending unit 53 is configured to send a first transaction for setting a biometric feature to any full node in the blockchain, so that each full node in the blockchain sets the biometric feature and the trusted user list corresponding to the first account in its local account database, wherein the data field of the first transaction includes the biometric feature and the trusted user list.

[0114] In one embodiment, the first acquiring unit 51 is further configured to receive the biometric characteristics of the first user from a biometric characteristics collection device.

[0115] Figure 6 A device 600 for storing user biometrics in a blockchain according to an embodiment of the present specification is shown, wherein the blockchain is a consortium blockchain, and each full node in the blockchain is a consensus node of the blockchain. The device is deployed in the blockchain as a first node of a full node, and includes:

[0116] The receiving unit 61 is configured to receive, from the blockchain, a first transaction for setting a biometric feature issued by a first account, wherein a data field of the first transaction includes at least a biometric feature corresponding to the first account and a trusted user list;

[0117] an adding unit 62, configured to, after the digital signature of the first transaction is verified, add the biometrics and the trusted user list corresponding to the first account to a local account database; and

[0118] The packaging unit 63 is configured to package the first transaction into a block and send it to at least one full node in the blockchain.

[0119] In one embodiment, the adding unit 62 is further configured to add a biometric ciphertext and a trusted user list corresponding to the first account in a local account database, wherein the biometric ciphertext is obtained by encrypting the biometric by the first node with a second encryption key jointly negotiated by the full nodes.

[0120] In one embodiment, the account database is a status tree having an MPT tree structure, wherein the adding unit 62 is further configured to add the biometric and trusted user list to the value of a leaf node corresponding to the first account in the local status tree, and to update the value of an existing node related to the leaf node in the status tree accordingly.

[0121] Figure 7A device 700 for resetting a blockchain account key according to an embodiment of the present specification is shown, wherein the blockchain is a consortium chain, and each full node in the blockchain is a consensus node of the blockchain, and each full node stores a first biometric corresponding to a first account of a first user and a trusted user list in its local account database, wherein the trusted user list includes an account identifier of a second account of a second user, and the device is deployed on a blockchain client corresponding to the second account, including:

[0122] A first acquiring unit 71 is configured to acquire a second biometric feature of the first user;

[0123] A second obtaining unit 72 is configured to obtain a second public key of the first account, where the second public key will be used to replace the first public key already existing in the first account; and

[0124] The sending unit 73 is configured to send a second transaction for resetting the public key of the first account to any full node in the blockchain, wherein the data field of the second transaction includes the second biometric and the second public key, so that each full node in the blockchain replaces the first public key of the first account stored locally with the second public key.

[0125] Figure 8 A device 800 for resetting a blockchain account key according to an embodiment of the present specification is shown, wherein the blockchain is a consortium chain, and each full node in the blockchain is a consensus node of the blockchain, and each full node stores a first biometric corresponding to a first account of a first user and a trusted user list in its local account database, wherein the trusted user list includes an account identifier of a second account of a second user, and the device is deployed in the blockchain as a second node of the full node, including:

[0126] The receiving unit 81 is configured to receive, from the blockchain, a second transaction for resetting the public key of the first account, which is sent by the second account, wherein the data field of the second transaction includes a second biometric feature and a second public key corresponding to the first account, and the second public key will be used to replace the first public key already in the first account;

[0127] a determination unit 82 configured to, after the digital signature of the second transaction is verified, determine whether the account identifier of the second account is in the trusted user list, and determine whether the second biometric feature is consistent with the first biometric feature;

[0128] a replacing unit 83 configured to, when it is determined that the account identifier of the second account is in the trusted user list and the second biometric feature is consistent with the first biometric feature, replace the locally stored first public key of the first account with the second public key; and

[0129] The packaging unit 84 is configured to package the second transaction into a block and send it to at least one full node in the blockchain.

[0130] In one embodiment, each of the full nodes stores a first biometric ciphertext corresponding to the first account in its local account database, wherein the first biometric ciphertext is encrypted with a second encryption key jointly agreed upon by the full nodes, and the device also includes a first decryption unit 85, configured to, before determining whether the second biometric is consistent with the first biometric, use the second decryption key jointly agreed upon by the full nodes to decrypt the first biometric ciphertext to obtain the first biometric.

[0131] In one embodiment, the data field of the second transaction includes a second biometric ciphertext, which is encrypted with a third encryption key jointly agreed upon by the full nodes. The device also includes a second decryption unit 86, which is configured to decrypt the first biometric ciphertext using the third decryption key jointly agreed upon by the full nodes before determining whether the second biometric is consistent with the first biometric to obtain the first biometric.

[0132] In one embodiment, the account database also stores a public key hash value of the first account, and the device also includes an updating unit 87 configured to update the public key hash value of the first account in the local account database after replacing the first public key of the first account stored locally with the second public key.

[0133] On the other hand, the present specification provides a computer-readable storage medium having a computer program stored thereon, which, when executed in a computer, causes the computer to execute any one of the above methods.

[0134] On the other hand, the present specification provides a computing device, including a memory and a processor, wherein executable code is stored in the memory, and when the processor executes the executable code, any of the above methods is implemented.

[0135] In the scheme according to the embodiment of this specification, the function of resetting the account key in the blockchain is realized by combining the user's biometric features and the configuration of the account content in the corresponding account database. Compared with the scheme of using two private keys for key resetting in the prior art, it saves the key management cost and facilitates the user's operation.

[0136] It should be understood that the descriptions such as “first” and “second” in this article are only used to distinguish similar concepts for the sake of simplicity of description and do not have any other limiting effect.

[0137] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0138] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0139] Those of ordinary skill in the art should further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those of ordinary skill in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0140] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented by hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0141] The specific implementation methods described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for storing a user's biometric features in a blockchain, wherein the blockchain is a consortium blockchain, and each full node in the blockchain is a consensus node of the blockchain, and the method is performed by a blockchain client corresponding to a first account of a first user, comprising: Acquiring a biometric feature of the first user; Acquire a trusted user list, wherein the trusted user list includes an account identifier of at least one second user, and the at least one second user is a preset trusted user of the first user; as well as Sending a transaction to a full node of the blockchain so that each full node in the blockchain sets a biometric feature and a trusted user list corresponding to the first account in an account database, so as to reset the key of the first account through a second user in the trusted user list; wherein the data field of the transaction includes the biometric feature and the trusted user list.

2. The method according to claim 1, wherein: Acquiring the biometric characteristic of the first user includes receiving the biometric characteristic of the first user from a biometric characteristic collection device.

3. The method according to claim 1, wherein: The biometric feature includes at least one of the following features: face, fingerprint and iris.

4. The method according to claim 1, wherein: The data field includes a biometric ciphertext, and the biometric ciphertext is obtained by encrypting the biometric by the client using a first encryption key jointly negotiated by the full nodes that is obtained in advance.

5. A method for storing a user's biometric features in a blockchain, wherein the blockchain is a consortium blockchain, each full node in the blockchain is a consensus node of the blockchain, and the method is performed by a first node among the full nodes of the blockchain, comprising: Receiving a first transaction issued by a first account, wherein a data field of the first transaction includes a first biometric characteristic corresponding to the first account and a trusted user list; adding a first biometric and a trusted user list corresponding to the first account in an account database according to the first transaction; Receiving a second transaction for resetting the public key of the first account, which is sent by a second account of a second user, wherein a data field of the second transaction includes a second biometric feature and a second public key corresponding to the first account; In a case where it is determined that the account identifier of the second account is in the trusted user list and the second biometric feature is consistent with the first biometric feature, the public key of the first account is reset to the second public key.

6. The method according to claim 5, wherein: Adding the first biometric characteristic and the trusted user list corresponding to the first account in the account database includes adding the biometric characteristic ciphertext and the trusted user list corresponding to the first account in the account database, wherein the biometric characteristic ciphertext is obtained by encrypting the first biometric characteristic by the first node with the second encryption key jointly negotiated by the full nodes.

7. The method according to claim 5, wherein: The account database is a state tree with an MPT tree structure, wherein adding the first biometric and the trusted user list corresponding to the first account in the account database includes adding the first biometric and the trusted user list to the value of the leaf node corresponding to the first account in the state tree, and updating the value of the existing node related to the leaf node in the state tree accordingly.

8. A method for storing a user's biometric features in a blockchain, wherein the blockchain is a consortium blockchain, each full node in the blockchain is a consensus node of the blockchain, and the method is performed by a first node among the full nodes of the blockchain, comprising: Receiving a transaction sent by a first account of a first user, wherein a data field of the transaction includes a biometric feature corresponding to the first account and a trusted user list; After the digital signature of the transaction is verified, adding the biometric feature and the trusted user list corresponding to the first account to the account database, so that the first user can reset the key through a second user in the trusted user list; and The transactions are packaged into a block and sent to at least one full node in the blockchain.

9. A method for resetting a blockchain account key, wherein the blockchain is a consortium chain, each full node in the blockchain is a consensus node of the blockchain, and the full node stores a first biometric corresponding to a first account of a first user and a trusted user list in its account database, wherein: The trusted user list includes an account identifier of a second account of a second user, and the method is executed by a blockchain client corresponding to the second account, including: Acquiring a second biometric feature of the first user; Obtaining a second public key of the first account; and Sending a second transaction to a full node of the blockchain, wherein a data field of the second transaction includes the second biometric and the second public key, so that each full node in the blockchain resets the public key of the first account to the second public key.

10. The method according to claim 9, wherein: The data field of the second transaction includes a second biometric ciphertext, which is obtained by the client encrypting the second biometric with a third encryption key jointly negotiated by the full nodes and obtained in advance.

11. A method for resetting a blockchain account key, wherein the blockchain is a consortium chain, each full node in the blockchain is a consensus node of the blockchain, and an account database of each full node in the blockchain stores a first biometric feature corresponding to a first account of a first user and a trusted user list, the method being performed by a second node in the full nodes of the blockchain, comprising: Receiving a second transaction for resetting the public key of the first account, which is sent by a second account of a second user, wherein a data field of the second transaction includes a second biometric feature and a second public key corresponding to the first account; After the digital signature of the second transaction is verified, if it is determined that the account identifier of the second account is in the trusted user list and the second biometric feature is consistent with the first biometric feature, resetting the public key of the first account to the second public key; The second transaction is packaged into a block and sent to at least one full node in the blockchain.

12. The method according to claim 11, wherein: Each of the full nodes stores a first biometric ciphertext corresponding to the first account in its local account database, wherein the first biometric ciphertext is encrypted with a second encryption key jointly agreed upon by the full nodes. The method also includes, before determining whether the second biometric is consistent with the first biometric, decrypting the first biometric ciphertext using a second decryption key jointly agreed upon by the full nodes to obtain the first biometric.

13. The method according to claim 11, wherein: The data field of the second transaction includes a second biometric ciphertext, which is encrypted with a third encryption key jointly agreed upon by the full nodes. The method also includes, before determining whether the second biometric is consistent with the first biometric, decrypting the first biometric ciphertext using the third decryption key jointly agreed upon by the full nodes to obtain the first biometric.

14. The method according to claim 11, wherein: The account database also stores a public key hash value of the first account. The method further includes, after resetting the public key of the first account to the second public key, updating the public key hash value of the first account in the account database.

15. A device for storing a user's biometric features in a blockchain, wherein the blockchain is a consortium blockchain, each full node in the blockchain is a consensus node of the blockchain, and the device is deployed on a blockchain client corresponding to a first account of a first user, comprising: A first acquisition unit, configured to acquire a biometric feature of the first user; A second acquisition unit is configured to acquire a trusted user list, wherein the trusted user list includes an account identifier of at least one second user, and the at least one second user is a preset trusted user of the first user; as well as The sending unit is configured to send a transaction to the full nodes of the blockchain, so that each full node in the blockchain sets the biometric characteristics and the trusted user list corresponding to the first account in the account database respectively, so that the first user can reset the key through the second user in the trusted user list; wherein the data field of the transaction includes the biometric characteristics and the trusted user list.

16. The device according to claim 15, wherein: The first acquisition unit is further configured to receive the biometric characteristics of the first user from a biometric characteristics collection device.

17. The device according to claim 15, wherein: The biometric feature includes at least one of the following features: face, fingerprint and iris.

18. The device according to claim 15, wherein: The data field includes a biometric ciphertext, and the biometric ciphertext is obtained by encrypting the biometric by the client using a first encryption key jointly negotiated by the full nodes that is obtained in advance.

19. A device for storing a user's biometric features in a blockchain, wherein the blockchain is a consortium blockchain, each full node in the blockchain is a consensus node of the blockchain, and the device is deployed in a first node among the full nodes of the blockchain, comprising: A receiving unit configured to receive a first transaction issued by a first account, wherein a data field of the first transaction includes a first biometric feature corresponding to the first account and a trusted user list; an adding unit configured to add a first biometric feature and a trusted user list corresponding to the first account in an account database according to the first transaction; The receiving unit is further configured to receive a second transaction for resetting the public key of the first account, issued by a second account of a second user, wherein the data field of the second transaction includes a second biometric feature and a second public key corresponding to the first account; The resetting unit is configured to reset the public key of the first account to the second public key when it is determined that the account identifier of the second account is in the trusted user list and the second biometric feature is consistent with the first biometric feature.

20. The device according to claim 19, wherein The adding unit is further configured to add a first biometric ciphertext and a trusted user list corresponding to the first account in an account database, wherein the biometric ciphertext is obtained by encrypting the first biometric by the first node with a second encryption key jointly negotiated by the full nodes.

21. The device according to claim 19, wherein The account database is a state tree with an MPT tree structure, wherein the adding unit is further configured to add the first biometric and the trusted user list to the value of a leaf node corresponding to the first account in the state tree, and to update the value of an existing node related to the leaf node in the state tree accordingly.

22. A device for resetting a blockchain account key, wherein the blockchain is a consortium chain, each full node in the blockchain is a consensus node of the blockchain, and the full node stores a first biometric feature corresponding to a first account of a first user and a list of trusted users in its account database, wherein: The trusted user list includes an account identifier of a second account of a second user, and the device is deployed on a blockchain client corresponding to the second account, including: A first acquiring unit, configured to acquire a second biometric feature of the first user; A second obtaining unit is configured to obtain a second public key of the first account; and The sending unit is configured to send a second transaction to a full node of the blockchain, wherein a data field of the second transaction includes the second biometric and the second public key, so that each full node in the blockchain resets the public key of the first account to the second public key.

23. The device according to claim 22, wherein: The data field of the second transaction includes a second biometric ciphertext, which is obtained by the client encrypting the second biometric with a third encryption key jointly negotiated by the full nodes and obtained in advance.

24. A device for resetting a blockchain account key, wherein the blockchain is a consortium chain, each full node in the blockchain is a consensus node of the blockchain, and an account database of each full node in the blockchain stores a first biometric feature corresponding to a first account of a first user and a trusted user list, wherein the device is deployed on a second node in the full nodes of the blockchain, comprising: A receiving unit configured to receive a second transaction issued by a second account of a second user, wherein a data field of the second transaction includes a second biometric feature and a second public key corresponding to the first account; a replacement unit configured to, after the verification of the digital signature of the second transaction is passed, reset the public key of the first account to the second public key if it is determined that the account identifier of the second account is in the trusted user list and the second biometric feature is consistent with the first biometric feature; The sending unit is configured to package the second transaction into a block and send it to at least one full node in the blockchain.

25. The device according to claim 24, wherein: Each of the full nodes stores a first biometric ciphertext corresponding to the first account in its local account database, wherein the first biometric ciphertext is encrypted with a second encryption key jointly agreed upon by the full nodes. The device also includes a first decryption unit configured to, before determining whether the second biometric is consistent with the first biometric, decrypt the first biometric ciphertext using the second decryption key jointly agreed upon by the full nodes to obtain the first biometric.

26. The device according to claim 24, wherein: The data field of the second transaction includes a second biometric ciphertext, which is encrypted with a third encryption key jointly agreed upon by the full nodes. The device also includes a second decryption unit, which is configured to decrypt the first biometric ciphertext using the third decryption key jointly agreed upon by the full nodes before determining whether the second biometric is consistent with the first biometric to obtain the first biometric.

27. The device according to claim 24, wherein: The account database also stores a public key hash value of the first account. The device also includes an updating unit configured to update the public key hash value of the first account in the account database after resetting the public key of the first account to the second public key.

28. A computer-readable storage medium having a computer program stored thereon, which, when executed in a computer, causes the computer to execute the method according to any one of claims 1 to 14.

29. A computing device comprising a memory and a processor, characterized in that: The memory stores executable codes, and when the processor executes the executable codes, the method according to any one of claims 1 to 14 is implemented.

Images