CN109933407B

CN109933407B - Block chain DAPP virtual machine, data processing method and computing equipment

Info

Publication number: CN109933407B
Application number: CN201910143395.3A
Authority: CN
Inventors: 杨杰; 聂和勇; 孙金虎; 孙玉辰; 杨志伟
Original assignee: Shanghai Nanchao Information Technology Co ltd
Current assignee: Shanghai Nanchao Information Technology Co ltd
Priority date: 2019-02-26
Filing date: 2019-02-26
Publication date: 2021-06-01
Anticipated expiration: 2039-02-26
Also published as: CN109933407A

Abstract

The application discloses a block chain DAPP virtual machine, a data processing method and computing equipment. Wherein, this virtual machine includes: the control module is connected with a DAPP code storage unit in the block chain node host and used for receiving a DAPP code and generating an engine instance based on the DAPP code and user configuration; the engine module is connected with the control module and used for receiving the engine instance and executing the engine instance; and the bridging module is respectively connected with the engine module and the API module of the node host, and is used for receiving the access request sent by the engine module, sending the access request to the API module, receiving the access result returned by the API module and sending the access result to the engine module. The scheme can enable developers to develop the DAPP by using a uniform language, lowers the development threshold of technicians for the DAPP, and enables the DAPP to be interpreted and executed across different blockchain platforms due to the consistency on the language level.

Description

Block chain DAPP virtual machine, data processing method and computing equipment

Technical Field

The present Application relates to the field of computer technologies, and in particular, to a block chain DAPP (Decentralized Application) virtual machine, a data processing method, and a computing device.

Background

A blockchain is a system that operates in a P2P network to solve trust problems. The data is separated from the owner through decentralization, the privacy of the user is protected, and the trust mechanism of the original centralized service according to an authority is separated. Blockchains solve the trust problem on decentralized networks by creating applications through the use of a range of techniques, such as cryptography and consensus algorithms. Currently, mainstream platforms for blockchains include Ethereum and EOS. Ethereum is currently widely adopted with the intelligent contract high level language solid. The intelligent contract language adopted by EOS is Web Assembly (wasm). The language is usually realized by C/C + + programming. Wherein, the identity is a new language and has a learning threshold for developers, and the C/C + + is less friendly to the developers than Javascript. At present, compatibility between two platforms is poor, contracts written on Ethereum cannot run on EOS and need to be rewritten, and vice versa.

With the development of the blockchain technology, more and more functions begin to be developed under the blockchain system, wherein DAPP is an application established on the blockchain system, and more technicians are invested in the development of DAPP, so as to realize more application functions based on the blockchain. Due to the high threshold of block chain DAPP programming technology and the poor compatibility among mainstream platforms, the development and popularization of DAPP are greatly restricted, and the popularization of various services based on DAPP is hindered.

Disclosure of Invention

It is an object of the present application to overcome the above problems or to at least partially solve or mitigate the above problems.

According to a first aspect of the present application, there is provided a block chain DAPP Virtual Machine (VM), comprising:

the control module is connected with a DAPP code storage unit in a block chain node Host (Host) and used for receiving a DAPP code and generating the engine instance based on the DAPP code and user configuration;

the engine module is connected with the control module and used for receiving the engine instance and executing the engine instance;

and the bridge module is respectively connected with the engine module and an Application Programming Interface (API) module of the node host, and is configured to receive an access request sent by the engine module, send the access request to the API module, receive an access result returned by the API module, and send the access result to the engine module.

The solution can reduce the development threshold of the DAPP, for example, the development can be realized only by adopting a uniform scripting language such as Javascript, the DAPP developed by the scripting language is consistent on a language level, and the consistency on the language level can enable the DAPP to be interpreted and executed across different blockchain platforms. The virtual machine can provide explanation and running environment for the DAPP through the embedded engine module, so that the DAPP running environment is isolated from the running environment of the block chain link points, the safety of the block chain link points is guaranteed, and the difficulty of cross-platform development of the DAPP is reduced.

Optionally, the control module is configured to receive codes of more than two DAPPs, generate corresponding engine instances for each code of a DAPP, and send all the engine instances to the engine module for parallel execution.

Optionally, the control module is further configured to: invoking an internal method of the DAPP code in the block link point host.

Optionally, the control module is further configured to: and monitoring the use of the resources by the DAPP, and terminating the operation of the DAPP when the used resources are greater than or equal to an upper limit.

Optionally, the bridge module is further configured to, after receiving the access request sent by the engine module, perform security check on the access request, and send the access request to the API module when the check is passed.

According to a second aspect of the present application, there is provided a data processing method, based on a blockchain DAPP virtual machine, where the blockchain DAPP virtual machine includes: the control module is connected with a DAPP code storage unit in the block chain node host; the engine module is connected with the control module; the bridge module is respectively connected with the engine module and the API module of the node host;

the method comprises the following steps:

s100, the control module receives a DAPP code sent by a DAPP code storage unit in the block chain node host, and generates the engine instance based on the DAPP code and user configuration;

s300, the engine module receives the engine instance sent by the control module and executes the engine instance;

s500, the engine module responds to an access request of a user and sends the access request to the bridge module;

s700, the bridge module sends the access request to the API module, receives the access result returned by the API module and sends the access result to the engine module.

The method can enable developers to develop the DAPP by using the uniform language, reduces the development threshold of technicians on the DAPP, and enables the DAPP to be interpreted and executed across different blockchain platforms due to the consistency on the language level.

Optionally, in S100, the control module is configured to receive codes of more than two DAPPs, generate a corresponding engine instance for each code of a DAPP, and send all the engine instances to the engine module.

Optionally, the method further comprises: the control module monitors the use of resources by the DAPP and terminates the operation of the DAPP if the used resources are greater than or equal to an upper limit.

Optionally, in S700, after receiving the access request sent by the engine module, the bridge module performs security check on the access request, and sends the access request to the API module when the check is passed.

According to a third aspect of the present application, there is provided a computing device comprising a memory, a processor, and a blockchain DAPP virtual machine stored in the memory and executable by the processor, the blockchain DAPP virtual machine comprising:

the control module is connected with a DAPP code storage unit in the block chain node host and used for receiving a DAPP code and generating the engine instance based on the DAPP code and user configuration;

and the bridge module is respectively connected with the engine module and the API module of the node host, and is used for receiving the access request sent by the engine module, sending the access request to the API module, receiving the access result returned by the API module and sending the access result to the engine module.

The above and other objects, advantages and features of the present application will become more apparent to those skilled in the art from the following detailed description of specific embodiments thereof, taken in conjunction with the accompanying drawings.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. Some specific embodiments of the present application will be described in detail hereinafter by way of illustration and not limitation with reference to the accompanying drawings. The same reference numbers in the drawings identify the same or similar elements or components. Those skilled in the art will appreciate that the drawings are not necessarily drawn to scale. In the drawings:

FIG. 1 is a schematic block diagram of a blockchain DAPP virtual machine according to one embodiment of the present application;

FIG. 2 is a schematic block diagram of a cross-platform blockchain DAPP virtual machine according to one embodiment of the present application;

FIG. 3 is a schematic flow chart diagram of a data processing method according to an embodiment of the present application.

Detailed Description

In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The embodiment of the application provides a block chain DAPP virtual machine, which is hereinafter referred to as a virtual machine for short. Fig. 1 is a schematic block diagram of a blockchain DAPP virtual machine according to one embodiment of the present application. The virtual machine 100 may include: a control module 110, an engine module 120, and a bridge module 130.

The control module 110, which may also be referred to as a Ruff VM ctrl module, is connected to the DAPP code storage unit 210 in the block-node host 200, and is configured to receive a code of a DAPP, and generate the engine instance based on the code of the DAPP and a user configuration. In an alternative embodiment, the DAPP is a smart contract, and the block link point host is loaded with the original code of the smart contract, and the DAPP is loaded into the virtual machine through an interface provided by a control module of the virtual machine, such as a createScript interface. Because the original code of the intelligent contract embodies the business logic, the virtual machine can execute the corresponding business logic by loading.

An engine module 120, connected to the control module, for receiving the engine instance and executing the engine instance. Optionally, the engine module may be a Javascript engine module. The engine module can customize an instance Javascript engine module according to the configuration of a user, such as parameters of CPU size, Memory size and the like, and deliver the code of the DAPP to the Javascript engine module for execution.

