CN116094739A - Encryption method, encryption device and related equipment - Google Patents

Abstract

The application provides an encryption method, an encryption device and related equipment, wherein the method is applied to a user node in a blockchain network and comprises the following steps: firstly, a first extended public key comprising encrypted blood-edge information, first supervision and authorization information and a public key of a user node is obtained, then the public key of the user node is used for encrypting first data to obtain a first ciphertext, and finally the first extended public key and the first ciphertext are uploaded to a blockchain, wherein the blood-edge information reflects the association relation between private keys of a plurality of nodes and the private key of the user node, the first supervision and authorization information is used for a first authorized node in the plurality of nodes to restore a first decryption key, and the first decryption key is used for decrypting the encrypted blood-edge information. Therefore, the requirement of user-defined supervision of the upper level can be met, and the problem that the attribution relation between the user and the upper level is additionally exposed in the prior art is solved.

Description

Encryption method, device and related equipment

technical field

The present application relates to the field of computer technology, in particular to an encryption method, device and related equipment.

Background technique

Blockchain technology has broad application prospects in many fields such as digital government affairs, digital currency, and financial asset transaction settlement because it can realize the characteristics of openness, transparency, non-tampering, and non-forgery of all data without the need for a third party.

However, the openness and transparency of the blockchain has the problem of exposing users' sensitive data (such as tax information, salary information, travel trajectories, etc.) to the blockchain in practical applications. If the user uses the public key to encrypt sensitive data and then uploads it to the blockchain, when the user's superior (assuming that the user is a user who needs to pay taxes, the user's superior can include the county tax bureau, the city tax bureau, the provincial tax bureau and the State Taxation Bureau , assuming that the user is an employee of a subsidiary, the user's superior can be the head office to which the subsidiary belongs) When it is necessary to supervise the sensitive data uploaded by the user to the blockchain, the user needs to transmit the private key to the user's superior through the network, and the private key is transmitted During the process, it may be maliciously stolen, resulting in the leakage of the user's private key, resulting in the leakage of the user's sensitive data.

At present, the use of hierarchical deterministic encryption algorithms can not only realize the supervision of users' superiors, but also avoid the leakage of users' sensitive data. However, because the algorithm introduces the affiliation relationship (also called blood relationship) between the user and the user's superior, it will lead to the leakage of the affiliation relationship between the user and the user's superior. In addition, the above algorithm realizes that all user superiors can supervise the sensitive data uploaded by users to the blockchain, and users cannot customize the supervisory superiors, which has low flexibility and poor user experience.

Contents of the invention

This application provides an encryption method, device and related equipment, which can realize user-defined supervisory superiors, optimize user experience, and can solve the problem of additionally exposing the affiliation relationship between users and their superiors existing in the prior art.

In the first aspect, an encryption method is provided, which is applied to a user node in a blockchain network, including: first, obtaining a first extended public key, and then using the public key of the user node to encrypt the first data, thereby Obtain the first ciphertext, and finally, upload the first extended public key and the first ciphertext to the block chain, wherein the first extended public key includes the encrypted blood relationship information, the first supervisory authorization information and the public key of the user node, The blood relationship information reflects the relationship between the private keys of multiple nodes and the private key of the user node. The first supervisory authorization information is used for the first authorized node among the multiple nodes to restore the first decryption key, and the first decryption key The key is used to decrypt the encrypted blood relationship information.

Through the above scheme, it can be seen that the user node can obtain the extended public key including the encrypted blood relationship information, regulatory authorization information and its own public key, and then use its own public key to encrypt the data to obtain the ciphertext, and finally send its own extended public key and The ciphertext is uploaded to the blockchain. Since the blood relationship information reflects the relationship between the private key of multiple nodes and the private key of the user node, the supervisory authorization information is used to restore the authorized node among multiple nodes to obtain The decryption key for decrypting the encrypted blood relationship information. In this way, after multiple upper-level nodes obtain the extended public key and ciphertext of the user node from the blockchain, the authorized nodes among the multiple nodes can key to regenerate the private key of the user node, and the unauthorized node cannot regenerate the private key of the user node according to the extended public key. Therefore, only the authorized node can decrypt the ciphertext to obtain the data of the user node, realizing the user The data supervision of nodes, and unauthorized nodes cannot supervise the data of user nodes. It can be seen that this solution can realize user-defined supervisory superiors and meet the needs of user-defined supervisory superiors.

In addition, through the above scheme, it can also be known that the extended public key uploaded by the user node to the blockchain includes encrypted blood relationship information. Even if an unauthorized node obtains the extended public key, only the encrypted Lineage information, therefore, can solve the problem of additional exposure of the affiliation relationship between users and their superiors existing in the prior art.

In a possible implementation manner, the method further includes: firstly, obtaining a second extended public key according to the first extended public key, and then using the public key of the user node to encrypt the second data, thereby obtaining the second ciphertext, Finally, upload the second extended public key and the second ciphertext to the blockchain, wherein the second extended public key includes the encrypted blood relationship information, the second supervisory authorization information and the public key of the user node, and the second supervisory authorization information uses In order for a second authorized node among the plurality of nodes to restore the first decryption key, the second authorized node includes the first authorized node, and the number of the second authorized node is greater than the number of the first authorized node.

Through the above scheme, it can be seen that the user node can dynamically increase the number of authorized nodes by modifying the supervisory authorization information in the extended public key, so that more nodes can supervise the data uploaded by the user node to the blockchain, unlike the existing What the technology achieves is that all user superiors can supervise, and users cannot customize the supervisory superiors. Therefore, this solution has strong flexibility and can optimize user experience.

In a possible implementation manner, the method further includes: firstly, obtaining a third extended public key according to the first extended public key, and then using the public key of the user node to encrypt the third data, thereby obtaining the third ciphertext, Finally, upload the third extended public key and the third ciphertext to the blockchain, where the third extended public key includes the re-encrypted blood relationship information, the third supervisory authorization information and the public key of the user node, and the third supervisory authorization information It is used for the third authorized node among multiple nodes to restore the second decryption key, the second decryption key is used to decrypt the re-encrypted blood relationship information, and the third authorized node belongs to the first authorized node nodes, the third authorized number of nodes is smaller than the first authorized number of nodes.

Through the above scheme, it can be seen that the user node can dynamically delete the number of authorized nodes by modifying the supervisory authorization information in the extended public key. Unlike the existing technology, all user superiors can be supervised, and users cannot customize supervisory superiors. . Therefore, this solution has strong flexibility and can optimize user experience.

In a possible implementation, the first extended public key can be obtained in the following manner: first, obtain the extended private key, which includes blood relationship information and the private key of the user node, and then encrypt the data with the first decryption key blood relationship information, get the encrypted blood relationship information, use the public key of the first authorized node to encrypt the first decryption key, obtain the first regulatory authorization information, and calculate the public key of the user node according to the private key of the user node, Finally, the first extended public key is obtained according to the public key of the user node, the encrypted blood relationship information and the first supervisory authorization information. In this way, after obtaining the first extended public key, the first authorized node can use its own private key to decrypt the first supervisory authorization information in the first extended public key to obtain the first decryption key, and then use the second A decryption key decrypts the encrypted blood relationship information to obtain the blood relationship information, and the unauthorized node cannot obtain the first decryption key according to the first regulatory authorization information, so it cannot obtain the blood relationship information, which can solve the problems existing in the existing technology This additionally exposes the problem of affiliation between users and their superiors.

In a possible implementation manner, the encrypted blood relationship information includes the encrypted number of the user node and the encrypted numbers of multiple nodes.

Through the above scheme, it can be seen that the extended public key uploaded by the user node to the blockchain includes encrypted blood relationship information. Even if an unauthorized node obtains the extended public key, only the encrypted blood relationship information can be viewed. Therefore, the problem of additional exposure of the affiliation relationship between the user and its superior existing in the prior art can be solved.

In the second aspect, an encryption method is provided, which is applied to supervisory nodes in the blockchain network, including: first, obtaining the extended public key and ciphertext, and then decrypting the ciphertext according to the extended public key to obtain the target Data, where the extended public key includes encrypted blood relationship information, regulatory authorization information, and the public key of the user node. The blood relationship information reflects the relationship between the private keys of multiple nodes and the private key of the user node. The regulatory authorization information is used for The authorized node among the multiple nodes restores the decryption key, which is used to decrypt the encrypted blood relationship information. The ciphertext is obtained by encrypting the target data with the public key of the user node. The supervisory node belongs to Authorized nodes.

Through the above scheme, it can be seen that the supervisory node acquires the extended public key of the user node (including encrypted blood relationship information, customized supervisory authorization information, and the public key of the user node) and uses the public key of the user node to encrypt the sensitive data obtained by encrypting sensitive data. Then the supervision node can regenerate the private key of the user node according to the extended public key, and finally use the generated private key to decrypt the ciphertext of the sensitive data to obtain the corresponding sensitive data, so as to realize the supervision of the sensitive data uploaded by the user node to the blockchain .

In a possible implementation, the ciphertext can be decrypted according to the extended public key in the following manner to obtain the target data: first, restore the decryption key according to the regulatory authorization information, and then use the decryption key to decrypt the encrypted The blood relationship information is decrypted to obtain the blood relationship information, and according to the blood relationship information, the private key of the user node is generated, and finally the ciphertext is decrypted with the private key of the user node to obtain the target data.

In a possible implementation manner, the supervisory authorization information is obtained by the user node encrypting the decryption key according to the public key of the authorized node. In this way, the supervisory node can decrypt the supervisory authorization information according to its own private key to obtain the decryption key, thereby realizing the decryption of the encrypted blood relationship information to obtain the blood relationship information, and the unauthorized node cannot restore the decryption key according to the supervisory authorization information. Therefore, blood relationship information cannot be obtained, which can solve the problem of additional exposure of the affiliation relationship between the user and its superior in the existing technology.

In a possible implementation manner, the encrypted blood relationship information includes the encrypted number of the user node and the encrypted numbers of multiple nodes.

In a third aspect, an encryption device is provided, the device is applied to a user node in a blockchain network, and the device includes various modules for executing the encryption method in the first aspect or any possible implementation manner of the first aspect.

In a fourth aspect, an encryption device is provided, which is applied to a supervisory node in a blockchain network, and the device includes various modules for executing the encryption method in any possible implementation manner of the first aspect or the second aspect.

In a fifth aspect, a computer-readable storage medium is provided, the computer-readable medium stores instructions, and the instructions are used to implement the method provided in any possible implementation manners of the first aspect to the second aspect above.

According to a sixth aspect, a computing device is provided, and the computer device includes a processor and a memory; the processor is configured to execute instructions stored in the memory, so that the computing device implements any of the above-mentioned first to second aspects. A method provided by a possible implementation.

In a seventh aspect, a computer program product is provided, including a computer program. When the computer program is read and executed by a computing device, the computing device executes any possible implementation manners of the above-mentioned first aspect to the second aspect to provide Methods.

Description of drawings

FIG. 1 is a schematic diagram of a system architecture involved in the present application;

Fig. 2 is a schematic diagram of layered encryption based on BIP32 involved in the present application;

Fig. 3 is a schematic diagram of the sensitive data of the superior node supervising the user node involved in this application;

FIG. 4 is a schematic flow diagram of an encryption method applied to a user node provided by the present application;

Fig. 5 is a schematic flow diagram of obtaining the extended public key according to the extended private key provided by this application;

FIG. 6 is a schematic flowchart of an encryption method applied to a supervisory node provided by the present application;

FIG. 7 is a schematic flow diagram of adding a supervisory node provided by the present application;

Fig. 8 is a schematic flow diagram of deleting a supervisory node provided by the present application;

FIG. 9 is a schematic structural diagram of an encryption device provided by the present application;

FIG. 10 is a schematic structural diagram of another encryption device provided by the present application;

FIG. 11 is a schematic structural diagram of a computing device provided by the present application.

Detailed ways

The technical solution provided by this application will be described below with reference to the accompanying drawings.

The terms "first" and "second" in the embodiments of the present application are used for description purposes only, and cannot be interpreted as indicating or implying relative importance or implicitly indicating the quantity of indicated technical features. Thus, a feature defined as "first" and "second" may explicitly or implicitly include one or more of these features.

In the embodiments of the present application, "at least one" means one or more, and "multiple" means two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist at the same time, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the contextual objects are an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one item (unit) of a, b or c can represent: a, b, c, a-b, a-c, b-c or a-b-c, wherein a, b, c can be single or multiple.

In order to make the technical solution provided by this application clearer, before describing the technical solution provided by this application in detail, explanations of relevant terms and related technologies are given first.

Block chain: In a narrow sense, block chain is a chained data structure with block as the basic unit. The digital summary is used in the block to verify the transaction history obtained before, which is suitable for distributed bookkeeping. Anti-tampering and scalability requirements in scenarios; in a broad sense, blockchain also refers to the distributed accounting technology implemented by the blockchain structure, including distributed consensus, privacy and security protection, point-to-point communication technology, network protocols, smart contract etc.

The goal of the blockchain is to implement a distributed data record ledger, which only allows addition and does not allow deletion. The underlying structure of the ledger is a linear linked list. The linked list is composed of "blocks" in series. The hash (hash) value of the previous block is recorded in the subsequent block. Whether each block (and the transaction in the block) is legal can be calculated by calculating the hash value. way for a quick check. If a node in the network proposes to add a new block, it must go through a consensus mechanism to reach a consensus on the block.

Symmetric key: It can also be called a private key or a shared key, that is, the data encryption party and the data decryption party must use the same key to encrypt and decrypt data.

Asymmetric key: including public key (public key) and private key (private key). The public key is used to encrypt data, and the private key is used to decrypt data. Data encrypted with the public key can only be decrypted with the private key. The public key can be calculated by the formula "public key = private key·G", where G is the base point of the elliptic curve. It should be noted that the process of calculating the public key according to the above formula is irreversible, that is, the public key can be calculated based on the private key, but the private key cannot be deduced from the public key.

The 32nd bitcoin improvement proposal (bitcoin improvement proposals, BIP): referred to as BIP32, the specific content of this proposal is: according to a random number seed, obtain n private keys through hierarchical deterministic derivation, so that the digital wallet is stored , you only need to save a seed, and when you need to use any private key for decryption, the private key can be re-derived based on the seed. Among them, the digital wallet is a tool for managing private keys (generation, storage, signature).

BIP32 is often used in scenarios where layered encryption is required in blockchain networks. The following describes the process of layered encryption based on BIP32 in detail in conjunction with the blockchain network shown in Figure 1.

As shown in Figure 1, the block chain network includes node 100, node 110, node 120, node 1101, node 1102, node 1201 and node 1202, wherein, node 100, node 110, node 120, node 1101, node 1102, node 1201 and node 1202 may include mobile phones, tablet computers, notebook computers, palmtop computers, smart speakers, mobile internet devices (mobile internet device, MID), point of sales (point of sales, POS) machines, wearable devices (such as smart watches, Smart bracelets, etc.), etc., any two nodes can be connected through a network, and the network can be a wireless network or a wired network, which is not specifically limited here.

The blockchain network shown in Figure 1 can be understood as a system with a hierarchical relationship, in which node 100 is the highest-level organization as the first layer of the organization, and node 110 and node 120 are two departments under node 100, Belonging to node 100, as the second layer of the organization, node 1101 and node 1102 are two members under node 110, belonging to node 110, node 1201 and node 1202 are two members under node 120, belonging to node 120 , as the third layer of the organization. For example, node 100 is the provincial taxation bureau, node 110 and node 120 are two city taxation bureaus under the jurisdiction of the provincial taxation bureau, node 1101, node 1102, node 1201 and node 1202 correspond to users under the jurisdiction of the two city taxation bureaus; another example , node 100 is the Supreme Court, node 110 and node 120 are two provincial courts under the jurisdiction of the Supreme Court, node 1101, node 1102, node 1201 and node 1202 correspond to the municipal courts under the jurisdiction of the two provincial courts, etc. It can be seen that node 100 is the direct superior node of node 110 and node 120, node 110 is the direct superior node of node 1101 and node 1102, node 120 is the direct superior node of node 1201 and node 1202, node 100 is also node 1101, node 1102 , the indirect superior node of node 1201 and node 1202.

Taking node 100 as an example, the process of node 100 performing layered encryption based on BIP32 is shown in Figure 2:

Node 100 randomly selects a seed, and then uses SHA512 to hash the seed to obtain a 512-bit hash value. Then, node 100 determines the left 256 bits of the obtained hash value as its own private key, and the right 256 bits Determined as your own chain code.

After node 100 determines its own private key and chain code, if node 100 determines that it needs to generate a private key for node 110 or node 120, take node 110 as an example to generate a private key, it first determines a number for node 110, such as 1, Then use SHA512 to hash your own key (private key or public key, take the private key as an example in Figure 2), chain code and the characters formed by the number of node 110 to obtain a 512-bit hash value, and then , the node 100 determines the left 256 bits of the obtained hash value as the private key of the node 110, and the right 256 bits determine the chain code of the node 110, thereby determining the extended private key of the node 110 (including the private key of the node 110 and the node 110 chain code), and finally send the extended private key to the node 110. Among them, the function of numbering is to distinguish a node and other nodes belonging to the same level as the node under the jurisdiction of the parent node of the node. For example, the numbering of node 110 is to distinguish node 110 from node 120, and the numbering of node 1101 is to distinguish Node 1101 and Node 1102.

If node 100 determines that it needs to generate a private key for node 1101, node 1102, node 1201 or node 1202, it first generates a private key for node 110 or node 120 by referring to the above process, and then node 110 or node 120 refers to the above node 100 as a node 110 The process of generating a private key corresponds to generating a private key for node 1101, node 1102, node 1201 or node 1202, after node 110 or node 120 generates a private key for the corresponding node, the generated private key is sent in the form of an extended private key to the corresponding node.

It should be noted that in BIP32, the process of the upper-level node generating a private key for the lower-level node based on its own private key is irreversible, that is, the lower-level node cannot deduce the private key of the upper-level node based on its own private key.

After each node shown in Figure 1 obtains its own extended private key, if it needs to encrypt and upload sensitive data to the blockchain, it can calculate the public key according to the private key in the extended private key, and then use the public key to pair the sensitive The data is encrypted, and then the extended public key (including the chain code of the node and the public key of the node, etc.) and the ciphertext of the sensitive data are uploaded to the blockchain, as shown in Figure 3.

After a node uploads its own extended public key and sensitive data ciphertext to the blockchain (hereinafter, the nodes that upload sensitive data ciphertext to the blockchain are collectively referred to as user nodes), other nodes in the blockchain network will It can be known that the user node has uploaded data, and the extended public key and sensitive data ciphertext uploaded by the user node can be obtained from the blockchain, but only the upper-level nodes of the user node (including direct upper-level nodes and indirect upper-level nodes) can regenerate The private key of the node, and use the private key to decrypt the ciphertext of sensitive data to obtain sensitive data. Non-superior nodes cannot generate the private key of the node, so they cannot decrypt the ciphertext of sensitive data to obtain sensitive data.

The following describes the process of decrypting the sensitive data ciphertext by the superior node of the user node, as shown in FIG. 3 . In FIG. 3 , node 100 decrypts the sensitive data ciphertext uploaded to the blockchain by node 1101 as an example.

After node 100 obtains the extended public key and sensitive data ciphertext of node 1101 from the blockchain, it can generate the private keys of all subordinate nodes (including direct subordinates and indirect subordinates) under its jurisdiction, and according to the private key of each subordinate node key to generate the public key of each lower-level node, and then compare the generated public key with the public key included in the obtained extended public key to determine the corresponding private key, and then use the private key to decrypt the ciphertext of the sensitive data to obtain the sensitive data.

In summary, BIP32 can realize the supervision of the user's superiors on the data uploaded to the blockchain by the user, and has the advantage of preventing the user's sensitive data from being exposed to other users except the superior.

In specific implementation, there are other BIP recommendations such as BIP39 or BIP44. The process of layered encryption in these BIP recommendations is similar to the layered encryption process of BIP32, and will not be repeated here.

It should be noted that Figure 1 is only an example. In a specific implementation, the blockchain network may include more or fewer nodes, and each node may include more or fewer subordinate nodes. Figure 1 does not should be considered specifically defined.

Authorized nodes: Refers to the nodes that have been granted supervisory authority by the user node among the superior nodes of the user node. These nodes can supervise the sensitive data uploaded by the user node to the blockchain, that is, these nodes are obtained from the blockchain. After encrypting the uploaded sensitive data ciphertext with your own public key, you can regenerate the private key of the user node, and then use the generated private key to decrypt the sensitive data ciphertext to obtain sensitive data.

Unauthorized nodes: Refers to nodes among the upper-level nodes of the user node that have not been granted supervisory authority by the user node. These nodes cannot supervise the sensitive data uploaded by the user node to the blockchain.

The application scenarios involved in this application are introduced below.

This application involves a scenario where a user needs to encrypt and upload sensitive data to the blockchain and the user's superior needs to supervise the sensitive data uploaded by the user, as shown in the blockchain network shown in Figure 1.

At present, when user nodes in the blockchain network shown in Figure 1 need to encrypt and upload sensitive data to the blockchain, they usually use the method of layered encryption based on BIP32. From the above, the method of layered encryption based on BIP32 The introduction of the method shows that if the upper-level node needs to supervise the sensitive data uploaded by the user node to the blockchain, the upper-level node needs to generate the private key of all the lower-level nodes under its jurisdiction, and then generate the public key of each lower-level node according to the private key of each lower-level node , and finally compare the generated public key with the public key of the user node included in the obtained extended public key to determine the corresponding private key and decrypt the sensitive data. This process is cumbersome and takes a lot of time. less efficient.

In view of the problems existing in the method of layered encryption based on BIP32, the prior art provides a layered deterministic encryption algorithm:

This algorithm has been improved on the basis of the BIP32-based layered encryption method. The specific improvement is that when the upper-level node generates an extended private key for the lower-level node, the blood relationship information between itself and the lower-level node is added to the extended private key. The lineage information is used to reflect the relationship between the private key of the upper-level node and the private key of the lower-level node, that is, to reflect that the private key of the lower-level node is generated by the upper-level node according to its own private key. The number of the node and the number of the lower-level node, the association relationship reflected is specifically that the private key of the lower-level node is generated by the upper-level node according to its own private key, its own chain code and the number of the lower-level node.

For example, assuming that the lower-level node is node 1101 shown in Figure 1, the upper-level nodes of node 1101 are node 110 and node 100, the number of node 1101 is 1, the number of node 110 is 10, and the number of node 100 is 0, then node 110 The kinship information in the extended private key of is (0; 1), which reflects that the private key of node 110 is generated by node 100 according to its own private key, its own chain code and the number 1 of node 110, and the extended private key of node 1101 The blood relationship information in the key is (0; 1; 10), which reflects that the private key of node 1101 is generated by node 110 according to its own private key, its own chain code and the number 10 of node 1101, and reflects the private key of node 1101. The key is generated by the node 100 according to its own private key, its own chain code and the number 1 of the node 110 .

It should be noted that the blood relationship information above is (0; 1)/(0; 1; 10) as an example only, for example, the blood relationship information can also be (10)/(1; 10), excluding the highest level The number of node 100.

Based on the above improvements, the hierarchical deterministic encryption algorithm can make the extended public key obtained by the user node according to the extended private key also include blood relationship information, then when the upper node of the user node obtains the extended public key uploaded by the user node from the blockchain and After the sensitive data is ciphered, the upper-level node can directly regenerate the private key of the user node according to the blood relationship information included in the extended public key, without generating the private key of all the lower-level nodes under its jurisdiction, and then determine the private key of the user node from it. Therefore, It can reduce the time spent by the upper-level node to obtain the private key of the user node, thereby improving the supervision efficiency.

However, it can be seen that in the hierarchical deterministic encryption algorithm, the extended public key uploaded by the user node to the blockchain includes blood relationship information, and the non-superior nodes of the user node can also obtain the extended public key of the user node from the blockchain. Key, so as to obtain blood relationship information, which additionally exposes the association between the private key of the user node and the private key of its superior node, that is, the affiliation relationship between the user and its superior. In addition, the hierarchical deterministic encryption algorithm realizes that all the superiors of the user can supervise the sensitive data uploaded by the user, but in practical applications, users usually do not want all the superiors to supervise the sensitive data uploaded by themselves, but by Users define which superiors can supervise and which superiors cannot supervise. It is obvious that the hierarchical deterministic encryption algorithm cannot meet the above needs of users.

This application provides an encryption method, device and related equipment, which can be applied to the blockchain network shown in Figure 1 to solve the problem of additional exposure of the affiliation relationship between users and their superiors in the above-mentioned layered deterministic encryption algorithm. And meet the needs of user-defined supervisory superiors.

Please refer to FIG. 4, which is a schematic flowchart of an encryption method provided by the present application. The encryption method is specifically applied to user nodes in the blockchain network shown in FIG. 1 that need to upload sensitive data to the blockchain.

As shown in Figure 4, the method includes:

S401. Obtain an extended private key including blood relationship information and a private key of a user node.

Among them, the blood relationship information reflects the relationship between the private keys of multiple nodes (referring to the superior node of the user node) and the private key of the user node. The private key of the user node is used for the calculation of the user node to obtain its own public key. The public key It is used for the user node to encrypt the sensitive data to be uploaded to the block chain (the first data, the second data, the third data described below) to obtain the sensitive data ciphertext (the first ciphertext described below, the second data Second ciphertext, third ciphertext).

Optionally, the extended private key may also include other information such as the chain code of the user node and the level of the user node, which is not specifically limited in this application. Wherein, the chain code of the user node is used to generate a private key for the subordinate node when the user node includes the subordinate node and needs to generate a private key for the subordinate node.

For the sake of brevity, this embodiment does not describe in detail the process of obtaining the extended private key by the user node. This process is the same as the process of obtaining the extended private key by the user node in the above-mentioned layered deterministic encryption algorithm. For details, please refer to the relevant description above. No more details here.

S402. According to the extended private key, obtain the first extended public key including the encrypted blood relationship information, the first supervisory authorization information and the public key of the user node, wherein the first supervisory authorization information is used for the first slave among the multiple nodes The authorized node restores the first decryption key, and the first decryption key is used to decrypt the encrypted blood relationship information.

From the above introduction to the hierarchical deterministic encryption algorithm, it can be seen that blood relationship information can be used by the upper-level node of the user node to regenerate the private key of the user node. It can be understood that when the blood relationship information is encrypted, if the upper-level node of the user node If you want to regenerate the private key of the user node according to the blood relationship information, you need to obtain the key for decrypting the encrypted blood relationship information, that is, the first decryption key, so as to decrypt the encrypted blood relationship information.

In this embodiment, since the user node authorizes multiple upper-level nodes through the first supervision authorization information, only authorized nodes among the multiple upper-level nodes can restore the first decryption key according to the first supervision authorization information, and Use the first decryption key to decrypt the encrypted blood relationship information, and then regenerate the private key of the user node according to the blood relationship information, and the unauthorized nodes among the multiple upper-level nodes cannot restore the first decryption key according to the first supervisory authorization information. key, so the blood relationship information cannot be decrypted, and the private key of the user node cannot be regenerated based on the blood relationship information.

The following describes in detail the process of the user node obtaining the first extended public key according to the extended private key in conjunction with FIG. 5. As shown in FIG. 5, the process may include the following steps:

S4021. Randomly generate a first decryption key, and use the first decryption key to encrypt blood relationship information to obtain encrypted blood relationship information.

Wherein, the first decryption key may be a symmetric key. In the case where the first decryption key is a symmetric key, the blood relationship information is encrypted using the first decryption key to obtain the encrypted blood relationship information, then the subsequent user node Or if other nodes want to decrypt the encrypted blood relationship information to obtain the blood relationship information, the decryption key used needs to be the first decryption key.

In a specific implementation, the user node can use a random algorithm to randomly generate the first decryption key, which can be a 256-bit or 512-bit character, which is not specifically limited here; the user node uses the first decryption key to process blood relationship information The algorithm used for encryption may be advanced encryption standard (AES) algorithm or triple data encryption algorithm (triple data encryption algorithm, referred to as 3DES), etc., which is not specifically limited in this application.

S4022. Use the public key of the first authorized node among the multiple nodes to encrypt the first decryption key to obtain the first supervisory authorization information.

It can be understood that since the public key and private key of the first authorized node are paired, use the public key of the first authorized node to encrypt the first decryption key to obtain the first supervisory authorization information, then subsequent users If a node or other nodes want to decrypt the first supervisory authorization information to obtain the first decryption key, the decryption key used must be the private key of the first authorized node.

The following continues to take the user node as node 1101, and the upper-level nodes of the user node as nodes 110 and 100 as an example, to introduce the user node to obtain the first supervision authorization information and the first authorized node to restore the first decryption encryption according to the first supervision authorization information. The detailed process of the key:

First, assuming that node 100 is the first authorized node, and node 110 is an unauthorized node, node 1101 can obtain the first supervisory authorization information by referring to the following formula (1):

First supervisory authorization information = {R G, Skey+R PK ₁₀₀ } (1)

Among them, Skey is the first decryption key, PK ₁₀₀ is the public key of node 100, G is the base point of the elliptic curve, and R is the random number selected by node 1101.

When the node 100 obtains the above-mentioned first supervisory authorization information, the node 100 can refer to the following formula (2) to restore the first decryption key:

Skey'＝(Skey+R·PK ₁₀₀ )-SK ₁₀₀ ·(R·G) (2)

Wherein, Skey' is the first decryption key restored by the node 100, and SK ₁₀₀ is the private key of the node 100.

Assuming that both node 100 and node 110 are the first authorized nodes as an example, node 1101 can obtain the first supervisory authorization information by referring to the following formula (3):

The first regulatory authorization information = {R G, Skey+R PK ₁₀₀ , Skey+R PK ₁₁₀ } (3)

Wherein, PK ₁₁₀ is the public key of node 110 .

When the node 100 obtains the above first supervisory authorization information, the node 100 may continue to refer to the above formula (2) to restore the first decryption key.

When the node 110 obtains the above-mentioned first supervisory authorization information, the node 110 may refer to the following formula (4) to restore the first decryption key.

Skey"＝(Skey+R·PK ₁₁₀ )-SK ₁₁₀ ·(R·G) (4)

Wherein, Skey" is the first decryption key restored by the node 110, and SK ₁₁₀ is the private key of the node 110.

It should be noted that the above-mentioned formulas (1) and (2) for the user node to obtain the first supervision authorization information are only used as an example. In a specific implementation, the user node can also refer to other methods to obtain the first supervision authorization information, for example , when the first authorized node includes node 100 and node 110, the first supervisory authorization information={R·G, Skey+R·PK ₁₀₀ , Skey+R·PK ₁₁₀ , H(Skey)}, where, H (Skey) is used by the first authorized node to verify the integrity of the restored first decryption key.

S4023. Calculate and obtain the public key of the user node according to the private key of the user node.

Specifically, the public key of the user node = the private key G of the user node.

S4024. Obtain a first extended public key according to the encrypted blood relationship information, the first supervisory authorization information, and the public key of the user node.

Optionally, the first extended public key may also include other information such as the chain code of the user node and the level of the user node, which is not specifically limited in this application.

S403. Encrypt the first data by using the public key of the user node to obtain the first ciphertext.

Wherein, the first data is the first sensitive data to be uploaded to the block chain by the user node.

It can be understood that since the public key of the user node and the private key of the user node are paired, and the first data is encrypted using the public key of the user node to obtain the first ciphertext, then if the subsequent user node or other nodes want to encrypt the first data A ciphertext is decrypted to obtain the first data, and the decryption key used needs to be the private key of the user node.

S404. Upload the first extended public key and the first ciphertext to the blockchain.

After the user node uploads the first extended public key and the first ciphertext to the blockchain, each node in the blockchain network can obtain the first extended public key and the first ciphertext. It can be seen from S403 that the block If each node in the chain network wants to decrypt the first ciphertext, the decryption key used needs to be the private key of the user node.

It can be seen from the relevant description in S402 that the first authorized node among the multiple upper-level nodes of the user node included in the blockchain network can regenerate the private key of the user node according to blood relationship information, while the unauthorized one among the multiple upper-level nodes The node cannot regenerate the private key of the user node according to the blood relationship information, and the non-superior node of the user node cannot regenerate the private key of the user node according to the blood relationship information. Therefore, only the first authorized node can decrypt the first ciphertext to obtain The first data realizes the supervision of the first data, and unauthorized nodes cannot supervise the first data. In addition, it can also be known that the first extended public key uploaded by the user node to the blockchain includes encrypted blood relationship information, even if unauthorized upper-level nodes and non-superior nodes of the user node obtain the first extended public key, What is viewed is only the encrypted blood relationship information. Therefore, the problem of additionally exposing the affiliation relationship between the user and its superior can be solved in the prior art.

In summary, according to the encryption method provided by this application shown in Figure 4 and Figure 5, it can meet the needs of users to customize their supervisory superiors, and solve the problem of additional exposure of the affiliation relationship between users and their superiors existing in the existing technology. question.

Next, please refer to Figure 6. Figure 6 is a schematic flow diagram of another encryption method provided by this application. This encryption method is specifically applied to the upper-level node in the blockchain network shown in Figure 1 that is granted supervisory authority by the user node , hereinafter, the upper-level node granted supervisory authority by the user node will be referred to as supervisory node for short.

As shown in Figure 6, the method includes:

S601. Obtain a first extended public key and a first ciphertext, wherein the first extended public key includes encrypted blood relationship information, first supervisory authorization information, and the public key of the user node, and the first ciphertext is the user node using its own The public key is obtained by encrypting the first data.

Specifically, the supervisory node can obtain the first extended public key and the first ciphertext from the blockchain.

S602. Restore and obtain the first decryption key according to the first supervisory authorization information.

S603. Use the first decryption key to decrypt the encrypted blood relationship information to obtain the blood relationship information.

S604. Generate a private key of the user node according to the blood relationship information.

S605. Decrypt the first ciphertext by using the private key of the user node to obtain the first data.

For the sake of brevity, this embodiment does not elaborate on concepts such as the first extended public key, the first ciphertext, the first supervisory authorization information, the first decryption key, blood relationship information, the private key of the user node, and the first data. Introduced, there is no process for the supervisory node to restore the first decryption key according to the first supervisory authorization information, use the first decryption key to decrypt the encrypted blood relationship information to obtain the blood relationship information, and generate the private key of the user node according to the blood relationship information etc. for detailed introduction, please refer to the relevant descriptions in the embodiment in FIG. 4 and FIG. 5 for details.

In summary, according to the encryption method provided by this application shown in Figure 6, the supervisory node obtains the extended public key of the user node (including encrypted blood relationship information, customized regulatory authorization information, and the public key of the user node) and uses the user node The public key of the node encrypts the sensitive data ciphertext obtained by encrypting the sensitive data, and then the supervisory node can regenerate the private key of the user node according to the extended public key, and finally use the generated private key to decrypt the sensitive data ciphertext to obtain the corresponding sensitive data, so as to realize the Supervision of sensitive data uploaded by user nodes to the blockchain.

In the encryption method provided by this application shown in Figure 4 and Figure 5, the user node can also dynamically add or delete supervisory nodes by modifying the supervisory authorization information in the first extended public key. The two processes are introduced below.

(1) Adding supervision nodes

As shown in Figure 7, the process may include the following steps:

S701. Obtain, according to the first extended public key, a second extended public key including encrypted blood relationship information, second supervisory authorization information, and a public key of a user node.

Wherein, the second supervisory authorization information is obtained by modifying the first supervisory authorization information by the user node, and the second supervisory authorization information is used for the second authorized node among the plurality of nodes to restore the first decryption key, and the second authorized The number of nodes includes the first authorized node, and the number of the second authorized node is greater than the number of the first authorized node, that is to say, the second supervisory authorization information can not only be restored by the first authorized node among the multiple nodes The first decryption key can also be used by nodes other than the first authorized node in the second authorized nodes to restore the first decryption key, that is, the number of supervisory nodes is increased.

Continuing to take the user node as node 1101, the superior node as node 110 and node 100, the first authorized node as node 100, and the first regulatory authorization information = {R G, Skey+R PK ₁₀₀ } as an example, assuming that The added supervision node is node 110, and node 1101 can refer to the following formula (5) to obtain the second supervision authorization information:

Second supervisory authorization information = {R G, Skey+R PK ₁₀₀ , Skey+R PK ₁₁₀ } (5)

When the node 100 obtains the above-mentioned second supervisory authorization information, the node 100 may continue to refer to the formula (2) in the above-mentioned S4022 to restore the first decryption key.

When the node 110 obtains the above-mentioned second supervisory authorization information, the node 110 may refer to the formula (4) in the above-mentioned S4022 to restore the first decryption key.

S702. Encrypt the second data by using the public key of the user node to obtain a second ciphertext.

S703. Upload the second extended public key and the second ciphertext to the blockchain.

It can be understood that after the user node uploads the second extended public key and the second ciphertext to the blockchain, except for the previously authorized upper-level nodes (that is, the first authorized node) can regenerate the second extended public key according to the second extended public key The private key of the user node, using the private key of the user node to decrypt the second ciphertext to obtain the second data, in addition to realizing the supervision of the second data, the newly added supervisory node can also regenerate the private key of the user node according to the second extended public key. key, use the private key of the user node to decrypt the second ciphertext to obtain the second data, and realize the supervision of the second data.

It can be understood that after the user node uploads the second extended public key and the second ciphertext to the blockchain, each node in the blockchain network can obtain the second extended public key and the second ciphertext, but due to the The second ciphertext is encrypted by the user node using its own public key. The private key of the user node can only be regenerated by the second authorized node based on the blood relationship information, but the unauthorized node cannot generate it. Therefore, the unauthorized node It is not possible to decrypt the second ciphertext to obtain the second data.

It should be noted that the process of adding a supervisory node shown in Figure 7 is only an example. For example, in a specific implementation, the user node may obtain the encrypted data using the third decryption key according to the first extended public key. The blood relationship information, the fourth regulatory authorization information and the fourth extended public key of the public key of the user node, wherein the fourth regulatory authorization information is obtained by modifying the first regulatory authorization information by the user node, and the fourth regulatory authorization information is used for the A second authorized node of the plurality of nodes restores the third decryption key.

(2) Delete the supervision node

As shown in Figure 8, the process may include the following steps:

S801. Obtain, according to the first extended public key, a third extended public key including re-encrypted blood relationship information, third supervisory authorization information, and a public key of a user node.

Wherein, the third supervisory authorization information is obtained by modifying the first supervisory authorization information by the user node, and the third supervisory authorization information is used for the third authorized node among the plurality of nodes to recover the second decryption key, and the second decryption key The key is used to decrypt the re-encrypted blood relationship information, the third authorized node belongs to the first authorized node, and the number of third authorized nodes is less than the number of first authorized nodes, that is to say, the third supervisory Authorization information can only be used by the third authorized node in the first authorized node to restore the second decryption key, and nodes other than the third authorized node cannot restore the second decryption key, which reduces the number of supervisory nodes quantity.

Continue to use the user node as node 1101, the superior node as node 110 and node 100, the first authorized node as node 100 and node 1101, the first supervisory authorization information = {R·G, Skey+R·PK ₁₀₀ , Skey+ R·PK ₁₁₀ } as an example, assuming that the supervisory node to be deleted is node 110, node 1101 can refer to the following formula (6) to obtain the third supervisory authorization information:

Third supervisory authorization information = {R G, Skey+R PK ₁₀₀ } (6)

When the node 100 obtains the above-mentioned third supervisory authorization information, the node 100 may continue to refer to the formula (2) in the above-mentioned S4022 to restore the first decryption key.

When the node 110 acquires the above-mentioned third supervision authorization information, since the supervision authority of the node 110 is deleted, the node 110 cannot recover the second decryption key according to the third supervision authorization information.

S802. Encrypt the third data by using the public key of the user node to obtain a third ciphertext.

S803. Upload the third extended public key and the third ciphertext to the blockchain.

It can be understood that after the user node uploads the third extended public key and the third ciphertext to the blockchain, each node in the blockchain network can obtain the third extended public key and the third ciphertext, but due to the The three ciphertexts are obtained by encrypting the user node with its own public key. The private key of the user node can only be regenerated by the third authorized node based on the blood relationship information, but cannot be generated by the unauthorized node. Therefore, the third authorized node Nodes can decrypt the third ciphertext to obtain the third data, and realize the supervision of the third data, while unauthorized nodes cannot decrypt the third ciphertext to obtain the third data.

For simplicity, the embodiments shown in Fig. 7 and Fig. 8 do not regenerate the private key of the user node according to the second extended public key/third extended public key to the authorized node, and decrypt the second ciphertext/third ciphertext. The process described in the text is described in detail. This process is similar to the process in which the supervisory node regenerates the private key of the user node according to the first extended public key and decrypts the first ciphertext described in the embodiment shown in FIG. 6. For details, please refer to FIG. 6 Relevant descriptions of the illustrated embodiments will not be repeated here.

In summary, through the encryption method provided by this application, user nodes can also dynamically add or delete supervisory nodes by modifying the supervisory authorization information in the extended public key, which is highly flexible and can optimize user experience.

The method of the embodiment of the present application has been described in detail above. In order to facilitate better implementation of the above-mentioned solution of the embodiment of the present application, correspondingly, the following also provides related equipment for cooperating with the implementation of the above-mentioned solution.

Referring to Fig. 9, Fig. 9 is a schematic structural diagram of an encryption device 900 provided by the present application. The device 900 can be applied to a user node in the blockchain network shown in Fig. 1 that needs to upload sensitive data to the blockchain. The user node can It is a personal computer, a terminal device, etc., and is not specifically limited here.

As shown in Figure 9, the device 900 provided by this application includes: an acquisition module 910, an encryption module 920, and an uplink module 930, wherein,

Obtaining module 910, configured to obtain a first extended public key, wherein the first extended public key includes encrypted blood relationship information, first supervisory authorization information, and a public key of a user node, and the blood relationship information reflects multiple nodes (referring to the user node's The relationship between the private key of the upper-level node (including the direct upper-level node and the indirect upper-level node) and the private key of the user node, the first supervisory authorization information is used for the first authorized node among the multiple nodes to restore the first decryption Key, the first decryption key is used to decrypt the encrypted blood relationship information.

An encryption module 920, configured to use the public key of the user node to encrypt the first data, so as to obtain the first ciphertext.

An uploading module 930, configured to upload the first extended public key and the first ciphertext to the blockchain.

In a possible implementation manner, the obtaining module 910 is further configured to obtain the second extended public key according to the first extended public key, and the encryption module 920 is further configured to use the public key of the user node to encrypt the second data, thereby To obtain the second ciphertext, the uploading module 930 is also used to upload the second extended public key and the second ciphertext to the blockchain. Wherein, the second extended public key includes encrypted blood relationship information, second supervisory authorization information and the public key of the user node, and the second supervisory authorization information is used for the second authorized node among the plurality of nodes to restore the first decryption key. key, the second authorized nodes include the first authorized nodes, and the number of the second authorized nodes is greater than the number of the first authorized nodes.

In a possible implementation manner, the obtaining module 910 is further configured to obtain the third extended public key according to the first extended public key, and the encryption module 920 is further configured to use the public key of the user node to encrypt the third data, thereby To obtain the third ciphertext, the uploading module 930 is also used to upload the third extended public key and the third ciphertext to the blockchain. Wherein, the third extended public key includes the re-encrypted blood relationship information, the third supervisory authorization information and the public key of the user node, and the third supervisory authorization information is used for the third authorized node among the plurality of nodes to restore the second decryption key, the second decryption key is used to decrypt the re-encrypted blood relationship information, the third authorized node belongs to the first authorized node, and the number of the third authorized nodes is less than the number of the first authorized nodes.

In a possible implementation, the acquiring module 910 is specifically configured to: firstly, acquire the extended private key, which includes the blood relationship information and the private key of the user node, and then use the first decryption key to encrypt the blood relationship information to obtain the encrypted After the consanguinity information, use the public key of the first authorized node to encrypt the first decryption key to obtain the first supervisory authorization information, and calculate the public key of the user node according to the private key of the user node, and finally according to the user node’s The public key, the encrypted blood relationship information and the first regulatory authorization information are used to obtain the first extended public key.

In a possible implementation manner, the encrypted blood relationship information includes the encrypted number of the user node and the encrypted numbers of multiple nodes.

Referring to Fig. 10, Fig. 10 is a schematic structural diagram of another encryption device 1000 provided by the present application. The device 1000 can be applied to a supervisory node granted supervisory authority by a user node in the blockchain network shown in Fig. 1. The supervisory node can It is a personal computer, a terminal device, etc., and is not specifically limited here.

As shown in Figure 10, the device 1000 provided by this application includes: an acquisition module 1010 and a decryption module 1020, wherein,

Obtaining module 1010, used to acquire extended public key (such as above first extended public key, second extended public key, third public key) and ciphertext (such as above first ciphertext, second ciphertext, third ciphertext ), where the extended public key includes encrypted blood relationship information, regulatory authorization information (such as the first regulatory authorization information, second regulatory authorization information, and third regulatory authorization information above) and the public key of the user node. The blood relationship information reflects multiple The relationship between the private key of the node and the private key of the user node, the supervisory authorization information is used to restore the decryption key for the authorized node among multiple nodes, and the decryption key is used to decrypt the encrypted blood relationship information, The ciphertext is obtained by encrypting the target data (such as the first data, second data, and third data above) with the public key of the user node, and the supervision node belongs to the authorized node.

Decryption module 1020, configured to decrypt the ciphertext according to the extended public key, so as to obtain the target data.

In a possible implementation manner, the decryption module 1020 is specifically configured to: firstly, restore the decryption key according to the regulatory authorization information, and then use the decryption key to decrypt the encrypted blood relationship information to obtain the blood relationship information, and according to the blood relationship information , generate the private key of the user node, and finally use the private key of the user node to decrypt the ciphertext to obtain the target data.

In a possible implementation manner, the supervisory authorization information is obtained by the user node encrypting the decryption key according to the public key of the authorized node.

In a possible implementation manner, the encrypted blood relationship information includes the encrypted number of the user node and the encrypted numbers of multiple nodes.

Specifically, for the implementation of various operations performed by the device 900 shown in FIG. 9 and the device 1000 shown in FIG. 10 , refer to the description in the relevant content in the above-mentioned encryption method embodiment. For the sake of brevity, details are not repeated here.

It should be understood that the device 900 shown in FIG. 9 and the device 1000 shown in FIG. 10 are only an example provided by the embodiment of the present application, and the device 900 shown in FIG. 9 may have more or fewer components than those shown in FIG. 9 Components, two or more components can be combined, or can be implemented with different configurations of components, the device 1000 shown in Figure 10 can have more or fewer components than those shown in Figure 10, and two or more components can be combined multiple components, or may have different configurations of components.

Referring to FIG. 11 , FIG. 11 is a schematic structural diagram of a computing device 1100 provided in the present application. The computing device 1100 includes: a processor 1110 , a memory 1120 and a communication interface 1130 . Can be connected to each other through the bus 1140 . in,

The processor 1110 may read the program code (including instructions) stored in the memory 1120, and execute the program code stored in the memory 1120, so that the computing device 1100 executes the steps in the encryption method provided by the above method embodiments, or makes the computing device 1100 deploy The encryption device 900 and/or the encryption device 1000 .

The processor 1110 may have multiple specific implementation forms, such as a central processing unit (central processing unit, CPU), or a combination of a CPU and a hardware chip. The aforementioned hardware chip may be an application-specific integrated circuit (application-specific integrated circuit, ASIC), a programmable logic device (programmable logic device, PLD) or a combination thereof. The aforementioned PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL) or any combination thereof. Processor 1110 executes various types of digitally stored instructions, such as software or firmware programs stored in memory 1120, which enable computing device 1100 to provide various services.

The memory 1120 is used to store program codes, which are controlled and executed by the processor 1110, so as to execute the processing steps of the user node or supervisory node in any of the above-mentioned embodiments in FIG. 4-FIG. 8 . The program code may include one or more software modules, and the one or more software modules may be the software modules provided in the embodiment of FIG. Steps S401 to S404 in the embodiment, steps S4021 to S4024 in the embodiment in FIG. 5, steps S701 to S703 in the embodiment in FIG. 7, and steps S801 to S803 in the embodiment in FIG. to repeat. Alternatively, the one or more software modules may be the software modules provided in the embodiment of FIG. 10, such as the acquisition module 1010 and the decryption module 1020, which may be specifically used to execute steps S601 to S605 in the embodiment of FIG. 6, which will not be repeated here. repeat.

The memory 1120 may include a volatile memory (volatile memory), such as a random access memory (random access memory, RAM); the memory 1120 may also include a non-volatile memory (non-volatile memory), such as a read-only memory (read-only memory, ROM), flash memory (flash memory), hard disk (hard disk drive, HDD) or solid-state drive (solid-state drive, SSD); the memory 1120 may also include a combination of the above types.

The communication interface 1130 can be a wired interface (such as an Ethernet interface, a fiber optic interface, other types of interfaces (such as an infiniBand interface)) or a wireless interface (such as a cellular network interface or using a wireless local area network interface) for communicating with other computing devices or devices. communication. The communication interface 1130 can adopt a protocol family above the transmission control protocol/internet protocol (transmission control protocol/internet protocol, TCP/IP), for example, a remote function call (remote function call, RFC) protocol, a simple object access protocol (simple object access protocol) , SOAP) protocol, simple network management protocol (simple network management protocol, SNMP) protocol, common object request broker architecture (common object request broker architecture, CORBA) protocol and distributed protocols, etc.

The bus 1140 can be a peripheral component interconnect express (PCIe) bus, or an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a computer fast link (compute express link, CXL), cache coherent interconnect for accelerators (CCIX), etc. The bus 1140 can be divided into an address bus, a data bus, a control bus, and the like. In addition to the data bus, the bus 1140 may also include a power bus, a control bus, a status signal bus, and the like. However, for clarity of illustration, the various buses are labeled as bus 1140 in the figure. For ease of representation, only one thick line is used in FIG. 11 , but it does not mean that there is only one bus or one type of bus.

The above-mentioned computing device 1100 is used to execute the method executed in the above-mentioned encryption method embodiment, which belongs to the same concept as the above-mentioned method embodiment, and its specific implementation process is detailed in the above-mentioned method embodiment, and will not be repeated here.

It should be understood that the computing device 1100 is only an example provided by the embodiment of the present application, and the computing device 1100 may have more or fewer components than those shown in FIG. 11 , and two or more components may be combined, or It can be realized with different configurations of components.

The present application also provides a computer-readable storage medium, in which instructions are stored, and when the instructions are executed, some or all steps of the encryption method described in the above-mentioned embodiments can be implemented.

The present application also provides a computer program product. When the computer program product is read and executed by a computer, some or all steps of the encryption method described in the above method embodiments can be realized.

In the above-mentioned embodiments, the descriptions of each embodiment have their own emphases, and for parts not described in detail in a certain embodiment, reference may be made to relevant descriptions of other embodiments.

In the above-mentioned embodiments, all or part may be implemented by software, hardware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, DSL) or wireless (eg, infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium, or a semiconductor medium.

The foregoing is only a specific implementation manner of the present application. Those skilled in the art may conceive changes or substitutions based on the specific implementation methods provided in this application, and all of them shall fall within the protection scope of this application.

Claims (17)

1. An encryption method, characterized in that, the method is applied to a user node in a block chain network, comprising: Obtaining a first extended public key, wherein the first extended public key includes encrypted blood relationship information, first supervisory authorization information, and the public key of the user node, and the blood relationship information reflects the relationship between the private keys of multiple nodes and the The association relationship between the private keys of the user nodes, the first supervisory authorization information is used for the first authorized node among the plurality of nodes to restore the first decryption key, and the first decryption key is used Decrypting the encrypted blood relationship information; encrypting the first data by using the public key of the user node, so as to obtain the first ciphertext; uploading the first extended public key and the first ciphertext to a block chain. 2. The method according to claim 1, characterized in that the method further comprises: Obtain a second extended public key according to the first extended public key, where the second extended public key includes encrypted blood relationship information, second supervision authorization information, and the public key of the user node, and the second supervision The authorization information is used for restoring the first decryption key by a second authorized node among the plurality of nodes, the second authorized node includes the first authorized node, and the second authorized node The authorized number of nodes is greater than the first authorized number of nodes; encrypting the second data by using the public key of the user node, so as to obtain the second ciphertext; uploading the second extended public key and the second ciphertext to the block chain. 3. The method according to claim 1, wherein the method further comprises: Obtain a third extended public key according to the first extended public key, wherein the third extended public key includes re-encrypted blood relationship information, third supervisory authorization information, and the public key of the user node, the third extended public key The supervisory authorization information is used for the third authorized node among the plurality of nodes to restore the second decryption key, and the second decryption key is used for decrypting the re-encrypted blood relationship information, and the first Three authorized nodes belong to the first authorized node, and the third authorized node number is smaller than the first authorized node number; encrypting the third data by using the public key of the user node, so as to obtain the third ciphertext; uploading the third extended public key and the third ciphertext to the block chain. 4. The method according to any one of claims 1 to 3, wherein said acquiring the first extended public key comprises: Obtain an extended private key, where the extended private key includes the blood relationship information and the private key of the user node; Encrypting the blood relationship information using a first decryption key to obtain the encrypted blood relationship information; Encrypting the first decryption key using the public key of the first authorized node to obtain the first supervisory authorization information; According to the private key of the user node, calculate the public key of the user node; A first extended public key is obtained according to the public key of the user node, the encrypted blood relationship information, and the first supervisory authorization information. 5. The method according to any one of claims 1 to 4, wherein the encrypted blood relationship information includes the encrypted user node number and the encrypted multiple node numbers. 6. An encryption method, characterized in that the method is applied to a supervisory node in a block chain network, comprising: Obtain the extended public key and ciphertext, wherein the extended public key includes encrypted lineage information, supervisory authorization information, and the public key of the user node, and the lineage information reflects the private keys of multiple nodes and the private key of the user node. The association relationship between keys, the supervisory authorization information is used for the authorized nodes among the multiple nodes to restore the decryption key, and the decryption key is used to decrypt the encrypted blood relationship information, so The ciphertext is obtained by encrypting the target data by the user node using the public key of the user node, and the supervisory node belongs to the authorized node; Decrypt the ciphertext according to the extended public key to obtain the target data. 7. The method according to claim 6, wherein the decrypting the ciphertext according to the extended public key to obtain the target data comprises: recovering the decryption key based on the supervisory authorization information; Decrypting the encrypted blood relationship information using the decryption key to obtain the blood relationship information; generating a private key of the user node according to the blood relationship information; Decrypt the ciphertext by using the private key of the user node to obtain the target data. 8. The method according to claim 6 or 7, wherein the supervisory authorization information is obtained by the user node encrypting the decryption key according to the public key of the authorized node. 9. The method according to any one of claims 6 to 8, wherein the encrypted blood relationship information includes the encrypted user node number and the encrypted multiple node numbers. 10. An encryption device, characterized in that the device is applied to a user node in a block chain network, comprising: An acquisition module, configured to acquire a first extended public key, wherein the first extended public key includes encrypted blood relationship information, first supervisory authorization information, and the public key of the user node, and the blood relationship information reflects multiple nodes The association relationship between the private key of the user node and the private key of the user node, the first supervisory authorization information is used for the first authorized node among the plurality of nodes to recover the first decryption key, and the first A decryption key is used to decrypt the encrypted blood relationship information; An encryption module, configured to use the public key of the user node to encrypt the first data, so as to obtain the first ciphertext; An uploading module, configured to upload the first extended public key and the first ciphertext to the block chain. 11. The apparatus of claim 10, wherein: The obtaining module is further configured to obtain a second extended public key according to the first extended public key, wherein the second extended public key includes encrypted blood relationship information, second supervisory authorization information, and the user node's a public key, the second supervisory authorization information is used to recover the first decryption key by a second authorized node of the plurality of nodes, the second authorized node includes the first authorized nodes, the second number of authorized nodes is greater than the first number of authorized nodes; The encryption module is further configured to use the public key of the user node to encrypt the second data, so as to obtain the second ciphertext; The on-chain module is further configured to upload the second extended public key and the second ciphertext to the block chain. 12. The apparatus of claim 10, wherein: The obtaining module is further configured to obtain a third extended public key according to the first extended public key, wherein the third extended public key includes re-encrypted blood relationship information, third supervisory authorization information, and the user node public key, the third supervisory authorization information is used for the third authorized node among the plurality of nodes to restore the second decryption key, and the second decryption key is used for the re-encrypted The blood relationship information is decrypted, the third authorized node belongs to the first authorized node, and the number of the third authorized nodes is smaller than the number of the first authorized nodes; The encryption module is further configured to use the public key of the user node to encrypt the third data, so as to obtain the third ciphertext; The on-chain module is further configured to upload the third extended public key and the third ciphertext to the block chain. 13. The device according to any one of claims 10 to 12, wherein the acquisition module is specifically used for: Obtain an extended private key, where the extended private key includes the blood relationship information and the private key of the user node; Encrypting the blood relationship information using a first decryption key to obtain the encrypted blood relationship information; Encrypting the first decryption key using the public key of the first authorized node to obtain the first supervisory authorization information; According to the private key of the user node, calculate the public key of the user node; A first extended public key is obtained according to the public key of the user node, the encrypted blood relationship information, and the first supervisory authorization information. 14. The device according to any one of claims 10 to 13, wherein the encrypted blood relationship information includes the encrypted user node number and the encrypted multiple node numbers. 15. An encryption device, characterized in that the device is applied to a supervisory node in a blockchain network, comprising: An acquisition module, configured to acquire an extended public key and ciphertext, wherein the extended public key includes encrypted lineage information, supervisory authorization information, and public keys of user nodes, and the lineage information reflects the relationship between the private keys of multiple nodes and all The association relationship between the private keys of the user nodes, the supervision and authorization information is used for the authorized node among the multiple nodes to restore the decryption key, and the decryption key is used for the encryption of the blood relationship The information is decrypted, and the ciphertext is obtained by encrypting the target data by the user node using the public key of the user node, and the supervisory node belongs to the authorized node; A decryption module, configured to decrypt the ciphertext according to the extended public key, so as to obtain the target data. 16. A computing device, characterized in that, the computing device comprises a processor and a memory; the processor is configured to execute instructions stored in the memory, so that the computing device implements any one of claims 1 to 9. Methods. 17. A computer-readable storage medium, wherein the computer-readable medium stores instructions, and the instructions are used to implement the method according to any one of claims 1-9.

Images