WO2024016984A1

WO2024016984A1 - Smart contract deployment method and apparatus, device, medium, and product

Info

Publication number: WO2024016984A1
Application number: PCT/CN2023/103599
Authority: WO
Inventors: 罗锦旭
Original assignee: 深圳前海环融联易信息科技服务有限公司
Priority date: 2022-07-21
Filing date: 2023-06-29
Publication date: 2024-01-25
Also published as: CN115203330B; CN115203330A

Abstract

Disclosed in the present application are a smart contract deployment method and apparatus, a computer device, and a storage medium. The method comprises: on the basis of a preset blockchain integrated development environment, generating a first smart contract to be deployed; generating a target container running the first smart contract, and deploying the first smart contract into the target container; issuing an identity certificate of the target container according to a preset node certificate; calling a preset container orchestrator to access the target container into a main chain network for identity verification; and after the identity verification of the target container succeeds, diffusing the first smart contract in the main chain network. Offline and on-chain unified deployment of the smart contract is realized by means of the target container and the identity certificate, such that a time limit of debugging deployment is shortened, and the deployment debugging efficiency of the smart contract is improved.

Description

Smart contract deployment method and its devices, equipment, media, and products

This application requires the priority of the Chinese patent application submitted to the China Patent Office on July 21, 2022, with the application number 202210862683.6 and the application name "Smart Contract Deployment Method and Devices, Equipment, Media, and Products", and all its contents are approved The reference is incorporated into the application.

Technical field

This application relates to the field of alliance chains, and in particular to a smart contract deployment method and system, and computer storage media.

Background technique

The alliance chain is only for members of a specific group and limited third parties. Multiple pre-selected nodes are designated internally as bookkeepers. The generation of each block is jointly decided by all pre-selected nodes. Other access nodes can participate in transactions. However, it does not involve the accounting process, and other third parties can conduct limited inquiries through the open API of the blockchain.

The inventor of this application discovered during research that the alliance chain smart contracts are written offline and deployed to the blockchain nodes controlled by themselves, and then debugged based on the smart contract logs. With this deployment and debugging method, smart contracts can only be debugged based on entity blockchain nodes, which is a time-consuming, labor-intensive and inefficient process.

Contents of the invention

The purpose of this application is to provide a smart contract deployment method, system, and computer storage medium to at least solve the problem of low efficiency in the deployment of existing alliance chains.

In order to solve the above technical problems, this application provides a smart contract deployment method, including:

Based on the preset blockchain integrated development environment, generate the first smart contract to be deployed;

Generate a target container that runs the first smart contract, and deploy the first smart contract to the target container;

Issue the identity certificate of the target container according to the preset node certificate;

Call the preset container orchestrator to connect the target container to the main chain network for identity verification;

When the identity verification of the target container passes, the first smart contract is diffused in the main chain network.

In order to solve the above technical problems, embodiments of the present application also provide a smart contract deployment device, including:

The generation module is used to generate the first smart contract to be deployed based on the preset blockchain integrated development environment;

A deployment module, configured to generate a target container for running the first smart contract, and deploy the first smart contract into the target container;

An issuance module, used to issue the identity certificate of the target container according to the preset node certificate;

The processing module is used to call the preset container orchestrator to connect the target container to the main chain network for identity verification;

An execution module, configured to diffuse the first smart contract in the main chain network after the identity verification of the target container passes.

In order to solve the above technical problems, embodiments of the present application also provide a computer device, including a memory and a processor. Computer readable instructions are stored in the memory. When the computer readable instructions are executed by the processor, the computer readable instructions cause the computer readable instructions to be executed by the processor. The processor performs the following steps:

Generate a target container that runs the first smart contract, and deploy the first smart contract into the target container;

In order to solve the above technical problems, embodiments of the present application also provide a storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, they cause one or more processors to perform the following steps:

The beneficial effects of the embodiments created by this application are: after the first smart contract is generated in the blockchain integrated development environment, the first smart contract is deployed in the target container of the node, and the target container runs the first smart contract, and After obtaining the identity certificate issued by the node certificate, the target container can access the main chain network, and spread the first smart contract on the chain through the main chain network, thereby realizing multi-node verification on the chain and improving the verification efficiency. efficiency. Through the target container and identity certificate, the unified deployment of smart contracts offline and on the chain is realized, which shortens the time limit for debugging and deployment and improves the efficiency of smart contract debugging and deployment.

Description of drawings

The above and/or additional aspects and advantages of the present application will become apparent and readily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

Figure 1 is a basic flow diagram of a smart contract deployment method according to a specific embodiment of the present application;

Figure 2 is a schematic diagram of the basic structure of a smart contract deployment device according to a specific embodiment of the present application;

Figure 3 is a basic structural block diagram of a computer device according to a specific embodiment of the present application.

Detailed ways

The embodiments of the present application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements with the same or similar functions. The embodiments described below with reference to the drawings are exemplary and are only used to explain the present application and cannot be construed as limiting the present application.

Those skilled in the art will understand that, unless expressly stated otherwise, the singular forms "a", "an", "the" and "the" used herein may also include the plural form. It should be further understood that the word "comprising" used in the description of this application refers to the presence of stated features, integers, steps, operations, elements and/or components, but does not exclude the presence or addition of one or more other features, Integers, steps, operations, elements, components and/or groups thereof.

It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. It should also be understood that terms, such as those defined in general dictionaries, are to be understood to have meanings consistent with their meaning in the context of the prior art, and are not to be used in an idealistic or overly descriptive manner unless specifically defined as here. to explain the formal meaning.

Those skilled in the art can understand that the "terminal" used here includes both a wireless signal receiver device that only has a wireless signal receiver without a transmission capability, and a device that has receiving and transmitting hardware that can A device that performs receiving and transmitting hardware for bidirectional communications on a bidirectional communications link. Such equipment may include: cellular or other communication equipment with a single line display or a multi-line display or a cellular or other communication equipment without a multi-line display; PCS (Personal Communications Service, personal communication system), which can combine voice, data Processing, fax and/or data communication capabilities; PDA (Personal Digital Assistant), which may include a radio frequency receiver, pager, Internet/Intranet access, web browser, notepad, calendar and/or GPS (Global Positioning System (Global Positioning System) receiver; a conventional laptop and/or palmtop computer or other device having and/or including a radio frequency receiver. As used herein, a "terminal" may be portable, transportable, installed in a vehicle (air, maritime and/or land), or adapted and/or configured to operate locally, and/or in a distributed form. Operating anywhere on Earth and/or space. The "terminal" used here can also be a communication terminal, an Internet access terminal, a music/video playback terminal, for example, it can be a PDA, MID (Mobile Internet Device, mobile Internet device) and/or a mobile phone with music/video playback function, It can also be a smart TV, set-top box and other devices.

The hardware referred to by names such as "server", "client", and "service node" in this application are essentially electronic devices with equivalent capabilities to personal computers, and are equipped with a central processing unit (including arithmetic units and controllers). ), memory, input devices, output devices and other necessary components disclosed by the von Neumann principle. The computer program is stored in its memory. The central processor transfers the program stored in the external memory into the memory to run, and executes the program. The instructions in it interact with input and output devices to complete specific functions.

It should be pointed out that the concept of "server" in this application can also be extended to the situation of server cluster. According to the network deployment principles understood by those skilled in the art, the servers should be logically divided. In physical space, these servers can be independent of each other but can be called through interfaces, or they can be integrated into a physical server. A computer or a computer cluster. Those skilled in the art should understand this modification, but it should not limit the implementation of the network deployment method of the present application.

One or several technical features of this application, unless expressly specified, can be deployed on a server for implementation. The client remotely calls the online service interface provided by the server to implement access, or it can be directly deployed and run on the client to implement access.

The neural network models cited or possibly cited in this application, unless expressly specified, can be deployed on a remote server and remotely called on the client, or can be deployed on a client with competent device capabilities for direct calling. In some embodiments, , when it runs on the client, its corresponding intelligence can be obtained through transfer learning, so as to reduce the requirements for client hardware running resources and avoid excessive occupation of client hardware running resources.

Various data involved in this application, unless expressly specified, can be stored remotely in a server or in a local terminal device, as long as they are suitable for being called by the technical solution of this application.

Those skilled in the art should know that although the various methods of the present application are described based on the same concept and are common to each other, these methods can all be executed independently unless otherwise specified. Similarly, the various embodiments disclosed in this application are all proposed based on the same inventive concept. Therefore, the same expressed concepts, as well as the concepts that are appropriately transformed for convenience only, although the conceptual expressions are different, should be regarded as equivalent. understand.

Unless the mutually exclusive relationship between the various embodiments to be disclosed in this application is explicitly stated, the relevant technical features involved in the various embodiments can be cross-combined to flexibly construct new embodiments, as long as such combination does not deviate from the present disclosure. The application must be creative and can meet the needs of the existing technology or solve some deficiencies in the existing technology. Those skilled in the art will be aware of modifications to this.

Please refer to Figure 1, which is a basic flow diagram of the smart contract deployment method in this embodiment.

As shown in Figure 1, it includes:

S1100. Based on the preset blockchain integrated development environment, generate the first smart contract to be deployed;

In this implementation, the first smart contract is collected through the blockchain integrated development environment. The collection method can be a smart contract generated by collecting input from peripheral devices through the blockchain integrated development environment, or it can be a blockchain integrated The development environment loads the smart contract generated by local or remote project class files.

The first smart contract specifically refers to the smart contract developed by the user and to be deployed. Only by uploading the first smart contract to each node of the blockchain can the deployment of the first smart contract be completed.

The blockchain integrated development environment is an online development environment. Users can directly launch the blockchain integrated development environment through the web page to develop smart contracts. Depending on the specific application scenario, in some implementations, the blockchain integrated development environment can also be a development toolkit installed locally.

In some implementations, the blockchain integrated development environment is a consortium chain integrated development environment exclusive to the consortium chain. Consortium chain users can use the blockchain integrated development environment to develop smart contracts online through web pages, and then, through the block chain integrated development environment, The chain integrated development environment starts the alliance chain deployment of the first smart contract.

S1200. Generate a target container for running the first smart contract, and deploy the first smart contract to the target container;

After the blockchain integrated development environment generates the first smart contract, the first smart contract needs to be deployed. The deployment method is: through the user-controlled blockchain node terminal or the temporary blockchain terminal logged into the user account, a target container for deploying the first smart contract is generated, and the target container verifies and tests the first smart contract. , upload the first smart contract to the blockchain.

In some implementations, after the blockchain integrated development environment generates the first smart contract, the node terminal starts or activates a target terminal for running the first smart contract according to the first smart contract. Head Standard containers are containers built through pre-computer programs to run smart contracts issued by block nodes. The target container can be a single specific container, or it can refer to two or more containers with the same functions depending on the application scenario.

After the target container is started, the first smart contract needs to be converted into a binary instruction file that can be read and executed by computer logic. The process of converting the first smart contract into a binary instruction file is called compilation. The compilation process can be compiled by the compiler that comes with the target container, or by the compiler associated with the target container. For example, after the target container is activated, it sends compilation instructions to the compiler associated with it, and the compiler receives the compilation instructions. Finally, compile the first smart contract. The file generated by compiling the first smart contract is a compiled file.

After generating the compiled file of the first smart contract, the compiled file needs to be converted into an image file that can be run by the target contract. The conversion process of the image file is to compile the file into a file in a set format according to the operating logic of the target container. The image file can be produced and converted through the image tool that comes with the target container, or through the image tool associated with the target container. After the image file is converted, the image file is sent to the target container, and the target container stores the image file in the container's image storage space to complete the deployment of the image file. When the target container runs the first smart contract, it only needs to read the image file from the container's image storage space and run it.

In some implementations, in order to ensure the reliability of the smart contract on the chain, the target container needs to run the first smart contract and generate the corresponding test log. If an error message appears in the test log during the test, the patch script corresponding to the error model is searched in the preset patch database according to the model of the error message. After getting the patch script, activate other target containers that are the same as the target container. These target containers are defined as trial and error containers. After the trial and error container is started, the first smart contract and the corresponding patch script are deployed to the trial and error container at the same time for running. Through the running results, it is observed whether the patch script can solve the corresponding error problem. If the same type of error does not appear in the test log of the trial and error container, it means that the patch script is useful. Otherwise, it means that the patch script cannot automatically repair the first smart contract and needs to be repaired manually. When the same type of error does not appear in the test log of the trial and error container, the target container embeds the patch script into the first smart contract according to the error report position in the test log, updates the first smart contract, and realizes the automation of the smart contract. Error repair helps improve the launch efficiency and reliability of the first smart contract.

S1300. Issue the identity certificate of the target container according to the preset node certificate;

In this implementation, each blockchain node has a node certificate indicating its legal identity. The node certificate is a certificate file issued by the blockchain accounting node, certificate management node, certification node or other node with certificate issuance function after each blockchain node is successfully registered. With the node certificate, the blockchain node can recognize the identity of the main chain, be qualified to access the main chain network, and be qualified to propagate smart contracts in the main chain network.

When a blockchain node connects to the main chain network, identity authentication is required, and when the target container connects to the main chain network, identity authentication is also required. When each target container accesses the main chain network, the blockchain node needs to perform identity authentication first, and then request the main chain network to issue a legal identity certificate to the target container, and then the target container requests identity verification.

In some implementations, in order to simplify the difficulty of obtaining the target container certificate, the identity certificate of the target container is directly issued to the target container by the blockchain node based on the node certificate.

When the first smart contract is deployed to the target container, the target container will send a certificate request to the blockchain node where it is located. After receiving the certificate request, the blockchain node will read the node certificate stored locally. The node certificate records the owner information, issuer information, certificate signature and other information of the node certificate.

Based on the node certificate, the blockchain node generates a sub-certificate of the node certificate. The sub-certificate also records owner information, issuer information, certificate signature and other information. Among them, the owner information is recorded as the target container information, and the issuer information records the certificate information of the node certificate. The blockchain node issues the generated sub-certificate to the target container. After receiving the sub-certificate, the target container uses the sub-certificate as its own identity certificate.

S1400. Call the preset container orchestrator to connect the target container to the main chain network and perform identity verification;

In this implementation, a container orchestrator is provided, and the container editor can be (not limited to): Kubernetes orchestrator, OpenShift orchestrator, Docker Swarm orchestrator, Mesos orchestrator, Google Container Engine orchestrator and other container orchestrators.

After the first smart contract and identity certificate are deployed in the target container, the first smart contract and identity certificate need to be uploaded to the main chain network. To upload the above information to the main chain network, the target container needs to call the connection interface connected to the main chain network. The container editor is used to configure the connection interface to the target container. The connection interface is the uplink interface, and the uplink interface is the API interface.

After the container orchestrator allocates an uplink interface to the target container, the target container calls the uplink interface, starts the routing link, and connects the target container to the main chain network. In some implementations, the main chain network is a consortium chain, but the main chain network can be a public chain network or a private chain network.

After the target container is connected to the main chain network through the uplink interface, the target container sends the identity certificate to the main chain network. After receiving the identity certificate sent by the target container, the main chain network verifies the identity of the target container through the preset authentication rules. verify. After the identity certificate is verified, the main chain network confirms the identity of the target container, and the target container has the identity to upload smart contracts to the main chain network. If the identity certificate verification fails, the main chain network determines that the target container has illegal access and disconnects from the target container.

S1500. After the identity verification of the target container passes, diffuse the first smart contract in the main chain network.

When the identity certificate of the target container is verified on the main chain network, the target container sends the first smart contract to the main chain network. After receiving the first smart contract, the main chain network broadcasts the first smart contract on the chain and broadcasts the first smart contract to the main chain network. The smart contract is diffused. After receiving the diffused first smart contract, other nodes in the main chain network store the first smart contract so that when receiving the task corresponding to the first smart contract, they can call the first smart contract. implement.

In the above implementation, after generating the first smart contract in the blockchain integrated development environment, the first smart contract is deployed in the target container of the node, and the target container runs the first smart contract, and obtains the identity of the node certificate issued After obtaining the certificate, the target container can access the main chain network, and spread the first smart contract on-chain through the main chain network, thereby realizing multi-node verification on the chain and improving the efficiency of verification. Through the target container and identity certificate, the unified deployment of smart contracts offline and on the chain is realized, which shortens the time limit for debugging and deployment and improves the efficiency of smart contract debugging and deployment.

In some implementations, the first smart contract is deployed to the target container in the format of an image file. S1200 includes:

S1211. Compile the first smart contract and generate a compiled file of the first smart contract;

Convert the first smart contract into a binary instruction file that can be read and executed by computer logic. The process of converting the first smart contract into a binary instruction file is called compilation. The compilation process can be compiled by the compiler that comes with the target container, or by the compiler associated with the target container. For example, after the target container is activated, it sends compilation instructions to the compiler associated with it, and the compiler receives the compilation instructions. Finally, compile the first smart contract. The file generated by compiling the first smart contract is a compiled file.

S1212. Generate the image file of the first smart contract according to the compiled file;

After generating the compiled file of the first smart contract, the compiled file needs to be converted into an image file that can be run by the target contract. The conversion process of the image file is to compile the file into a file in a set format according to the operating logic of the target container. The image file can be produced and converted through the image tool that comes with the target container, or through the image tool associated with the target container.

S1213. Start the target container according to the image file, and deploy the image file to the target container.

After the image file is converted, start or activate a target terminal for running the first smart contract. The target container is a container built by pre-computer programming to run smart contracts published by block nodes. The target container can be a single specific container, or it can refer to two or more containers with the same functions depending on the application scenario.

Send the image file to the target container, and the target container stores the image file in the container's image storage space to complete the deployment of the image file. When the target container runs the first smart contract, it only needs to read the image file from the container's image storage space and run it.

In some embodiments, the target container obtains the identity certificate through the node certificate. Specifically, S1300 includes:

S1311. Read the pre-stored node certificate and the certificate request sent by the target container;

Each blockchain node has a node certificate indicating its legal identity. The node certificate is a certificate file issued by the blockchain accounting node, certificate management node, certification node or other node with certificate issuance function after each blockchain node is successfully registered. With the node certificate, the blockchain node can recognize the identity of the main chain, be qualified to access the main chain network, and be qualified to propagate smart contracts in the main chain network.

S1312. Generate a sub-certificate of the node certificate according to the certificate request, and issue the sub-certificate to the target container as the identity certificate.

In some implementations, authentication is required after the target container is connected to the main chain network. Specifically, S1400 includes:

S1411. Call the container orchestrator to allocate an uplink port to the target container;

S1412. Connect the target container to the main chain network according to the uplink interface;

S1413. Send the identity certificate to the main chain network, so that the main chain network verifies the identity information of the target container based on the identity certificate.

In some implementations, in addition to sending the first smart contract issued by the blockchain node to the main chain network, the target container can also receive the second smart contract sent by other blockchain nodes. After receiving the second smart contract, the district Blockchain nodes need to verify the second smart contract. Specifically, after S1500 include:

S1610. The target container receives the second smart contract to be verified in the main chain network;

The target container sends the first smart contract to the main chain network, and the blockchain node can also receive the second smart contract broadcasted by the main chain network to the blockchain node through the target container. The second smart contract is a smart contract uploaded by other blockchain nodes in the blockchain. After receiving the second smart contract, the target container needs to test the second smart contract. After the test is correct, the second smart contract can be tested. Do a local deployment.

S1620. Start the verification container configured according to the second smart contract, wherein the verification container is used to run the second smart contract;

After the target container receives the second smart contract, the blockchain node where the target container is located activates the verification container capable of running the second smart contract based on the environmental parameters required for the operation of the second smart contract. The verification container is a pre-configured container used to verify smart contracts. The blockchain node where the target container is located will pre-build the verification container corresponding to each smart contract according to the existing smart contract types in the blockchain. Therefore, when the second smart contract is received, the corresponding verification container can be activated according to the type of the second smart contract.

S1630. The target container sends the second smart contract to the verification container for verification.

When the second smart contract is received by the target container and the verification container for deploying the second smart contract is activated, the target container sends the second smart contract to the verification container for verification. The verification method is: the verification container runs the second smart contract, generates a verification log during the operation, and sends the verification log to the main chain network to complete the verification of the second smart contract. The verification method in some implementations is: the second smart contract has its own running result. After the verification container runs the second smart contract, a verification result will be generated, and the verification result will be matched with the running result. If the match is successful, The verification passes, otherwise, the verification fails.

The second smart contract received by the verification container is an image file. Therefore, the second smart contract can be deployed directly in the verification container. If the second smart contract received by the target container is not an image file, the second smart contract needs to be decoded first, and then deployed after converting the decoded file of the second smart contract into an image file.

The target container forwards the second smart contract to the verification container through a third party, for example, through the container orchestrator or the master controller, which forwards the second smart contract to the verification container.

In the above implementation, the second smart contract is received through the target container to avoid the problem that the blockchain node needs to establish a connection with the main chain network when receiving the second smart contract that needs to be verified. The first smart contract can be uploaded with only one connection. The contract can also receive the second smart contract, which improves the transmission efficiency, reduces the number of times the connection interface is called, and realizes interface reuse.

In some implementations, since containers cannot perceive each other's existence and cannot interact with each other, information transmission between the target container and the verification container requires third-party information transfer, which reduces the information cost. transmission efficiency. S1630 includes:

S1631. Read the target storage address of the target container;

In order to solve the problem that information cannot be transmitted between the target container and the verification container, the storage problem of the two containers is reused to solve the information transmission barrier.

After receiving the second smart contract, read the target storage address of the target container. The target storage address is the storage space exclusive to the target container. It is configured by the blockchain node or container orchestrator when the target container is built or started.

S1632. Construct the verification storage address of the verification container according to the target storage address, and make the target storage address and the verification storage address overlap with each other;

After reading the target storage address of the target container, configure the storage address of the verification container, and configure the verification storage address of the verification container to be the same address as the target storage address. In this way, the target storage address and the verification storage address overlap with each other.

S1633. The target container stores the second smart contract in the target storage address;

After the target storage address and the verification storage address overlap each other, the target container stores the second smart contract in the target storage address.

S1634. The verification container reads the second smart contract in the verification storage address and verifies the second smart contract.

The verification container queries and verifies whether information has been written in the verification storage address through scheduled queries. When the target container stores the second smart contract in the target storage address, the verification container will query and verify that the information has been written in the verification storage address. This At this time, the verification container reads the second smart contract. After the verification container reads the second smart contract, it performs operation verification on the second smart contract.

By overlapping the target storage address and the verification storage address, the direct transfer of smart contracts between the verification container and the target container is achieved, improving the verification efficiency of the second smart contract.

In some implementations, after the verification container completes running the second smart contract, the verification log of the second smart contract needs to be uploaded to the main chain network. After S1630 includes:

S1640. After the second smart contract verification is completed, release the verification container and send a release message and verification log to the container orchestrator;

After the verification container finishes running the second smart contract, the verification container is released according to the program settings. After the verification container is released, all resources and permissions granted to the verification container are returned. Before verifying that the container is released, send release information and verification logs to the container orchestrator. Among them, the release information is to notify the container orchestrator to eliminate the coding and status monitoring of the verification container, and the verification log is the operation log generated by running the second smart contract.

S1650. The container orchestrator sends the verification log to the target container according to the release information;

After receiving the release information, the container orchestrator releases the status monitoring of the verification container, deletes the encoding information of the verification container, and then sends the verification log to the target container, which uploads the verification log to the main chain network.

S1660. The target container sends the verification log to the main chain network.

After receiving the verification log sent by the container orchestrator, the target container uploads the verification log to the main chain network. The main chain network collects the verification log to generate verification of the second smart contract by the full-link blockchain node. result. In some implementations, after the target container completes sending the verification log, the target container disconnects from the main chain network and starts the release process.

By uploading the verification log through the target container, there is no need for the verification container to be connected to the main chain network, and there is no need for the verification container to perform identity verification. This increases the upload rate of verification logs, reduces the frequency of resource usage, and saves computing resources.

In some embodiments, following S1500 includes:

S1711. Obtain the debugging interface of the first smart contract and the visual debugging icon of the first smart contract;

After the deployment of the first smart contract is completed, enter the debugging module of the blockchain integrated development environment. The debugging module has the debugging interface of the first smart contract. After entering the debugging module, the operation page of the blockchain integrated development environment is generated. Visual debugging icon of the first smart contract.

S1712. According to the debugging icon and the debugging interface, call the first smart contract in the blockchain integrated development environment for test operation.

When the user starts the debugging task of the first smart contract through the debugging icon, the debugging module calls the first smart contract through the debugging interface to perform test operation and completes the test of the first smart contract. After the deployment is completed, the first smart contract is tested in the blockchain integrated development environment based on the visual icons, which improves testing efficiency.

Please refer to Figure 2 for details. Figure 2 is a schematic diagram of the basic structure of the smart contract deployment device in this embodiment.

As shown in Figure 2, a smart contract deployment device includes: a generation module 1100, a deployment module 1200, an issuance module 1300, a processing module 1400 and an execution module 1500. The generation module 1100 is used to generate the first smart contract to be deployed based on the preset blockchain integrated development environment; the deployment module 1200 is used to generate a target container for running the first smart contract, and transfer the first smart contract to Deployed to the target container; the issuance module 1300 is used to issue the identity certificate of the target container according to the preset node certificate; the processing module 1400 is used to call the preset container orchestrator to connect the target container to the main chain In the network, identity verification is performed; the execution module 1500 is used to diffuse the first smart contract in the main chain network after the identity verification of the target container passes.

After generating the first smart contract in the blockchain integrated development environment, deploy the first smart contract in the node In the target container of the node, the target container runs the first smart contract, and after obtaining the identity certificate issued by the node certificate, the target container can access the main chain network, and run the first smart contract through the main chain network. Diffusion on the chain enables multi-node verification on the chain and improves the efficiency of verification. Through the target container and identity certificate, the unified deployment of smart contracts offline and on the chain is realized, which shortens the time limit for debugging and deployment and improves the efficiency of smart contract debugging and deployment.

Optionally, the smart contract deployment device also includes:

The first processing sub-module is used to compile the first smart contract and generate the compiled file of the first smart contract;

The first compilation submodule is used to generate the image file of the first smart contract according to the compilation file;

The first execution sub-module is used to start the target container according to the image file and deploy the image file to the target container.

Optionally, the smart contract deployment device also includes:

The second processing submodule is used to read the pre-stored node certificate and the certificate request sent by the target container;

The second execution sub-module is configured to generate a sub-certificate of the node certificate according to the certificate request, and issue the sub-certificate to the target container as the identity certificate.

Optionally, the smart contract deployment device also includes:

The first calling sub-module is used to call the container orchestrator to allocate an uplink interface to the target container;

The third processing sub-module is used to connect the target container to the main chain network according to the uplink interface;

The third execution sub-module is used to send the identity certificate to the main chain network, so that the main chain network verifies the identity information of the target container based on the identity certificate.

Optionally, the smart contract deployment device also includes:

The first receiving sub-module is used by the target container to receive the second smart contract to be verified in the main chain network;

The fourth processing sub-module is used to start the verification container configured according to the second smart contract, wherein the verification container is used to run the second smart contract;

The fourth execution sub-module is used by the target container to send the second smart contract to the verification container for verification.

Optionally, the smart contract deployment device also includes:

The second reading sub-module is used to read the target storage address of the target container;

A first storage submodule configured to construct a verification storage address of the verification container according to the target storage address, and make the target storage address and the verification storage address overlap with each other;

The fifth processing sub-module is used for the target container to store the second smart contract in the target storage address;

The fifth execution sub-module is used for the verification container to read the second smart contract in the verification storage address and verify the second smart contract.

Optionally, the smart contract deployment device also includes:

The first release submodule is used to release the verification container after the verification of the second smart contract is completed, and send a release message and verification log to the container orchestrator;

The sixth processing sub-module is used for the container orchestrator to send the verification log to the target container according to the release information;

The sixth execution sub-module is used for the target container to send the verification log to the main chain network.

Optionally, the smart contract deployment device also includes:

The seventh processing sub-module is used to obtain the debugging interface of the first smart contract and the visual debugging icon of the first smart contract;

The seventh execution sub-module is used to call the first smart contract in the blockchain integrated development environment for test operation according to the debugging icon and the debugging interface.

In order to solve the above technical problems, embodiments of the present application also provide computer equipment. Please refer to Figure 3 for details. Figure 3 is a basic structural block diagram of the computer equipment in this embodiment.

As shown in Figure 3, a schematic diagram of the internal structure of computer equipment. The computer device includes a processor, non-volatile storage media, memory and a network interface connected by a system bus. Among them, the non-volatile storage medium of the computer device stores an operating system, a database and computer-readable instructions. The database can store a sequence of control information. When the computer-readable instructions are executed by the processor, the processor can achieve a A smart contract deployment method. The processor of the computer device is used to provide computing and control capabilities to support the operation of the entire computer device. Computer readable instructions may be stored in the memory of the computer device, and when executed by the processor, the computer readable instructions may cause the processor to execute a smart contract deployment method. The network interface of the computer device is used for communication with the terminal connection. Those skilled in the art can understand that the structure shown in Figure 3 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied. The specific computer equipment can May include more or fewer parts than shown, or combine certain parts, or have a different arrangement of parts.

In this embodiment, the processor is used to execute the specific functions of the generation module 1100, the deployment module 1200, the issuance module 1300, the processing module 1400 and the execution module 1500 in Figure 2, and the memory stores program codes and various data required to execute the above modules. Network interfaces are used for data transmission to user terminals or between servers. The memory in this embodiment stores the program code and data required to execute all sub-modules in the smart contract deployment device, and the server can call the server's program code and data to execute the functions of all sub-modules.

After the computer device generates the first smart contract in the blockchain integrated development environment, it deploys the first smart contract in the target container of the node, and the target container runs the first smart contract, and obtains the identity certificate issued by the node certificate. Finally, the target container can be connected to the main chain network, and the first smart contract is diffused on the chain through the main chain network, thereby realizing multi-node verification on the chain and improving the efficiency of verification. Through the target container and identity certificate, the unified deployment of smart contracts offline and on the chain is realized, which shortens the time limit for debugging and deployment and improves the efficiency of smart contract debugging and deployment.

This application also provides a storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, they cause the one or more processors to execute the steps of the smart contract deployment method of any of the above embodiments.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. The program can be stored in a computer-readable storage medium. When executed, the flow of the above method embodiments may be included. Procedure. Among them, the aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM).

Those skilled in the art can understand that the steps, measures, and solutions in the various operations, methods, and processes that have been discussed in this application can be alternated, changed, combined, or deleted. Furthermore, other steps, measures, and solutions in the various operations, methods, and processes that have been discussed in this application can also be alternated, changed, rearranged, decomposed, combined, or deleted. Furthermore, the steps, measures, and solutions in the prior art with various operations, methods, and processes disclosed in this application can also be replaced, changed, rearranged, decomposed, combined, or deleted.

The above are only some of the embodiments of the present application. It should be pointed out that those of ordinary skill in the technical field can also make several improvements and modifications without departing from the principles of the present application. These improvements and modifications can also be made. should be regarded as the scope of protection of this application.

Claims

A smart contract deployment method, including:

Based on the preset blockchain integrated development environment, generate the first smart contract to be deployed;

Generate a target container that runs the first smart contract, and deploy the first smart contract to the target container;

Issue the identity certificate of the target container according to the preset node certificate;

Call the preset container orchestrator to connect the target container to the main chain network for identity verification;

When the identity verification of the target container passes, the first smart contract is diffused in the main chain network.
The smart contract deployment method according to claim 1, wherein generating a target container for running the first smart contract and deploying the first smart contract to the target container includes:

Compile the first smart contract and generate a compiled file of the first smart contract;

Generate an image file of the first smart contract according to the compiled file;

Start the target container according to the image file, and deploy the image file to the target container.
The smart contract deployment method according to claim 1, wherein the issuance of the identity certificate of the target container according to the preset node certificate includes:

Read the pre-stored node certificate and the certificate request sent by the target container;

Generate a subcertificate of the node certificate according to the certificate request, and issue the subcertificate to the target container as the identity certificate.
The smart contract deployment method according to claim 1, wherein said calling a preset container orchestrator to connect the target container to the main chain network and performing identity verification includes:

Call the container orchestrator to allocate an uplink port to the target container;

Connect the target container to the main chain network according to the uplink interface;

The identity certificate is sent to the main chain network, so that the main chain network verifies the identity information of the target container according to the identity certificate.
The smart contract deployment method according to claim 1, wherein after the identity verification of the target container is passed, after the first smart contract is diffused in the main chain network, the method includes:

The target container receives the second smart contract to be verified in the main chain network;

Start a verification container configured according to the second smart contract, wherein the verification container is used to run the second smart contract;

The target container sends the second smart contract to the verification container for verification.
The smart contract deployment method according to claim 5, wherein the target container sending the second smart contract to the verification container for verification includes:

Read the target storage address of the target container;

Construct the verification storage address of the verification container according to the target storage address, and make the target storage address and the verification storage address overlap with each other;

The target container stores the second smart contract in the target storage address;

The verification container reads the second smart contract in the verification storage address and verifies the second smart contract. The contract can be verified.
The smart contract deployment method according to claim 5, wherein after the target container sends the second smart contract to the verification container for verification, it includes:

When the second smart contract verification is completed, release the verification container and send a release message and verification log to the container orchestrator;

The container orchestrator sends the verification log to the target container according to the release information;

The target container sends the verification log to the main chain network.
The smart contract deployment method according to claim 1, wherein after the identity verification of the target container is passed, after the first smart contract is diffused in the main chain network, the method includes:

Obtain the debugging interface of the first smart contract and the visual debugging icon of the first smart contract;

According to the debugging icon and the debugging interface, the first smart contract is called in the blockchain integrated development environment for test operation.
A smart contract deployment device, including:

The generation module is used to generate the first smart contract to be deployed based on the preset blockchain integrated development environment;

A deployment module, configured to generate a target container for running the first smart contract, and deploy the first smart contract into the target container;

An issuance module, used to issue the identity certificate of the target container according to the preset node certificate;

The processing module is used to call the preset container orchestrator to connect the target container to the main chain network for identity verification;

An execution module, configured to diffuse the first smart contract in the main chain network after the identity verification of the target container passes.
A computer device includes a memory and a processor. Computer-readable instructions are stored in the memory. When the computer-readable instructions are executed by the processor, they cause the processor to perform the following steps:

Based on the preset blockchain integrated development environment, generate the first smart contract to be deployed;

Generate a target container that runs the first smart contract, and deploy the first smart contract into the target container;

Issue the identity certificate of the target container according to the preset node certificate;

Call the preset container orchestrator to connect the target container to the main chain network for identity verification;

When the identity verification of the target container passes, the first smart contract is diffused in the main chain network.
The computer device of claim 10, wherein the processor further performs the following steps:

Generating a target container for running the first smart contract and deploying the first smart contract to the target container includes:

Compile the first smart contract and generate a compiled file of the first smart contract;

Generate an image file of the first smart contract according to the compiled file;

Start the target container according to the image file, and deploy the image file to the target container.
The computer device of claim 10, wherein the processor further performs the following steps:

The issuance of the identity certificate of the target container according to the preset node certificate includes:

Read the pre-stored node certificate and the certificate request sent by the target container;

Generate a subcertificate of the node certificate according to the certificate request, and issue the subcertificate to the target container as the identity certificate.
The computer device of claim 10, wherein the processor further performs the following steps:

The calling of the preset container orchestrator to connect the target container to the main chain network and identity verification include:

Call the container orchestrator to allocate an uplink port to the target container;

Connect the target container to the main chain network according to the uplink interface;

The identity certificate is sent to the main chain network, so that the main chain network verifies the identity information of the target container according to the identity certificate.
The computer device of claim 10, wherein the processor further performs the following steps:

After the identity verification of the target container passes, the first smart contract is diffused in the main chain network, including:

The target container receives the second smart contract to be verified in the main chain network;

Start a verification container configured according to the second smart contract, wherein the verification container is used to run the second smart contract;

The target container sends the second smart contract to the verification container for verification.
The computer device of claim 14, wherein the processor further performs the following steps:

The target container sends the second smart contract to the verification container for verification including:

Read the target storage address of the target container;

Construct the verification storage address of the verification container according to the target storage address, and make the target storage address and the verification storage address overlap with each other;

The target container stores the second smart contract in the target storage address;

The verification container reads the second smart contract in the verification storage address and verifies the second smart contract.
The computer device of claim 14, wherein the processor further performs the following steps:

After the target container sends the second smart contract to the verification container for verification, it includes:

When the second smart contract verification is completed, release the verification container and send a release message and verification log to the container orchestrator;

The container orchestrator sends the verification log to the target container according to the release information;

The target container sends the verification log to the main chain network.
The computer device of claim 10, wherein the processor further performs the following steps:

After the identity verification of the target container passes, the first smart contract is diffused in the main chain network, including:

Obtain the debugging interface of the first smart contract and the visual debugging icon of the first smart contract;

According to the debugging icon and the debugging interface, the first smart contract is called in the blockchain integrated development environment for test operation.
A storage medium storing computer-readable instructions that, when executed by one or more processors, causes one or more processors to perform the following steps:

Based on the preset blockchain integrated development environment, generate the first smart contract to be deployed;

Generate a target container that runs the first smart contract, and deploy the first smart contract into the target container;

Issue the identity certificate of the target container according to the preset node certificate;

Call the preset container orchestrator to connect the target container to the main chain network for identity verification;

When the identity verification of the target container passes, the first smart contract is diffused in the main chain network.
The storage medium of claim 18, wherein the one or more processors are further configured to perform the following steps:

Generating a target container for running the first smart contract and deploying the first smart contract to the target container includes:

Compile the first smart contract and generate a compiled file of the first smart contract;

Generate an image file of the first smart contract according to the compiled file;

Start the target container according to the image file, and deploy the image file to the target container.
The storage medium of claim 18, wherein the one or more processors are further configured to perform the following steps:

The issuance of the identity certificate of the target container according to the preset node certificate includes:

Read the pre-stored node certificate and the certificate request sent by the target container;

Generate a subcertificate of the node certificate according to the certificate request, and issue the subcertificate to the target container as the identity certificate.