WO2021102616A1

WO2021102616A1 - Smart contract development method and device, electronic apparatus, and storage medium

Info

Publication number: WO2021102616A1
Application number: PCT/CN2019/120516
Authority: WO
Inventors: 郭子雷; 来鑫; 陈磊
Original assignee: 深圳市网心科技有限公司
Priority date: 2019-11-25
Filing date: 2019-11-25
Publication date: 2021-06-03

Abstract

A smart contract development method and device, an electronic apparatus, and a computer-readable storage medium. The method comprises: acquiring smart contract source code, and using a compiler to compile the smart contract source code into bytecode; determining a language type of the bytecode, and determining, according to the language type, a virtual machine executing the bytecode; and determining an execution environment corresponding to the virtual machine, and executing the bytecode on the basis of the execution environment. By using the smart contract development method provided by the present application, a unified blockchain platform supports a variety of virtual machines, and is compatible with bytecode in a variety of languages, such that a user is not limited to a specific virtual machine, and a virtual machine in the blockchain is adaptable and pluggable.

Description

Smart contract development method, device, electronic equipment and storage medium

Technical field

This application relates to the field of blockchain technology, and more specifically, to a smart contract development method and device, an electronic device, and a computer-readable storage medium.

Background technique

Blockchain technology uses block chain data structures to verify and store data, uses distributed node consensus algorithms to generate and update data, uses cryptography to ensure the security of data transmission and access, and uses intelligence composed of automated script codes. A new distributed infrastructure and calculation method in which contracts are used to program and manipulate data.

In the early days of blockchain technology, for example, Bitcoin only had simple accounting functions, and then introduced flexible and programmable smart contracts, allowing users to deploy credible smart protocols on the blockchain, which greatly explored the development of blockchain technology potential.

In related technologies, different types of virtual machines can be used to develop smart contracts using different high-level languages. However, because the underlying bytecodes of different types of virtual machines cannot be interoperable, one set of code cannot run on multiple platforms or a single platform supports multiple bytecode formats, which restricts the promotion of smart contract applications and greatly hinders the block The development of chain technology.

Therefore, how to provide a unified blockchain platform to support smart contracts developed using different high-level languages on different types of virtual machines is a technical problem that needs to be solved by those skilled in the art.

Summary of the invention

The purpose of this application is to provide a smart contract development method and device, an electronic device, and a computer-readable storage medium, providing a unified blockchain platform, and supporting smart contracts developed on different types of virtual machines using different high-level languages. contract.

In order to achieve the above objectives, this application provides a smart contract development method, including:

Obtain the smart contract source code, and use a compiler to compile the smart contract source code into bytecode;

Determining the language type of the bytecode, and determining a virtual machine that executes the bytecode according to the language type;

The execution environment corresponding to the virtual machine is determined, and the bytecode is executed based on the execution environment.

Wherein, the execution of the bytecode based on the execution environment includes:

Determine an API list corresponding to the virtual machine; wherein the API list is a list that records API interfaces supported by the virtual machine;

When a target operation exists in the bytecode, determining whether there is an API interface corresponding to the target operation in the API list;

If yes, execute the target operation based on the execution environment.

Wherein, the execution of the target operation based on the execution environment includes:

Determine the target blockchain system corresponding to the target operation, and use the API interface corresponding to the target operation to execute the target operation on the target blockchain system based on the execution environment; wherein the API interface is API interface conforming to preset standards.

Wherein, after said using the API interface corresponding to the target operation to execute the target operation on the target blockchain system based on the execution environment, the method further includes:

Receive the operation result of the target blockchain system.

Wherein, the virtual machine includes any one or a combination of any of an evm type virtual machine, a wasm type virtual machine, and a jvm type virtual machine.

Wherein, the use of a compiler to compile the smart contract source code into bytecode includes:

Using a compiler to compile the smart contract source code into bytecode, and add an identifier corresponding to the language type of the bytecode to the bytecode;

Correspondingly, the determining the language type of the bytecode includes:

An identifier is obtained from the bytecode, and the language type of the bytecode is determined by identifying the identifier.

In order to achieve the above objective, this application provides a smart contract development device, including:

Compilation module, used to obtain the smart contract source code, and use a compiler to compile the smart contract source code into bytecode;

A determining module, configured to determine the language type of the bytecode, and determine a virtual machine that executes the bytecode according to the language type;

The execution module is used to determine the execution environment corresponding to the virtual machine, and execute the bytecode based on the execution environment.

To achieve the above objective, the present application provides an electronic device, the electronic device includes a memory and a processor, the memory stores a smart contract development program that can run on the processor, the smart contract development program When executed by the processor, it is realized: obtain the smart contract source code, and use a compiler to compile the smart contract source code into bytecode; determine the language type of the bytecode, and determine to execute the Bytecode virtual machine; determine the execution environment corresponding to the virtual machine, and execute the bytecode based on the execution environment.

Wherein, when the smart contract development program is executed by the processor, it also implements: determining an API list corresponding to the virtual machine; wherein the API list is a list that records the API interfaces supported by the virtual machine; when the When there is a target operation in the bytecode, it is determined whether there is an API interface corresponding to the target operation in the API list; if so, the target operation is executed based on the execution environment.

In order to achieve the above objective, this application provides a computer-readable storage medium with a smart contract development program stored on the computer-readable storage medium. The smart contract development program is executed by a processor to implement the smart contract development method as described above. A step of.

In order to achieve the above objective, this application provides a computer program product, including computer instructions, which when run on a computer, enable the computer to execute any one of the smart contract development methods described above.

It can be seen from the above solution that a smart contract development method provided by this application includes: obtaining the smart contract source code, and using a compiler to compile the smart contract source code into bytecode; determining the language type of the bytecode, and A virtual machine that executes the bytecode is determined according to the language type; an execution environment corresponding to the virtual machine is determined, and the bytecode is executed based on the execution environment.

The smart contract development method provided in this application divides the smart contract into different types of virtual machines for execution by identifying the language type of the bytecode. Through multi-virtual machine technology, smart contracts of different language types can be run on a blockchain platform at the same time to jointly operate the state database of the same blockchain system. It can be seen that, in the smart contract development method provided by this application, a unified blockchain platform can support multiple virtual machines and be compatible with bytecodes of multiple different languages, so that users are not limited to specific virtual machines and realize blocks. The virtual machine on the chain can be adapted and plug-in. This application also discloses a smart contract development device, an electronic device and a computer-readable storage medium, which can also achieve the above technical effects.

Description of the drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work.

Figure 1 is a system architecture diagram in related technologies;

Figure 2 is a flowchart of a smart contract development method disclosed in an embodiment of the application;

Figure 3 is a flowchart of another smart contract development method disclosed in an embodiment of the application;

FIG. 4 is a system architecture diagram of an application embodiment provided by this application;

Figure 5 is a structural diagram of a smart contract development device disclosed in an embodiment of the application;

FIG. 6 is a structural diagram of an electronic device disclosed in an embodiment of the application;

FIG. 7 is a structural diagram of another electronic device disclosed in an embodiment of the application.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the present invention clearer, the following further describes the present invention in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present invention, but not used to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of the present invention.

The terms "first", "second", "third", "fourth", etc. (if any) in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects, without having to use To describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances so that the embodiments described herein can be implemented in a sequence other than the content illustrated or described herein. In addition, the terms "including" and "having" and any variations of them are intended to cover non-exclusive inclusions. For example, a process, method, device, product, or device that includes a series of steps or units is not necessarily limited to the clearly listed Those steps or units may include other steps or units that are not clearly listed or are inherent to these processes, methods, products, or equipment.

It should be noted that the descriptions related to "first", "second", etc. in the present invention are only used for descriptive purposes, and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. . Therefore, the features defined with "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but it must be based on what can be achieved by a person of ordinary skill in the art. When the combination of technical solutions is contradictory or cannot be achieved, it should be considered that such a combination of technical solutions does not exist. , Is not within the protection scope of the present invention.

In related technologies, different types of virtual machines can be used to develop smart contracts using different high-level languages. For example, the evm (full English name: environment virtual machine) virtual machine used by Ethereum to develop smart contracts, its high-level language is solidity, and EOS (full English name: Enterprise Operation System, a blockchain operating system designed for commercial distributed applications ) Used wasm (full English name: Web Assembly) virtual machine, and its high-level language is C++. As shown in Figure 1, the most critical technology is the high-level language used to develop smart contracts, the compiled bytecode, and the virtual machine that executes the bytecode. The above two types of virtual machines are closely connected to their specific blockchain systems, and they have their own special execution environments such as memory and storage, special supported bytecodes, and contract compilers. For example, user A writes a solidity contract to register on Ethereum, and user B writes a C++ contract to register on EOS. There is no data exchange between the two, and user A’s solidity contract cannot be registered on EOS.

It can be seen that the underlying bytecodes of multiple virtual machines cannot be interoperable, and a set of codes cannot be run on multiple platforms or a single platform supports multiple bytecode formats, which restricts the promotion of smart contract applications and greatly hinders the development of blockchain technology. development of. Therefore, in this application, the smart contract is divided into different types of virtual machines for execution by identifying the language type of the bytecode. A unified blockchain platform can support multiple virtual machines, compatible with bytecodes of multiple different languages, so that users are not limited to specific virtual machines, and realize the adaptability and plug-inization of virtual machines on the blockchain.

The embodiment of the application discloses a smart contract development method, provides a unified blockchain platform, and supports smart contracts developed on different types of virtual machines using different high-level languages.

Referring to Fig. 2, a flow chart of a smart contract development method disclosed in an embodiment of the present application, as shown in Fig. 2, includes:

S101: Obtain the smart contract source code, and use a compiler to compile the smart contract source code into bytecode;

The execution subject of this embodiment is a unified blockchain platform, and the purpose is to support smart contracts developed using different high-level languages on different types of virtual machines. In this step, the smart contract source code is obtained. The smart contract source code includes source code written in different high-level languages, such as solidity language, C++ language, and so on. The source code of different programming languages is compiled into bytecode with different compilers, and the bytecode can be executed on a virtual machine.

S102: Determine the language type of the bytecode, and determine a virtual machine that executes the bytecode according to the language type;

The purpose of this step is to select a suitable virtual machine to execute the bytecode through the language type of the bytecode. First, determine the language type corresponding to the bytecode, and use the smart contract source code written in different programming languages to compile into bytecodes of different language types, such as wasm type, evm type, etc. The specific determination method is not limited here. Preferably, the use of a compiler to compile the smart contract source code into bytecode includes: using a compiler to compile the smart contract source code into bytecode, and download Adding the identifier corresponding to the language type of the bytecode to the bytecode; correspondingly, the determining the language type of the bytecode includes: obtaining the identifier from the bytecode, and identifying the The identifier determines the language type of the bytecode. In specific implementation, the compiler adds an identifier to the bytecode. For example, if the smart contract source code is written in solidity language, add ".evm" to the bytecode. If the smart contract source code is written in C++ language, Then add ".asm" to the bytecode. When determining the virtual machine that executes the bytecode execution, the identifier in the bytecode can be extracted, and the virtual machine corresponding to the identifier can be determined. For example, the virtual machine corresponding to ".evm" is an evm type virtual machine, and the virtual machine corresponding to ".asm" is a wasm type virtual machine.

S103: Determine an execution environment corresponding to the virtual machine, and execute the bytecode based on the execution environment.

In specific implementation, different types of virtual machines require different execution environments to parse and execute bytecodes. The operating environment of each type of virtual machine on the platform can be configured separately according to actual needs. For example, a larger CPU or larger execution memory space can be allocated to a certain type of virtual machine.

Preferably, the step of executing the bytecode based on the execution environment includes: determining an API list corresponding to the virtual machine; wherein the API list is a list that records API interfaces supported by the virtual machine; When the bytecode has a target operation, it is determined whether there is an API interface corresponding to the target operation in the API list; if so, the target operation is executed based on the execution environment.

In specific implementation, different types of virtual machines use their own interfaces to access blockchain system resources. For the different functions of different blockchain systems, different virtual machines can support different API interfaces, realizing more detailed virtual machine management, that is, each type of virtual machine has a corresponding API list. For example, you can specify that a certain type of virtual machine does not support contract transfers and restrict functions such as blockchain data reading. The API list corresponding to this type of virtual machine does not include contract transfer and data reading interfaces. For another example, EOS supports super nodes, Ethereum does not support super nodes, etc., the API list corresponding to the evm type virtual machine includes the interface to implement the super node, and the API list corresponding to the wasm type virtual machine does not include the implementation of the super node. The interface of the node. When executing the bytecode, if the bytecode includes a target operation, if the API interface corresponding to the target operation exists in the API list, the target operation is executed, otherwise the target operation is rejected.

More preferably, the step of executing the target operation based on the execution environment includes: determining the target blockchain system corresponding to the target operation, and using the API interface corresponding to the target operation to perform the target operation based on the execution environment. The target operation is executed on the target blockchain system; wherein, the API interface is an API interface meeting a preset standard.

In the specific implementation, a unified API interface for virtual machines is provided in a unified blockchain platform to shield the underlying implementation details of the underlying blockchain platform. Generally speaking, different blockchain platforms have various APIs. For example, on platforms that support decentralized exchanges, there will be user orders and trading operation interfaces. EOS platform has trading CPU and memory. Interface and so on. The calling methods, parameters, and return values of these different interfaces are different. Here, through a unified API interface, that is, an API interface that meets the preset standards, contract developers do not need to care too much about the implementation details of the underlying blockchain platform, and only need to call the API.

It is understandable that after the use of the API interface corresponding to the target operation to execute the target operation on the target blockchain system based on the execution environment, it may also include the operation of receiving the target blockchain system Results of the steps.

The smart contract development method provided by the embodiment of the application divides the smart contract into different types of virtual machines for execution by identifying the language type of the bytecode. Through multi-virtual machine technology, smart contracts of different language types can be run on a blockchain platform at the same time to jointly operate the state database of the same blockchain system. It can be seen that, in the smart contract development method provided by the embodiments of this application, a unified blockchain platform can support multiple virtual machines and is compatible with bytecodes of multiple different languages, so that users are not limited to specific virtual machines. The virtual machine on the blockchain can be adapted and plug-in.

The embodiment of the application discloses a smart contract development method. Compared with the previous embodiment, this embodiment further explains and optimizes the technical solution. specific:

Referring to Fig. 3, a flowchart of another smart contract development method provided by an embodiment of the present application, as shown in Fig. 3, includes:

S201: Obtain smart contract source code, and use a compiler to compile the smart contract source code into bytecode, and add an identifier corresponding to the language type of the bytecode to the bytecode;

S202: Obtain an identifier from the bytecode, and determine the language type of the bytecode by identifying the identifier;

S203: Determine the virtual machine corresponding to the bytecode according to the language type, and determine the execution environment corresponding to the virtual machine;

S204: Determine an API list corresponding to the virtual machine; where the API list is a list that records API interfaces supported by the virtual machine;

S205: When there is a target operation in the bytecode, determine whether there is an API interface corresponding to the target operation in the API list; if yes, go to S206; if not, go to S208;

S206: Determine the target blockchain system corresponding to the target operation, and use the API interface corresponding to the target operation to execute the target operation on the target blockchain system based on the execution environment; wherein, the API The interface is an API interface that meets the preset standards;

S207: Receive the operation result of the target blockchain system;

S208: Reject the target operation.

It can be seen that, by identifying bytecode, this embodiment divides the smart contract into different virtual machines for execution, and supports multiple types of virtual machines. Through independent virtual machine execution environment and API list, fine-grained virtual machine management and plug-in adaptation are realized. Through a unified API interface, shield the implementation details of the underlying blockchain platform and support the access of multiple blockchain systems.

The following describes an application embodiment provided by this application. The system includes a wasm type virtual machine and a jvm type virtual machine. As shown in FIG. 4, the following steps may be included:

Step 1: The source code of the smart contract is compiled into bytecode by a compiler;

Step 2: After the recognition layer, the bytecode is passed to different virtual machines for execution;

Step 3: The virtual machine receives the bytecode, sets the execution environment according to the configuration, and executes the contract bytecode;

Step 4: During the execution of the bytecode, the virtual machine API list will be accessed, and then the blockchain system resources will be accessed through the unified API interface;

Step 5: Through the API interface, the corresponding operation is executed on the blockchain system of A and B and returned to the virtual machine.

If developer A uses solidity to write a smart contract with a permission list, and developer B can only use C++, but the permission list is required. At this time, this system can be used to arrange the contracts of developers A and B on the same blockchain platform to realize resource interoperability and data sharing, which is very flexible and efficient.

The following describes a smart contract development device provided by an embodiment of the present application. The smart contract development device described below and the smart contract development method described above can be cross-referenced.

Referring to Fig. 5, a structural diagram of a smart contract development device provided by an embodiment of the present application, as shown in Fig. 5, includes:

The compilation module 501 is used to obtain the smart contract source code, and use a compiler to compile the smart contract source code into bytecode;

The determining module 502 is configured to determine the language type of the bytecode, and determine the virtual machine that executes the bytecode according to the language type;

The execution module 503 is configured to determine the execution environment corresponding to the virtual machine, and execute the bytecode based on the execution environment.

The smart contract development device provided by the embodiment of the present application differentiates the smart contract for execution on different types of virtual machines by identifying the language type of the bytecode. Through multi-virtual machine technology, smart contracts of different language types can be run on a blockchain platform at the same time to jointly operate the state database of the same blockchain system. It can be seen that, in the smart contract development device provided by the embodiments of this application, the unified blockchain platform can support multiple virtual machines and be compatible with bytecodes of multiple different languages, so that users are not limited to specific virtual machines. The virtual machine on the blockchain can be adapted and plug-in.

On the basis of the foregoing embodiment, as a preferred implementation manner, the execution module 503 includes:

The first determining unit is configured to determine the execution environment corresponding to the virtual machine;

The second determining unit is configured to determine an API list corresponding to the virtual machine; wherein the API list is a list that records API interfaces supported by the virtual machine;

The judging unit is configured to judge whether the API interface corresponding to the target operation exists in the API list when the target operation exists in the bytecode; if so, start the work flow of the execution unit;

The execution unit is configured to execute the target operation based on the execution environment.

On the basis of the above-mentioned embodiment, as a preferred implementation, the execution unit specifically determines the target blockchain system corresponding to the target operation, and uses the API interface corresponding to the target operation to pair the target blockchain system based on the execution environment. The unit that executes the target operation on the target blockchain system; wherein, the API interface is an API interface that meets a preset standard.

On the basis of the foregoing embodiment, as a preferred implementation manner, it further includes:

The receiving module is used to receive the operation result of the target blockchain system.

On the basis of the foregoing embodiment, as a preferred implementation manner, the determining module 502 includes:

The third determining unit is configured to obtain an identifier from the bytecode, and determine the language type of the bytecode by identifying the identifier;

The fourth determining unit is configured to determine a virtual machine that executes the bytecode according to the language type.

On the basis of the foregoing embodiment, as a preferred implementation manner, the language types include solidity language and C++ language.

On the basis of the foregoing embodiment, as a preferred implementation manner, the virtual machine includes any one or a combination of any of an evm-type virtual machine, a wasm-type virtual machine, and a jvm-type virtual machine.

This application also provides an electronic device, which may be a PC (Personal Computer, personal computer), or a terminal device such as a smart phone, a tablet computer, a palmtop computer, and a portable computer. The electronic device may be a node forming a CDN network or a blockchain network.

Referring to FIG. 6, a structural diagram of an electronic device provided by an embodiment of the present application, as shown in FIG. 6, may include a memory 11, a processor 12 and a bus 13.

The memory 11 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), magnetic memory, magnetic disk, optical disk, and the like. In some embodiments, the memory 11 may be an internal storage unit of an electronic device, such as a hard disk of the electronic device. In other embodiments, the memory 11 may also be an external storage device of the electronic device, such as a plug-in hard disk, a smart media card (SMC), and a secure digital (SD) card equipped on the electronic device. Flash Card, etc. Further, the memory 11 may also include both an internal storage unit of an electronic device and an external storage device. The memory 11 can be used not only to store application software and various data of the installed electronic device, such as the code of the smart contract development program 01, etc., but also to temporarily store data that has been output or will be output.

In some embodiments, the processor 12 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip, and is used to run the program code or processing stored in the memory 11 The data implements the smart contract development method provided in any of the above embodiments, for example, executes the smart contract development program 01.

The bus 13 may be a peripheral component interconnect standard (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 6, but it does not mean that there is only one bus or one type of bus.

The embodiment of the application divides the smart contract into different types of virtual machines for execution by identifying the language type of the bytecode. Through multi-virtual machine technology, smart contracts of different language types can be run on a blockchain platform at the same time to jointly operate the state database of the same blockchain system. It can be seen that the unified blockchain platform provided by the embodiments of the present application can support multiple virtual machines and be compatible with bytecodes of multiple different languages, so that users are not limited to specific virtual machines and realize virtual machines on the blockchain. Adaptable and plug-in.

On the basis of the foregoing embodiment, as a preferred implementation manner, referring to FIG. 7, the electronic device further includes:

The input interface 14 is used to obtain externally imported computer programs, parameters, and instructions, and store them in the memory 11 under the control of the processor 12. The input interface 14 can be connected to an input device to receive parameters or instructions manually input by the user. The input device can be a touch layer covered on a display screen, a button, a trackball, or a touchpad provided on a terminal shell, or a keyboard, a touchpad, or a mouse.

The display unit 15 is used for displaying the data processed by the processor 12 and for displaying a visualized user interface. The display unit 15 may be an LED display, a liquid crystal display, a touch liquid crystal display, an OLED (Organic Light-Emitting Diode, organic light emitting diode) touch device, etc.

The network port 16 is used to communicate with external terminal devices. The communication technology used in the communication connection can be wired communication technology or wireless communication technology, such as mobile high-definition link technology (MHL), universal serial bus (USB), high-definition multimedia interface (HDMI), wireless fidelity technology (WiFi), Bluetooth communication technology, low-power Bluetooth communication technology, communication technology based on IEEE802.11s, etc.

Figure 7 only shows the electronic device with components 11-16 and the smart contract development program 01. Those skilled in the art can understand that the structure shown in Figure 7 does not constitute a limitation on the electronic device, and may include Fewer or more components, or combinations of certain components, or different component arrangements.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part.

The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present invention are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server or a data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the device, device and unit described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed device, device, and method may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another device, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

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 this understanding, the technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes. .

It should be noted that the sequence numbers of the above-mentioned embodiments of the present invention are only for description, and do not represent the advantages and disadvantages of the embodiments. And the terms "include", "include" or any other variants thereof in this article are intended to cover non-exclusive inclusion, so that a process, device, article or method including a series of elements not only includes those elements, but also includes those elements that are not explicitly included. The other elements listed may also include elements inherent to the process, device, article, or method. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, device, article, or method that includes the element.

The above are only preferred embodiments of the present invention, and do not limit the scope of the present invention. Any equivalent structure or equivalent process transformation made by using the contents of the description and drawings of the present invention, or directly or indirectly applied to other related technical fields , The same reason is included in the scope of patent protection of the present invention.

Claims

A smart contract development method is characterized in that it includes:

Obtain the smart contract source code, and use a compiler to compile the smart contract source code into bytecode;

Determining the language type of the bytecode, and determining a virtual machine that executes the bytecode according to the language type;

The execution environment corresponding to the virtual machine is determined, and the bytecode is executed based on the execution environment.
The smart contract development method according to claim 1, wherein said executing said bytecode based on said execution environment comprises:

Determine an API list corresponding to the virtual machine; wherein the API list is a list that records API interfaces supported by the virtual machine;

When a target operation exists in the bytecode, determining whether there is an API interface corresponding to the target operation in the API list;

If yes, execute the target operation based on the execution environment.
The smart contract development method according to claim 2, wherein the executing the target operation based on the execution environment comprises:

Determine the target blockchain system corresponding to the target operation, and use the API interface corresponding to the target operation to execute the target operation on the target blockchain system based on the execution environment; wherein the API interface is API interface conforming to preset standards.
The smart contract development method according to claim 3, wherein after said using the API interface corresponding to the target operation to execute the target operation on the target blockchain system based on the execution environment, the method further comprises:

Receive the operation result of the target blockchain system.
The smart contract development method according to claim 1, wherein the virtual machine includes any one or a combination of any one of an evm type virtual machine, a wasm type virtual machine, and a jvm type virtual machine.
The smart contract development method according to any one of claims 1 to 5, wherein said using a compiler to compile the smart contract source code into bytecode comprises:

Using a compiler to compile the smart contract source code into bytecode, and add an identifier corresponding to the language type of the bytecode to the bytecode;

Correspondingly, the determining the language type of the bytecode includes:

An identifier is obtained from the bytecode, and the language type of the bytecode is determined by identifying the identifier.
A smart contract development device, which is characterized in that it includes:

Compilation module, used to obtain the smart contract source code, and use a compiler to compile the smart contract source code into bytecode;

A determining module, configured to determine the language type of the bytecode, and determine a virtual machine that executes the bytecode according to the language type;

The execution module is used to determine the execution environment corresponding to the virtual machine, and execute the bytecode based on the execution environment.
An electronic device, characterized in that the electronic device includes a memory and a processor, the memory stores a smart contract development program that can run on the processor, and the smart contract development program is used by the processor. Implementation during execution: Obtain the smart contract source code, and use a compiler to compile the smart contract source code into bytecode; determine the language type of the bytecode, and determine the virtual execution of the bytecode according to the language type Machine; determine the execution environment corresponding to the virtual machine, and execute the bytecode based on the execution environment.
The electronic device according to claim 8, wherein when the smart contract development program is executed by the processor, it further implements: determining an API list corresponding to the virtual machine; wherein, the API list is a record of the virtual machine A list of API interfaces supported by the computer; when the bytecode has a target operation, it is determined whether there is an API interface corresponding to the target operation in the API list; if so, the target operation is executed based on the execution environment.
A computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the smart contract development method according to any one of claims 1 to 6 is realized A step of.