Smart contract deployment method and apparatus, smart contract execution method and apparatus, and electronic device

Abstract

Disclosed in the present application are a smart contract deployment method and apparatus, a smart contract execution method and apparatus, an electronic device, and a readable medium. The smart contract deployment method comprises: in response to receiving a contract template deployment instruction generated by a smart contract center management institution on the basis of a contract template registration request sent by a smart contract developer, deploying a contract template; in response to receiving a contract product deployment instruction generated by the smart contract center management institution on the basis of a contract product creation request sent by a smart contract service institution, deploying a contract product; and in response to receiving a contract instance signing instruction that is sent by the smart contract service institution and is forwarded by the smart contract center management institution and a contract instance confirmation instruction sent by a user wallet, deploying a contract instance. By means of layered parameterized configuration by different entities for management of smart contracts, the present application can implement centralized management and distributed operation of smart contracts, thereby improving the efficiency of ecological supervision and contract execution.

Description

A method, execution method, apparatus, and electronic device for deploying smart contracts.

[0001] This disclosure claims priority to Chinese Patent Application No. 202411824298.8, filed on December 11, 2024, entitled "A Smart Contract Deployment Method, Execution Method, Apparatus and Electronic Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to methods for deploying and executing smart contracts, apparatus, electronic devices, and readable media. Background Technology

[0003] In traditional smart contract systems, developers upload the underlying smart contract code and deploy it directly as a smart contract for users. This approach is suitable for scenarios with a small number of smart contracts. However, when smart contracts are diverse in type and have different calling entities, the review and testing results of smart contracts are difficult to reuse, and the business information of smart contracts is difficult to monitor comprehensively. This makes it difficult to quickly replicate and promote the application of smart contracts and to effectively manage the smart contract ecosystem. Summary of the Invention

[0004] This disclosure provides a smart contract deployment method, execution method, device, electronic device, and readable medium. By configuring and managing smart contracts layer by layer through different entities, centralized management and distributed operation of smart contracts can be achieved, improving the efficiency of ecosystem supervision and contract execution.

[0005] To achieve the above technical objectives, the embodiments of this disclosure adopt the following technical solutions:

[0006] In a first aspect, embodiments of this disclosure provide a smart contract deployment method, applied to a smart contract operation and management organization, the method comprising:

[0007] In response to receiving a contract template deployment instruction generated by the smart contract center management agency based on the contract template registration request sent by the smart contract developer, the contract template is deployed based on the modular environment interface. The contract template includes interface information, contract template code, contract template identifier and template parameter information to be configured.

[0008] In response to receiving a contract product deployment instruction generated by the smart contract center management organization based on a contract product creation request sent by the smart contract service provider, the contract product is deployed. The contract product includes a contract template identifier, a contract product identifier, and configuration parameters. The configuration parameters are used to configure the template parameter information to be configured.

[0009] In response to receiving the contract instance signing instruction sent by the smart contract service provider and the contract instance confirmation instruction sent by the user wallet, which are forwarded by the smart contract center management authority, a contract instance is deployed. The contract instance includes a contract product identifier, a contract instance identifier, and a contract wallet identifier.

[0010] In some possible implementations, a contract product query request sent by a smart contract service provider and forwarded by the smart contract center management authority is received, and a contract product query response is generated, wherein the contract product query response includes a contract template identifier and a contract product identifier.

[0011] In some possible implementations, deploying a contract instance includes: binding a user wallet to the contract instance and using the user wallet identifier as the contract wallet identifier; or generating a sub-wallet under the user wallet, binding the sub-wallet to the contract instance, and using the sub-wallet identifier as the contract wallet identifier.

[0012] In some possible implementations, the contract instance deployment results are sent to the smart contract central management authority, wherein the contract instance deployment results include the contract product identifier, the contract instance identifier, and the contract wallet identifier.

[0013] Secondly, this disclosure provides a smart contract deployment method, applied to a smart contract central management organization, the method comprising:

[0014] In response to receiving a contract template registration request from a smart contract developer, a contract template deployment instruction is generated and sent to the smart contract operation and management organization, so that the smart contract operation and management organization can deploy the contract template based on the modular environment interface. The contract template includes interface information, contract template code, contract template identifier and template parameter information to be configured.

[0015] In response to receiving a contract product creation request from a smart contract service provider, a contract product deployment instruction is generated and sent to the smart contract runtime management provider to enable the smart contract runtime management provider to deploy the contract product. The contract product includes a contract template identifier, a contract product identifier, and configuration parameters, whereby the configuration parameters are used to configure the template parameter information to be configured.

[0016] The system receives and forwards the contract instance signing instruction sent by the smart contract service provider to the smart contract operation and management organization, so that the smart contract operation and management organization can deploy the contract instance based on the contract instance signing instruction and the contract instance confirmation instruction sent by the user wallet. The contract instance includes a contract product identifier, a contract instance identifier, and a contract wallet identifier.

[0017] In some possible implementations, the contract instance deployment results obtained by the smart contract operation management agency from deploying contract instances are received and saved, wherein the contract instance deployment results include the contract product identifier, the contract instance identifier, and the contract wallet identifier.

[0018] In some possible implementations, a contract template query request is received from a smart contract service provider, and a contract template query response is returned, wherein the contract template query response includes a contract template identifier; and / or,

[0019] Forward the contract product query request sent by the smart contract service provider to the smart contract operation and management organization, and receive the contract product query response returned by the smart contract operation and management organization. The contract product query response includes the contract template identifier and the contract product identifier.

[0020] In some possible implementations, in response to receiving a contract template registration request from a smart contract developer, a contract template deployment instruction is generated and sent to the smart contract runtime management authority, including:

[0021] Receive contract template registration requests from smart contract developers. The contract template registration request includes the contract template code and template parameter information to be configured.

[0022] Review contract template registration requests; and

[0023] If the review is approved, a contract template deployment instruction is generated and sent to the smart contract operation and management agency.

[0024] In some possible implementations, in response to receiving a contract product creation request from a smart contract service provider, a contract product deployment instruction is generated and sent to the smart contract runtime management authority, including:

[0025] Receive contract product creation requests from smart contract service providers. The contract product creation requests include contract template identifiers and configuration parameters.

[0026] Reviewing contract product creation requests; and

[0027] If the review is approved, a contract product deployment instruction is generated and sent to the smart contract operation and management agency.

[0028] Thirdly, this disclosure provides a smart contract execution method, applied to a smart contract operation management organization, wherein the smart contract is deployed according to the smart contract deployment method of the first aspect, the method comprising:

[0029] In response to receiving a smart contract trigger command, the contract instance, contract product, and contract template are loaded into the virtual machine; and

[0030] The virtual machine executes the contract instance.

[0031] In some possible implementations, in response to receiving a smart contract trigger instruction, the contract instance, contract product, and contract template are loaded into the virtual machine, including:

[0032] Receive smart contract trigger instructions, obtain associated contract products based on the contract instance, obtain associated contract templates based on the contract products, verify the contract instance, contract products, and contract templates, and load the contract instance, contract products, and contract templates into the virtual machine if the verification is successful.

[0033] In some possible implementations, the virtual machine executes contract instances, including:

[0034] The virtual machine executes the contract instance and sends transaction instructions to the core system of the smart contract runtime management organization through the environment interface to complete the transaction.

[0035] In some possible implementations, the core system generates cross-agency transaction messages and sends them to the smart contract central management authority to complete the transaction.

[0036] Fourthly, embodiments of this disclosure provide a smart contract deployment device, applied to a smart contract operation and management organization, the device comprising:

[0037] The contract template deployment module is configured to respond to the contract template deployment instruction generated by the smart contract center management agency based on the contract template registration request sent by the smart contract developer, and deploy the contract template based on the modular environment interface. The contract template includes interface information, contract template code, contract template identifier and template parameter information to be configured.

[0038] The contract product deployment module is configured to deploy a contract product in response to a contract product deployment instruction generated by the smart contract center management agency based on a contract product creation request sent by the smart contract service agency. The contract product includes a contract template identifier, a contract product identifier, and configuration parameters. The configuration parameters are used to configure the template parameter information to be configured.

[0039] The contract instance deployment module is configured to deploy a contract instance in response to receiving a contract instance signing instruction sent by the smart contract service provider and a contract instance confirmation instruction sent by the user wallet, which are forwarded by the smart contract center management agency. The contract instance includes a contract product identifier, a contract instance identifier, and a contract wallet identifier.

[0040] Fifthly, embodiments of this disclosure provide a smart contract deployment device, applied to a smart contract central management organization, the device comprising:

[0041] The contract template management module is configured to generate and send a contract template deployment instruction to the smart contract operation management organization in response to a contract template registration request sent by a smart contract developer. This instruction enables the smart contract operation management organization to deploy the contract template based on a modular environment interface. The contract template includes interface information, contract template code, contract template identifier, and template parameter information to be configured.

[0042] The contract product management module is configured to, in response to a contract product creation request received from a smart contract service provider, generate and send a contract product deployment instruction to the smart contract runtime management provider, enabling the smart contract runtime management provider to deploy the contract product. The contract product includes a contract template identifier, a contract product identifier, and configuration parameters. The configuration parameters are used to configure the template parameter information to be configured.

[0043] The contract instance management module receives and forwards the contract instance signing instruction sent by the smart contract service provider to the smart contract operation management agency, so that the smart contract operation management agency can deploy the contract instance based on the contract instance signing instruction and the contract instance confirmation instruction sent by the user wallet. The contract instance includes a contract product identifier, a contract instance identifier, and a contract wallet identifier.

[0044] Sixthly, embodiments of this disclosure provide a smart contract execution device, applied to a smart contract operation management organization, wherein the smart contract is deployed according to the smart contract deployment device of the fourth aspect, the device comprising:

[0045] The smart contract loading module is configured to load the contract instance, contract product, and contract template into the virtual machine in response to a received smart contract trigger command; and

[0046] The virtual machine is configured to execute contract instances.

[0047] In a seventh aspect, embodiments of this disclosure provide an electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by one or more processors, cause the one or more processors to implement the methods of the first aspect, the second aspect, and the third aspect.

[0048] Eighthly, embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the methods of the first, second, and third aspects.

[0049] The first aspect of the technical solution provided by the embodiments of this disclosure brings at least the following beneficial effects: In response to receiving a contract template deployment instruction generated by the smart contract center management agency based on a contract template registration request sent by a smart contract developer, a contract template is deployed; in response to receiving a contract product deployment instruction generated by the smart contract center management agency based on a contract product creation request sent by a smart contract service agency, a contract product is deployed; in response to receiving a contract instance signing instruction forwarded by the smart contract center management agency from a smart contract service agency and a contract instance confirmation instruction sent by a user wallet, a contract instance is deployed. The embodiments of this disclosure abstract smart contracts into multiple layers: environment interface, contract template, contract product, and contract instance, supporting participants in managing smart contracts through layer-by-layer parameterized configuration; simultaneously, the smart contract center management agency can supervise and deploy contract templates and contract products, and each smart contract operation management agency can run contract instances, realizing centralized management and distributed operation of smart contracts, which helps improve the efficiency of ecosystem supervision and contract execution.

[0050] It should be noted that the technical effects of any of the implementation methods in aspects two through eight can be found in the technical effects of the corresponding implementation methods in aspect one, and will not be repeated here.

[0051] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0052] To more clearly illustrate the technical solutions in the prior art and the embodiments of this disclosure, the accompanying drawings used in the description of the prior art and the embodiments of this disclosure will be briefly introduced below. Of course, the accompanying drawings described below with reference to the embodiments of this disclosure are only a part of the embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort, and such other drawings also fall within the protection scope of this disclosure.

[0053] Figure 1 shows a schematic diagram of the configuration of a smart contract deployment and execution system according to at least one embodiment of the present disclosure;

[0054] Figure 2 shows a flowchart of a smart contract deployment process according to at least one embodiment of the present disclosure;

[0055] Figure 3 illustrates the main steps of a smart contract deployment method according to at least one embodiment of the present disclosure;

[0056] Figure 4 shows a schematic diagram of the structure of a contract template, a contract product, and a contract instance according to at least one embodiment of the present disclosure;

[0057] Figure 5 shows an interactive flowchart of a smart contract deployment method according to at least one embodiment of the present disclosure;

[0058] Figure 6 shows a schematic diagram of the main modules of a smart contract deployment apparatus according to at least one embodiment of the present disclosure;

[0059] Figure 7 shows a schematic diagram of the environment interface of a smart contract operation management agency according to at least one embodiment of the present disclosure;

[0060] Figure 8 shows an interactive flowchart of a smart contract deployment method according to at least one embodiment of the present disclosure;

[0061] Figure 9 illustrates an interactive flowchart of a smart contract execution method according to at least one embodiment of the present disclosure;

[0062] Figure 10 shows a schematic diagram of an electronic device according to at least one embodiment of the present disclosure;

[0063] Figure 11 shows a schematic diagram of a computer-readable medium according to at least one embodiment of the present disclosure. Detailed Implementation

[0064] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the described embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0065] In the following text, any methods, apparatus, examples, and contents that do not fully correspond to the scope defined by the claims are not derived from the present invention. Such methods, apparatus, examples, and contents, as well as all subsequent descriptions, are for illustrative purposes only, or to highlight specific aspects or features of the claims.

[0066] Note that the examples described below are merely specific examples and are not intended to limit the embodiments of this disclosure to the specific shapes, hardware, connections, operations, values, conditions, data, sequences, etc., shown and described. Those skilled in the art can utilize the concepts of this disclosure to construct further embodiments not mentioned herein by reading this specification.

[0067] The terminology used in this disclosure is that which is currently widely used in the art in consideration of the functionality of this disclosure; however, these terms may vary depending on the intent, precedent, or new technology of those skilled in the art. Furthermore, specific terms may be chosen by the applicant, and in such cases, their detailed meanings will be described in the detailed description of this disclosure. Therefore, the terminology used in this specification should not be construed as simple names, but rather based on the meaning of the terms and the overall description of this disclosure.

[0068] To better understand the embodiments of this disclosure, the relevant terms involved in this disclosure will first be defined and explained.

[0069] Smart contracts are self-executing computer programs that automatically execute corresponding terms when preset conditions are met. Smart contracts typically contain a set of predefined rules, according to which the parties to the smart contract agree to interact with each other.

[0070] Deploying a smart contract instance: This deploys the code of a smart contract into the execution entity, making it an executable contract entity.

[0071] It should be noted that the technical solutions in this disclosure, including the collection, updating, analysis, processing, use, transmission, and storage of user personal information, all comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken to prevent unauthorized access to user personal information data and to safeguard user personal information security, network security, and national security.

[0072] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0073] Figure 1 illustrates a schematic diagram of the configuration of a smart contract deployment and execution system according to at least one embodiment of the present disclosure. The smart contract deployment and execution system of the present disclosure includes: a smart contract central management organization 110, a smart contract operation management organization 120, a smart contract service organization 130, and smart contract developers 140. The smart contract central management organization 110 is responsible for the unified registration and management of master data such as smart contract templates, contract products, contract instances, and contract wallets; providing transfer control services such as mandatory checks and validity checks; and verifying the execution of smart contract code afterward to ensure the mandatory nature of the smart contract. It may be, for example, a central bank or other centralized smart contract review, management, and supervision organization. The smart contract operation management organization 120 is an operating organization that builds, manages, and maintains the operating environment according to standards. For example, in a central bank digital currency system, it is an operating organization. The smart contract service organization 130 is an organization that provides basic payment capabilities and provides services externally by overlaying smart contracts. For example, in a central bank digital currency system, it includes operating organizations, interbank cooperation organizations, and acceptance service organizations. Smart contract developer 140 is a smart contract development organization responsible for developing smart contract code, configuring interface information, and setting template parameter information to be configured.

[0074] The smart contract central management organization 110 is a centralized organization, and there can be one or more smart contract operation management organizations 120, thereby realizing centralized management of the smart contract central management organization 110 and distributed operation of the smart contract operation management organizations 120. The smart contract operation management organization 120 includes a smart contract runtime environment 121 and a core system 122. The core system 122 provides underlying digital currency capabilities such as ledger recording, payment, and wallet management. In one specific embodiment, the core system 122 includes modules such as ledger 1221, payment transaction 1222, and wallet management 1223. The smart contract runtime environment 121 is used for hierarchical management of contract templates 11, contract products 12, and contract instances 13. When a smart contract is invoked, it can be loaded into the virtual machine 1211 and interact with the core system 122 through the environment interface 1212 to complete the transaction. In one specific embodiment, the smart contract central management organization 110 includes a contract module management module 111, which can provide contract template management services to smart contract developers 140. In one specific embodiment, the smart contract central management institution 110 further includes a contract product management module 112, which can provide contract product management services to the smart contract service institution 130 to achieve layer-by-layer abstraction and templated assembly of smart contract capabilities. In one specific embodiment, the smart contract central management institution 110 may also include a contract instance management module (not shown in the figure), which can be used to provide management of contract instances and contract wallets. In one specific embodiment, the smart contract central management institution 110 may further include a transaction transfer service module 113, which supports interaction between multiple smart contract operation management institutions 120 in cross-institutional transactions. Therefore, the embodiments of this disclosure provide cross-institutional contract transaction capabilities and the expansion capabilities of multiple smart contract operation management institutions 120.

[0075] Figure 2 shows a block diagram of a smart contract deployment process 100 according to at least one embodiment of the present disclosure. Figure 4 shows a schematic diagram of the structure of contract templates, contract products, and contract instances according to at least one embodiment of the present disclosure. In the embodiments of the present disclosure, smart contract deployment can be decomposed from bottom to top into four layers: environment interface deployment (step S101), contract template deployment (step S102), contract product deployment (step S103), and contract instantiation (step S104). The template management of the bottom three layers is realized, thereby supporting the centralized management and distributed operation of smart contracts. Furthermore, the results of smart contract audit and testing by the smart contract central management agency 110 can be reused to monitor smart contract business information in a timely manner, quickly replicate scenario applications, and achieve efficient management of the smart contract ecosystem.

[0076] Step S101: Deployment of Environment Interface 1212. Environment Interface 1212 enables control and invocation of smart contracts. It is physically distributed and deployed in the smart contract runtime environment 121 of each smart contract runtime management organization 120, but logically unified and modular. Environment Interface 1212 interfaces downwards with the underlying capabilities of the smart contract runtime environment 121 and the core system 122, and upwards provides a standardized interface for the execution of contract instances 13. Figure 7 shows a schematic diagram of the structure of the environment interface of the smart contract runtime management organization according to at least one embodiment of this disclosure. Environment Interface 1212 is modularly divided into context information query interfaces, transaction interfaces, storage operation interfaces, oracle interfaces, and log interfaces. The context information query interfaces are further divided into wallet information query interfaces and transaction information query interfaces. The transaction interfaces are divided into contract invocation interfaces and money transfer interfaces. This modular setting of Environment Interface 1212 helps improve the standardization and normalization of contract module 11 deployment and facilitates review and supervision by the smart contract central management organization 110.

[0077] Step S102: Contract template deployment. Contract template 11 consists of code and a description file. The code can be loaded into the virtual machine 1211 of the smart contract runtime environment 121 and executed. During execution, it will call the environment interface 1212 to query wallet and transaction information, and trigger payment transactions according to the rules agreed upon in the template. The description file may include, for example, metadata such as the contract template ID (i.e., contract template identifier), contract template name, and developer information, as well as the interface information provided by the contract template and template parameter information that can be parameterized and configured during the subsequent construction of contract product 12. The interface information is set according to the modular environment interface 1212 in step S101, and the deployment of contract template 11 is completed based on this environment interface. It is understood that the interface of the contract template can be independent of the environment interface. During execution, the contract template calls the environment interface and encapsulates the interface for external exposure to achieve modular assembly of the contract template.

[0078] Step S103, Contract Product Deployment. Based on contract template 11, the smart contract service provider further defines the concrete services it provides to customers through contract product 12. This process is the productization or parameterization of smart contracts. For example, based on the pre-order consumption contract template 11, parameters such as card refund fees and whether transfer is supported are set to form a pre-order consumption fund management service with specific rules and terms that customers can directly use. Contract product 12 consists of a set of data, which may include metadata such as contract product ID (i.e., contract product identifier), contract product name, contract template ID, and smart contract service provider, as well as configuration parameters for contract product 12 that parameterize the template parameter information of the associated contract template 11. That is, the configuration parameters are used to configure the template parameter information to be configured.

[0079] Step S104, Contract Instance Deployment. The contract instance 13 deployment process is a customization process for contract product 12. Contract instance 13 is an instantiated smart contract generated after the client signs up for the contract product. It consists of a set of data, which may include, for example, metadata such as contract instance ID (i.e., contract instance identifier), contract instance status, contract product ID, contract wallet ID, and information of each signatory to the smart contract. In a specific embodiment, contract instance 13 may also include status data.

[0080] Understandably, to establish the association between contract template 11 and environment interface 1212, the contract template code of contract module 11 needs to include the association between contract template 11 and environment interface 1212. To establish the association between contract product 12 and contract template 11, contract template 11 needs to include the contract template ID and the template parameters to be configured, while contract product 12 correspondingly includes the contract module ID and configuration parameters. To establish the association between contract instance 13 and contract product 12, contract product 12 needs to include the contract product ID, while contract instance 13 correspondingly includes the contract product ID. Through the association of the above data, layered deployment of smart contracts is achieved.

[0081] It is important to note that a contract product 12 can only belong to one contract template 11, and a contract template 11 can generate one or more contract products 12. A contract product 12 can generate one or more contract instances 13, and a contract instance 13 belongs to only one contract product 12. A contract instance 13 can call multiple oracles, and an oracle can be called by multiple contract instances 13. After a user completes the deployment of contract instance 13 by sending a contract instance confirmation command through their user wallet, the wallet controlled by contract instance 13 becomes the contract wallet. If contract instance 13 directly controls the user wallet that sent the contract instance confirmation command during contract signing, then that user wallet is a contract wallet. If contract instance 13 generates a sub-wallet under the user wallet that sent the contract instance confirmation command during contract signing, and the contract instance controls that sub-wallet, then that sub-wallet is a contract wallet. To implement the invocation and permission verification of contract instance 13, contract instance 13 can include a contract wallet ID (i.e., contract wallet identifier) ​​and a contract instance ID.

[0082] Figure 3 illustrates the main steps of a smart contract deployment method 300 according to at least one embodiment of the present disclosure. Figure 5 shows an interactive flowchart of the smart contract deployment method according to at least one embodiment of the present disclosure.

[0083] In step S301, the smart contract operation management organization 120, in response to receiving the contract template deployment instruction generated by the smart contract center management organization 110 based on the contract template registration request sent by the smart contract developer 140, deploys the contract template 11 based on the modular environment interface 1212. The contract template 11 includes interface information, contract template code, contract template identifier, and template parameter information to be configured.

[0084] In this embodiment, the smart contract developer 140 completes the development of the contract template code, generates and sends a contract template registration request to the smart contract center management agency 110 (step S1021). It is understood that the contract template registration request may include contract template code and a description file. The description file includes template parameter information to be configured. In one specific embodiment, the description file in the contract template 11 may also include metadata and interface information. In one specific embodiment, the metadata may include information such as the contract template ID, contract template name, and developer. In one specific embodiment, the description file may be generated and sent by the smart contract developer 140. In one specific embodiment, the description file may also be generated or configured by the smart contract center management agency 110 itself. In one specific embodiment, the description file may also be partially sent by the smart contract developer 140 and partially generated or configured by the smart contract center management agency 110; this is not limited here. For example, the smart contract developer 140 may set the contract template ID in the sent contract template registration request, or the smart contract center management agency 110 may generate the contract template ID after verifying the contract template code.

[0085] After receiving a contract template registration request, the contract template management module 111 of the smart contract center management organization 110 reviews the request (step S1022). The review may include issues such as code security, quality, and consistency, as well as whether it meets the normative requirements of the contract template 11. It may also further verify whether the contract template registration request submitted by the smart contract developer 140 matches its development permissions.

[0086] The smart contract center management organization 110 registers approved contract template registration requests and manages contract template 11 in the contract template management module 111 (step S1023). Contract template 11 includes interface information, contract template code, contract template identifier, and template parameter information to be configured. For contract template registration requests that fail the review, in a specific embodiment, the review result of registration failure is returned to the smart contract developer 140 (step S1023').

[0087] The contract template management module 111 of the smart contract center management organization 110 further generates a contract template deployment instruction based on the contract template registration request (step S1024), which includes the contract template 11. The smart contract operation management organization 120 deploys the contract template 11 based on the templated environment interface 1212 deployed thereon (step S1025).

[0088] In one specific embodiment, after approving the contract template registration request, the smart contract central management agency 110 returns the registration result to the smart contract developer 140 (step S1024'). Whether to return this result and the specific timing of the return can be set as needed, and this disclosure does not limit this.

[0089] In step S302, the smart contract operation management organization 120, in response to receiving the contract product deployment instruction generated by the smart contract center management organization 110 based on the contract product creation request sent by the smart contract service organization 130, deploys the contract product 12. In a specific embodiment, the contract product 12 includes a contract template identifier, a contract product identifier, and configuration parameters, wherein the configuration parameters are used to configure the template parameter information to be configured.

[0090] The smart contract service provider 130 creates a contract product 12 based on the registered contract template 11. In this embodiment, the smart contract service provider 130 sends a contract product creation request to the smart contract center management institution 110 (step S1033). It is understood that the contract product creation request may include a contract template ID and configuration parameters. The contract template is located through the contract template ID, and the template parameter information to be configured in the contract template is further configured according to the configuration parameters. The configuration parameters, for example, are key-value pairs, including parameter keys, parameter values, and parameter types. In one specific embodiment, other metadata of the contract product 12, such as the contract product ID and contract product name, may be generated and sent by the smart contract service provider 130, or generated or configured by the smart contract center management institution 110; this is not limited here.

[0091] In one specific embodiment, before the smart contract service provider 130 sends a contract product creation request to the smart contract center management provider 110, it can query the existing contract templates 11. For example, the smart contract service provider 130 can obtain a list of contract templates 11 that it is authorized to deploy through a query step. It is understood that the timing of this query step can also be set freely as needed, and this disclosure does not limit it. In this embodiment of the disclosure, the smart contract service provider 130 can also send a contract template query request to the smart contract center management provider 110 (step S1031) and receive a contract template query response returned by the smart contract center management provider 110 (step S1032). In one specific embodiment, the contract template query response includes at least the contract template ID.

[0092] In one specific embodiment, the query process can be further divided into list query and detail query. For example, the smart contract service provider 130 can first send a contract template list query request to the smart contract center management provider 110. In one specific embodiment, the contract template list query request may include the requester identifier, and may further include the identifier of the smart contract operation management provider to which the query is requested. The smart contract center management provider 110 sends a contract template list query response message back to the smart contract service provider 130. The response message may include, for example, information such as: contract template list, contract template identifier, contract template status, contract template name, contract template description, permission mode (e.g., public or private), and template developer. For contract templates for which further details are desired, the smart contract service provider 130 can further send a contract template detail query request to the smart contract center management provider 110. This request may include the contract template identifier and the requester identifier. The smart contract center management organization 110 sends a response message to the smart contract service organization 130 regarding the contract template details query. The response message includes, for example, the contract template identifier, contract template status, contract template name, contract template description, permission mode (e.g., public or private), template developer, and control object (contract wallet information). The specific fields of the response message can be set as needed.

[0093] The smart contract center management organization 110 reviews the contract product creation request (step S1304). The review content may include the validity of the contract template 11, the deployment permissions of the smart contract service organization 130, etc.

[0094] The smart contract center management organization 110 registers approved contract product creation requests and manages contract products 12 in the contract product management module 112 (step S1035). Contract product 12 includes information such as configuration parameters, contract template identifier, and contract product identifier. For contract product creation requests that fail the review, in a specific embodiment, a review result indicating creation failure is returned to the smart contract service organization 130 (step S1035').

[0095] The contract product management module 112 of the smart contract center management agency 110 further generates a contract product deployment instruction based on the contract product creation request (step S1036), which includes contract product 12. The smart contract operation management agency 120 deploys contract product 12 (step S1037). The deployed contract product 12 is available to the user to which the smart contract operation management agency 120 belongs. Different smart contract operation management agencies 120 can deploy the same or different contract products 12.

[0096] In one specific embodiment, after approving the contract product creation request, the smart contract center management agency 110 returns the creation result to the smart contract service agency 130 (step S1036'). Whether to return the result and the specific timing of the return can be set as needed, and this disclosure does not limit this.

[0097] In step S303, the smart contract operation management organization 120, in response to receiving the contract instance signing instruction sent by the smart contract service organization 130 and the contract instance confirmation instruction sent by the user wallet forwarded by the smart contract center management organization 110, deploys the contract instance 13. In a specific embodiment, the contract instance 13 includes a contract product identifier, a contract instance identifier, and a contract wallet identifier.

[0098] The smart contract service provider 130 deploys contract instance 13 based on the created contract product 12. In this embodiment, the smart contract service provider 130 sends a contract instance signing instruction to the smart contract operation management provider 120 through the smart contract center management provider 110 (step S1045). In one specific embodiment, the contract instance signing instruction includes information on each signatory of the contract instance 13 to be deployed. Based on the contract instance signing instruction, the smart contract operation management provider 120 sends a signing confirmation request to each signatory through the transaction transfer service module 113, and waits for each signatory to return a contract instance confirmation instruction. For example, each signatory may include a user of the smart contract operation management provider 120, whose user wallet is opened at the smart contract operation management provider 120, and the user sends the contract instance confirmation instruction through their user wallet. It is understood that the contract instance signing instruction may include the contract product ID and signatory information, using the contract product ID to locate the contract product and its associated contract template. In one specific embodiment, other metadata of contract instance 13, such as contract instance ID and contract instance name, may be generated and sent by smart contract service provider 130, or generated or configured by smart contract operation management provider 120, without limitation here.

[0099] In one specific embodiment, before the smart contract service provider 130 sends the contract instance signing instruction, it can query the existing contract products 12. For example, the smart contract service provider 130 can obtain a list of contract products 12 that it is authorized to deploy through a query step. It is understood that the timing of this query step can also be set freely as needed, and this disclosure does not limit it. In this embodiment, the smart contract service provider 130 can send a contract product query request to the smart contract center management institution 110 (step S1041), and the smart contract center management institution 110 forwards it to the smart contract operation management institution 120 (step S1042). The smart contract operation management institution 120 generates and returns a contract product query response to the smart contract center management institution 110 (step S1043), and the smart contract center management institution 110 forwards the contract product query response to the smart contract service provider 130 (step S1044). In one specific embodiment, the contract product query response includes at least the contract product ID and its associated contract template ID.

[0100] In one specific embodiment, the query process can be further divided into list query and detail query. For example, the smart contract service provider 130 can first send a contract product list query request to the smart contract center management provider 110. This request may include the smart contract service provider identifier, and may further include the identifier of the smart contract operation management provider to be queried. The smart contract center management provider 110 sends a contract product list query response message generated by the smart contract operation management provider 120 back to the smart contract service provider 130. The response message may include, for example, the contract product identifier, the smart contract operation management provider identifier, the smart contract service provider identifier, the contract product name, the contract product description, and the contract template identifier. For contract products for which further details are desired, the smart contract service provider 130 can further send a contract product detail query request to the smart contract center management provider 110. This request may include the contract product identifier and the smart contract service provider identifier. The smart contract center management organization 110 sends a response message to the smart contract service organization 130, generated by the smart contract operation management organization 120, regarding the query of contract product details. The response message includes, for example, the contract product identifier, the smart contract operation management organization identifier, the smart contract service organization identifier, the contract product name, the contract product description, the contract template identifier, and the contracting party information. The specific fields of the response message can be configured as needed.

[0101] The smart contract operation management organization 120, upon receiving a contract instance confirmation instruction from the relevant signatory (including the user wallet), deploys the contract instance in the smart contract operation environment 121 (step S1046). The contract instance 13 includes information such as a contract product identifier, a contract instance identifier, and a contract wallet identifier. The contract product identifier establishes an association between the contract instance 13 and the contract product 12. In one specific embodiment, when deploying the contract instance 13, the user wallet can be bound to the contract instance 13, and the user wallet identifier can be used as the contract wallet identifier. In another specific embodiment, when deploying the contract instance 13, a sub-wallet can also be generated under the user wallet, bound to the contract instance 13, and the sub-wallet identifier can be used as the contract wallet identifier.

[0102] In one specific embodiment, the smart contract operation management organization 120 sends the smart contract signing result to the smart contract service organization 130 (step S1047') and the contract instance deployment result to the smart contract center management organization 110 (step S1047). The contract instance deployment result includes the contract product ID, the contract instance ID, and the contract wallet ID. The smart contract center management organization 110 can receive and save the contract instance deployment result, establish the correspondence between the contract template, contract product, contract instance, and contract wallet, and verify it during subsequent smart contract calls. It can also be easily queried by users, the smart contract service organization 130, etc.

[0103] Figure 6 shows a schematic diagram of the main modules of a smart contract deployment device 600 according to at least one embodiment of the present disclosure. The smart contract deployment device 600 is applied to a smart contract operation management organization 120 and includes a contract template deployment module 610, a contract product deployment module 620, and a contract instance deployment module 630.

[0104] The contract template deployment module 610 is configured to deploy the contract template 11 based on the modular environment interface 1212 in response to a contract template deployment instruction generated by the smart contract center management agency 110 according to the contract template registration request sent by the smart contract developer 140. In one specific embodiment, the contract template 11 includes interface information, contract template code, contract template identifier, and template parameter information to be configured.

[0105] The contract product deployment module 620 is configured to deploy contract product 12 in response to receiving a contract product deployment instruction generated by the smart contract center management organization 110 based on a contract product creation request sent by the smart contract service organization 130. In one specific embodiment, contract product 12 includes a contract template identifier, a contract product identifier, and configuration parameters, wherein the configuration parameters are used to configure the template parameter information to be configured.

[0106] The contract instance deployment module 630 is configured to deploy contract instance 13 in response to receiving a contract instance signing instruction sent by the smart contract service provider 130 and a contract instance confirmation instruction sent by the user wallet, which are forwarded by the smart contract center management agency 110. In one specific embodiment, contract instance 13 includes a contract product identifier, a contract instance identifier, and a contract wallet identifier.

[0107] Figure 8 illustrates an interactive flowchart of a smart contract deployment method 800 according to at least one embodiment of the present disclosure. The method is applied to a smart contract central management organization 110 and includes:

[0108] In step S801, the contract template management module 111 is configured to generate and send a contract template deployment instruction to the smart contract runtime management organization 120 in response to receiving a contract template registration request from the smart contract developer 140, so that the smart contract runtime management organization 120 can deploy the contract template 11 based on the modular environment interface 1212. In a specific embodiment, the contract template 11 includes interface information, contract template code, contract template identifier, and template parameter information to be configured.

[0109] In step S802, the contract product management module 112 is configured to generate and send a contract product deployment instruction to the smart contract operation management agency 120 in response to receiving a contract product creation request from the smart contract service agency 130, so that the smart contract operation management agency 120 deploys the contract product 12. In a specific implementation, the contract product 12 includes a contract template identifier, a contract product identifier, and configuration parameters, which are used to configure the template parameter information to be configured.

[0110] Step 803: The contract instance management module (not shown in the figure) receives and forwards the contract instance signing instruction sent by the smart contract service provider 130 to the smart contract operation management provider 120, so that the smart contract operation management provider 120 deploys the contract instance 13 based on the contract instance signing instruction and the contract instance confirmation instruction sent by the user wallet. In a specific embodiment, the contract instance 13 includes a contract product identifier, a contract instance identifier, and a contract wallet identifier.

[0111] Figure 9 illustrates an interactive flowchart of a smart contract execution method 900 according to at least one embodiment of the present disclosure. The method includes steps S901 and S902.

[0112] Step S901, the smart contract loading module (not shown in the figure) is configured to load the contract instance 13, contract product 12 and contract template 11 into the virtual machine 1211 in response to receiving a smart contract trigger instruction.

[0113] It is understood that contract instance 13, contract product 12, and contract template 11 are deployed according to the smart contract steps and methods of this disclosure embodiment. The smart contract triggering instruction can be a fund transfer instruction for the contract wallet (the contract wallet is bound to contract instance 13, and contract instance 13 can be identified through the contract wallet), or it can be a contract call instruction for contract instance 13; this disclosure does not limit this. Based on the smart contract triggering instruction, the associated contract product 12 is obtained according to contract instance 13, the associated contract template 11 is obtained according to contract product 12, contract instance 13, contract product 12, and contract template 11 are verified, and if the verification is successful, contract instance 13, contract product 12, and contract template 11 are loaded into virtual machine 1211.

[0114] Step S902, virtual machine 1211 is configured to execute contract instance 13.

[0115] Virtual machine 1211 executes contract instance 13 and sends transaction instructions to the core system 122 of smart contract operation management institution 120 through environment interface 1212 to complete the transaction. In one embodiment, when the transaction is a cross-institutional transaction, the core system 122 generates a cross-institutional transaction message and sends it to the transaction transfer service module 113 of smart contract central management institution 110 to complete the transaction. In this embodiment, smart contract central management institution 110, as a centralized system, can be connected to the core systems 122 of multiple smart contract operation management institutions 120 through the transaction transfer service module 113. When the transaction transfer service module 113 receives a cross-institutional transaction message sent by the core system 122 of a smart contract operation management institution 120, it can verify the cross-institutional transaction message, and after successful verification, forward it to the core system 122 of the counterparty (other smart contract operation management institutions 120) for processing and receive its response to complete the transaction.

[0116] The embodiments disclosed herein abstract smart contracts into multiple layers, including environment interfaces, contract templates, contract products, and contract instances, supporting participants in managing smart contracts through layer-by-layer parameterized configuration. Simultaneously, a central management organization for smart contracts can supervise and deploy contract templates and contract products, while individual smart contract operation management organizations can run contract instances. This achieves centralized management and distributed operation of smart contracts, contributing to improved efficiency in ecosystem supervision and contract execution.

[0117] It should be noted that the above application scenarios are merely exemplary, intended to describe one or more aspects of this disclosure in specific scenarios. However, these aspects are not essential, and various modifications can be made to the application scenario. It is readily understood that the specific application scenarios described in this disclosure are not limited.

[0118] At least some embodiments of this disclosure also provide an electronic device. FIG10 shows a schematic diagram of an electronic device 1000 according to at least one embodiment of this disclosure.

[0119] As shown in Figure 10, the electronic device 1000 includes one or more processors 1010 and a memory 1020. The memory 1020 includes one or more computer program modules 1021. These computer program modules 1021 are stored in the memory 1020 and are executed by the processor 1010. Each computer program module 1021 includes instructions for executing a smart contract deployment method, a smart contract execution method, and additional aspects thereof according to at least one embodiment of the present disclosure. When executed by the processor 1010, these instructions can perform one or more steps of the smart contract deployment method, smart contract execution method, and additional aspects thereof according to at least one embodiment of the present disclosure. The memory 1020 and the processor 1010 can be interconnected via a bus system and / or other forms of connection mechanisms (not shown). For example, the bus can be a Peripheral Component Interconnect Standard (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc.

[0120] For example, processor 1010 may be a central processing unit (CPU), a digital signal processor (DSP), or other processing unit with data processing capabilities and / or program execution capabilities, such as a field-programmable gate array (FPGA). Processor 1010 may be a general-purpose processor or a special-purpose processor, capable of controlling other components in electronic device 1000 to perform desired functions.

[0121] Exemplarily, memory 1020 may include any combination of one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, erasable programmable read-only memory (EPROM), portable compact disc read-only memory (CD-ROM), USB memory, flash memory, etc. One or more computer program modules 1021 may be stored on the computer-readable storage medium, and processor 1010 may run one or more computer program modules 1021 to implement various functions of electronic device 1000. The computer program modules include multiple computer-executable instructions. Various application programs and various data, as well as various data used and / or generated by the application programs, may also be stored in the computer-readable storage medium.

[0122] For example, electronic device 1000 may also include input devices such as touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, and gyroscopes; output devices such as liquid crystal displays, speakers, and vibrators; storage devices such as magnetic tapes and hard disks (HDDs or SDDs); and communication devices such as network interface cards like LAN cards and modems. The communication devices allow electronic device 1000 to communicate wirelessly or wiredly with other devices to exchange data and perform communication processing via networks such as the Internet. A drive is connected to the I / O interface as needed. Removable storage media, such as disks, optical disks, magneto-optical disks, and semiconductor memories, are installed on the drive as needed so that computer programs read from them can be installed into the storage device as required.

[0123] For example, the electronic device 1000 may further include a peripheral interface (not shown in the figure). This peripheral interface can be of various types, such as a USB interface, a Lightning interface, etc. The communication device can communicate wirelessly with networks and other devices, such as the Internet, intranets and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs). Wireless communication can use any of a variety of communication standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Wi-Fi (e.g., based on IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11n standards), Voice over Internet Protocol (VoIP), Wi-MAX, protocols for email, instant messaging, and / or Short Message Service (SMS), or any other suitable communication protocol.

[0124] The electronic device 1000 may be, for example, a system-on-a-chip (SOC) or a device including the SOC. It can be any device such as a mobile phone, tablet, laptop, e-reader, game console, television, digital photo frame, navigator, home appliance, communication base station, industrial controller, server, etc., or any combination of data processing devices and hardware. The embodiments of this disclosure do not limit this. The specific functions and technical effects of the electronic device 1000 can be found in the description above of the smart contract deployment method, smart contract execution method, and additional aspects according to at least one embodiment of this disclosure, and will not be repeated here.

[0125] Figure 11 shows a schematic diagram of a readable storage medium 1100 according to at least one embodiment of the present disclosure.

[0126] As shown in Figure 11, a computer program 1110 is stored on a readable storage medium 1100, which is a computer-readable storage medium. When the computer program 1110 is executed by a processor, it performs one or more steps of the smart contract deployment method, smart contract execution method and its additional aspects as described above.

[0127] For example, when the program code is read by a computer, the computer can execute the program code stored in the computer storage medium to perform one or more steps to implement, for example, the smart contract deployment method, the smart contract execution method, and additional aspects thereof according to at least one embodiment of the present disclosure.

[0128] For example, the readable storage medium may include a memory card of a smartphone, a storage component of a tablet computer, a hard disk of a personal computer, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), portable compact disc read-only memory (CD-ROM), flash memory, and other readable storage media or any combination thereof. The readable storage medium 1100 may be a non-transitory readable storage medium.

[0129] At least some of the embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other.

[0130] It should be noted that, in this disclosure, relational terms such as "first," "second," etc., are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0131] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, or they may sometimes be executed in reverse order, depending on the functions involved; that is, the preceding or following operations are not necessarily executed precisely in sequence. Instead, various steps may be processed in reverse order or simultaneously as needed. Furthermore, other operations may be added to these processes, or one or more operations may be removed from these processes.

[0132] The units described in the embodiments of this disclosure can be implemented in software or hardware. The described units can also be located in a processor. The names of these units do not, in some cases, constitute a limitation on the unit itself.

[0133] The following points should be noted regarding this disclosure:

[0134] (1) The accompanying drawings of the embodiments of this disclosure only involve the structures involved in the embodiments of this disclosure. Other structures can be referred to the general design.

[0135] (2) Where there is no conflict, the embodiments of this disclosure and the features in the embodiments can be combined with each other to obtain new embodiments.

[0136] The above are merely exemplary embodiments of this disclosure and are not intended to limit the scope of protection of this disclosure, which is determined by the appended claims.

Claims

1. A smart contract deployment method, applied to a smart contract operation and management organization, the method comprising: In response to receiving a contract template deployment instruction generated by the smart contract center management agency based on a contract template registration request sent by a smart contract developer, the contract template is deployed based on a modular environment interface, wherein the contract template includes interface information, contract template code, contract template identifier, and template parameter information to be configured; In response to receiving a contract product deployment instruction generated by the smart contract center management organization based on a contract product creation request sent by the smart contract service organization, the contract product is deployed. The contract product includes the contract template identifier, the contract product identifier, and configuration parameters, wherein the configuration parameters are used to configure the template parameter information to be configured. In response to receiving the contract instance signing instruction sent by the smart contract service provider and the contract instance confirmation instruction sent by the user wallet, which are forwarded by the smart contract center management authority, a contract instance is deployed, wherein the contract instance includes the contract product identifier, the contract instance identifier, and the contract wallet identifier.

2. The method according to claim 1, wherein, The system receives a contract product query request forwarded by the smart contract center management organization from the smart contract service organization, and generates a contract product query response, wherein the contract product query response includes the contract template identifier and the contract product identifier.

3. The method according to claim 1, wherein, The deployment contract instance includes: Bind the user wallet to the contract instance, and use the user wallet identifier as the contract wallet identifier; or A sub-wallet is generated under the user wallet, the sub-wallet is bound to the contract instance, and the identifier of the sub-wallet is used as the identifier of the contract wallet.

4. The method according to claim 1, wherein, Send the contract instance deployment result to the smart contract center management agency, wherein the contract instance deployment result includes the contract product identifier, the contract instance identifier, and the contract wallet identifier.

5. A smart contract deployment method, applied to a smart contract central management organization, the method comprising: In response to receiving a contract template registration request from a smart contract developer, a contract template deployment instruction is generated and sent to the smart contract operation and management organization, so that the smart contract operation and management organization can deploy the contract template based on a modular environment interface. The contract template includes interface information, contract template code, contract template identifier, and template parameter information to be configured. In response to receiving a contract product creation request from a smart contract service provider, a contract product deployment instruction is generated and sent to the smart contract operation management provider to enable the smart contract operation management provider to deploy the contract product. The contract product includes a contract template identifier, a contract product identifier, and configuration parameters, wherein the configuration parameters are used to configure the template parameter information to be configured. The system receives and forwards the contract instance signing instruction sent by the smart contract service provider to the smart contract operation management organization, so that the smart contract operation management organization can deploy the contract instance based on the contract instance signing instruction and the contract instance confirmation instruction sent by the user wallet. The contract instance includes the contract product identifier, the contract instance identifier, and the contract wallet identifier.

6. The method according to claim 5, wherein, Receive and save the contract instance deployment results obtained by the smart contract operation management organization, wherein the contract instance deployment results include the contract product identifier, the contract instance identifier, and the contract wallet identifier.

7. The method according to claim 5, wherein, Receive a contract template query request sent by the smart contract service provider, and return a contract template query response, wherein the contract template query response includes the contract template identifier; and / or, The system forwards the contract product query request sent by the smart contract service provider to the smart contract operation management organization, and receives the contract product query response returned by the smart contract operation management organization, wherein the contract product query response includes the contract template identifier and the contract product identifier.

8. The method according to claim 5, wherein, The step of responding to a contract template registration request sent by a smart contract developer, generating and sending a contract template deployment instruction to the smart contract runtime management organization, includes: Receive a contract template registration request sent by the smart contract developer, the contract template registration request including contract template code and template parameter information to be configured; Review the contract template registration request; and If the review is approved, the contract template deployment instruction is generated and sent to the smart contract operation management organization.

9. The method according to claim 5, wherein, The step of responding to receiving a contract product creation request from a smart contract service provider and generating and sending a contract product deployment instruction to the smart contract operation management provider includes: Receive a contract product creation request sent by the smart contract service provider, wherein the contract product creation request includes the contract template identifier and configuration parameters; The contract product creation request was reviewed; and If the review is approved, a contract product deployment instruction is generated and sent to the smart contract operation management organization.

10. A smart contract execution method, applied to a smart contract operation management organization, wherein the smart contract is deployed according to the smart contract deployment method of claim 1, the method comprising: In response to receiving a smart contract trigger instruction, the contract instance, the contract product, and the contract template are loaded into the virtual machine; as well as The virtual machine executes the contract instance.

11. The method according to claim 10, wherein, The step of loading the contract instance, the contract product, and the contract template into the virtual machine in response to receiving a smart contract trigger instruction includes: Receive a smart contract trigger instruction, obtain the associated contract product based on the contract instance, obtain the associated contract template based on the contract product, verify the contract instance, the contract product and the contract template, and if the verification is successful, load the contract instance, the contract product and the contract template into the virtual machine.

12. The method according to claim 10 or 11, wherein, The virtual machine executes the contract instance, including: The virtual machine executes the contract instance and sends transaction instructions to the core system of the smart contract operation and management organization through the environment interface to complete the transaction.

13. The method according to claim 12, wherein, The core system generates cross-institutional transaction messages and sends these messages to the smart contract center management organization to complete the transaction.

14. A smart contract deployment device, applied to a smart contract operation and management organization, the device comprising: The contract template deployment module is configured to deploy a contract template based on a modular environment interface in response to a contract template deployment instruction generated by the smart contract center management agency based on a contract template registration request sent by a smart contract developer. The contract template includes interface information, contract template code, contract template identifier, and template parameter information to be configured. The contract product deployment module is configured to deploy a contract product in response to receiving a contract product deployment instruction generated by the smart contract center management agency based on a contract product creation request sent by the smart contract service agency. The contract product includes a contract template identifier, a contract product identifier, and configuration parameters, wherein the configuration parameters are used to configure the template parameter information to be configured. The contract instance deployment module is configured to deploy a contract instance in response to receiving a contract instance signing instruction sent by the smart contract service provider and a contract instance confirmation instruction sent by the user wallet, which are forwarded by the smart contract center management agency. The contract instance includes the contract product identifier, the contract instance identifier, and the contract wallet identifier.

15. A smart contract deployment device, applied to a smart contract central management organization, the device comprising: The contract template management module is configured to generate and send a contract template deployment instruction to the smart contract operation management organization in response to receiving a contract template registration request from a smart contract developer, so that the smart contract operation management organization can deploy the contract template based on a modular environment interface. The contract template includes interface information, contract template code, contract template identifier, and template parameter information to be configured. The contract product management module is configured to, in response to receiving a contract product creation request from a smart contract service provider, generate and send a contract product deployment instruction to the smart contract operation management provider, so that the smart contract operation management provider deploys the contract product. The contract product includes a contract template identifier, a contract product identifier, and configuration parameters, wherein the configuration parameters are used to configure the template parameter information to be configured. The contract instance management module receives and forwards the contract instance signing instruction sent by the smart contract service provider to the smart contract operation management organization, so that the smart contract operation management organization can deploy the contract instance based on the contract instance signing instruction and the contract instance confirmation instruction sent by the user wallet. The contract instance includes the contract product identifier, the contract instance identifier, and the contract wallet identifier.

16. A smart contract execution device, applied to a smart contract operation management organization, wherein the smart contract is deployed according to the smart contract deployment device of claim 14, the device comprising: The smart contract loading module is configured to load the contract instance, the contract product, and the contract template into the virtual machine in response to receiving a smart contract trigger instruction; The virtual machine is configured to execute the contract instance.

17. An electronic device comprising: One or more processors; as well as Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-13.

18. A computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the method as described in any one of claims 1-13.

Images