Methods, devices, and related products for updating encryption modules in blockchain systems

Abstract

This application discloses a method, apparatus, and related products for updating an encryption module in a blockchain system. The method involves receiving an encryption module update request generated by the blockchain system; encrypting the update request using security parameters to generate an encryption module retrieval instruction; verifying the retrieval instruction according to a generated trapdoor; if valid, generating a project repository access request to access a project repository storing a second encryption module that replaces the first encryption module in the blockchain system. The first encryption module is loaded into the blockchain system as an encryption plugin, and the second encryption module is loaded into a plugin framework in the project repository via a predefined encryption algorithm code entry point. The project repository authenticates the access request; if authentication is successful, the first encryption module in the blockchain system is updated to the second encryption module via remote dependency.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular to a method, apparatus, and related products for updating an encryption module in a blockchain system. Background Technology

[0002] A blockchain is a chain of blocks, each containing specific information, linked together in chronological order. This chain is stored on all servers; as long as at least one server in the system is operational, the entire blockchain is secure. These servers are called nodes in the blockchain system, providing storage space and computing power. Modifying information in the blockchain requires the consent of more than half of the nodes and modification of the information across all nodes. Since these nodes are typically controlled by different entities, tampering with information in the blockchain is extremely difficult.

[0003] In the application of blockchain technology, terminal block nodes are involved. Each block node is equivalent to a terminal, and for it to participate in the overall blockchain system, it must be loaded with necessary code and resource packages. Currently, this is often implemented using static libraries. Among these, encryption algorithms are a crucial function for blockchain. When the encryption algorithm is implemented as a static library, updating the encryption algorithm requires updating the entire dynamic library, resulting in high update costs. Summary of the Invention

[0004] To address the aforementioned issues, this application provides a method, apparatus, and related products for updating an encryption module in a blockchain system.

[0005] The embodiments of this application disclose the following technical solutions:

[0006] A method for updating an encryption module in a blockchain system, comprising:

[0007] Receive encryption module update requests generated by the blockchain system;

[0008] The encryption module update request is encrypted using security parameters to generate an encryption module retrieval instruction. The security dimension parameter used for encryption is set to 100, so that the feature value dimension of the encryption module retrieval instruction is equal to 2048, and it includes at least the receiving timestamp of the encryption module update request.

[0009] The generated trapdoor is used to verify the encryption module's call instruction. The trapdoor is obtained by performing a hash operation based on a predetermined verification private key and a set encryption algorithm code entry point.

[0010] If valid, a project repository access request is generated to access the project repository containing a second encryption module that replaces the first encryption module in the blockchain system. The first encryption module is loaded into the blockchain system as an encryption plugin, and the second encryption module is loaded into the plugin framework loaded in the project repository as a plugin project through the set encryption algorithm code entry point.

[0011] The project repository authenticates access requests to the project repository. If the authentication is successful, the first encryption module in the blockchain system is updated to the second encryption module through remote dependency.

[0012] Optionally, accessing the project repository storing the second encryption module that replaces the first encryption module in the blockchain system includes: creating a first plugin project and a second plugin project, wherein the second plugin project and the first plugin project are mutually real and fake, the plugin project with the fake identity in the first plugin project and the second plugin project is used to manage the encryption algorithm code entry point, and the plugin project with the real identity in the first plugin project and the second plugin project is used to enable the plugin project with the fake identity to access the encryption algorithm code entry point.

[0013] Optionally, accessing the project repository storing the second encryption module that replaces the first encryption module in the blockchain system further includes: the plugin project with a real identity calling the plugin project with a fake identity in the first plugin project and the second plugin project to load the second encryption module as a plugin project in the plugin framework loaded in the project repository.

[0014] Optionally, accessing the project repository storing the second encryption module that replaces the first encryption module in the blockchain system further includes: creating the first plugin project and the second plugin project in the created project repository through the created plugin project declaration.

[0015] An update device for an encryption module in a blockchain system, characterized in that it comprises:

[0016] The first program unit is used to receive the encryption module update request generated by the blockchain system;

[0017] The second program unit is used to encrypt the encryption module update request using security parameters and generate an encryption module retrieval instruction. The security dimension parameter used for encryption is set to 100, so that the feature value dimension of the encryption module retrieval instruction is equal to 2048, and it includes at least the receiving timestamp of the encryption module update request.

[0018] The third program unit is used to verify the encryption module's call instruction according to the generated trapdoor, wherein the trapdoor is obtained by hashing a predetermined verification private key and a set encryption algorithm code entry point;

[0019] The fourth program unit is used to generate a project repository access request in response to the legality of the encryption module call instruction, so as to access the project repository storing the second encryption module that replaces the first encryption module in the blockchain system. The first encryption module is loaded in the blockchain system in the form of an encryption plugin, and the second encryption module is loaded in the plugin framework loaded in the project repository in the form of a plugin project through the set encryption algorithm code entry point.

[0020] The fourth program unit is used to enable the project repository to authenticate the access request to the project repository. If the authentication is successful, the first encryption module in the blockchain system is updated to the second encryption module through remote dependency.

[0021] Optionally, the fourth program unit is further configured to: create a first plugin project and a second plugin project, wherein the second plugin project and the first plugin project are mutually real and fake, wherein the plugin project with the fake identity in the first plugin project and the second plugin project is used to manage the encryption algorithm code entry point, and the plugin project with the real identity in the first plugin project and the second plugin project is used to enable the plugin project with the fake identity to access the encryption algorithm code entry point.

[0022] Optionally, the fourth program unit is further configured to: the plugin project with a real identity in the first plugin project and the second plugin project call the plugin project with a fake identity to load the second encryption module as a plugin project in the plugin framework loaded in the project repository.

[0023] The apparatus according to claim 10, wherein the fourth program unit is further configured to: create the first plugin project and the second plugin project in the created project repository by means of a created plugin project declaration.

[0024] An electronic device includes a memory and a processor, wherein the memory stores an executable program, and the processor performs the following steps when running the executable program:

[0025] Receive encryption module update requests generated by the blockchain system;

[0026] The encryption module update request is encrypted using security parameters to generate an encryption module retrieval instruction. The security dimension parameter used for encryption is set to 100, so that the feature value dimension of the encryption module retrieval instruction is equal to 2048, and it includes at least the receiving timestamp of the encryption module update request.

[0027] The generated trapdoor is used to verify the encryption module's call instruction. The trapdoor is obtained by performing a hash operation based on a predetermined verification private key and a set encryption algorithm code entry point.

[0028] If valid, a project repository access request is generated to access the project repository containing a second encryption module that replaces the first encryption module in the blockchain system. The first encryption module is loaded into the blockchain system as an encryption plugin, and the second encryption module is loaded into the plugin framework loaded in the project repository as a plugin project through the set encryption algorithm code entry point.

[0029] The project repository authenticates access requests to the project repository. If the authentication is successful, the first encryption module in the blockchain system is updated to the second encryption module through remote dependency.

[0030] A computer program product having an executable program stored thereon, wherein running the executable program performs the following steps:

[0031] Receive encryption module update requests generated by the blockchain system;

[0032] The encryption module update request is encrypted using security parameters to generate an encryption module retrieval instruction. The security dimension parameter used for encryption is set to 100, so that the feature value dimension of the encryption module retrieval instruction is equal to 2048, and it includes at least the receiving timestamp of the encryption module update request.

[0033] The generated trapdoor is used to verify the encryption module's call instruction. The trapdoor is obtained by performing a hash operation based on a predetermined verification private key and a set encryption algorithm code entry point.

[0034] If valid, a project repository access request is generated to access the project repository containing a second encryption module that replaces the first encryption module in the blockchain system. The first encryption module is loaded into the blockchain system as an encryption plugin, and the second encryption module is loaded into the plugin framework loaded in the project repository as a plugin project through the set encryption algorithm code entry point.

[0035] The project repository authenticates access requests to the project repository. If the authentication is successful, the first encryption module in the blockchain system is updated to the second encryption module through remote dependency.

[0036] In the technical solution of this application embodiment, an encryption module update request generated by the blockchain system is received; the encryption module update request is encrypted using security parameters to generate an encryption module retrieval instruction, wherein the security dimension parameter used for encryption is set to 100, so that the feature value dimension of the encryption module retrieval instruction is equal to 2048, and includes at least the receiving timestamp of the encryption module update request; the encryption module retrieval instruction is verified according to the generated trapdoor, wherein the trapdoor is obtained by hashing based on a predetermined verification private key and a set encryption algorithm code entry; if valid, a project repository access request is generated to access the project repository storing a second encryption module that replaces the first encryption module in the blockchain system. The first encryption module is loaded in the blockchain system as an encryption plugin, and the second encryption module is loaded in the plugin framework loaded in the project repository as a plugin project through the set encryption algorithm code entry; the project repository authenticates the project repository access request. If the authentication is successful, the first encryption module in the blockchain system is updated to the second encryption module through remote dependency, so that when there is an update to the encryption algorithm, it can be implemented based on the plugin, thereby reducing the cost of updating the encryption algorithm. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 This is a schematic diagram of a method for updating an encryption module in a blockchain system, according to an embodiment of this application.

[0039] Figure 2 This is a schematic diagram of the structure of an update device for an encryption module in a blockchain system, according to an embodiment of this application.

[0040] Figure 3 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application;

[0041] Figure 4 This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0042] Implementing any technical solution of the embodiments of this application does not necessarily require achieving all of the above advantages at the same time.

[0043] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0044] In the technical solution of this application embodiment, an encryption module update request generated by the blockchain system is received; the encryption module update request is encrypted using security parameters to generate an encryption module retrieval instruction, wherein the security dimension parameter used for encryption is set to 100, so that the feature value dimension of the encryption module retrieval instruction is equal to 2048, and includes at least the receiving timestamp of the encryption module update request; the encryption module retrieval instruction is verified according to the generated trapdoor, wherein the trapdoor is obtained by hashing based on a predetermined verification private key and a set encryption algorithm code entry; if valid, a project repository access request is generated to access the project repository storing a second encryption module that replaces the first encryption module in the blockchain system. The first encryption module is loaded in the blockchain system as an encryption plugin, and the second encryption module is loaded in the plugin framework loaded in the project repository as a plugin project through the set encryption algorithm code entry; the project repository authenticates the project repository access request. If the authentication is successful, the first encryption module in the blockchain system is updated to the second encryption module through remote dependency, so that when there is an update to the encryption algorithm, it can be implemented based on the plugin, thereby reducing the cost of updating the encryption algorithm.

[0045] Figure 1 This is a schematic flowchart illustrating a method for updating an encryption module in a blockchain system, as described in an embodiment of this application. Figure 1 As shown, it includes:

[0046] S101, Receive the encryption module update request generated by the blockchain system;

[0047] S102. Encrypt the encryption module update request using security parameters to generate an encryption module retrieval instruction;

[0048] In this embodiment, the security dimension parameter used for encryption is set to 100, so that the feature value dimension of the encryption module's call instruction is equal to 2048, and at least includes the timestamp of the encryption module's update request.

[0049] S103. Verify the encryption module's retrieval instructions based on the generated trapdoor;

[0050] In this embodiment, the trapdoor is obtained by performing a hash operation based on a predetermined verification private key and a set encryption algorithm code entry point;

[0051] If valid, execute S104: Generate a project repository access request to access the project repository containing the second encryption module that replaces the first encryption module in the blockchain system;

[0052] If the request is invalid, the encryption module update request will be rejected.

[0053] In this embodiment, the first encryption module is loaded into the blockchain system in the form of an encryption plugin, and the second encryption module is loaded into the plugin framework loaded in the project repository in the form of a plugin project through the set encryption algorithm code entry point.

[0054] S105. The project repository authenticates the access request to the project repository. If the authentication is successful, the first encryption module in the blockchain system is updated to the second encryption module through remote dependency.

[0055] Optionally, accessing the project repository storing the second encryption module that replaces the first encryption module in the blockchain system includes: creating a first plugin project and a second plugin project, wherein the second plugin project and the first plugin project are mutually real and fake, the plugin project with the fake identity in the first plugin project and the second plugin project is used to manage the encryption algorithm code entry point, and the plugin project with the real identity in the first plugin project and the second plugin project is used to enable the plugin project with the fake identity to access the encryption algorithm code entry point.

[0056] Optionally, accessing the project repository storing the second encryption module that replaces the first encryption module in the blockchain system further includes: the plugin project with a real identity in the first plugin project and the second plugin project calling the plugin project with a fake identity, so as to load the second encryption module as a plugin project in the plugin framework loaded in the project repository, thereby facilitating the rapid embedding and calling of the plugin, and facilitating subsequent upgrades to the encryption algorithm.

[0057] In this embodiment, by establishing a true / false relationship between the first plugin project and the second plugin project, the management of the encryption algorithm code entry point is achieved based on the plugin project with the false identity, while the plugin project with the true identity is used to enable the plugin project with the false identity to access the encryption algorithm code entry point. This enables mutual calls based on plugin projects, improving the directness and efficiency of data.

[0058] Optionally, accessing the project repository storing the second encryption module that replaces the first encryption module in the blockchain system further includes: creating the first plugin project and the second plugin project in the created project repository through the created plugin project declaration.

[0059] For example, by creating a plugin project declaration, the first plugin project and the second plugin project are created in the created project repository. This includes: creating a plugin project declaration, defining the generic arguments according to the set generic arguments as the execution entry point of the encryption algorithm code, so as to create a pseudo plugin project declaration and manage the entry point of the encryption algorithm code through the plugin project with the pseudo identity, thereby improving the security performance of the encryption algorithm and avoiding attacks.

[0060] In this embodiment, the plugin project and the host project can be located in the same local project repository by means of the mapping relationship between the plugin project ID, the host project ID and the local project repository.

[0061] In this embodiment, based on the created plugin project declaration, the creation of the first plugin project and the second plugin project can be achieved quickly, satisfying the real-time update of the encryption algorithm.

[0062] Optionally, accessing the project repository storing a second encryption module that replaces the first encryption module in the blockchain system further includes:

[0063] The program calls the created plugin project and the host project to create the project repository.

[0064] In this embodiment, creating the project repository based on the created plugin project and the host project can specifically include:

[0065] The plugin project parses the created target declaration folder to determine the repository address and dependent data packages. The host project then creates the plugin project and the host project based on the repository address and dependent data packages.

[0066] By parsing the target declaration folder, the repository address and dependent data packages can be quickly determined, thereby improving the speed of creating plugin projects and host projects.

[0067] In this embodiment, the created target declaration folder can be parsed using a script code file. The script code file specifies the address of the target declaration file, and the repository address and dependent data packets are obtained from the address of the target declaration file. The repository address is specifically the address of the repository where the code is stored, and the dependent data packets include all data packets required to implement encryption.

[0068] Optionally, the creation of the plugin project and the host project through the call, and the creation of the project repository, include:

[0069] Based on the set unique identifier logical offset, assign IDs to the called plugin project and the host project;

[0070] A project repository is created based on the IDs assigned to the plugin project and the host project.

[0071] For example, assigning IDs to the invoked plugin project and host project based on the set unique identifier logical offset may include: assigning IDs to the plugin project and host project according to the set ID logical offset and the set ID anchor point.

[0072] By using logical offsets and defined ID anchor points, the IDs of the plugin project and the host project can be accurately assigned. Specifically, for example, the IDs of the plugin project and the host project can be assigned in segments.

[0073] Specifically, the allocation of IDs for the plugin project and the host project can be achieved using two logical offsets and an ID anchor point. Specifically, starting from the ID anchor point and using the logical offset as the step size, the IDs for the plugin project and the host project are calculated respectively.

[0074] Optionally, the step of calling the created plugin project and host project to create the project repository further includes:

[0075] The created target declaration folder is parsed to determine the repository address and dependent data packages. Based on the repository address and dependent data packages, the plugin project and the host project are created.

[0076] Optionally, assigning IDs to the called plugin project and host project based on the set unique identifier logical offset includes: assigning IDs to the plugin project and host project according to the set ID logical offset and the set ID anchor point.

[0077] Figure 2 This is a schematic diagram of the structure of an update device for an encryption module in a blockchain system, as described in an embodiment of this application; Figure 2 As shown, it includes:

[0078] The first program unit 201 is used to receive the encryption module update request generated by the blockchain system;

[0079] The second program unit 202 is used to encrypt the encryption module update request using security parameters and generate an encryption module retrieval instruction. The security dimension parameter used for encryption is set to 100, so that the feature value dimension of the encryption module retrieval instruction is equal to 2048, and it includes at least the receiving timestamp of the encryption module update request.

[0080] The third program unit 203 is used to verify the encryption module call instruction according to the generated trapdoor, wherein the trapdoor is obtained by hashing a predetermined verification private key and a set encryption algorithm code entry point;

[0081] The fourth program unit 204 is used to generate a project repository access request in response to the legality of the encryption module call instruction, so as to access the project repository storing the second encryption module that replaces the first encryption module in the blockchain system. The first encryption module is loaded in the blockchain system in the form of an encryption plugin, and the second encryption module is loaded in the plugin framework loaded in the project repository in the form of a plugin project through the set encryption algorithm code entry point.

[0082] The fifth program unit 205 is used to enable the project repository to authenticate the access request to the project repository. If the authentication is successful, the first encryption module in the blockchain system is updated to the second encryption module through remote dependency.

[0083] Optionally, the fourth program unit is further configured to: create a first plugin project and a second plugin project, wherein the second plugin project and the first plugin project are mutually real and fake, wherein the plugin project with the fake identity in the first plugin project and the second plugin project is used to manage the encryption algorithm code entry point, and the plugin project with the real identity in the first plugin project and the second plugin project is used to enable the plugin project with the fake identity to access the encryption algorithm code entry point.

[0084] Optionally, the fourth program unit is further configured to: the plugin project with a real identity in the first plugin project and the second plugin project call the plugin project with a fake identity to load the second encryption module as a plugin project in the plugin framework loaded in the project repository.

[0085] The apparatus according to claim 10, wherein the fourth program unit is further configured to: create the first plugin project and the second plugin project in the created project repository by means of a created plugin project declaration.

[0086] Optionally, the fourth program unit is further configured to:

[0087] The program calls the created plugin project and the host project to create the project repository.

[0088] Optionally, the fourth program unit is further configured to:

[0089] Based on the set unique identifier logical offset, assign IDs to the called plugin project and the host project;

[0090] A project repository is created based on the IDs assigned to the plugin project and the host project.

[0091] Optionally, the fourth program unit is further configured to:

[0092] The created target declaration folder is parsed to determine the repository address and dependent data packages. Based on the repository address and dependent data packages, the plugin project and the host project are created.

[0093] Optionally, the fourth program unit is further configured to: assign IDs to the plugin project and the host project based on the set ID logical offset and the set ID anchor point positioning.

[0094] Figure 3 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application; as shown Figure 3 As shown, it includes a memory 301 and a processor 302. The memory stores an executable program, and when the processor runs the executable program, it performs the following steps:

[0095] Receive encryption module update requests generated by the blockchain system;

[0096] The encryption module update request is encrypted using security parameters to generate an encryption module retrieval instruction. The security dimension parameter used for encryption is set to 100, so that the feature value dimension of the encryption module retrieval instruction is equal to 2048, and it includes at least the receiving timestamp of the encryption module update request.

[0097] The generated trapdoor is used to verify the encryption module's call instruction. The trapdoor is obtained by performing a hash operation based on a predetermined verification private key and a set encryption algorithm code entry point.

[0098] If valid, a project repository access request is generated to access the project repository containing a second encryption module that replaces the first encryption module in the blockchain system. The first encryption module is loaded into the blockchain system as an encryption plugin, and the second encryption module is loaded into the plugin framework loaded in the project repository as a plugin project through the set encryption algorithm code entry point.

[0099] The project repository authenticates access requests to the project repository. If the authentication is successful, the first encryption module in the blockchain system is updated to the second encryption module through remote dependency.

[0100] Figure 4 This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application; as shown Figure 4 As shown, the hardware structure of the electronic device may include: a processor 401, a communication interface 402, a computer-readable medium 403, and a communication bus 404.

[0101] The processor 401, communication interface 402, and computer-readable medium 403 communicate with each other through communication bus 404.

[0102] Optionally, the communication interface 402 can be an interface of a communication module, such as the interface of a GSM module;

[0103] Specifically, the processor 401 can be configured to run an executable program stored in the memory, thereby executing all or part of the processing steps of any of the above method embodiments.

[0104] Processor 401 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor.

[0105] The electronic devices in this application embodiments exist in various forms, including but not limited to:

[0106] (1) Mobile communication devices: These devices are characterized by their mobile communication capabilities and primarily aim to provide voice and data communication. These terminals include: smartphones (e.g., iPhones), multimedia phones, feature phones, and low-end phones, etc.

[0107] (2) Ultra-mobile personal computer devices: These devices fall under the category of personal computers, possessing computing and processing capabilities, and generally also have mobile internet access features. These terminals include PDAs, MIDs, and UMPCs, such as the iPad.

[0108] (3) Portable entertainment devices: These devices can display and play multimedia content. This category includes audio and video players (such as iPods), handheld game consoles, e-book readers, as well as smart toys and portable car navigation devices.

[0109] (4) Server: A device that provides computing services. The components of a server include a processor 410, hard disk, memory, system bus, etc. Servers are similar to general computer architectures, but because they need to provide highly reliable services, they have higher requirements in terms of processing power, stability, reliability, security, scalability, and manageability.

[0110] (5) Other electronic devices with data interaction functions.

[0111] It should be noted that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for the device and system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiments. The device and system embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components indicated as modules may or may not be physical modules, that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of the solution in this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0112] The above description is merely one specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for updating an encryption module in a blockchain system, characterized in that, include: Receive encryption module update requests generated by the blockchain system; The encryption module update request is encrypted using security parameters to generate an encryption module retrieval instruction. The security dimension parameter used for encryption is set to 100, so that the feature value dimension of the encryption module retrieval instruction is equal to 2048, and it includes at least the receiving timestamp of the encryption module update request. The generated trapdoor is used to verify the encryption module's call command. The trapdoor is obtained by performing a hash operation based on a predetermined verification private key and a set encryption algorithm code entry point. If valid, a project repository access request is generated to access the project repository containing a second encryption module that replaces the first encryption module in the blockchain system. The first encryption module is loaded into the blockchain system as an encryption plugin, and the second encryption module is loaded into the plugin framework loaded in the project repository as a plugin project through the set encryption algorithm code entry point. The project repository authenticates access requests to the project repository. If the authentication is successful, the first encryption module in the blockchain system is updated to the second encryption module through remote dependency. The access to the project repository storing the second encryption module that replaces the first encryption module in the blockchain system includes: creating a first plugin project and a second plugin project, wherein the second plugin project and the first plugin project are mutually real and fake, the plugin project with the fake identity in the first plugin project and the second plugin project is used to manage the encryption algorithm code entry point, and the plugin project with the real identity in the first plugin project and the second plugin project is used to enable the plugin project with the fake identity to access the encryption algorithm code entry point.

2. The method according to claim 1, characterized in that, The access to the project repository storing the second encryption module that replaces the first encryption module in the blockchain system also includes: the plugin project with a real identity in the first plugin project and the second plugin project calling the plugin project with a fake identity to load the second encryption module as a plugin project in the plugin framework loaded in the project repository.

3. The method according to claim 1, characterized in that, The access to the project repository storing the second encryption module that replaces the first encryption module in the blockchain system also includes: creating the first plugin project and the second plugin project in the created project repository through the created plugin project declaration.

4. A device for updating an encryption module in a blockchain system, characterized in that, include: The first program unit is used to receive the encryption module update request generated by the blockchain system; The second program unit is used to encrypt the encryption module update request using security parameters and generate an encryption module retrieval instruction. The security dimension parameter used for encryption is set to 100, so that the feature value dimension of the encryption module retrieval instruction is equal to 2048, and it includes at least the receiving timestamp of the encryption module update request. The third program unit is used to verify the encryption module's call instruction according to the generated trapdoor, wherein the trapdoor is obtained by hashing a predetermined verification private key and a set encryption algorithm code entry point; The fourth program unit is used to generate a project repository access request in response to the legality of the encryption module call instruction, so as to access the project repository storing the second encryption module that replaces the first encryption module in the blockchain system. The first encryption module is loaded in the blockchain system in the form of an encryption plugin, and the second encryption module is loaded in the plugin framework loaded in the project repository in the form of a plugin project through the set encryption algorithm code entry point. The fourth program unit is used to enable the project repository to authenticate the access request to the project repository. If the authentication is successful, the first encryption module in the blockchain system is updated to the second encryption module through remote dependency. The fourth program unit is further configured to: create a first plugin project and a second plugin project, wherein the second plugin project and the first plugin project are mutually real and fake, the plugin project with the fake identity in the first plugin project and the second plugin project is used to manage the encryption algorithm code entry point, and the plugin project with the real identity in the first plugin project and the second plugin project is used to enable the plugin project with the fake identity to access the encryption algorithm code entry point.

5. The apparatus according to claim 4, characterized in that, The fourth program unit is further configured to: call the plugin project with a real identity in the first plugin project and the second plugin project to load the second encryption module as a plugin project into the plugin framework loaded in the project repository.

6. The apparatus according to claim 4, characterized in that, The fourth program unit is further configured to: create the first plugin project and the second plugin project in the created project repository by declaring the created plugin project.

7. An electronic device, characterized in that, The system includes a memory and a processor, wherein the memory stores an executable program, and the processor executes the following steps when running the executable program: Receive encryption module update requests generated by the blockchain system; The encryption module update request is encrypted using security parameters to generate an encryption module retrieval instruction. The security dimension parameter used for encryption is set to 100, so that the feature value dimension of the encryption module retrieval instruction is equal to 2048, and it includes at least the receiving timestamp of the encryption module update request. The generated trapdoor is used to verify the encryption module's call command. The trapdoor is obtained by performing a hash operation based on a predetermined verification private key and a set encryption algorithm code entry point. If valid, a project repository access request is generated to access the project repository containing a second encryption module that replaces the first encryption module in the blockchain system. The first encryption module is loaded into the blockchain system as an encryption plugin, and the second encryption module is loaded into the plugin framework loaded in the project repository as a plugin project through the set encryption algorithm code entry point. The project repository authenticates access requests to the project repository. If the authentication is successful, the first encryption module in the blockchain system is updated to the second encryption module through remote dependency. The access to the project repository storing the second encryption module that replaces the first encryption module in the blockchain system includes: creating a first plugin project and a second plugin project, wherein the second plugin project and the first plugin project are mutually real and fake, the plugin project with the fake identity in the first plugin project and the second plugin project is used to manage the encryption algorithm code entry point, and the plugin project with the real identity in the first plugin project and the second plugin project is used to enable the plugin project with the fake identity to access the encryption algorithm code entry point.

8. A computer program product, characterized in that, It contains an executable program, and when the executable program is run, the following steps are performed: Receive encryption module update requests generated by the blockchain system; The encryption module update request is encrypted using security parameters to generate an encryption module retrieval instruction. The security dimension parameter used for encryption is set to 100, so that the feature value dimension of the encryption module retrieval instruction is equal to 2048, and it includes at least the receiving timestamp of the encryption module update request. The generated trapdoor is used to verify the encryption module's call command. The trapdoor is obtained by performing a hash operation based on a predetermined verification private key and a set encryption algorithm code entry point. If valid, a project repository access request is generated to access the project repository containing a second encryption module that replaces the first encryption module in the blockchain system. The first encryption module is loaded into the blockchain system as an encryption plugin, and the second encryption module is loaded into the plugin framework loaded in the project repository as a plugin project through the set encryption algorithm code entry point. The project repository authenticates access requests to the project repository. If the authentication is successful, the first encryption module in the blockchain system is updated to the second encryption module through remote dependency. The access to the project repository storing the second encryption module that replaces the first encryption module in the blockchain system includes: creating a first plugin project and a second plugin project, wherein the second plugin project and the first plugin project are mutually real and fake, the plugin project with the fake identity in the first plugin project and the second plugin project is used to manage the encryption algorithm code entry point, and the plugin project with the real identity in the first plugin project and the second plugin project is used to enable the plugin project with the fake identity to access the encryption algorithm code entry point.

Images