WO2022134186A1

WO2022134186A1 - Smart contract calling method and apparatus for blockchains, server, and storage medium

Info

Publication number: WO2022134186A1
Application number: PCT/CN2020/142026
Authority: WO
Inventors: 李伟; 蔡亮; 匡立中; 张帅; 钟蔚蔚
Original assignee: 杭州趣链科技有限公司
Priority date: 2020-12-21
Filing date: 2020-12-31
Publication date: 2022-06-30
Also published as: CN112631803A

Abstract

The present application relates to the technical field of blockchains, and in particular to a smart contract calling method and apparatus for blockchains, a server, and a storage medium. In the present application, each blockchain is registered and deployed to a middle-tier server in advance, a corresponding chain identifier is allocated for the blockchain, and each smart contract is registered to the middle-tier server, and a corresponding contract identifier is allocated for the smart contract. In this way, when a client calls the smart contract, only one smart contract calling request having the chain identifier and the contract identifier needs to be sent; and upon receiving the smart contract calling request, the middle-tier server initiates a corresponding smart contract execution request to the corresponding blockchain according to the chain identifier and the contract identifier, obtains a corresponding smart contract execution result, and returns the smart contract execution result to the client. In the process, the middle-tier server does not need to perform customized encapsulation on each smart contract in different blockchain platforms, thereby reducing the difficulty of updating and maintaining a code of the middle-tier server.

Description

Blockchain smart contract calling method, device, server and storage medium

This application claims the priority of the Chinese patent application filed with the State Intellectual Property Office on December 21, 2020, the application number is 202011543148.1, and the application name is "blockchain smart contract calling method, device, server and storage medium", which The entire contents of this application are incorporated by reference.

technical field

The present application relates to the field of blockchain technology, and in particular, to a method, device, server and storage medium for invoking a smart contract of a blockchain.

Background technique

In the actual blockchain system, a middle-tier server is usually set up between the underlying blockchain platform and the client, which is responsible for data encoding/decoding, contract function encapsulation and The client's subscription information processing to the blockchain, etc.

At present, for the needs of the client to call smart contracts to multiple different blockchain platforms, the middle-tier server usually needs to customize the packaging for each smart contract in different blockchain platforms, and then provide the packaged interface to the Client call. In this way, once the middle-tier server is connected to many blockchain platforms or smart contracts, it will be very difficult to update and maintain the code of the middle-tier server.

technical problem

In view of this, the embodiments of the present application provide a blockchain smart contract calling method, device, server and storage medium, which can reduce the difficulty of updating and maintaining the code of the middle-tier server.

technical solutions

A first aspect of the embodiments of the present application provides a blockchain smart contract calling method, including:

Receive a smart contract invocation request sent by the client, where the smart contract invocation request includes the contract identifier of the target smart contract and the chain identifier of the target blockchain where the target smart contract is located, wherein the target blockchain has been registered and deployed to the middle-tier server, and the target smart contract has been registered with the middle-tier server;

Find the contract information of the target smart contract according to the contract identifier;

Based on the contract information and the chain identifier, initiate a smart contract execution request to the target blockchain, and obtain the execution result of the target smart contract;

Return the execution result of the target smart contract to the client.

The embodiments of the present application pre-register and deploy different blockchains to the middle-tier server, assign corresponding chain identifiers to the blockchains, and register each smart contract to the middle-tier server to assign corresponding contract identifiers to the smart contracts. With this setting, when the client calls the smart contract, it only needs to issue a smart contract call request with the chain ID and the contract ID. Initiate the corresponding smart contract execution request to the corresponding blockchain, obtain the corresponding smart contract execution result and return it to the client. In the above process, the middle-tier server does not need to customize and encapsulate each smart contract in different blockchain platforms, which can reduce the difficulty of updating and maintaining the code of the middle-tier server.

In an embodiment of the present application, based on the contract information and the chain identifier, initiating a smart contract execution request to the target blockchain, and acquiring the execution result of the target smart contract, may include:

activate the software development kit corresponding to the chain identifier;

The activated software development kit is invoked to initiate a smart contract execution request to the target blockchain according to the contract information, and obtain the execution result of the target smart contract.

Further, the smart contract invocation request also includes attribute information of the target smart contract, the smart contract execution request is initiated to the target blockchain according to the contract information, and the execution result of the target smart contract is obtained. , which can include:

A smart contract execution request is initiated to the target blockchain through the contract information and the attribute information, and the execution result of the target smart contract is obtained.

In an embodiment of the present application, the target blockchain is a blockchain of the Ethereum platform, the contract information includes a contract address and an interface description file of the target smart contract, and the attribute information includes the target The contract function name and function call parameters of the smart contract, the smart contract execution request is initiated to the target blockchain through the contract information and the attribute information, and the execution result of the target smart contract is obtained, which may include:

Initiate a smart contract execution request to the target blockchain in combination with the contract address, the interface description file, the contract function name and the function call parameters, and obtain the execution result of the target smart contract.

In an embodiment of the present application, the target blockchain is a blockchain of the fabric platform, the contract information includes a contract name of the target smart contract, and the attribute information includes a contract function of the target smart contract name and function call parameters, the sending a smart contract execution request to the target blockchain through the contract information and the attribute information, and obtaining the execution result of the target smart contract, may include:

A smart contract execution request is initiated to the target blockchain in combination with the contract name, the contract function name and the function call parameters, and the execution result of the target smart contract is obtained.

In an embodiment of the present application, the target blockchain can be registered and deployed to the middle-tier server through the following steps:

Obtain the connection information and related files of the target blockchain;

Initialize a software development kit corresponding to the platform type of the target blockchain according to the connection information and related files;

Connectivity testing is performed on the software development kit that has been initialized;

If the connectivity test passes, store the connection information and related files in a database, and assign a chain identifier to the target blockchain, so as to register and deploy the target blockchain to the middle layer server.

In an embodiment of the present application, the target smart contract can be registered with the middle-tier server through the following steps:

deploying the target smart contract into the target blockchain, and obtaining contract information of the target smart contract;

The registration of the target smart contract is completed according to the contract information, and a contract identifier is allocated to the target smart contract.

A second aspect of the embodiments of the present application provides a blockchain smart contract invocation device, which is applied to a middle-tier server, and the device includes:

The contract invocation request receiving module is used to receive a smart contract invocation request sent by the client, where the smart contract invocation request includes the contract identifier of the target smart contract and the chain identifier of the target blockchain where the target smart contract is located, wherein, The target blockchain has been registered and deployed to the middle-tier server, and the target smart contract has been registered with the middle-tier server;

a contract information search module, configured to search for the contract information of the target smart contract according to the contract identifier;

a smart contract search module, configured to initiate a smart contract execution request to the target blockchain based on the contract information and the chain identifier, and obtain the execution result of the target smart contract;

The smart contract return module is used for returning the execution result of the target smart contract to the client.

A third aspect of the embodiments of the present application provides a server, including a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the computer program when the processor executes the computer program. The steps of the method for invoking a smart contract of a blockchain provided by the first aspect of the embodiments of this application.

A fourth aspect of the embodiments of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the implementation of the first aspect of the embodiments of the present application is implemented The steps of the smart contract of the blockchain to call the method.

A fifth aspect of the embodiments of the present application provides a computer program product that, when the computer program product runs on a terminal device, enables the terminal device to execute the blockchain smart contract calling method described in the first aspect of the embodiments of the present application A step of.

It can be understood that, for the beneficial effects of the second aspect to the fifth aspect, reference may be made to the relevant description in the first aspect, which is not repeated here.

Description of drawings

1 is a schematic structural diagram of a smart contract invocation system adopted by a blockchain smart contract invocation method provided by an embodiment of the present application;

FIG. 2 is a flowchart of an embodiment of a method for invoking a blockchain smart contract provided by an embodiment of the present application;

3 is a flowchart of an embodiment of another blockchain smart contract invocation method provided by an embodiment of the present application;

4 is a schematic diagram of the principle of a smart contract calling method for the Ethereum blockchain provided by an embodiment of the present application;

5 is a schematic diagram of the principle of a method for invoking a smart contract on a fabric block chain provided by an embodiment of the present application;

6 is a structural diagram of an embodiment of a blockchain smart contract invocation device provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of a server provided by an embodiment of the present application.

Embodiments of the present invention

In the following description, for the purpose of illustration rather than limitation, specific details such as a specific system structure and technology are set forth in order to provide a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may be practiced in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail. In addition, in the description of the specification of the present application and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the description, and should not be construed as indicating or implying relative importance.

Blockchain is a distributed shared ledger and database, which has the characteristics of decentralization, immutability, traceability, traceability, collective maintenance, openness and transparency. At present, in the actual blockchain system, a middle-tier server is usually set up to be responsible for data encoding and decoding, contract function encapsulation, and the business system to the blockchain in the communication process between the blockchain and the business system (client). Subscription information processing, etc. However, for the processing of calling smart contracts from the business system to the blockchain, the middle-tier server usually needs to customize the packaging for each smart contract in different blockchain platforms in advance. When the business requirements change (for example, adding a new block chain or a smart contract), the code needs to be re-modified and tested. The code update process also needs to suspend the service, which will bring adverse effects to the normal operation of the business system. Moreover, once the middle-tier server is connected to many blockchain platforms or smart contracts, it will be very difficult to update and maintain the code of the middle-tier server.

In view of the above problems, the embodiments of the present application provide a blockchain smart contract calling method, device, server, and storage medium, which can avoid customized packaging of each smart contract in different blockchain platforms, thereby reducing intermediate The difficulty of updating and maintaining the tier server code.

It should be understood that the execution body of each method embodiment of the present application may be various types of terminal devices or servers, such as mobile phones, tablet computers, notebook computers, desktop computers, and wearable devices.

FIG. 1 is a schematic structural diagram of a smart contract invocation system adopted by a blockchain smart contract invocation method provided in an embodiment of the present application. Figure 1 includes a business system, a middle-tier server and multiple different blockchain platforms. The business system is the client, and the smart contract needs to be called from the blockchain platform through the middle-tier server; the middle-tier server is responsible for the blockchain and business The data encoding and decoding, contract function encapsulation, and subscription information processing of the business system to the blockchain in the system (client) communication process are the execution subjects of each method embodiment proposed in this application; various blockchain platforms (For example, fabric or Ethereum, etc.) are connected with the middle-tier server to complete data interaction. It should be noted that this application does not limit the type and quantity of the connected blockchain platforms.

For the specific working principle of the above-mentioned smart contract calling system, reference may be made to the method embodiments described below.

Please refer to FIG. 2, which shows a blockchain smart contract calling method provided by an embodiment of the present application, including:

201. Receive a smart contract invocation request sent by a client, where the smart contract invocation request includes a contract identifier of a target smart contract and a chain identifier of a target blockchain where the target smart contract is located;

If a client such as a business system needs to call a target smart contract, it can send a smart contract call request to the middle-tier server. The smart contract call request includes the contract identifier of the target smart contract and the target area where the target smart contract is located. The chain identity of the blockchain. Specifically, the business system can call the contract invocation interface provided by the middle-tier server, and submit a contract invocation request containing specified information (such as chain ID, contract ID, contract name, and function call parameters) to the middle-tier server. After receiving the smart contract calling request, the middle-tier server can find the corresponding target blockchain according to the chain ID in the request, and obtain the corresponding target smart contract from the target blockchain according to the contract ID in the request.

The target blockchain is pre-registered and deployed to the middle-tier server, and the target smart contract has been deployed to the target blockchain and registered to the middle-tier server. After the target blockchain is registered, the middle-tier server will assign a chain ID to the target blockchain to uniquely represent the target blockchain. After the target smart contract is registered, the middle-tier server will also assign a contract ID to the target smart contract to uniquely represent the target smart contract. The middle-tier server can send the registered chain identifiers of different blockchains and the registered contract identifiers of different smart contracts to each client, so that the client can use it when calling the smart contract.

(1) Obtain the connection information and related files of the target blockchain;

(2) Initialize the software development kit corresponding to the platform type of the target blockchain according to the connection information and related files;

(3) Connectivity test is performed on the software development kit that has been initialized;

(4) If the connectivity test passes, store the connection information and related files in the database, and assign a chain identifier to the target blockchain, so as to register and deploy the target blockchain to all the middle-tier server.

The above steps describe the registration and deployment process of the target blockchain, however, it should be understood that any blockchain can be registered and deployed to the middle-tier server through the same steps above. When the target blockchain is registered, the user can click on the middle-tier server to create a new blockchain, and then obtain the connection information and related files of the target blockchain. Wherein, the connection information may include information such as blockchain IP address, blockchain interface, blockchain platform type and platform version, and related files may include SDK certificates and other blockchain-related files.

The connection information and related files can be submitted to the middle-tier server through the corresponding interface, and the submitted connection information or related files will vary depending on the blockchain platform. After receiving the connection information and related files submitted by the target blockchain, the middle-tier server will initialize the SDK (software development kit) corresponding to the platform type of the target blockchain according to the information and files. The initialization parameters can include Blockchain IP address, blockchain interface and SDK certificate, etc. For example, if the platform type of the target blockchain is fabric, the SDK corresponding to the fabric platform is initialized; if the platform type of the target blockchain is Ethereum, the SDK corresponding to the Ethereum platform is initialized, and so on.

After the software development kit is initialized, the middle-tier server performs a connectivity call test to verify whether it can be connected and used normally. If the connectivity test passes, the middle-tier server will store the connection information and related files in the database, and assign a chain ID to the target blockchain, thus completing the operation of registering and deploying the target blockchain to the middle-tier server; If the connectivity test fails, it means that the target blockchain registration fails, and an error message can be returned to remind technicians to find the cause of the blockchain registration error.

(1) Deploy the target smart contract into the target blockchain, and obtain the contract information of the target smart contract;

(2) Complete the registration of the target smart contract according to the contract information, and assign a contract identifier to the target smart contract.

The above steps describe the deployment and registration process of the target smart contract deployment, however, it should be understood that any smart contract can be registered to the middle-tier server through the same steps above. After the registration and deployment of the target blockchain is completed, the registration process of the target smart contract needs to be performed. Specifically, the target smart contract is first deployed to the registered target blockchain, and the corresponding contract information is obtained. For the blockchain of the Ethereum platform, the contract address and the contract interface description file can be obtained as the contract information; For the blockchain of the fabric platform, the contract name can be obtained as contract information. After obtaining the contract information of the target smart contract, the middle-tier server will complete the registration of the target smart contract according to the contract information, and assign a contract ID to it. The chain identifies the chain ID association.

202. Find the contract information of the target smart contract according to the contract identifier;

After receiving the smart contract calling request, the middle-tier server searches for the contract information of the target smart contract according to the contract identifier in the request. Specifically, the contract information of the target smart contract can be stored in the database of the middle-tier server after the contract is registered. At this time, the middle-tier server can find the corresponding contract information from the database through the contract identifier. For the blockchain of the Ethereum platform, the contract information here can be the contract address and interface description file corresponding to the contract identifier; for the fabric platform The contract information here can be the contract name corresponding to the contract identifier.

203. Based on the contract information and the chain identifier, initiate a smart contract execution request to the target blockchain, and obtain the execution result of the target smart contract;

The corresponding target blockchain can be determined through the chain identifier, and then the contract information is used to initiate a smart contract execution request to the target blockchain, thereby obtaining the execution result of the target smart contract. For a more specific description of step 203, reference may be made to the next embodiment of the present application.

204. Return the execution result of the target smart contract to the client.

After obtaining the execution result of the target smart contract from the target blockchain, the middle-tier server will return the obtained execution result to the client, thereby completing a smart contract invocation process. In addition, if the invocation of the target smart contract fails, the middle-tier server can return notification information of the failure of the invocation of the smart contract to the client.

In general, the key technical points of this application are:

(1) When the middle-tier server connects to a new blockchain, the implementation method of modifying the middle-tier code and then updating in the prior art is modified to the method of submitting new chain connection information for registration;

(2) When a new contract is deployed on the blockchain, the method of encapsulating the new contract interface by the middle-tier server in the existing technology and exposing it to the business system through a specific interface is modified to only register the necessary for smart contract calls Information (contract address, contract name, etc.) is sent to the middle-tier server, and only the general contract calling interface is provided to the middle-tier server to make custom calls, which greatly improves the flexibility of operation.

Please refer to FIG. 3, which shows another blockchain smart contract calling method provided by the embodiment of the present application, including:

301. Receive a smart contract invocation request sent by a client, where the smart contract invocation request includes a contract identifier of a target smart contract and a chain identifier of a target blockchain where the target smart contract is located;

302. Find the contract information of the target smart contract according to the contract identifier;

Steps 301-302 are the same as steps 201-202, for details, please refer to the relevant description of steps 201-202.

303. Activate a software development kit corresponding to the chain identifier;

The middle-tier server can determine the corresponding target blockchain through the chain identification, find the corresponding chain information, and activate the SDK corresponding to the chain identification, that is, the software development kit. When the target blockchain is registered, its corresponding SDK has been initialized, and in step 303, the initialized SDK will be activated and started.

304. Invoke the activated software development kit to initiate a smart contract execution request to the target blockchain according to the contract information, and obtain the execution result of the target smart contract;

Call the activated software development kit to realize the execution result of the smart contract from the blockchain. The specific operation method is to initiate a smart contract execution request to the target blockchain according to the contract information, and obtain the target smart contract. The execution result of the contract.

The smart contract invocation request sent by the business system may also include other attribute information of the target smart contract, such as contract function name, function invocation parameters and other information. When calling the target smart contract, this part of the attribute information can be combined with the contract information and submitted to the corresponding target blockchain to initiate a smart contract execution request.

For the blockchain of the Ethereum platform, the contract information includes the contract address and interface description file, and combined with the contract function name and function call parameters submitted from the business system, it sends a smart contract execution request to the blockchain to obtain The corresponding smart contract execution result.

For the blockchain of the fabric platform, the contract information includes the contract name, combined with the contract function name and function call parameters submitted from the business system, and sends a smart contract execution request to the blockchain to obtain the corresponding smart contract execution. result.

305. Return the execution result of the target smart contract to the client.

After obtaining the execution result of the target smart contract from the target blockchain, the middle-tier server will return the obtained execution result to the client, thereby completing a smart contract invocation process. In addition, if the invocation of the target smart contract fails due to the absence of the contract address, the non-existence of the contract function name, or the illegal contract parameter list, the middle-tier server can return the notification information of the failure of the smart contract invocation to the client.

For ease of understanding, the following uses an actual application scenario to illustrate the blockchain smart contract calling method proposed in this application.

FIG. 4 is a schematic schematic diagram of a method for invoking a smart contract on the Ethereum blockchain provided by an embodiment of the present application. In Figure 4, business system A needs to call the smart contract in the Ethereum blockchain through the middle-tier server. The specific operation process is as follows:

(4.1) The business system A calls the contract calling interface provided by the middle-tier server, which will contain information such as chain ID, contract ID, contract function name (method Name) and function call parameter list (argList). The contract call request is submitted to the middle-tier server;

(4.2) After receiving the contract call request, the middle-tier server queries the corresponding blockchain information through the chain ID, and then activates the SDK corresponding to the chain ID, that is, the SDK corresponding to the Ethereum platform (Fig. SDK-eth in 4);

(4.3) The middle-tier server queries the corresponding contract information from the database through the contract ID. For the blockchain of the Ethereum platform, the contract information can include information such as the contract address (address) and the contract interface description file (ABI). ;

(4.4) The middle-tier server calls the activated SDK. For the blockchain of the Ethereum platform, the contract address (address) and the contract interface description file (ABI) corresponding to the contract ID (contract ID) are combined with the contract interface description file (ABI), as well as the data sent by business system A. Contract function name (method Name) and function call parameter list (argList) and other information, initiate a smart contract execution request to the Ethereum blockchain corresponding to the chain ID to find and obtain the contract address (address) corresponding to the smart contract. Results of the;

(4.5) If the smart contract invocation is successful, the middle-tier server returns the execution result of the smart contract to the business system A, thus completing a smart contract invocation process. If the smart contract invocation fails, for example, the smart contract invocation fails due to the absence of the contract address (address), the non-existence of the contract function name (method Name), or the invalid function call parameter list (argList), the middle-tier server can return The error message that the smart contract invocation failed is sent to the business system A.

FIG. 5 is a schematic diagram of the principle of a method for invoking a smart contract on a fabric blockchain provided by an embodiment of the present application. In Figure 5, the business system B needs to call the smart contract in the fabric blockchain through the middle-tier server. The specific operation process is as follows:

(5.1) The business system B calls the contract calling interface provided by the middle-tier server, which will contain information such as chain ID, contract ID, contract function name (method Name) and function call parameter list (argList). The contract call request is submitted to the middle-tier server;

(5.2) After receiving the contract call request, the middle-tier server queries the corresponding blockchain information through the chain ID, and then activates the SDK corresponding to the chain ID, that is, the SDK corresponding to the fabric platform (Figure 5). SDK-fabric in );

(5.3) The middle-tier server queries the corresponding contract information from the database through the contract ID. For the blockchain of the fabric platform, the contract information can include contract name and other information;

(5.4) The middle-tier server calls the activated SDK. For the blockchain of the fabric platform, combine the contract name (contract Name) corresponding to the contract ID (contract ID), and the contract function name (method Name) and the contract function name (method Name) sent by business system B. Function call parameter list (argList) and other information, initiate a smart contract execution request to the fabric blockchain corresponding to the chain ID to find and obtain the execution result of the smart contract corresponding to the contract name;

(5.5) If the smart contract invocation is successful, the middle-tier server returns the execution result of the smart contract to the business system B, thereby completing a smart contract invocation process. If the smart contract invocation fails, for example, the contract name (contract Name) does not exist, the contract function name (method Name) does not exist, or the function invocation parameter list (argList) is invalid due to the reason that the smart contract invocation fails, the middle-tier server can return The error message that the smart contract call fails is sent to the business system B.

It should be noted that although the above only lists the actual application scenarios for the Ethereum blockchain and the fabric blockchain, this application can implement smart contract calls based on any blockchain platform. If you need to support new blockchains The platform only needs the middle-tier server to customize the operation of the following links, and then it can permanently support the new blockchain platform's smart contract invocation proxy process. The specific links include:

(1) According to the connection requirements of the new blockchain platform, a new type of blockchain registration information is added;

(2) According to the contract calling specification of the new blockchain platform, a new type of smart contract registration information has been added;

(3) According to the contract call specification of the new blockchain platform, implement the SDK initialization and transaction packaging logic of the new platform.

It should be understood that the size of the sequence numbers of the steps in the above-mentioned various embodiments does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. .

A method for invoking a smart contract of a blockchain is mainly described above, and a device for invoking a smart contract of a blockchain will be described below.

Referring to FIG. 6, an embodiment of a blockchain smart contract invocation device in the embodiment of the present application includes:

The contract invocation request receiving module 601 is configured to receive a smart contract invocation request sent by the client, where the smart contract invocation request includes the contract identifier of the target smart contract and the chain identifier of the target blockchain where the target smart contract is located, wherein , the target blockchain has been registered and deployed to the middle-tier server, and the target smart contract has been registered to the middle-tier server;

A contract information search module 602, configured to search for the contract information of the target smart contract according to the contract identifier;

A smart contract search module 603, configured to initiate a smart contract execution request to the target blockchain based on the contract information and the chain identifier, and obtain the execution result of the target smart contract;

The smart contract returning module 604 is configured to return the execution result of the target smart contract to the client.

In an embodiment of the present application, the smart contract search module may include:

a toolkit activation unit for activating a software development toolkit corresponding to the chain identifier;

A smart contract search unit, configured to call the activated software development toolkit to initiate a smart contract execution request to the target blockchain according to the contract information, and obtain the execution result of the target smart contract.

Further, the smart contract invocation request further includes attribute information of the target smart contract, and the smart contract search unit may be specifically configured to: initiate a smart contract to the target blockchain through the contract information and the attribute information contract execution request, and obtain the execution result of the target smart contract.

In an embodiment of the present application, the target blockchain is a blockchain of the Ethereum platform, the contract information includes a contract address and an interface description file of the target smart contract, and the attribute information includes the target The contract function name and function call parameters of the smart contract. The smart contract search unit may include:

The first contract search subunit is used to initiate a smart contract execution request to the target blockchain in combination with the contract address, the interface description file, the contract function name and the function call parameters, and obtain the target smart The execution result of the contract.

In an embodiment of the present application, the target blockchain is a blockchain of the fabric platform, the contract information includes a contract name of the target smart contract, and the attribute information includes a contract function of the target smart contract name and function call parameters, the smart contract lookup unit may include:

The second contract search subunit is configured to initiate a smart contract execution request to the target blockchain by combining the contract name, the contract function name and the function call parameter, and obtain the execution result of the target smart contract.

In an embodiment of the present application, the smart contract invoking device may further include:

A block chain information acquisition module, used to acquire the connection information and related files of the target block chain;

a toolkit initialization module for initializing a software development toolkit corresponding to the platform type of the target blockchain according to the connection information and related files;

A connectivity test module, used to perform connectivity test on the initialized software development kit;

A chain identification allocation module is used to store the connection information and related files in a database if the connectivity test passes, and assign a chain identification to the target blockchain, thereby registering the target blockchain and deployed to the middle-tier server.

a smart contract deployment module, configured to deploy the target smart contract into the target blockchain and obtain contract information of the target smart contract;

The contract identification allocation module is used for completing the registration of the target smart contract according to the contract information, and assigning a contract identification to the target smart contract.

Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, any blockchain as shown in FIG. 2 or FIG. 3 is implemented. The steps for the smart contract to call a method.

The embodiment of the present application also provides a computer program product, when the computer program product runs on the terminal device, the terminal device is made to execute the steps of implementing any blockchain smart contract invocation method as shown in FIG. 2 or FIG. 3 . .

FIG. 7 is a schematic diagram of a server provided by an embodiment of the present application. As shown in FIG. 7 , the server 7 of this embodiment includes a processor 70 , a memory 71 , and a computer program 72 stored in the memory 71 and executable on the processor 70 . When the processor 70 executes the computer program 72, the steps in each of the above embodiments of the smart contract invocation method are implemented, for example, steps 201 to 204 shown in FIG. 2 . Alternatively, when the processor 70 executes the computer program 72, the functions of the modules/units in each of the foregoing apparatus embodiments, such as the functions of the modules 601 to 604 shown in FIG. 6 , are implemented.

The computer program 72 may be divided into one or more modules/units, which are stored in the memory 71 and executed by the processor 70 to complete the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program 72 in the server 7 .

The so-called processor 70 may be a central processing unit (Central Processing Unit, CPU), and may also be other general-purpose processors, digital signal processors (Digital Signal Processors, DSP), application specific integrated circuits (Application Specific Integrated Circuits) Integrated Circuit, ASIC), off-the-shelf programmable gate array (Field-Programmable Gate Array, 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 the processor may be any conventional processor or the like.

The memory 71 may be an internal storage unit of the server 7 , such as a hard disk or a memory of the server 7 . The memory 71 may also be an external storage device of the server 7, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a Secure Digital (SD) card equipped on the server 7, Flash card (Flash Card) and so on. Further, the memory 71 may also include both an internal storage unit of the server 7 and an external storage device. The memory 71 is used to store the computer program and other programs and data required by the server. The memory 71 may also be used to temporarily store data that has been output or will be output.

The above-mentioned embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the above-mentioned embodiments, those of ordinary skill in the art should understand that: it can still be used for the above-mentioned implementations. The technical solutions described in the examples are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions in the embodiments of the application, and should be included in the within the scope of protection of this application.

Claims

A method for invoking a smart contract of a blockchain, applied to a middle-tier server, characterized in that the method comprises:

Receive a smart contract invocation request sent by the client, where the smart contract invocation request includes the contract identifier of the target smart contract and the chain identifier of the target blockchain where the target smart contract is located, wherein the target blockchain has been registered and deployed to the middle-tier server, and the target smart contract has been registered with the middle-tier server;

Find the contract information of the target smart contract according to the contract identifier;

Based on the contract information and the chain identifier, initiate a smart contract execution request to the target blockchain, and obtain the execution result of the target smart contract;

Return the execution result of the target smart contract to the client.
The smart contract calling method according to claim 1, wherein based on the contract information and the chain identifier, a smart contract execution request is initiated to the target blockchain, and an execution result of the target smart contract is obtained ,include:

activate the software development kit corresponding to the chain identifier;

The activated software development kit is invoked to initiate a smart contract execution request to the target blockchain according to the contract information, and obtain the execution result of the target smart contract.
The smart contract invocation method according to claim 2, wherein the smart contract invocation request further includes attribute information of the target smart contract, and the smart contract is initiated to the target blockchain according to the contract information. Execute the request and obtain the execution result of the target smart contract, including:

A smart contract execution request is initiated to the target blockchain through the contract information and the attribute information, and the execution result of the target smart contract is obtained.
The method for invoking a smart contract according to claim 3, wherein the target blockchain is a blockchain of the Ethereum platform, and the contract information includes a contract address and an interface description file of the target smart contract. The attribute information includes the contract function name and function call parameters of the target smart contract, the smart contract execution request is initiated to the target blockchain through the contract information and the attribute information, and the data of the target smart contract is obtained. Execution results, including:

Initiate a smart contract execution request to the target blockchain in combination with the contract address, the interface description file, the contract function name and the function call parameters, and obtain the execution result of the target smart contract.
The smart contract calling method according to claim 3, wherein the target blockchain is a blockchain of a fabric platform, the contract information includes a contract name of the target smart contract, and the attribute information includes all The contract function name and function call parameters of the target smart contract, the smart contract execution request is initiated to the target blockchain through the contract information and the attribute information, and the execution result of the target smart contract is obtained, including:

A smart contract execution request is initiated to the target blockchain in combination with the contract name, the contract function name and the function call parameters, and the execution result of the target smart contract is obtained.
The smart contract invocation method according to any one of claims 1 to 5, wherein the target blockchain is registered and deployed to the middle-tier server through the following steps:

Obtain the connection information and related files of the target blockchain;

Initialize a software development kit corresponding to the platform type of the target blockchain according to the connection information and related files;

Connectivity testing is performed on the software development kit that has been initialized;

If the connectivity test passes, store the connection information and related files in a database, and assign a chain identifier to the target blockchain, so as to register and deploy the target blockchain to the middle layer server.
The smart contract invocation method according to claim 6, wherein the target smart contract is registered to the middle-tier server through the following steps:

deploying the target smart contract into the target blockchain, and obtaining contract information of the target smart contract;

The registration of the target smart contract is completed according to the contract information, and a contract identifier is allocated to the target smart contract.
A smart contract invocation device for blockchain, applied to a middle-tier server, characterized in that the device includes:

The contract invocation request receiving module is used to receive a smart contract invocation request sent by the client, where the smart contract invocation request includes the contract identifier of the target smart contract and the chain identifier of the target blockchain where the target smart contract is located, wherein, The target blockchain has been registered and deployed to the middle-tier server, and the target smart contract has been registered with the middle-tier server;

a contract information search module, configured to search for the contract information of the target smart contract according to the contract identifier;

a smart contract search module, configured to initiate a smart contract execution request to the target blockchain based on the contract information and the chain identifier, and obtain the execution result of the target smart contract;

The smart contract return module is used for returning the execution result of the target smart contract to the client.
A server, comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, when the processor executes the computer program, the implementation of claims 1 to 7 The steps of the smart contract calling method of the blockchain described in any one of the steps.
A computer-readable storage medium storing a computer program, characterized in that, when the computer program is executed by a processor, the blockchain according to any one of claims 1 to 7 is implemented The steps for the smart contract to call a method.