The bridging module 130, which may also be referred to as a Ruff VM Bridge module, is connected to the engine module and the API module 220 of the node host, respectively, and is configured to receive the access request sent by the engine module and send the access request to the API module, and receive the access result returned by the API module and send the access result to the engine module. DAPP cannot directly manipulate the resources of a block-node host for security reasons. Since the engine module itself does not have the capability to access or operate the blockchain node host, when the DAPP needs to perform some function, such as initiating a transfer, etc., the engine module will generate an access request and forward the access request to the Ruff VM Bridge module.

By adopting the method, a layer of uniform abstraction, namely a universal DAPP API (data application protocol), such as a basic transfer function, a basic key value pair operation function and the like, is extracted on the basis of a block chain bottom layer environment, so that a DAPP developer does not need to directly face a specific block chain platform environment when developing DAPP, and can acquire data or realize functions by calling the DAPP API. The DAPP developed based on the scheme can run on a block chain link point host which integrates a general DAPP virtual machine and provides a DAPP API, and the bottom layer implementation of a block chain is not needed, so that the cross-chain running of the DAPP is realized.

Optionally, the control module is further configured to: invoking an internal method of the DAPP code in the block link point host. When a user needs to call an internal method of the DAPP, the node host calls the internal method of the DAPP, such as a setUserCode interface, through an interface provided by the Ruff VM, and at this time, a method name and a related parameter list of the DAPP need to be specified. In this case, the developer of the DAPP can call the internal method using the DAPP in a general-purpose language without paying attention to what development language the block link point is implemented in.

Optionally, the control module is further configured to: and monitoring the use of the resources by the DAPP, and terminating the operation of the DAPP when the used resources are greater than or equal to an upper limit. Alternatively, the upper limit may be specified by a user. This approach may limit access of the DAPP to block-linked point resources. The nodes configure the node resources, such as Memory, CPU time, etc., that the DAPP virtual machine can access, thereby providing the DAPP with the capability of operating the block chain, such as initiating a transfer, querying user balance, etc. The accessibility may be embodied by a configuration manifest, which may be implemented by creating key value pairs (keys) on the blockchain. The DAPP is accessible for resources on the configuration manifest, otherwise it is not.

Optionally, the bridge module is further configured to, after receiving the access request sent by the engine module, perform security check on the access request, and send the access request to the API module when the check is passed. The API module includes an API list (Table). In an alternative embodiment, the access request is a transfer request. The security check by the bridge module includes: confirm that the API to be called does exist and the parameters are correct. The bridge module calls an API module provided by the node host, such as a transfer module, and returns an execution result to the DAPP of the Javascript engine module after the calling is completed. The DAPP may execute different logic or choose to terminate the operation of the DAPP based on the returned results.

Fig. 2 is a schematic block diagram of a cross-platform blockchain DAPP virtual machine according to one embodiment of the present application. The way in which the DAPP runs on different block chains is explained below with reference to fig. 2. Ruff VM is first embedded at the corresponding block link point. Wherein a block link point may comprise nodes of a plurality of different platforms. For example, the first blockchain node 210 may be an Ethereum platform node that embeds the virtual machine 211; the second blockchain node 220 may be an EOS platform node that is embedded in the virtual machine 212. It will be appreciated that virtual machines may also be embedded at more platform nodes. The Ruff VM can access a block-linked node host or a list of APIs on the host. The contents in the API list correspond to the respective API function modules. A developer develops DAPP in Javascript language, and completes service logic by using a block chain operation API provided by a Ruff VM, and specific bottom layer operations are realized by embedded Ruff VM block chain link points, such as Transfer (Transfer), state storage (DB store) and the like. The DAPP developed based on this approach can run on different blockchain platforms. The Ruff VM may be integrated in a block link point host in the form of a plug-in or a library, and the host provides the Ruff VM with the ability of DAPP to access the node host or other nodes in the chain according to actual needs by configuring the api.

An embodiment of the present application further provides a data processing method, where the method is based on a blockchain DAPP virtual machine, where the blockchain DAPP virtual machine includes: the control module is connected with a DAPP code storage unit in the block chain node host; the engine module is connected with the control module; and the bridge module is respectively connected with the engine module and the API module of the node host. It will be appreciated that the method may be based on any of the above-described blockchain DAPP virtual machines.

FIG. 3 is a schematic flow chart diagram of a data processing method according to an embodiment of the present application. The data processing method may comprise one or more of the following steps:

s100, the control module receives a DAPP code sent by a DAPP code storage unit in the block chain node host, and generates the engine instance based on the DAPP code and user configuration.

S300, the engine module receives the engine instance sent by the control module and executes the engine instance.

S500, the engine module responds to an access request of a user and sends the access request to the bridge module.

Optionally, the method further comprises: and calling an internal method of the DAPP code in the block chain node host through a control module.

Embodiments of the present application also provide a computing device comprising a memory, a processor, and a blockchain DAPP virtual machine stored in the memory and executable by the processor, which may be any one of the virtual machines described above. For example, in one optional embodiment, the virtual machine may include:

An aspect of embodiments of the present application also provides a computer-readable storage medium. The computer-readable storage medium includes a storage unit for program code, the storage unit storing any one of the blockchain DAPP virtual machines as described above, and provided with a program for executing the data processing method according to the present application, the program being executed by a processor.

An aspect of an embodiment of the present application also provides a computer program product containing instructions, including computer readable code, which when executed by a computing device, causes the computing device to execute the data processing method as described above.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed by a computer, cause the computer to perform, in whole or in part, the procedures or functions described in accordance with the embodiments of the application. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

Those of skill would further appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be understood by those skilled in the art that all or part of the steps in the method for implementing the above embodiments may be implemented by a program, and the program may be stored in a computer-readable storage medium, where the storage medium is a non-transitory medium, such as a random access memory, a read only memory, a flash memory, a hard disk, a solid state disk, a magnetic tape (magnetic tape), a floppy disk (floppy disk), an optical disk (optical disk), and any combination thereof.

The above description is only for the preferred embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A blockchain DAPP virtual machine, comprising:

the control module is connected with a DAPP code storage unit in the block chain node host and used for receiving a DAPP code and generating an engine instance based on the DAPP code and user configuration;

the engine module is connected with the control module and used for receiving the engine instance and executing the engine instance; and

the bridge module is respectively connected with the engine module and the API module of the node host, and is used for receiving the access request sent by the engine module, sending the access request to the API module, receiving the access result returned by the API module and sending the access result to the engine module;

the control module is used for receiving more than two DAPP codes, respectively generating corresponding engine instances for each DAPP code, and sending all the engine instances to the engine module for parallel execution.

2. The blockchain DAPP virtual machine of claim 1, wherein the control module is further configured to: invoking an internal method of the DAPP code in the block link point host.

3. The blockchain DAPP virtual machine of claim 1, wherein the control module is further configured to: and monitoring the use of the resources by the DAPP, and terminating the operation of the DAPP when the used resources are greater than or equal to an upper limit.

4. The blockchain DAPP virtual machine according to any one of claims 1 to 3, wherein the bridge module is further configured to, after receiving the access request sent by the engine module, perform a security check on the access request, and if the check is passed, send the access request to the API module.

5. A data processing method is based on a block chain DAPP virtual machine, and the block chain DAPP virtual machine comprises: the control module is connected with a DAPP code storage unit in the block chain node host; the engine module is connected with the control module; the bridge module is respectively connected with the engine module and the API module of the node host;

the method comprises the following steps:

s100, the control module receives a DAPP code sent by a DAPP code storage unit in the block chain node host, and generates an engine instance based on the DAPP code and user configuration;

s500, the engine module responds to an access request of a user and sends the access request to the bridge module; and

s700, the bridge module sends the access request to the API module, receives an access result returned by the API module and sends the access result to the engine module;

the control module is used for receiving more than two DAPP codes, respectively generating corresponding engine instances for each DAPP code, and sending all the engine instances to the engine module.

6. The method of claim 5, further comprising: the control module monitors the use of resources by the DAPP and terminates the operation of the DAPP if the used resources are greater than or equal to an upper limit.

7. The method according to claim 5 or 6, wherein in S700, after receiving the access request sent by the engine module, the bridge module performs security check on the access request, and if the check is passed, sends the access request to the API module.

8. A computing device comprising a memory, a processor, and a blockchain DAPP virtual machine stored in the memory and executable by the processor, the blockchain DAPP virtual machine comprising: