Smart contract management method, device, terminal equipment and medium

Abstract

This application relates to the field of blockchain technology, and in particular to a smart contract management method, apparatus, terminal device, and medium. The method obtains a list interface of target smart contract components through a smart contract management interface. Based on the address list in this list interface, it obtains a framework form for the target operation, retrieves a form after the user has filled in the content of the target operation in the framework form, and calls the target smart contract component through the smart contract management interface to execute the content in the form. This allows for modification or addition of smart contract components based on the content of the target operation, simplifying the modification or addition process and facilitating the management of smart contract components.

Description

Technical Field

[0001] The present application belongs to the field of blockchain technology, and in particular, relates to a smart contract management method, apparatus, terminal device and medium. Background Art

[0002] There are many types of blockchains, such as Fabric and Ethereum. Different types of blockchains provide different types of smart contract management engines, smart contract languages, and software development kit (SDK) languages. For example, the Fabric blockchain provides an execution engine for the Docker environment, supports smart contracts in the Go language, and supports SDKs in languages ​​such as Go and Java. Another example is that the Ethereum blockchain provides an Ethereum Virtual Machine (EVM) execution engine, supports smart contracts in languages ​​such as Solidity and Vyper, and supports SDKs in languages ​​such as Go and JavaScript. It can be seen that different types of blockchains, smart contract management engines, smart contract languages, and SDK languages ​​can constitute many types of smart contracts. Therefore, when modifying or adding a smart contract, it is necessary to edit the blockchain, smart contract management engine, smart contract language, and SDK language one by one. The modification or addition process is relatively complicated and inconvenient for the management of smart contracts. Summary of the invention

[0003] The embodiments of the present application provide a smart contract management method, apparatus, terminal device and medium, which can solve the problem that existing smart contracts are difficult to manage.

[0004] In a first aspect, an embodiment of the present application provides a smart contract management method, the smart contract management method comprising:

[0005] Obtain a list interface of a target smart contract component, where the list interface is a list of addresses for at least one operation under the target smart contract component;

[0006] According to the list interface of the target smart contract component, obtain a framework form corresponding to the target operation in the at least one operation, wherein the framework form is used to fill in the content of the target operation;

[0007] According to the frame form, an execution form is obtained, wherein the execution form is a form fed back by the user after filling in the content of the target operation in the frame form;

[0008] Call the target smart contract component to execute the content of the target operation in the execution form.

[0009] In a second aspect, an embodiment of the present application provides a smart contract management device, the smart contract management device comprising:

[0010] An interface acquisition module, used to acquire a list interface of a target smart contract component, wherein the list interface is an address list for at least one operation under the target smart contract component;

[0011] A framework form acquisition module, used to acquire a framework form corresponding to a target operation in the at least one operation according to the list interface of the target smart contract component, wherein the framework form is used to fill in the content of the target operation;

[0012] An execution form acquisition module is used to acquire an execution form according to the frame form, wherein the execution form is a form fed back by the user after filling in the content of the target operation in the frame form;

[0013] The execution operation module is used to call the target smart contract component and execute the content of the target operation in the execution form.

[0014] In a third aspect, an embodiment of the present application provides a terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the smart contract management method as described in the first aspect is implemented.

[0015] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the smart contract management method as described in the first aspect is implemented.

[0016] In a fifth aspect, an embodiment of the present application provides a computer program product, which, when executed on a terminal device, enables the terminal device to execute the smart contract management method described in the first aspect above.

[0017] Compared with the prior art, the embodiments of the present application have the following beneficial effects: the present application obtains the list interface of the target smart contract component through the interface of smart contract management, obtains the framework form of the target operation according to the address list in the list interface, obtains the form after the user fills in the content of the target operation in the framework form, and calls the target smart contract component through the interface of smart contract management to execute the content in the form, so that the smart contract component can be modified or added according to the content of the target operation, making the process of modifying or adding the smart contract component relatively simple, which is conducive to the management of the smart contract component. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0019] Figure 1 This is a flowchart of a smart contract management method provided in Example 1 of the present application;

[0020] Figure 2 This is a flowchart of a smart contract management method provided in Example 2 of the present application;

[0021] Figure 3 It is a structural diagram of a smart contract management device provided in Example 3 of the present application;

[0022] Figure 4 It is a structural diagram of a terminal device provided in Example 4 of the present application. DETAILED DESCRIPTION

[0023] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0024] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0025] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0026] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0027] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0028] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0029] The smart contract management method provided in the embodiment of the present application can be applied to terminal devices such as handheld computers, desktop computers, laptops, ultra-mobile personal computers (UMPCs), netbooks, cloud servers, personal digital assistants (PDAs), etc. The embodiment of the present application does not impose any restrictions on the specific type of terminal devices.

[0030] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0031] In order to illustrate the technical solution of the present application, a specific embodiment is provided below for illustration.

[0032] See also Figure 1 , is a flow chart of a smart contract management method provided in the first embodiment of the present application. The smart contract management method can be used in a terminal device. As shown in the figure, the smart contract management method can include the following steps:

[0033] Step S101, obtain the list interface of the target smart contract component.

[0034] Among them, the smart contract component may refer to the architecture of an artificially developed smart contract, which is used to implement at least one operation on a type of resource using a type of implementation language under a type of blockchain. Therefore, the target smart contract component may refer to at least one operation on a target resource using a target implementation language under a target blockchain. The list interface is an address list for the architecture of the smart contract, that is, the specific manifestation of the smart contract component in the device, and the application structure of the target smart contract component may refer to the address list for at least one operation under the target smart contract component.

[0035] For example, develop a smart contract component that supports Fabric blockchain, smart contract resources, Go contract implementation language under Gosdkv1.0.0-beta1 and Docker execution environment, and supports contract deployment, calling and upgrade operations. The corresponding manifest interface is as follows, where the identity document (ID) is used to indicate the name of Fabric blockchain, smart contract resources, Go contract implementation language under Gosdkv1.0.0-beta1 and Docker execution environment, and deployment, calling and upgrade operations. "name" is used to indicate the name of Fabric blockchain, smart contract resources, Go contract implementation language under Gosdkv1.0.0-beta1 and Docker execution environment, and deployment, calling and upgrade operations. "description" is used to indicate the description of Fabric blockchain, smart contract resources, Go contract implementation language under Gosdkv1.0.0-beta1 and Docker execution environment, and deployment, calling and upgrade operations:

[0036]

[0037]

[0038] Step S102: Obtain a framework form corresponding to a target operation in at least one operation according to the list interface of the target smart contract component.

[0039] Among them, the list interface of the above-mentioned target smart contract component includes an address list of at least one operation, and each operation in the at least one operation corresponds to a framework form. The target operation in the at least one operation is selected according to user needs, and the framework form corresponding to the target operation is obtained. The framework form may refer to a program with a fixed framework or format. The framework form may include a framework for filling in the content of the target operation. The content of the target operation may refer to specific parameters, configurations and other information for the target operation. The content of the target operation can be filled in according to user needs. For example, the target operation is the deployment operation in the example of step S101 above. The framework form of the deployment operation is as follows. In the example, the validateDes needs to enter the compressed package (byte stream) of the Go contract code in tar.gz format, which is the content filled in by the user. Other contents are not repeated here. "configName" is used to indicate the name of the framework form, "description" is used to indicate the description of the framework form, and "configs" indicates the framework form:

[0040]

[0041]

[0042] Optionally, according to the list interface of the target smart contract component, obtaining a framework form corresponding to the target operation in at least one operation includes:

[0043] According to the list interface of the target smart contract component, obtain the form path of the target operation in at least one operation, where the form path is a path determined according to the implementation path of the target operation;

[0044] Get the frame form according to the form path.

[0045] Among them, there is at least one operation in the list interface of the target smart contract component. The user determines the target operation in at least one operation according to the needs, that is, the form path corresponding to the target operation can be determined. The form path is determined by the corresponding blockchain ID, resource ID, implementation language ID and operation ID in the list interface of the smart contract component.

[0046] For example, referring to the example of step S101 above, when the target operation is a deployment operation, the blockchain ID is fab141, the resource ID is contract, the implementation language ID is gosdk100beta1dockergo14, and the deployment operation ID is deploy. Therefore, the form path for the deployment operation can be expressed as fab141 / contract / gosdk100beta1dockergo14 / deploy. According to the form path, a framework form can be uniquely determined, that is, a framework form for performing deployment operations on smart contract resources using GoSDKv1.0.0-beta1 and the Gov1.4 language in the Docker execution environment under the blockchain version of Fabricv1.4.1.

[0047] Optionally, after obtaining the framework form corresponding to the target operation in at least one operation according to the list interface of the target smart contract component, the method further includes:

[0048] Get the content corresponding to the target operation entered by the user in the frame form.

[0049] The terminal device may interact with the front end (ie, the user end), and outputting the frame form may be outputting the frame form from the terminal device to the front end for display, and the user may input content corresponding to the target operation in the output frame form.

[0050] Step S103, obtaining the execution form according to the framework form.

[0051] Among them, the execution form is a form that is fed back after the user fills in the content of the target operation in the framework form. For example, in the example of step S102 above, a compressed package (byte stream) of the Go contract code tar.gz format is input at validateDes. The input compressed package (byte stream) of the Go contract code tar.gz format is one of the contents of the target operation. After the user fills in the part that needs to be filled in or input in the framework form, an execution form is generated.

[0052] Optionally, based on the form path, obtaining the frame form includes:

[0053] Obtain a mapping table, the mapping table including a form path and a frame form corresponding to the form path;

[0054] Get the framework form based on the form path and mapping table.

[0055] The mapping table stores at least one form path and a framework form corresponding to each form path. The framework form corresponding to the form path can be obtained in the mapping table according to the form path.

[0056] Step S104, calling the target smart contract component to execute the content of the target operation in the execution form.

[0057] Among them, the list interface of the target smart contract component is a list of addresses corresponding to at least one operation executed on the target resource using the target implementation language under the target blockchain. An execution form is added to the address list so that the content of the target operation in the execution form can be executed.

[0058] Optionally, calling the target smart contract component to execute the target operation in the execution form includes:

[0059] According to the list interface of the target smart contract component, obtain the address list of the target operation;

[0060] According to the address list of the target operation, the content of the target operation in the execution form is executed.

[0061] Among them, the address list corresponding to the target operation is obtained from the address list corresponding to at least one operation included in the list interface of the target smart contract component, and an execution form is added to the address list corresponding to the target operation to realize the execution of the content of the target operation in the execution form, thereby avoiding the generation of other operations.

[0062] Optionally, the address list of the target operation includes: a target blockchain, a target resource, and a target implementation language for implementing the target operation;

[0063] Accordingly, according to the address list of the target operation, the content of executing the target operation in the execution form includes:

[0064] In the target blockchain, the target operation in the execution form is executed on the target resource using the target implementation language.

[0065] Among them, the list interface of the target smart contract component includes the target blockchain, target resources and target implementation language. The content part of the target operation in the list interface of the target execution contract component is empty. The content of the target operation in the execution form is added to the list interface to form a complete program. The execution of the complete program is the content of the target operation in the execution form, that is, the target operation is performed on the target resources using the target implementation language in the target blockchain. For example, referring to the example of step S101 above, after obtaining the execution form of the deployment operation, the GoSDKv1.0.0-beta1 and the Gov1.4 language in the Docker execution environment are used under the blockchain version of Fabricv1.4.1 to perform the deployment operation on the smart contract resources, wherein the content of the deployment operation is the content of the deployment operation in the execution form.

[0066] The embodiment of the present application obtains the list interface of the target smart contract component through the interface of smart contract management, obtains the framework form of the target operation according to the address list in the list interface, obtains the form after the content of the target operation is filled in the framework form as feedback from the user, and calls the target smart contract component through the interface of smart contract management to execute the content in the form, so that the smart contract component can be modified or added according to the content of the target operation, making the process of modifying or adding the smart contract component relatively simple, which is conducive to the management of the smart contract component.

[0067] See also Figure 2 , is a flow chart of a smart contract management method provided in Embodiment 2 of the present application. The smart contract management method can be used in a terminal device. As shown in the figure, the smart contract management method can include the following steps:

[0068] Step S201, obtain a list of smart contract components.

[0069] Among them, the smart contract component list includes identification information of at least one developed smart contract component, the developed smart contract components are stored in the terminal device, and each smart contract component corresponds to identification information representing the smart contract component. When the terminal device is used to run the smart contract management method, the identification information of the smart contract component in the terminal device is scanned to generate a smart contract component list.

[0070] Step S202, obtaining identification information selected by the user from the smart contract component list, and determining that the developed smart contract corresponding to the identification information is the target smart contract component.

[0071] Among them, the terminal device interacts with the front end (i.e., the user end) for data, and the terminal device outputs the generated smart contract component list to the front end for display. The user can know the smart contract components that have been developed in the terminal device based on the displayed smart contract component list.

[0072] In the front-end interface, the user triggers a selection instruction to select the identification information of a smart contract component from the smart contract component list, and the front-end sends the selection instruction to the terminal device. The terminal device receives the selection instruction, which is to obtain the identification information of the target smart contract component selected by the user from the output smart contract component list.

[0073] Step S203: Obtain the list interface of the target smart contract component according to the identification information of the target smart contract component.

[0074] Among them, after the user selects the identification information of the target smart contract component, the target smart contract component is found in the terminal device according to the identification information of the target smart contract component. The specific manifestation of the target smart contract component in the device is the list interface of the target smart contract component. The target smart contract component and the list interface have been explained in the above step S101, which will not be repeated here.

[0075] Step S204: Obtain a framework form corresponding to a target operation in at least one operation according to the list interface of the target smart contract component.

[0076] Step S205: Obtain the execution form according to the framework form.

[0077] Step S206, calling the target smart contract component to execute the content of the target operation in the execution form.

[0078] Among them, the contents of step S204 to step S206 are the same as those of the above-mentioned step S102 to step S104, and the description of step S102 to step S104 may be referred to, and will not be repeated here.

[0079] When the terminal device runs the smart contract management method, the application scans all smart contract components in the terminal device, generates a list of smart contract components, and outputs the list of smart contract components to the front-end display, obtains the target smart contract component selected by the user from the list of smart contract components displayed on the front-end, and the target operation selected by the user in at least one operation in the list interface of the target smart contract component, the terminal device obtains the framework form corresponding to the target operation, and outputs the framework form to the front-end display, obtains the execution form fed back after the content of the target operation filled in by the user in the framework form, and executes the content of the target operation in the execution form according to the list interface of the target smart contract component, so as to realize the execution of the target operation on the target resource using the target implementation language under the target blockchain, and the content of the target operation is the content of the target operation in the execution form.

[0080] The embodiment of the present application scans the developed smart contract components in the terminal device, generates a smart contract component list, and outputs the smart contract component list for users to query and select, which is convenient for users to use and avoids users from selecting smart contract components that have not yet been developed.

[0081] Corresponding to the smart contract management method in the above embodiment, Figure 3 A structural block diagram of the smart contract management device provided in Example 3 of the present application is shown. For the sake of convenience of explanation, only the parts related to the embodiment of the present application are shown.

[0082] See also Figure 3 , the smart contract management device includes:

[0083] An interface acquisition module 31 is used to acquire a list interface of a target smart contract component, where the list interface is a list of addresses for at least one operation under the target smart contract component;

[0084] A framework form acquisition module 32, used to acquire a framework form corresponding to a target operation in at least one operation according to the list interface of the target smart contract component, and the framework form is used to fill in the content of the target operation;

[0085] The execution form acquisition module 33 is used to acquire the execution form according to the frame form, where the execution form is the form that the user returns after filling in the content of the target operation in the frame form;

[0086] The execution operation module 34 is used to call the target smart contract component and execute the content of the target operation in the execution form.

[0087] Optionally, the smart contract management device further includes:

[0088] A list acquisition module, used to acquire a list of smart contract components, where the list of smart contract components includes identification information of at least one developed smart contract component;

[0089] An identification information acquisition module, used to obtain the identification information selected by the user from the smart contract component list, and determine that the developed smart contract corresponding to the identification information is the target smart contract component;

[0090] Accordingly, the interface acquisition module 31 is specifically used for:

[0091] According to the identification information of the target smart contract component, obtain the list interface of the target smart contract component.

[0092] Optionally, the framework form acquisition module 32 includes:

[0093] A path acquisition unit, used to acquire a form path of a target operation in at least one operation according to a list interface of a target smart contract component, where the form path is a path determined according to an implementation path of the target operation;

[0094] The frame form acquisition unit is used to acquire the frame form according to the form path.

[0095] Optionally, the framework form acquisition unit is specifically used for:

[0096] Obtain a mapping table, the mapping table including a form path and a frame form corresponding to the form path;

[0097] Get the framework form based on the form path and mapping table.

[0098] Optionally, the execution operation module 34 includes:

[0099] A description acquisition unit is used to obtain the address list of the target operation according to the list interface of the target smart contract component;

[0100] The execution operation unit is used to execute the content of the target operation in the execution form according to the address list of the target operation.

[0101] Optionally, the address list of the target operation includes: a target blockchain, a target resource, and a target implementation language for implementing the target operation;

[0102] Accordingly, the above-mentioned execution operation unit is specifically used for:

[0103] In the target blockchain, the target implementation language is used to execute the content of the target operation in the execution form on the target resource.

[0104] Optionally, the smart contract management device further includes:

[0105] The content acquisition module is used to obtain the content corresponding to the target operation entered by the user in the framework form after obtaining the framework form corresponding to the target operation in at least one operation according to the list interface of the target smart contract component.

[0106] It should be noted that the information interaction, execution process and other contents between the above-mentioned modules are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0107] Figure 4 This is a schematic diagram of the structure of a terminal device provided in Embodiment 4 of the present application. Figure 4 As shown, the terminal device 4 of this embodiment includes: at least one processor 40 ( Figure 4 (only one is shown in the figure) a processor, a memory 41, and a computer program 42 stored in the memory 41 and executable on at least one processor 40. When the processor 40 executes the computer program 42, the steps in any of the above-mentioned smart contract management method embodiments are implemented.

[0108] The terminal device may include, but is not limited to, a processor 40 and a memory 41. Those skilled in the art will appreciate that Figure 4 It is only an example of the terminal device 4 and does not constitute a limitation on the terminal device 4. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, it may also include input and output devices, network access devices, etc.

[0109] The processor 40 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0110] In some embodiments, the memory 41 may be an internal storage unit of the terminal device 4, such as a hard disk or memory of the terminal device 4. In other embodiments, the memory 41 may also be an external storage device of the terminal device 4, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the terminal device 4. Further, the memory 41 may also include both an internal storage unit and an external storage device of the terminal device 4. The memory 41 is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as program codes of computer programs. The memory 41 may also be used to temporarily store data that has been output or is to be output.

[0111] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned device can refer to the corresponding process in the above-mentioned method embodiment, which will not be repeated here. If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned method embodiment when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device capable of carrying computer program code, recording medium, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.

[0112] The present application implements all or part of the processes in the above-mentioned embodiment method, and may also be completed through a computer program product. When the computer program product runs on a terminal device, the terminal device implements the steps in the above-mentioned method embodiment when executing the computer program product.

[0113] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0114] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0115] In the embodiments provided in the present application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0116] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0117] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A smart contract management method, characterized in that: The smart contract management method includes: Obtain a list interface of a target smart contract component, where the list interface is a list of addresses for at least one operation under the target smart contract component; According to the list interface, a frame form corresponding to a target operation in the at least one operation is obtained, wherein the frame form is used to fill in the content of the target operation; specifically, the frame form includes a frame for filling in the content of the target operation, wherein the content of the target operation includes specific parameters and configuration information for the target operation; According to the frame form, an execution form is obtained, wherein the execution form is a form fed back by the user after filling in the content of the target operation in the frame form; Call the list interface of the target smart contract component to execute the content of the target operation in the execution form; The content of calling the list interface of the target smart contract component and executing the target operation in the execution form includes: According to the list interface of the target smart contract component, obtain the address list of the target operation; According to the address list of the target operation, execute the content of the target operation in the execution form; The address list of the target operation includes: a target blockchain, a target resource, and a target implementation language for implementing the target operation; Accordingly, the content of executing the target operation in the execution form according to the address list of the target operation includes: In the target blockchain, the target implementation language is used to execute the content of the target operation in the execution form on the target resource.

2. The smart contract management method according to claim 1, characterized in that: The smart contract management method further includes: Obtain a smart contract component list, wherein the smart contract component list includes identification information of at least one developed smart contract component; Obtaining identification information selected by a user from the smart contract component list, and determining that the developed smart contract corresponding to the identification information is the target smart contract component; Accordingly, the interface for obtaining the list of target smart contract components includes: According to the identification information of the target smart contract component, obtain the list interface of the target smart contract component.

3. The smart contract management method according to claim 1, characterized in that: The obtaining, according to the list interface of the target smart contract component, a framework form corresponding to the target operation in the at least one operation comprises: According to the list interface of the target smart contract component, obtain a form path of the target operation in the at least one operation, where the form path is a path determined according to an implementation path of the target operation; The frame form is obtained according to the form path.

4. The smart contract management method according to claim 3, characterized in that: The obtaining of the frame form according to the form path comprises: Acquire a mapping table, wherein the mapping table includes the form path and a framework form corresponding to the form path; The framework form is obtained according to the form path and the mapping table.

5. The smart contract management method according to any one of claims 1 to 4, characterized in that: After obtaining the framework form corresponding to the target operation in the at least one operation according to the list interface of the target smart contract component, the method further includes: The content corresponding to the target operation input by the user in the frame form is obtained.

6. A smart contract management device, characterized in that: The smart contract management device comprises: An interface acquisition module, used to acquire a list interface of a target smart contract component, wherein the list interface is an address list for at least one operation under the target smart contract component; A framework form acquisition module, used to acquire a framework form corresponding to a target operation in the at least one operation according to the list interface of the target smart contract component, wherein the framework form is used to fill in the content of the target operation; specifically, the framework form includes a framework for filling in the content of the target operation, wherein the content of the target operation includes specific parameters and configuration information for the target operation; An execution form acquisition module is used to acquire an execution form according to the frame form, wherein the execution form is a form fed back by the user after filling in the content of the target operation in the frame form; An execution operation module, used to call the target smart contract component and execute the content of the target operation in the execution form; The calling of the target smart contract component and the execution of the target operation in the execution form include: According to the list interface of the target smart contract component, obtain the address list of the target operation; According to the address list of the target operation, execute the content of the target operation in the execution form; The address list of the target operation includes: a target blockchain, a target resource, and a target implementation language for implementing the target operation; Accordingly, the content of executing the target operation in the execution form according to the address list of the target operation includes: In the target blockchain, the target implementation language is used to execute the content of the target operation in the execution form on the target resource.

7. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the smart contract management method according to any one of claims 1 to 5 is implemented.

8. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the smart contract management method as described in any one of claims 1 to 5 is implemented.

Images