CN115203330B - Intelligent contract deployment method and device, equipment, medium and product thereof - Google Patents
Intelligent contract deployment method and device, equipment, medium and product thereof Download PDFInfo
- Publication number
- CN115203330B CN115203330B CN202210862683.6A CN202210862683A CN115203330B CN 115203330 B CN115203330 B CN 115203330B CN 202210862683 A CN202210862683 A CN 202210862683A CN 115203330 B CN115203330 B CN 115203330B
- Authority
- CN
- China
- Prior art keywords
- target container
- container
- intelligent contract
- verification
- certificate
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000012795 verification Methods 0.000 claims abstract description 162
- 238000011161 development Methods 0.000 claims abstract description 33
- 238000012545 processing Methods 0.000 claims description 23
- 238000012360 testing method Methods 0.000 claims description 19
- 230000008569 process Effects 0.000 description 11
- 230000006870 function Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 238000006243 chemical reaction Methods 0.000 description 4
- 238000004590 computer program Methods 0.000 description 4
- 238000012797 qualification Methods 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 238000009792 diffusion process Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000003062 neural network model Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000001902 propagating effect Effects 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000004888 barrier function Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/44—Program or device authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/658—Incremental updates; Differential updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
Abstract
The application discloses an intelligent contract deployment method, an intelligent contract deployment device, computer equipment and a storage medium, wherein the intelligent contract deployment method comprises the following steps: generating a first intelligent contract to be deployed based on a preset blockchain integrated development environment; generating a target container running the first intelligent contract, and deploying the first intelligent contract into the target container; issuing an identity certificate of the target container according to a preset node certificate; invoking a preset container orchestrator to access the target container into a main chain network for identity verification; and diffusing the first intelligent contract in the main chain network after the identity verification of the target container is passed. The unified deployment of intelligent contracts under line and on chain is realized through the target container and the identity certificate, the time limit of debugging deployment is shortened, and the efficiency of intelligent contract debugging deployment is improved.
Description
Technical Field
The invention relates to the field of alliance chains, in particular to an intelligent contract deployment method and system and a computer storage medium.
Background
The alliance chain only aims at members of a specific group and limited third parties, a plurality of preselected nodes are internally designated as billing people, the generation of each block is jointly determined by all preselected nodes, other access nodes can participate in transactions, but no accounting process is needed, and other third parties can perform limited inquiry through an API (application program interface) opened by the blockchain.
The inventor of the invention discovers in the research that the writing of the intelligent contracts of the alliance chains is that the writing is finished off-line, the intelligent contracts are respectively deployed to the block chain nodes controlled by the inventor, and then the intelligent contracts are debugged according to the intelligent contract logs. According to the deployment debugging method, intelligent contracts can only be debugged based on the block chain nodes of the entity, the process is time-consuming and labor-consuming, and the efficiency is low.
Disclosure of Invention
The invention aims to provide an intelligent contract deployment method, an intelligent contract deployment system and a computer storage medium, which are used for at least solving the problem of low deployment efficiency of the existing alliance chain.
In order to solve the technical problems, the invention provides an intelligent contract deployment method, which comprises the following steps:
generating a first intelligent contract to be deployed based on a preset blockchain integrated development environment;
generating a target container running the first intelligent contract, and deploying the first intelligent contract into the target container;
issuing an identity certificate of the target container according to a preset node certificate;
invoking a preset container orchestrator to access the target container into a main chain network for identity verification;
and diffusing the first intelligent contract in the main chain network after the identity verification of the target container is passed.
Optionally, the generating a target container running the first smart contract and deploying the first smart contract into the target container includes:
compiling the first intelligent contract to generate a compiling file of the first intelligent contract;
generating an image file of the first intelligent contract according to the compiling file;
and starting the target container according to the image file, and deploying the image file into the target container.
Optionally, the issuing the identity certificate of the target container according to the preset node certificate includes:
reading a prestored node certificate and a certificate request sent by the target container;
generating a sub-certificate of the node certificate according to the certificate request, and issuing the sub-certificate as the identity certificate to the target container.
Optionally, the calling a preset container composer to access the target container to a main network, and performing identity verification includes:
invoking the container orchestrator to allocate a ul interface for the target container;
connecting the target container to a backbone network according to the uplink interface;
the identity certificate occurs to the main chain network, so that the main chain network verifies the identity information of the target container according to the identity certificate.
Optionally, after the first smart contract is diffused in the backbone network after the authentication of the target container is passed, the method includes:
the target container receives a second intelligent contract to be verified in the main network;
starting a set verification container according to the second intelligent contract, wherein the verification container is used for running the second intelligent contract;
the target container sends the second intelligent contract to the verification container for verification.
Optionally, the target container sending the second smart contract to the verification container for verification includes:
reading a target storage address of the target container;
constructing a verification storage address of the verification container according to the target storage address, and overlapping the target storage address and the verification storage address;
the target container storing the second smart contract in the target storage address;
the verification container reads a second smart contract in the verification storage address and verifies the second smart contract.
Optionally, after the target container sends the second smart contract to the verification container for verification, the target container includes:
Releasing the verification container after the second intelligent contract is verified, and sending a release message and a verification log to the container composer;
the container composer sends the verification log to the target container according to the release information;
the target container sends the verification log to the backbone network.
Optionally, acquiring a debug interface of the first intelligent contract and a debug icon of the first intelligent contract visualization;
and calling the first intelligent contract in the blockchain integrated development environment to perform test operation according to the debugging icon and the debugging interface.
In order to solve the above technical problem, an embodiment of the present invention further provides an intelligent contract deployment apparatus, including:
the generation module is used for generating a first intelligent contract to be deployed based on a preset blockchain integrated development environment;
the deployment module is used for generating a target container for running the first intelligent contract and deploying the first intelligent contract into the target container;
the issuing module is used for issuing the identity certificate of the target container according to a preset node certificate;
the processing module is used for calling a preset container composer to access the target container into a main chain network for identity verification;
And the execution module is used for diffusing the first intelligent contract in the main chain network after the identity verification of the target container is passed.
Optionally, the smart contract deployment apparatus further includes:
the first processing sub-module is used for compiling the first intelligent contract to generate a compiling file of the first intelligent contract;
the first compiling sub-module is used for generating an image file of the first intelligent contract according to the compiling file;
and the first execution sub-module is used for starting the target container according to the image file and deploying the image file into the target container.
Optionally, the smart contract deployment apparatus further includes:
the second processing sub-module is used for reading the prestored node certificate and the certificate request sent by the target container;
and the second execution sub-module is used for generating a sub-certificate of the node certificate according to the certificate request and issuing the sub-certificate to the target container as the identity certificate.
Optionally, the smart contract deployment apparatus further includes:
the first calling sub-module is used for calling the container orchestrator to allocate a uplink interface for the target container;
A third processing sub-module for connecting the target container to a backbone network according to the uplink interface;
and the third execution sub-module is used for generating the identity certificate to the main chain network so that the main chain network can verify the identity information of the target container according to the identity certificate.
Optionally, the smart contract deployment apparatus further includes:
a first receiving sub-module, configured to receive, by the target container, a second smart contract to be verified in the backbone network;
a fourth processing sub-module for starting a verification container set according to the second smart contract, wherein the verification container is used for running the second smart contract;
and the fourth execution sub-module is used for sending the second intelligent contract to the verification container by the target container for verification.
Optionally, the smart contract deployment apparatus further includes:
the second reading submodule is used for reading the target storage address of the target container;
the first storage sub-module is used for constructing a verification storage address of the verification container according to the target storage address and enabling the target storage address and the verification storage address to be overlapped with each other;
A fifth processing sub-module for the target container to store the second smart contract in the target storage address;
and the fifth execution sub-module is used for reading the second intelligent contract in the verification storage address by the verification container and verifying the second intelligent contract.
Optionally, the smart contract deployment apparatus further includes:
the first release sub-module is used for releasing the verification container after the second intelligent contract is verified, and sending a release message and a verification log to the container composer;
a sixth processing sub-module, configured to send the verification log to the target container according to the release information by the container composer;
and a sixth execution sub-module, configured to send the verification log to the backbone network by using the target container.
Optionally, the smart contract deployment apparatus further includes:
a seventh processing sub-module, configured to obtain a debug interface of the first smart contract and a debug icon visualized by the first smart contract;
and the seventh execution sub-module is used for calling the first intelligent contract in the blockchain integrated development environment to perform test operation according to the debugging icon and the debugging interface.
In order to solve the above technical problem, an embodiment of the present invention further provides a computer device, including a memory and a processor, where the memory stores computer readable instructions, and when the computer readable instructions are executed by the processor, the processor is caused to execute the steps of the above intelligent contract deployment method.
To solve the above technical problem, an embodiment of the present invention further provides a storage medium storing computer readable instructions, where the computer readable instructions when executed by one or more processors cause the one or more processors to execute the steps of the above intelligent contract deployment method.
The beneficial effects of the invention are: after a first intelligent contract is generated in the blockchain integrated development environment, the first intelligent contract is deployed in a target container of a node, the target container operates the first intelligent contract, after an identity card issued by a node certificate is obtained, the target container can be accessed into a main chain network, and the first intelligent contract is subjected to on-chain diffusion propagation through the main chain network, so that on-chain multi-node verification is realized, and the verification efficiency is improved. The unified deployment of intelligent contracts under line and on chain is realized through the target container and the identity certificate, the time limit of debugging deployment is shortened, and the efficiency of intelligent contract debugging deployment is improved.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:
FIG. 1 is a basic flow diagram of a smart contract deployment method according to one embodiment of the present application;
FIG. 2 is a schematic diagram of the basic structure of an intelligent contract deployment apparatus according to one embodiment of the present application;
fig. 3 is a basic structural block diagram of a computer device according to an embodiment of the present application.
Detailed Description
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals refer to the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the drawings are exemplary only for the purpose of illustrating the present application and are not to be construed as limiting the present application.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless expressly stated otherwise, as understood by those skilled in the art. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude 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 all terms (including technical 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 unless defined otherwise. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
As will be appreciated by those skilled in the art, a "terminal" as used herein includes both devices of a wireless signal receiver that have only wireless signal receivers without transmitting capabilities and devices of receiving and transmitting hardware that have devices capable of performing two-way communications over a two-way communications link. Such a device may include: a cellular or other communication device having a single-line display or a multi-line display or a cellular or other communication device without a multi-line display; a PCS (Personal Communications Service, personal communication system) that may combine voice, data processing, facsimile and/or data communication capabilities; a PDA (Personal Digital Assistant ) that can include a radio frequency receiver, pager, internet/intranet access, web browser, notepad, calendar and/or GPS (Global Positioning System ) receiver; a conventional laptop and/or palmtop computer or other appliance that has and/or includes a radio frequency receiver. As used herein, a "terminal" may be portable, transportable, installed in a vehicle (aeronautical, maritime, and/or land-based), or adapted and/or configured to operate locally and/or in a distributed fashion, to operate at any other location(s) on earth and/or in space. The "terminal" used herein may also be a communication terminal, a network access terminal, a music/video playing terminal, for example, a PDA, a MID (Mobile Internet Device ) and/or a mobile phone with music/video playing function, and may also be a smart tv, a set-top box, etc.
The hardware referred to by the names "server", "client", "service node" and the like in the present application is essentially an electronic device having the performance of a personal computer, and is a hardware device having necessary components disclosed by von neumann's principle, such as a central processing unit (including an arithmetic unit and a controller), a memory, an input device, and an output device, and a computer program is stored in the memory, and the central processing unit calls the program stored in the external memory to run in the memory, executes instructions in the program, and interacts with the input/output device, thereby completing a specific function.
It should be noted that the concept of "server" as referred to in this application is equally applicable to the case of a server farm. The servers should be logically partitioned, physically separate from each other but interface-callable, or integrated into a physical computer or group of computers, according to network deployment principles understood by those skilled in the art. Those skilled in the art will appreciate this variation and should not be construed as limiting the implementation of the network deployment approach of the present application.
One or several technical features of the present application, unless specified in the plain text, may be deployed either on a server to implement access by remotely invoking an online service interface provided by the acquisition server by a client, or directly deployed and run on the client to implement access.
The neural network model cited or possibly cited in the application can be deployed on a remote server and used for implementing remote call on a client, or can be deployed on a client with sufficient equipment capability for direct call unless specified in a clear text, and in some embodiments, when the neural network model runs on the client, the corresponding intelligence can be obtained through migration learning so as to reduce the requirement on the running resources of the hardware of the client and avoid excessively occupying the running resources of the hardware of the client.
The various data referred to in the present application, unless specified in the plain text, may be stored either remotely in a server or in a local terminal device, as long as it is suitable for being invoked by the technical solution of the present application.
Those skilled in the art will appreciate that: although the various methods of the present application are described based on the same concepts so as to be common to each other, the methods may be performed independently, unless otherwise indicated. Similarly, for each of the embodiments disclosed herein, the concepts presented are based on the same inventive concept, and thus, the concepts presented for the same description, and concepts that are merely convenient and appropriately altered although they are different, should be equally understood.
The various embodiments to be disclosed herein, unless the plain text indicates a mutually exclusive relationship with each other, the technical features related to the various embodiments may be cross-combined to flexibly construct a new embodiment, so long as such combination does not depart from the inventive spirit of the present application and can satisfy the needs in the art or solve the deficiencies in the prior art. This variant will be known to the person skilled in the art.
Referring to fig. 1, fig. 1 is a basic flow chart of an intelligent contract deployment method according to the present embodiment.
As shown in fig. 1, includes:
s1100, generating a first intelligent contract to be deployed based on a preset blockchain integrated development environment;
in this embodiment, the first intelligent contract is collected by the blockchain integrated development environment, and the collection mode can be an intelligent contract generated by collecting the input of the peripheral equipment through the blockchain integrated development environment, or an intelligent contract generated by loading a local or remote engineering file through the blockchain integrated development environment.
The first smart contract is specifically a smart contract to be deployed, which is developed by a user, and deployment of the first smart contract can be completed only by uploading the first smart contract to each node of the blockchain.
The blockchain integrated development environment is an online development environment, and a user can directly start the blockchain integrated development environment through a webpage to develop intelligent contracts. Depending on the particular application scenario, in some embodiments, the blockchain integrated development environment can also be a locally installed development kit.
In some embodiments, the blockchain integrated development environment is a blockchain-specific blockchain integrated development environment, and the blockchain user is able to develop the smart contract through the webpage on-line by the blockchain integrated development environment, and then initiate the blockchain deployment of the first smart contract through the blockchain integrated development environment.
S1200, generating a target container for running the first intelligent contract, and deploying the first intelligent contract into the target container;
after the blockchain integrated development environment generates the first smart contract, the first smart contract needs to be deployed. The deployment mode is as follows: and generating a target container for deploying the first intelligent contract by controlling the block chain link point terminal or the temporary block chain terminal logging in the user account by a user, and uploading the first intelligent contract to the block chain after verifying and testing the first intelligent contract by the target container.
In some embodiments, after the blockchain integrated development environment generates the first smart contract, the node terminal initiates or activates a target terminal for running the first smart contract according to the first smart contract. The target container is a container constructed by a pre-computer program for running intelligent contracts issued by block nodes. The target container can be a single specific container, or can refer to two or more containers with the same function according to different application scenes.
After the target container is started, a binary instruction file capable of being read and executed by computer logic needs to be performed on the first smart contract, and the process of converting the first smart contract into the binary instruction file is called compiling. The compiling process can be compiled by a compiler of the target container, and also can be compiled by a compiler associated with the target container, for example, after the target container is activated, a compiling instruction is sent to the compiler associated with the target container, and after the compiler receives the compiling instruction, the first intelligent contract is compiled. The file generated by compiling the first intelligent contract is a compiled file.
After the compiled file of the first smart contract is generated, the compiled file needs to be converted into an image file that can be run by the target contract. The conversion process of the mirror image file is to compile the file according to the running logic of the target container and the file manufactured according to the set format. The creation of the image file can be converted by the image tool carried by the target container or by an image tool associated with the target container. After the mirror image file is obtained through conversion, the mirror image file is sent to a target container, and the target container stores the mirror image file in a mirror image storage space of the container, so that deployment of the mirror image file is completed. When the target container runs the first intelligent contract, the image file is only required to be read from the image storage space of the container and run.
In some embodiments, to ensure the reliability of the uplink smart contract, the target container needs to run the first smart contract and generate a corresponding test log. If error reporting information appears in the test log in the test process, searching a patch script corresponding to the error reporting model in a preset patch database according to the model of the error reporting information. After the patch script is obtained, other target containers identical to the target container are activated, and the target containers are defined as error-checking containers. After the error testing container is started, the first intelligent contract and the corresponding patch script are deployed into the error testing container for operation, and whether the patch script can solve the corresponding error reporting problem is observed according to an operation result. If errors of the same model are not reported in the test logs of the error testing container, the patch script is useful, otherwise, the patch script cannot automatically repair the first intelligent contract and needs to be repaired manually. When the test logs of the error test container do not have errors of the same model, the target container embeds the patch script into the first intelligent contract according to the error report positions in the test logs, updates the first intelligent contract, realizes automatic error report repair of the intelligent contract, and is beneficial to improving the online efficiency and reliability of the first intelligent contract.
S1300, issuing an identity certificate of the target container according to a preset node certificate;
in this embodiment, each blockchain node has a node certificate indicating its legal identity. The node certificate is a certificate file issued to each blockchain node after each blockchain node is successfully registered by a billing node, a certificate management node, an authentication node or other nodes with a certificate issuing function. With the node certificate, the blockchain point can be recognized by the identity of the main chain, and has the qualification of accessing the main chain network and the qualification of propagating intelligent contracts in the main chain network.
When the block chain link point is connected to the main chain network, identity authentication is needed, and when the target container is connected to the main chain network, identity authentication is also needed. When each target container is accessed to the main network, the block chain link point is required to carry out identity authentication, then the main network is required to issue legal identity certificates to the target containers, and then the target containers are required to carry out identity authentication.
In some embodiments, to simplify the difficulty of obtaining the target container certificate, the identity certificate of the target container is issued by the block link point directly to the target container based on the node certificate.
After deploying the first smart contract to the target container, the target container sends a certificate request to the blockchain node where it resides. After receiving the certificate request, the blockchain node reads a locally stored node certificate, and the node certificate records information such as owner information, issuer information, certificate signature and the like of the node certificate.
A sub-certificate of the node certificate is generated based on the node certificate block link point, and information such as owner information, issuer information, certificate signature and the like is recorded in the sub-certificate. Wherein the owner information is recorded as target container information, and the issuer information is recorded as certificate information of the node certificate. The block chain link points issue the generated sub-certificate to the target container, and the target container takes the sub-certificate as an own identity certificate after receiving the sub-certificate.
S1400, calling a preset container composer to access the target container into a main chain network for identity verification;
in this embodiment, a container editor is provided, and the container editor may be (but is not limited to): container organizers such as Kubernetes orchestrator, openShift orchestrator, docker switch orchestrator, mesos orchestrator, google Container Engine orchestrator, and the like.
After the target container deploys the first intelligent contract and the identity certificate, the first intelligent contract and the identity certificate need to be uploaded into the main network. The target container uploads the information to the backbone network, and calls a connection interface connected to the backbone network. The container editor is used for configuring a connection interface to the target container, wherein the connection interface is a uplink interface, and the uplink interface is an API interface.
After the container orchestrator allocates a ul interface to the target container, the target container invokes the ul interface, initiates a routing link, and connects the target container to the backbone network. In some embodiments, the backbone network is a federated chain, however, the backbone network can be a public or private chain network.
After the target container is connected with the main chain network through the upper link port, the identity certificate is sent to the main chain network by the target container, and after the main chain network receives the identity certificate sent by the target container, the identity of the target container is verified through a preset identity verification rule. After the identity certificate passes the verification, the main network confirms the identity of the target container, and the target container has the identity of uploading the intelligent contract to the main network. If the identity certificate is not verified, the main network determines that the target container is illegally accessed and the connection with the target container is disconnected.
S1500, diffusing the first intelligent contract in the main chain network after the identity verification of the target container is passed.
When the identity certificate of the target container passes the verification of the main network, the target container sends a first intelligent contract to the main network, the main network receives the first intelligent contract, broadcasts the first intelligent contract in a chain, diffuses the first intelligent contract, and other nodes in the main network store the first intelligent contract after receiving the diffused first intelligent contract so as to call the first intelligent contract to execute when receiving a task corresponding to the first intelligent contract.
According to the embodiment, after the first intelligent contract is generated in the blockchain integrated development environment, the first intelligent contract is deployed in the target container of the node, the target container operates the first intelligent contract, after the identity card issued by the node certificate is obtained, the target container can be accessed into the main chain network, and the first intelligent contract is spread and propagated on the chain through the main chain network, so that on-chain multi-node verification is realized, and the verification efficiency is improved. The unified deployment of intelligent contracts under line and on chain is realized through the target container and the identity certificate, the time limit of debugging deployment is shortened, and the efficiency of intelligent contract debugging deployment is improved.
In some implementations, the first smart contract is deployed into the target container in the format of an image file. S1200 includes:
s1211, compiling the first intelligent contract to generate a compiling file of the first intelligent contract;
the process of converting a first smart contract into a binary instruction file, which can be read and executed by computer logic, is referred to as compiling, is performed on the first smart contract. The compiling process can be compiled by a compiler of the target container, and also can be compiled by a compiler associated with the target container, for example, after the target container is activated, a compiling instruction is sent to the compiler associated with the target container, and after the compiler receives the compiling instruction, the first intelligent contract is compiled. The file generated by compiling the first intelligent contract is a compiled file.
S1212, generating an image file of the first intelligent contract according to the compiled file;
after the compiled file of the first smart contract is generated, the compiled file needs to be converted into an image file that can be run by the target contract. The conversion process of the mirror image file is to compile the file according to the running logic of the target container and the file manufactured according to the set format. The creation of the image file can be converted by the image tool carried by the target container or by an image tool associated with the target container.
S1213, starting the target container according to the image file, and deploying the image file into the target container.
After the conversion to the image file, a target terminal for running the first smart contract is started or activated. The target container is a container constructed by a pre-computer program for running intelligent contracts issued by block nodes. The target container can be a single specific container, or can refer to two or more containers with the same function according to different application scenes.
And sending the image file to a target container, and storing the image file in an image storage space of the container by the target container to finish the deployment of the image file. When the target container runs the first intelligent contract, the image file is only required to be read from the image storage space of the container and run.
In some embodiments, the target container obtains the identity certificate through the node certificate. Specifically, S1300 includes:
s1311, reading a prestored node certificate and a certificate request sent by the target container;
each blockchain node has a node certificate thereon that indicates its legal identity. The node certificate is a certificate file issued to each blockchain node after each blockchain node is successfully registered by a billing node, a certificate management node, an authentication node or other nodes with a certificate issuing function. With the node certificate, the blockchain point can be recognized by the identity of the main chain, and has the qualification of accessing the main chain network and the qualification of propagating intelligent contracts in the main chain network.
S1312, generating a sub-certificate of the node certificate according to the certificate request, and issuing the sub-certificate as the identity certificate to the target container.
After deploying the first smart contract to the target container, the target container sends a certificate request to the blockchain node where it resides. After receiving the certificate request, the blockchain node reads a locally stored node certificate, and the node certificate records information such as owner information, issuer information, certificate signature and the like of the node certificate.
A sub-certificate of the node certificate is generated based on the node certificate block link point, and information such as owner information, issuer information, certificate signature and the like is recorded in the sub-certificate. Wherein the owner information is recorded as target container information, and the issuer information is recorded as certificate information of the node certificate. The block chain link points issue the generated sub-certificate to the target container, and the target container takes the sub-certificate as an own identity certificate after receiving the sub-certificate.
In some embodiments, authentication is required after the target container is connected to the backbone network. Specifically, S1400 includes:
s1411, calling the container orchestrator to allocate a uplink interface for the target container;
After the target container deploys the first intelligent contract and the identity certificate, the first intelligent contract and the identity certificate need to be uploaded into the main network. The target container uploads the information to the backbone network, and calls a connection interface connected to the backbone network. The container editor is used for configuring a connection interface to the target container, wherein the connection interface is a uplink interface, and the uplink interface is an API interface.
S1412, connecting the target container to a backbone network according to the ul interface;
after the container orchestrator allocates a ul interface to the target container, the target container invokes the ul interface, initiates a routing link, and connects the target container to the backbone network. In some embodiments, the backbone network is a federated chain, however, the backbone network can be a public or private chain network.
S1413, generating the identity certificate to the main chain network so that the main chain network can verify the identity information of the target container according to the identity certificate.
After the target container is connected with the main chain network through the upper link port, the identity certificate is sent to the main chain network by the target container, and after the main chain network receives the identity certificate sent by the target container, the identity of the target container is verified through a preset identity verification rule. After the identity certificate passes the verification, the main network confirms the identity of the target container, and the target container has the identity of uploading the intelligent contract to the main network. If the identity certificate is not verified, the main network determines that the target container is illegally accessed and the connection with the target container is disconnected.
In some embodiments, the target container may be capable of receiving a second smart contract sent by other blockchain nodes in addition to the first smart contract issued by the blockchain node to the backbone network, upon receipt of the second smart contract, the blockchain node may need to verify the second smart contract. Specifically, S1500 thereafter includes:
s1610, the target container receives a second intelligent contract to be verified in the main network;
the target container sends the first smart contract to the backbone network, and the blockchain link point is also capable of receiving a second smart contract broadcast by the backbone network to blockchain nodes through the target container. The second intelligent contract is an intelligent contract uploaded by other block chain nodes in the block chain, and after the target container receives the second intelligent contract, the second intelligent contract needs to be tested, and after the second intelligent contract is tested, the second intelligent contract is deployed locally.
S1620, starting a set verification container according to the second intelligent contract, wherein the verification container is used for running the second intelligent contract;
and after the target container receives the second intelligent contract, the blockchain node where the target container is positioned activates a verification container capable of operating the second intelligent contract according to the environmental parameters required by the operation of the second intelligent contract. The verification container is a preconfigured container for verifying the smart contract. And the blockchain node where the target container is located correspondingly pre-constructs a verification container corresponding to each intelligent contract according to the type of the intelligent contract existing in the blockchain. Thus, when a 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 intelligent 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 mode is as follows: the verification container runs the second intelligent contract, a verification log is generated in the running process, and the verification log is sent to the main network to finish the verification of the second intelligent contract. The verification in some embodiments is: and after the verification container operates the second intelligent contract, a verification result is generated, the verification result is matched with the operation result, if the matching is successful, the verification is passed, and otherwise, the verification is failed.
The second smart contract received by the verification container is approximately an image file, and therefore, the second smart contract can be deployed directly at 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 the second smart contract is deployed after the decoded file of the second smart contract is converted into the image file.
The target container sends the second smart contract to the verification container via a third party, e.g., via a container orchestrator or master, forwarding the second smart contract to the verification container.
In the above embodiment, the second intelligent contract is received through the target container, so that the problem that when the blockchain node receives the second intelligent contract which needs to be verified, connection with the main network is required to be established, the first intelligent contract can be uploaded only by one-time connection, the second intelligent contract can also be received, the transmission efficiency is improved, the number of times that the connection interface is called is reduced, and the interface multiplexing is realized.
In some embodiments, the containers cannot sense the existence of each other and cannot perform information interaction between the containers, so that information transmission between the target container and the verification container needs to be performed by a third party, and the efficiency of information transmission is reduced. S1630 includes:
s1631, reading a target storage address of the target container;
in order to solve the problem that information transmission cannot be carried out between the target container and the verification container, the information transmission barrier is solved by multiplexing the storage problems of the two containers.
And after receiving the second intelligent contract, reading a target storage address of the target container, wherein the target storage address is a storage space exclusive to the target container, and when the target container is constructed or started, the target storage address is configured by a blockchain node or a container composer.
S1632, constructing a verification storage address of the verification container according to the target storage address, and overlapping the target storage address and the verification storage address;
after the target storage address of the target container is obtained by reading, the storage address of the verification container is configured, and the verification storage address of the verification container is configured to be the same as the target storage address. This achieves a mutual overlap of the target memory address and the verification memory address.
S1633, the target container stores the second intelligent 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 intelligent contract in the verification storage address, and verifies the second intelligent contract.
The verification container inquires whether information is written in the verification storage address or not in a timing inquiry mode, and when the target container stores the second intelligent contract in the target storage address, the verification container inquires that the information is written in the verification storage address, and at the moment, the verification container reads the second intelligent contract. And after the verification container reads the second intelligent contract, performing operation verification on the second intelligent contract.
By overlapping the target storage address and the verification storage address, the intelligent contract between the verification container and the target container is directly transferred, and the verification efficiency of the second intelligent contract is improved.
In some embodiments, when the verification container runs to complete the second smart contract, a verification log of the second smart contract is uploaded into the backbone network. S1630 includes, after:
s1640, when the second intelligent contract is verified, releasing the verification container and sending a release message and a verification log to the container composer;
and after the verification container runs the second intelligent contract, releasing the verification container according to program setting, and giving all resources and rights of the verification container back after the verification container is released. Before the verification container is released, release information and a verification log are sent to the container orchestrator. Wherein the release information is a log informing the container orchestrator to eliminate encoding and status monitoring of the verification container, and the verification log is a running log generated by running the second smart contract.
S1650, the container composer sends the verification log to the target container according to the release information;
after receiving the release information, the container composer removes the state monitoring of the verification container, deletes the coded information of the verification container, then sends the verification log to the target container, and the target container uploads the verification log to the main network.
S1660, the target container sends the verification log to the backbone network.
And after receiving the verification log sent by the container composer, the target container uploads the verification log to the main network, and the main network collects the verification log to generate a verification result of the second intelligent contract by the full-link blockchain node. In some embodiments, after the target container has sent the verification log, the target container is disconnected from the backbone network and a release procedure is initiated.
The verification log is uploaded through the target container, the verification container is not required to be connected to the main network, and the verification container is not required to be used for identity verification, so that the uploading rate of the verification log is improved, the resource use frequency is reduced, and the calculation resource is saved.
In some embodiments, S1500 then comprises:
s1711, acquiring a debugging interface of the first intelligent contract and a visualized debugging icon of the first intelligent contract;
after the first intelligent contract is deployed, entering a debugging module of the blockchain integrated development environment, wherein the debugging module is provided with a debugging interface of the first intelligent contract, and after the first intelligent contract is deployed, generating a visual debugging icon of the first intelligent contract on an operation page of the blockchain integrated development environment.
S1712, calling the first intelligent contract in the blockchain integrated development environment to perform test operation according to the debugging icon and the debugging interface.
After a user starts a debugging task of the first intelligent contract through the debugging icon, the debugging module calls the first intelligent contract through the debugging interface to perform test operation, and the test of the first intelligent contract is completed. After deployment is completed, the first intelligent contract is tested in the blockchain integrated development environment according to the visualized icon, so that the testing efficiency is improved.
Referring specifically to fig. 2, fig. 2 is a schematic diagram of a basic structure of an intelligent contract deployment apparatus according to the present embodiment.
As shown in fig. 2, an intelligent contract deployment apparatus includes: a generation module 1100, a deployment module 1200, an issue module 1300, a processing module 1400, and an execution module 1500. The generating module 1100 is configured to generate a first smart contract to be deployed based on a preset blockchain integrated development environment; the deployment module 1200 is configured to generate a target container running the first smart contract, and deploy the first smart contract into the target container; the issuing module 1300 is configured to issue an identity certificate of the target container according to a preset node certificate; the processing module 1400 is configured to invoke a preset container composer to access the target container into a backbone network for identity verification; the execution module 1500 is configured to diffuse the first smart contract in the backbone network after the authentication of the target container passes.
After a first intelligent contract is generated in the blockchain integrated development environment, the first intelligent contract is deployed in a target container of a node, the target container operates the first intelligent contract, after an identity card issued by a node certificate is obtained, the target container can be accessed into a main chain network, and the first intelligent contract is subjected to on-chain diffusion propagation through the main chain network, so that on-chain multi-node verification is realized, and the verification efficiency is improved. The unified deployment of intelligent contracts under line and on chain is realized through the target container and the identity certificate, the time limit of debugging deployment is shortened, and the efficiency of intelligent contract debugging deployment is improved.
Optionally, the smart contract deployment apparatus further includes:
the first processing sub-module is used for compiling the first intelligent contract to generate a compiling file of the first intelligent contract;
the first compiling sub-module is used for generating an image file of the first intelligent contract according to the compiling file;
and the first execution sub-module is used for starting the target container according to the image file and deploying the image file into the target container.
Optionally, the smart contract deployment apparatus further includes:
The second processing sub-module is used for reading the prestored node certificate and the certificate request sent by the target container;
and the second execution sub-module is used for generating a sub-certificate of the node certificate according to the certificate request and issuing the sub-certificate to the target container as the identity certificate.
Optionally, the smart contract deployment apparatus further includes:
the first calling sub-module is used for calling the container orchestrator to allocate a uplink interface for the target container;
a third processing sub-module for connecting the target container to a backbone network according to the uplink interface;
and the third execution sub-module is used for generating the identity certificate to the main chain network so that the main chain network can verify the identity information of the target container according to the identity certificate.
Optionally, the smart contract deployment apparatus further includes:
a first receiving sub-module, configured to receive, by the target container, a second smart contract to be verified in the backbone network;
a fourth processing sub-module for starting a verification container set according to the second smart contract, wherein the verification container is used for running the second smart contract;
And the fourth execution sub-module is used for sending the second intelligent contract to the verification container by the target container for verification.
Optionally, the smart contract deployment apparatus further includes:
the second reading submodule is used for reading the target storage address of the target container;
the first storage sub-module is used for constructing a verification storage address of the verification container according to the target storage address and enabling the target storage address and the verification storage address to be overlapped with each other;
a fifth processing sub-module for the target container to store the second smart contract in the target storage address;
and the fifth execution sub-module is used for reading the second intelligent contract in the verification storage address by the verification container and verifying the second intelligent contract.
Optionally, the smart contract deployment apparatus further includes:
the first release sub-module is used for releasing the verification container after the second intelligent contract is verified, and sending a release message and a verification log to the container composer;
a sixth processing sub-module, configured to send the verification log to the target container according to the release information by the container composer;
And a sixth execution sub-module, configured to send the verification log to the backbone network by using the target container.
Optionally, the smart contract deployment apparatus further includes:
a seventh processing sub-module, configured to obtain a debug interface of the first smart contract and a debug icon visualized by the first smart contract;
and the seventh execution sub-module is used for calling the first intelligent contract in the blockchain integrated development environment to perform test operation according to the debugging icon and the debugging interface.
In order to solve the technical problems, the embodiment of the application also provides computer equipment. Referring specifically to fig. 3, fig. 3 is a basic structural block diagram of a computer device according to the present embodiment.
As shown in fig. 3, the internal structure of the computer device is schematically shown. The computer device includes a processor, a non-volatile storage medium, a memory, and a network interface connected by a system bus. The nonvolatile storage medium of the computer device stores an operating system, a database and computer readable instructions, the database can store a control information sequence, and the computer readable instructions can enable the processor to realize an intelligent contract deployment method when the computer readable instructions are executed by the processor. The processor of the computer device is used to provide computing and control capabilities, supporting the operation of the entire computer device. The memory of the computer device may have stored therein computer readable instructions that, when executed by the processor, cause the processor to perform a smart contract deployment method. The network interface of the computer device is for communicating with a terminal connection. It will be appreciated by those skilled in the art that the structure shown in fig. 3 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
The processor in this embodiment is configured to perform specific functions of the generating module 1100, the deploying module 1200, the issuing module 1300, the processing module 1400, and the executing module 1500 in fig. 2, and the memory stores program codes and various data required for executing the foregoing modules. The network interface is used for data transmission between the user terminal or the server. The memory in this embodiment stores program codes and data required for executing all the sub-modules in the smart contract deployment apparatus, and the server can call the program codes and data of the server to execute the functions of all the sub-modules.
After the computer equipment generates the first intelligent contract in the blockchain integrated development environment, the first intelligent contract is deployed in a target container of a node, the target container operates the first intelligent contract, after an identity certificate issued by a node certificate is obtained, the target container can be accessed into a main chain network, and the first intelligent contract is spread and propagated on the chain through the main chain network, so that on-chain multi-node verification is realized, and the verification efficiency is improved. The unified deployment of intelligent contracts under line and on chain is realized through the target container and the identity certificate, the time limit of debugging deployment is shortened, and the efficiency of intelligent contract debugging deployment is improved.
The present application also provides a storage medium storing computer readable instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of any of the above-described embodiments of the smart contract deployment method.
Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored in a computer-readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. The storage medium may be a nonvolatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a random access Memory (Random Access Memory, RAM).
Those of skill in the art will appreciate that the various operations, methods, steps in the flow, actions, schemes, and alternatives discussed in the present application may be alternated, altered, combined, or eliminated. Further, other steps, means, or steps in a process having various operations, methods, or procedures discussed in this application may be alternated, altered, rearranged, split, combined, or eliminated. Further, steps, measures, schemes in the prior art with various operations, methods, flows disclosed in the present application may also be alternated, altered, rearranged, decomposed, combined, or deleted.
The foregoing is only a partial embodiment of the present application, and it should be noted that, for a person skilled in the art, several improvements and modifications can be made without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.
Claims (10)
1. An intelligent contract deployment method, comprising:
generating a first intelligent contract to be deployed based on a preset blockchain integrated development environment;
generating a target container running the first intelligent contract, and deploying the first intelligent contract into the target container;
issuing an identity certificate of the target container according to a preset node certificate;
invoking a preset container orchestrator to access the target container into a main chain network for identity verification;
when the identity of the target container passes, diffusing the first intelligent contract in the main chain network;
the issuing the identity certificate of the target container according to the preset node certificate comprises the following steps:
reading a prestored node certificate and a certificate request sent by the target container;
generating a sub-certificate of the node certificate according to the certificate request, and issuing the sub-certificate as the identity certificate to the target container.
2. The smart contract deployment method of claim 1, wherein the generating a target container running the first smart contract and deploying the first smart contract into the target container comprises:
compiling the first intelligent contract to generate a compiling file of the first intelligent contract;
generating an image file of the first intelligent contract according to the compiling file;
and starting the target container according to the image file, and deploying the image file into the target container.
3. The smart contract deployment method of claim 1, wherein invoking a preset container orchestrator to access the target container into a backbone network for authentication comprises:
invoking the container orchestrator to allocate a ul interface for the target container;
connecting the target container to a backbone network according to the uplink interface;
the identity certificate occurs to the main chain network, so that the main chain network verifies the identity information of the target container according to the identity certificate.
4. The smart contract deployment method of claim 1, wherein after diffusing the first smart contract in the backbone network after the authentication of the target container passes, comprising:
The target container receives a second intelligent contract to be verified in the main network;
starting a set verification container according to the second intelligent contract, wherein the verification container is used for running the second intelligent contract;
the target container sends the second intelligent contract to the verification container for verification.
5. The smart contract deployment method of claim 4, wherein the target container sending the second smart contract into the verification container for verification comprises:
reading a target storage address of the target container;
constructing a verification storage address of the verification container according to the target storage address, and overlapping the target storage address and the verification storage address;
the target container storing the second smart contract in the target storage address;
the verification container reads a second smart contract in the verification storage address and verifies the second smart contract.
6. The smart contract deployment method of claim 4, wherein the target container, after sending the second smart contract into the verification container for verification, comprises:
Releasing the verification container after the second intelligent contract is verified, and sending a release message and a verification log to the container composer;
the container composer sends the verification log to the target container according to the release information;
the target container sends the verification log to the backbone network.
7. The smart contract deployment method of claim 1, wherein after diffusing the first smart contract in the backbone network after the authentication of the target container passes, comprising:
acquiring a debugging interface of the first intelligent contract and a visualized debugging icon of the first intelligent contract;
and calling the first intelligent contract in the blockchain integrated development environment to perform test operation according to the debugging icon and the debugging interface.
8. An intelligent contract deployment apparatus, comprising:
the generation module is used for generating a first intelligent contract to be deployed based on a preset blockchain integrated development environment;
the deployment module is used for generating a target container for running the first intelligent contract and deploying the first intelligent contract into the target container;
The issuing module is used for issuing the identity certificate of the target container according to a preset node certificate;
the processing module is used for calling a preset container composer to access the target container into a main chain network for identity verification;
the execution module is used for diffusing the first intelligent contract in the main chain network after the identity verification of the target container is passed;
the second processing sub-module is used for reading the prestored node certificate and the certificate request sent by the target container;
and the second execution sub-module is used for generating a sub-certificate of the node certificate according to the certificate request and issuing the sub-certificate to the target container as the identity certificate.
9. A computer device comprising a memory and a processor, the memory having stored therein computer readable instructions that, when executed by the processor, cause the processor to perform the steps of the smart contract deployment method of any of claims 1 to 7.
10. A storage medium storing computer readable instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of the smart contract deployment method of any of claims 1 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210862683.6A CN115203330B (en) | 2022-07-21 | 2022-07-21 | Intelligent contract deployment method and device, equipment, medium and product thereof |
| PCT/CN2023/103599 WO2024016984A1 (en) | 2022-07-21 | 2023-06-29 | Smart contract deployment method and apparatus, device, medium, and product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210862683.6A CN115203330B (en) | 2022-07-21 | 2022-07-21 | Intelligent contract deployment method and device, equipment, medium and product thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115203330A CN115203330A (en) | 2022-10-18 |
| CN115203330B true CN115203330B (en) | 2024-01-19 |
Family
ID=83583280
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210862683.6A Active CN115203330B (en) | 2022-07-21 | 2022-07-21 | Intelligent contract deployment method and device, equipment, medium and product thereof |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115203330B (en) |
| WO (1) | WO2024016984A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115203330B (en) * | 2022-07-21 | 2024-01-19 | 深圳前海环融联易信息科技服务有限公司 | Intelligent contract deployment method and device, equipment, medium and product thereof |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111327648A (en) * | 2018-12-13 | 2020-06-23 | 北京果仁宝软件技术有限责任公司 | Processing method and system based on block chain intelligent contract |
| CN111355718A (en) * | 2020-02-25 | 2020-06-30 | 中国工商银行股份有限公司 | Block chain intelligent contract cloud deployment system and method |
| CN112596754A (en) * | 2021-03-01 | 2021-04-02 | 腾讯科技（深圳）有限公司 | Block chain intelligent contract deployment method and device |
| WO2021098140A1 (en) * | 2019-11-21 | 2021-05-27 | 深圳壹账通智能科技有限公司 | Blockchain network deployment method, electronic device, and computer-readable storage medium |
| CN113239382A (en) * | 2021-02-09 | 2021-08-10 | 南京邮电大学 | Credible identity model based on block chain intelligent contract |
| CN113609219A (en) * | 2021-07-21 | 2021-11-05 | 微易签(杭州)科技有限公司 | Method, system, device and storage medium for verifying file based on block chain |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107819749A (en) * | 2017-10-26 | 2018-03-20 | 平安科技（深圳）有限公司 | Block catenary system and transaction data processing method based on ether mill |
| US20210149880A1 (en) * | 2019-11-20 | 2021-05-20 | Insolar Technologies GmbH | Systems and methods for extendable smart contracts in distributed ledger technology |
| US11693683B2 (en) * | 2021-01-08 | 2023-07-04 | Pivotal Software, Inc. | Container certificate injection |
| CN114157444A (en) * | 2021-09-10 | 2022-03-08 | 北京天德科技有限公司 | Block chain deployment system and deployment method based on container technology |
| CN115203330B (en) * | 2022-07-21 | 2024-01-19 | 深圳前海环融联易信息科技服务有限公司 | Intelligent contract deployment method and device, equipment, medium and product thereof |
-
2022
- 2022-07-21 CN CN202210862683.6A patent/CN115203330B/en active Active
-
2023
- 2023-06-29 WO PCT/CN2023/103599 patent/WO2024016984A1/en unknown
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111327648A (en) * | 2018-12-13 | 2020-06-23 | 北京果仁宝软件技术有限责任公司 | Processing method and system based on block chain intelligent contract |
| WO2021098140A1 (en) * | 2019-11-21 | 2021-05-27 | 深圳壹账通智能科技有限公司 | Blockchain network deployment method, electronic device, and computer-readable storage medium |
| CN111355718A (en) * | 2020-02-25 | 2020-06-30 | 中国工商银行股份有限公司 | Block chain intelligent contract cloud deployment system and method |
| CN113239382A (en) * | 2021-02-09 | 2021-08-10 | 南京邮电大学 | Credible identity model based on block chain intelligent contract |
| CN112596754A (en) * | 2021-03-01 | 2021-04-02 | 腾讯科技（深圳）有限公司 | Block chain intelligent contract deployment method and device |
| CN113609219A (en) * | 2021-07-21 | 2021-11-05 | 微易签(杭州)科技有限公司 | Method, system, device and storage medium for verifying file based on block chain |
Non-Patent Citations (1)
| Title |
|---|
| 基于区块链3.0架构的身份认证系统;李嶒;;宿州学院学报(11);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115203330A (en) | 2022-10-18 |
| WO2024016984A1 (en) | 2024-01-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109981279B (en) | Block chain system, communication method, device, equipment and medium | |
| CN110557420B (en) | Operation method and system of independent sub-chains | |
| CN111314172B (en) | Block chain-based data processing method, device, equipment and storage medium | |
| CN112714158B (en) | Transaction processing method, relay network, cross-link gateway, system, medium and equipment | |
| CN115203330B (en) | Intelligent contract deployment method and device, equipment, medium and product thereof | |
| CN109669859A (en) | Service test method, device, computer equipment and storage medium | |
| CN109814877A (en) | Project dispositions method and its device based on environmental management | |
| CN105260292A (en) | Log recording method, apparatus and system | |
| CN110362318A (en) | Using dispositions method, device, equipment and storage medium | |
| CN108390786B (en) | Business operation and maintenance method and device and electronic equipment | |
| CN116257438A (en) | Updating method of interface test case and related equipment | |
| CN109522723A (en) | POC scenario generation method, device, electronic equipment and storage medium | |
| CN106529297A (en) | Method and apparatus for obtaining application state information | |
| CN116599881A (en) | Cloud platform tenant modeling test method, device, equipment and storage medium | |
| CN113419952B (en) | Cloud service management scene testing device and method | |
| CN111708545A (en) | Business process deployment method and device, electronic equipment and storage medium | |
| CN110069253A (en) | Configure method, apparatus, computer equipment and the storage medium of service | |
| CN111369246A (en) | Calling authentication method and device of intelligent contract, electronic equipment and storage medium | |
| CN109766228A (en) | Verification method and device on a kind of line based on interface | |
| CN101251824B (en) | Method for testing public objects request proxy structure and tools | |
| CN110489276B (en) | Disaster recovery method and device for verification service based on business page | |
| CN105808439B (en) | Application program of intelligent card remote test system | |
| CN112968930B (en) | Intelligent contract of block chain key value pair and design method thereof | |
| US20230132531A1 (en) | Software Development Project Infrastructure Builder Tool | |
| CN116708463B (en) | Information processing method, device, equipment and medium based on multi-block chain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |