WO2023103341A1

WO2023103341A1 - Blockchain-based smart contract invocation method, apparatus and device

Info

Publication number: WO2023103341A1
Application number: PCT/CN2022/100650
Authority: WO
Inventors: 郭锐; 李辉忠; 范瑞彬; 张开翔
Original assignee: 深圳前海微众银行股份有限公司
Priority date: 2021-12-07
Filing date: 2022-06-23
Publication date: 2023-06-15
Also published as: CN113888173A; CN113888173B

Abstract

Provided in the embodiments of the present disclosure are a blockchain-based smart contract invocation method, apparatus and device. The method comprises: receiving pieces of transaction information sent by a client, wherein each piece of transaction information includes path information of a smart contract, to be executed, corresponding to the transaction information; putting the pieces of received transaction information into a scheduler, so that the scheduler distributes the pieces of transaction information to different executors; querying a storage unit by means of the executors and on the basis of the path information of the smart contracts, to be executed, corresponding to the pieces of transaction information, so as to acquire smart contracts corresponding to the pieces of transaction information, wherein the storage unit includes smart contracts which are stored according to a tree file directory structure, and the storage path of each smart contract is unique; and executing the smart contracts on the pieces of transaction information by means of the executors, so as to obtain an execution result. There is no need for executors to synchronize CNS table data related to smart contracts while concurrent execution is performed on a transaction, thereby improving the efficiency of a blockchain when concurrent execution of smart contracts is performed on transaction information.

Description

Smart contract call method, device and equipment based on block chain

This application claims the priority of the Chinese patent application with the application number 202111478999.7 and the application title "Blockchain-based smart contract call method, device and equipment" submitted to the China Patent Office on December 07, 2021, the entire content of which is passed References are incorporated in this application.

technical field

Embodiments of the present disclosure relate to the technical field of financial technology (Fintech), and in particular to a blockchain-based smart contract calling method, device and equipment.

Background technique

With the development of computer technology, more and more technologies are applied in the financial field. The traditional financial industry is gradually transforming into financial technology (Fintech), and the smart contract technology related to blockchain is no exception. However, due to the security of the financial industry It also puts forward higher requirements for smart contract technology.

At present, in the existing smart contract management process based on the consortium blockchain, usually the executor (Ethereum smart contract virtual machine) that executes the smart contract in the node of the blockchain will maintain a CNS (Contract Name Service , contract naming service) table, the CNS table stores the mapping relationship between the smart contract name and the smart contract address. Smart contract address, and obtain the corresponding smart contract from the smart contract address to execute the transaction.

However, in some scenarios, the blockchain needs to execute transactions in parallel, and multiple executors of the blockchain need to execute smart contracts in parallel. In this case, each executor needs to maintain a CNS table (the mapping relationship between the smart contract name and the smart contract address), when the user modifies the smart contract related information in the CNS table in an executor , it is necessary to synchronize the data of the modified CNS table to all other executors, otherwise other executors will execute wrong smart contracts, thus resulting in frequent synchronization of CNS table data between executors, affecting the blockchain Processing efficiency for executing multiple smart contracts in parallel.

technical solution

Embodiments of the present disclosure provide a blockchain-based smart contract calling method, device, and equipment to overcome the need for frequent synchronization of CNS table data between executors in the related art, which affects the parallel execution of multiple smart contracts by the blockchain. problem of processing efficiency.

In the first aspect, an embodiment of the present disclosure provides a method for invoking a smart contract based on blockchain, the method is applied to any node of the blockchain, and the node is provided with a system for scheduling and distributing transaction information. A scheduler, an executor for executing smart contracts and a storage unit for storing smart contracts, the method includes:

receiving the transaction information sent by the client, wherein the transaction information includes path information of the smart contract to be executed corresponding to the transaction information, wherein the path information corresponds to a unique smart contract storage path;

Putting the received transaction information into the scheduler so that the scheduler distributes the transaction information to different executors;

Based on the path information of the smart contract to be executed corresponding to each transaction information, each executor queries the storage unit to obtain the smart contract corresponding to each transaction information, wherein the storage unit contains each smart contract stored according to the tree file directory structure. contract, and the storage path of each smart contract is unique;

Each executor executes the smart contract on the transaction information to obtain an execution result.

In a possible design, the storage unit contains smart contracts stored in a tree-shaped file directory structure, and the storage path of each smart contract is unique, specifically: the storage unit contains Stored directory resources and smart contract resources; each directory resource contains multiple sub-resources, the same type of smart contract resources belong to the last sub-resource under the same directory resource, and the smart contract resource contains the code segment information of the smart contract and status information.

In a possible design, each executor queries the storage unit to obtain the smart contract corresponding to each transaction information based on the path information of the smart contract to be executed corresponding to each transaction information, including: corresponding to any transaction information Split the path information of the smart contract to be executed to obtain the names of the storage tables corresponding to the path information; access the corresponding storage tables in the storage unit in turn according to the names of the storage tables to obtain the corresponding smart contract resources.

In a possible design, the sequentially accessing the corresponding storage tables in the storage unit according to the names of the storage tables to obtain the smart contract resources corresponding to the path information includes: accessing the cache, from the cache Read each storage table whose name is the name of each storage table in turn; if each storage table can be read from the cache, then query each storage table sequentially from the cache according to the names of each storage table until it is determined The storage table corresponding to the smart contract resource, to obtain the smart contract resource corresponding to the path information from the storage table corresponding to the smart contract resource; if the storage table cannot be read from the cache, then from the storage unit of the block chain Query each storage table in turn according to the names of the storage tables until the storage table corresponding to the smart contract resource is determined, so as to obtain the smart contract resource corresponding to the path information from the storage table corresponding to the smart contract resource.

In a possible design, the storage tables are queried sequentially according to the names of the storage tables until the storage table corresponding to the smart contract resource is determined, so as to obtain the smart information corresponding to the path information from the storage table corresponding to the smart contract resource. Contract resources, including: according to the level of each storage table name in the path information, query the storage tables corresponding to each storage table name one by one to obtain the storage table corresponding to the smart contract resource, so as to obtain the storage table corresponding to the smart contract resource. Obtain the smart contract resource corresponding to the path information.

In a possible design, it also includes the step of storing each smart contract according to the tree file directory structure, as follows: determine any directory resource by creating or querying; write the smart contract to be created in the directory resource.

In one possible design, any directory resource is determined by creation or query, including:

Generate the storage table name of any directory resource according to the user's input; judge whether the storage table name of the directory resource already exists; if not, create the directory resource, wherein the directory resource includes the meta information of the directory; if If it exists, it is judged whether the name of the storage table is the table name of the smart contract resource, and if not, a prompt that the directory resource already exists is returned.

In a possible design, the writing the smart contract to be created in the directory resource includes: generating the storage table name of any smart contract according to user input; judging whether the storage table name of the smart contract is Exist; if not, then obtain the directory resource, and start the virtual machine to execute the smart contract, if the execution is successful, then write the code segment information and status information of the smart contract in the directory resource.

In the second aspect, the embodiment of the present disclosure provides a block chain-based smart contract calling device, the device is applied to any node of the block chain, and the node is provided with a system for scheduling and distributing transaction information. A scheduler, an executor for executing smart contracts and a storage unit for storing smart contracts, the device includes:

The receiving module is used to receive the transaction information sent by the client, wherein the transaction information includes the path information of the smart contract to be executed corresponding to the transaction information, wherein the path information corresponds to a unique smart contract storage path;

A scheduling module, configured to put the received transaction information into a scheduler so that the scheduler distributes the transaction information to different executors;

The dispatching module is used to query the storage unit to obtain the smart contract corresponding to each transaction information through each executor based on the path information of the smart contract to be executed corresponding to each transaction information, wherein the storage unit contains the following information according to the tree file directory Each smart contract stored in the structure, and the storage path of each smart contract is unique;

The execution module is configured to execute the smart contract on the transaction information through each executor to obtain an execution result.

In a third aspect, an embodiment of the present disclosure provides a service device, including: a processor and a memory;

the memory stores computer-executable instructions;

The processor executes the computer-executed instructions stored in the memory, so that the processor executes the blockchain-based smart contract calling method described in the first aspect and various possible designs of the first aspect.

In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the processor executes the computer-executable instructions, the above first aspect and the first The smart contract calling method based on the block chain described in various possible designs.

In the blockchain-based smart contract calling method, device, and equipment provided by the embodiments of the present disclosure, any node of the blockchain carries the path information of the smart contract to be executed corresponding to the transaction information in the transaction information, and the The path information corresponds to the unique storage path of the smart contract; the storage unit of each node of the blockchain stores the smart contracts stored according to the tree file directory structure, and the storage path of each smart contract is unique, the blockchain node According to the path information, each executor accesses the storage unit to obtain the corresponding smart contract according to the unique smart contract storage path, and executes the transaction information according to the smart contract to obtain the execution result. Since the smart contracts stored in the storage unit according to the tree-shaped file directory structure are unique and isolated from each other when they are scheduled by different executors, it is not necessary for each executor to perform smart contract-related CNS when executing transactions in parallel. The synchronization of table data improves the efficiency of blockchain in parallel execution of smart contracts for transaction information.

Description of drawings

FIG. 1 is a schematic diagram of a scenario of a blockchain-based smart contract calling method provided by the present disclosure;

FIG. 2 is a first schematic flow diagram of a blockchain-based smart contract calling method provided by an embodiment of the present disclosure;

FIG. 3 is a logical structure diagram of smart contracts stored according to the tree-shaped file directory structure provided by the embodiment of the present disclosure;

Fig. 4 is a schematic diagram of the actual storage form of the smart contract provided by the embodiment of the present disclosure;

FIG. 5 is a second schematic flow diagram of a blockchain-based smart contract calling method provided by an embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of a block chain-based smart contract calling device provided by an embodiment of the present disclosure;

FIG. 7 is a second structural diagram of a blockchain-based smart contract calling device provided by an embodiment of the present disclosure;

FIG. 8 is a schematic diagram of a hardware structure of a service device provided by an embodiment of the present disclosure.

Embodiments of the present invention

In order to make the purpose, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments It is a part of the embodiments of the present disclosure, but not all of them. Based on the embodiments in the present disclosure, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present disclosure.

Explanation of technical terms:

Blockchain: The blockchain system can be understood as a distributed storage system maintained and trusted by multiple nodes. The bottom layer of the blockchain is a chain composed of a series of blocks. In addition to recording the data of this block, each block also records the hash value of the previous block. In this way, a chained data structure is formed. A block consists of a block header and a block body, where the block header defines important fields such as the height of the block and the hash value of the previous block, while the block body mainly stores transaction data. The blockchain uses cryptography to ensure the security of data transmission and access, and uses a chain structure to ensure that the data on the chain cannot be tampered with.

Smart contract: A smart contract refers to a contract defined in digital form that can automatically execute terms. The digital form means that the contract must be implemented with computer code, because as long as the participants reach an agreement, the rights and obligations established by the smart contract will be automatically executed. And the results cannot be denied. In blockchain applications, when the transaction to deploy the smart contract reaches a consensus among most nodes, it can be considered that the smart contract has been embedded in the blockchain system.

Ethereum Virtual Machine (the executor of the smart contract): After the smart contract is compiled into a binary file, it is deployed to the node of the blockchain. The user triggers the execution of the smart contract by calling the interface of the smart contract. As the executor of the smart contract code, the Ethereum virtual machine executes the code of the smart contract and modifies the data (state) on the current blockchain. The modified data will be consensused to ensure consistency.

Referring to FIG. 1 , FIG. 1 is a schematic diagram of a scenario of a blockchain-based smart contract calling method provided by the present disclosure. In this scenario, it includes: client 101 and blockchain node 102, which can install SDK (Software Development Kit, software development kit) for initiating transactions and generating transaction information. Wherein the client 101 may be a personal computer, a mobile terminal or other devices such as servers.

Among them, the blockchain node 102 can be any node in the blockchain system, for example, it can be any node participating in the consensus process in the blockchain, or a leader node elected from the consensus nodes, and this disclosure does not make any any restrictions. The blockchain node 102 is used to receive the transaction information sent by the client, and obtain the smart contract corresponding to the transaction information. Based on the smart contract, the Ethereum virtual machine (executor) is used to execute the transaction information to obtain the execution result. Consensus is carried out in the blockchain, and after the consensus is completed, it is stored on the blockchain.

At present, in the smart contract management call based on the alliance blockchain, usually the executor (Ethereum smart contract virtual machine) that executes the smart contract in the node of the blockchain will maintain a CNS table. When the executor needs to When executing a smart contract for a certain transaction obtained, the CNS table will be accessed first to query the corresponding smart contract address, and the corresponding smart contract will be obtained from the smart contract address to execute the transaction. However, if the blockchain needs to execute transactions in parallel, multiple executors of the blockchain need to execute smart contracts in parallel. , the data of the modified CNS table must be synchronized to all other executors, otherwise other executors will execute wrong smart contracts, thus resulting in the need for frequent synchronization of CNS table data between executors, affecting blockchain parallelism Processing efficiency for executing multiple smart contracts.

In order to solve the above technical problems, this disclosure provides the following technical solutions: carrying the path information of the smart contract to be executed corresponding to the transaction information in the transaction information, and the path information corresponds to the unique storage path of the smart contract; The storage unit stores smart contracts that are stored according to the tree-shaped file directory structure, and the storage path of each smart contract is unique. Each executor of the blockchain node accesses the storage unit according to the path information and stores them according to the unique smart contract. The path obtains the corresponding smart contract, executes the transaction information according to the smart contract, and obtains the execution result. Since the smart contracts stored in the storage unit according to the tree-shaped file directory structure are unique and isolated from each other when they are scheduled by different executors, it is not necessary for each executor to synchronize the CNS table data when executing transactions in parallel , which greatly improves the efficiency of the blockchain in parallel execution of smart contracts for transaction information.

Referring to FIG. 2 , FIG. 2 is a first schematic flowchart of a blockchain-based smart contract calling method provided by an embodiment of the present disclosure. This embodiment is applied to any node of the block chain shown in Figure 1, and the node is provided with a scheduler for scheduling and distributing transaction information, an executor for executing smart contracts, and a storage device for storing smart contracts. unit, the above method is detailed as follows:

S201: Receive the transaction information sent by the client, wherein the transaction information includes the path information of the smart contract to be executed corresponding to the transaction information, wherein the path information corresponds to a unique storage path of the smart contract.

In the embodiment of the present disclosure, the client may be any client that has a transaction behavior, and the client generates transaction information according to the transaction behavior and sends it to any node of the blockchain. For example, a user purchases goods in an online mall and completes the transaction through the client, and the client sends the transaction information of the purchased goods to any node in the blockchain. In this embodiment, any node of the blockchain is any node among the consensus nodes in the blockchain. The leader node is elected from the consensus nodes of the blockchain. Any consensus node can be either a leader node or a replica node.

In the disclosed embodiment, while the client generates transaction information according to the transaction behavior, the user can specify the smart contract to be executed corresponding to the transaction information on the client side, and add the path information of the smart contract to be executed to the transaction information. Wherein, the path information corresponds to a unique smart contract storage path, and the corresponding smart contract is obtained through the unique smart contract storage path according to the path information.

S202: Put the received transaction information into the scheduler so that the scheduler distributes the transaction information to different executors.

In the embodiment of the present disclosure, the scheduler is a virtual scheduler set in the nodes of the blockchain, and the virtual scheduler distributes each transaction information that can execute the smart contract in parallel to different executors according to preset rules.

Wherein, the preset rule may be to evenly distribute each transaction information to each executor. For example, if there are 10 transaction information and 2 executors, 5 transaction information can be assigned to one executor, and the other 5 transaction information can be assigned to another executor.

S203: Through each executor, based on the path information of the smart contract to be executed corresponding to each transaction information, query the storage unit to obtain the smart contract corresponding to each transaction information, wherein the storage unit contains each smart contract stored according to the tree file directory structure contract, and the storage path of each smart contract is unique.

In the embodiment of the present disclosure, the storage unit contains smart contracts stored according to the tree-shaped file directory structure, and the storage path of each smart contract is unique, specifically: the storage unit contains directory resources stored in the form of a storage table and smart contract resources; each directory resource contains multiple sub-resources, and the same type of smart contract resources belong to the last sub-resource under the same directory resource, and the smart contract resource contains the code segment information and status information of the smart contract.

Referring to FIG. 3 , FIG. 3 is a logical structure diagram of smart contracts stored in a tree-shaped file directory structure according to an embodiment of the present disclosure. Among them, "/" is the root directory, which contains multiple directory resources, as shown in Figure 3, "sys", "usr", "apps", and "tables" are all directory resources, which are system class directories Resources, user class directory resources, application class directory resources, and table class directory resources. Wherein, each directory resource includes a plurality of sub-resources, and the sub-resources may be a sub-resource of the current directory resource, or may directly be smart contract resources. As shown in Figure 3, the sub-resources of "sys1" and "sys2" contained in "sys" are the directory resources of the next level of directory resources, and "sys1" and "sys2" each contain two system smart contract resources , where "sys1" includes "system smart contract resource 1" and "system smart contract resource 2"; "sys2" includes "system smart contract resource 3" and "system smart contract resource 4". Other "usr", "apps", and "tables" are directory resources, and their corresponding sub-resources are directly smart contract resources; among them, "usr" includes "user smart contract resource 1", "user smart contract resource 2 "; "apps" includes "application smart contract resource 1" and "application smart contract resource 2"; "tables" includes "table smart contract resource 1" and "table smart contract resource 2". In this embodiment, the above "resources" may be stored in the form of files or tables, and this disclosure does not impose any limitation on this.

Referring to FIG. 4, FIG. 4 is a schematic diagram of the actual storage form of the smart contract provided by the embodiment of the present disclosure. The storage unit contains directory resources and smart contract resources stored in the form of storage tables. As shown in Figure 4, the storage table name is: "/tables" is a directory resource, and the storage table names of the smart contract resources contained in it are "/tables/table1" and "/tables/table2". Among them, the storage table named "/tables" describes the meta information of smart contract resources, and the storage table named "/tables/table1" and "/tables/table2" respectively contain tables Data for smart contracts "table1" and "table2".

Specifically, through each executor, based on the path information of the smart contract to be executed corresponding to each transaction information, query the storage unit to obtain the smart contract corresponding to each transaction information, including:

Split the path information of the smart contract to be executed corresponding to any transaction information to obtain the names of the storage tables corresponding to the path information; access the corresponding storage tables in the storage unit in turn according to the names of the storage tables to obtain the path information corresponding smart contract resources.

In the embodiment of the present disclosure, the path information "/apps/Hello1" is taken as an example for description:

Split the path information "/apps/Hello1" into "/", "/apps" and "/apps/Hello1"; "/", "/apps" and "/apps/Hello1" respectively correspond to a storage table name, Among them, "/" is the name of the storage table of the root directory resource, "/apps" is the name of the storage table of the directory resource, and /apps/Hello1" is the name of the storage table of the smart contract resource.

Specifically, according to the names of the storage tables, the corresponding storage tables in the storage unit are sequentially accessed to obtain the smart contract resources corresponding to the path information, including: accessing the cache, and sequentially reading the storage tables whose names are the names of the storage tables from the cache ; If the storage tables can be read from the cache, query the storage tables in sequence according to the names of the storage tables from the cache until the storage table corresponding to the smart contract resource is determined, so as to obtain path information from the storage table corresponding to the smart contract resource Corresponding smart contract resources; if the storage tables cannot be read from the cache, query each storage table in turn from the storage unit of the blockchain according to the names of the storage tables until the storage table corresponding to the smart contract resource is determined, so as to obtain the data from the smart contract. Get the smart contract resource corresponding to the path information in the storage table corresponding to the resource.

Among them, query each storage table in turn according to the name of each storage table until the storage table corresponding to the smart contract resource is determined, so as to obtain the smart contract resource corresponding to the path information from the storage table corresponding to the smart contract resource, including: according to the name of each storage table in the path The level in the information, query the storage table corresponding to each storage table name one by one to obtain the storage table corresponding to the smart contract resource, and obtain the smart contract resource corresponding to the path information from the storage table corresponding to the smart contract resource.

In the embodiment of the present disclosure, after the transaction information of the smart contract that can be executed in parallel is distributed to different executors, each executor will first read the cache. If the executor has executed the same smart contract before, then the execution The server will cache the data corresponding to the smart contract, and the data corresponding to the smart contract includes each storage table corresponding to the storage path of the smart contract.

Take two smart contracts whose execution path information is "/apps/Hello1" and "/tables/table1" respectively for any executor as an example to illustrate:

The executor will first read the storage table named "/apps" and the storage table "/tables" from the cache; and then read the Take the storage table whose names are "/apps/Hello1" and "/tables/table1", respectively, where the storage table of "/apps/Hello1" and "/tables/table1" respectively contain Smart contract resources for the "Hello1" smart contract and the "table1" smart contract.

If the executor does not read the above storage tables from the cache, it will obtain the corresponding storage tables from the storage unit, and write the storage tables obtained from the storage unit into the executor. The writing process For slow writing, it takes longer than reading directly from the buffer.

It should be noted that each storage table of the smart contract can support distributed storage of data in the storage unit, so that when the executor loads each storage table from the storage unit, all data is dispersed.

Referring to Figure 3 and Figure 4, it can be understood that when the executor loads the smart contract from the storage unit, the sub-resources under each directory resource cannot have the same name. Therefore, from the root directory down to each smart contract resource The path of each is unique, making the smart contract loaded by the executor unique. In addition, when the executor loads the smart contract from the storage unit, the smart contracts of different paths can be executed by different executors, so that different smart contracts are isolated from each other.

In an embodiment of the present disclosure, when the executor loads the smart contract from the storage unit, it can also specify the path of a certain directory resource, and load all the smart contracts under the directory resource to the same executor, so that different execution The directory resources loaded by the server are different, so as to achieve the isolation of smart contracts at the directory resource level.

S204: Execute the smart contract on the transaction information through each executor, and obtain the execution result.

In the embodiment of the present disclosure, the executor executes the smart contract on the transaction information, obtains the execution result of the transaction information, and then sends the execution result of the transaction information to other consensus nodes in the blockchain for consensus. After the consensus of the execution result, the execution result of the transaction information is stored on the chain in the blockchain.

It can be seen from the above description that by carrying the path information of the smart contract to be executed corresponding to the transaction information in the transaction information, and the path information corresponds to the unique storage path of the smart contract; Each smart contract stored in the tree-shaped file directory structure, and the storage path of each smart contract is unique, each executor of the blockchain node accesses the storage unit according to the path information to obtain the corresponding smart contract according to the unique smart contract storage path, and Execute the transaction information according to the smart contract and get the execution result. Since the smart contracts stored in the storage unit according to the tree-shaped file directory structure are unique and isolated from each other when they are scheduled by different executors, it is not necessary for each executor to perform smart contract-related CNS when executing transactions in parallel. The synchronization of table data improves the efficiency of blockchain in parallel execution of smart contracts for transaction information.

Referring to FIG. 5 , FIG. 5 is a second schematic flow diagram of a blockchain-based smart contract calling method provided by an embodiment of the present disclosure. This embodiment also describes the steps of how to store each smart contract according to the tree-shaped file directory structure, which is detailed as follows:

S501: Determine any directory resource by creating or querying.

Specifically, by creating or querying, determine any directory resource, including:

Generate the storage table name of any directory resource according to the user's input;

Determine whether the storage table name of the directory resource already exists;

If it does not exist, create a directory resource and write the meta information of the directory in the directory resource;

If it exists, judge whether the storage table name is the table name of the smart contract resource, if not, return the prompt that the directory resource already exists.

In the embodiment of the present disclosure, the user can create a new directory resource under any existing directory resource.

Take the creation of the directory resource of "/apps/Hello" as an example to illustrate:

Generate the storage table name of "/apps/Hello/World";

Determine whether "/apps/Hello/World" already exists;

If it does not exist, create the directory "/apps/Hello/", and create the "/apps/Hello/World" storage table, and write the meta information of the directory in the "/apps/Hello/World" storage table, and get "/ apps/Hello/" directory resource, and returns a prompt that the directory was created successfully;

If it exists, access the storage table "/apps/Hello/World" of the directory "/apps/Hello/", and determine the storage table type of "/apps/Hello/World"; if the storage table type is a directory resource, return A reminder that the directory resource already exists; if the storage table type is a smart contract resource, a reminder that the smart contract resource already exists will be returned.

S502: Write the smart contract to be created in the directory resource.

Specifically, write the smart contract to be created in the directory resource, including:

Generate the storage table name of any smart contract according to the user's input;

Determine whether the storage table name of the smart contract already exists;

If it does not exist, the directory resource is obtained, and the virtual machine is started to execute the smart contract. If the execution is successful, the code segment information and status information of the smart contract are written in the directory resource.

In the embodiment of the present disclosure, when deploying a contract, it will be pre-determined that the parent directory of the level directory already exists and information can be written, and then the virtual machine is started to execute the deployment and creation contract operation; after the virtual machine is successfully executed, the contract table is created, And write the contract code segment, ABI, state data, etc. after the virtual machine is executed into the contract table, and finally record the meta information of the newly deployed contract in the data table of the parent directory.

Take the smart contract test1 of "/apps/Hello" as an example to illustrate:

Deployment smart contract "/apps/Hello/test1" storage table name;

Determine whether the storage table name "/apps/Hello/test1" already exists;

If it does not exist, obtain the directory resource "/apps/Hello", and start the virtual machine to execute the smart contract test1 to be deployed. If the execution is successful, write the code segment information and status information of the smart contract test1 in the directory resource, and Feedback the prompt of successful deployment; if the execution fails, return the prompt of execution failure;

If it exists, return the prompt that the smart contract "/apps/Hello/test1" already exists.

It should be noted that users can access the meta information of resources (directory resources and smart contract resources) under any path through the interface. When accessing, it is pre-determined whether there is a resource in the path, and if it exists, access the storage table of the upper-level directory resource to check whether the target resource under the path is a smart contract resource or a directory resource. If it is a smart contract resource, it will return the meta information of the smart contract; if it is a directory resource type, it will return the meta information of the directory resource, and return all sub-resources under the path (which contains all the smart contract meta information).

Referring to FIG. 6 , FIG. 6 is a first structural diagram of a block chain-based smart contract calling device provided by an embodiment of the present disclosure. As shown in Figure 6, the block chain-based smart contract calling device 60 is applied to any node of the block chain, and the node is provided with a scheduler for scheduling and distributing transaction information, for executing An executor of the smart contract and a storage unit for storing the smart contract, the device includes: a receiving module 601 , a scheduling module 602 , a processing module 603 and an executing module 604 .

Wherein, the receiving module 601 is used to receive the transaction information sent by the client, wherein the transaction information includes the path information of the smart contract to be executed corresponding to the transaction information, wherein the path information corresponds to a unique smart contract storage path ;

A scheduling module 602, configured to put the received transaction information into the scheduler so that the scheduler distributes the transaction information to different executors;

The processing module 603 is used to query the storage unit to obtain the smart contract corresponding to each transaction information through each executor based on the path information of the smart contract to be executed corresponding to each transaction information, wherein the storage unit contains information according to the tree file Each smart contract stored in the directory structure, and the storage path of each smart contract is unique;

The execution module 604 is configured to execute the smart contract on the transaction information through each executor to obtain an execution result.

By carrying the path information of the smart contract to be executed corresponding to the transaction information in the transaction information, and the path information corresponds to the unique storage path of the smart contract; the storage unit of each node of the blockchain stores the information according to the tree file directory structure Each stored smart contract, and the storage path of each smart contract is unique, each executor of the blockchain node accesses the storage unit according to the path information to obtain the corresponding smart contract according to the unique smart contract storage path, and executes the transaction according to the smart contract information to get the execution result. Since the smart contracts stored in the storage unit according to the tree-shaped file directory structure are unique and isolated from each other when they are scheduled by different executors, it is not necessary for each executor to perform smart contract-related CNS when executing transactions in parallel. The synchronization of table data improves the efficiency of blockchain in parallel execution of smart contracts for transaction information.

In one or more embodiments of the present disclosure, the storage unit contains smart contracts stored in a tree-shaped file directory structure, and the storage path of each smart contract is unique, specifically: the storage unit contains the following Store directory resources and smart contract resources stored in the form of tables; each directory resource contains multiple sub-resources, the same type of smart contract resources belong to the last sub-resource under the same directory resource, and the smart contract resource contains the code of the smart contract segment information and status information.

In one or more embodiments of the present disclosure, the scheduling module 602 is specifically configured to: split the path information of the smart contract to be executed corresponding to any transaction information, and obtain the storage Table name; according to the names of the storage tables, access the corresponding storage tables in the storage unit in order to obtain the smart contract resources corresponding to the path information.

In one or more embodiments of the present disclosure, the scheduling module 602 is specifically configured to sequentially access the corresponding storage tables in the storage unit according to the names of the storage tables, so as to obtain the intelligence information corresponding to the path information. The process of contract resources, including: accessing the cache, sequentially reading the storage tables whose names are the names of the storage tables from the cache; if the storage tables can be read from the cache, then from the cache Query each storage table in turn according to the names of the storage tables until the storage table corresponding to the smart contract resource is determined, so as to obtain the smart contract resource corresponding to the path information from the storage table corresponding to the smart contract resource; Each storage table is read from the storage unit of the blockchain, and each storage table is queried sequentially according to the names of the storage tables in the blockchain until the storage table corresponding to the smart contract resource is determined, so as to obtain all data from the storage table corresponding to the smart contract resource. The smart contract resource corresponding to the above path information.

In one or more embodiments of the present disclosure, the scheduling module 602 is specifically used to inquire each storage table in turn according to the names of the storage tables until the storage table corresponding to the smart contract resource is determined, so as to obtain from the smart contract resource The process of obtaining the smart contract resource corresponding to the path information in the corresponding storage table includes: according to the level of each storage table name in the path information, query the storage table corresponding to each storage table name one by one to obtain the smart contract resource The corresponding storage table is used to obtain the smart contract resource corresponding to the path information from the storage table corresponding to the smart contract resource.

The device provided in this embodiment can be used to implement the technical solutions of the above method embodiments, and its implementation principle and technical effect are similar, so this embodiment will not repeat them here.

Referring to FIG. 7 , FIG. 7 is a second schematic structural diagram of a blockchain-based smart contract calling device provided by an embodiment of the present disclosure. As shown in Figure 7, the block chain-based smart contract calling device 60 also includes:

A directory creation module 605, configured to determine any directory resource by creating or querying;

A contract creation module 606, configured to write the smart contract to be created in the directory resource.

In one or more embodiments of the present disclosure, the directory creation module 605 is specifically configured to generate the storage table name of any directory resource according to user input; determine whether the storage table name of the directory resource already exists; if If it does not exist, then create the directory resource, wherein the directory resource includes the meta information of the directory; if it exists, then judge whether the storage table name is the table name of the smart contract resource, if not, then return that the directory resource has been hints that exist.

In one or more embodiments of the present disclosure, the directory creation module 606 is specifically configured to generate the storage table name of any smart contract according to user input; determine whether the storage table name of the smart contract already exists; if If it does not exist, then obtain the directory resource, start a virtual machine to execute the smart contract, and if the execution is successful, write the code segment information and status information of the smart contract in the directory resource.

Referring to FIG. 8 , FIG. 8 is a schematic diagram of a hardware structure of a service device provided by an embodiment of the present disclosure. As shown in FIG. 8, the service device 80 of this embodiment includes: a processor 801 and a memory 802;

memory 802, for storing computer-executable instructions;

The processor 801 is configured to execute the computer-executed instructions stored in the memory, so as to realize the various steps executed by the server-side blockchain in the above-mentioned embodiments. For details, refer to the related descriptions in the foregoing method embodiments.

Optionally, the memory 802 can be independent or integrated with the processor 801 .

When the memory 802 is set independently, the service-based device further includes a bus 803 for connecting the memory 802 and the processor 801 .

An embodiment of the present disclosure also provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the processor executes the computer-executable instructions, the aforementioned blockchain-based intelligence Contract call method.

An embodiment of the present disclosure also provides a computer program product, when the computer program is executed by a processor, it implements the blockchain-based smart contract calling method as described above.

In the several embodiments provided in the present disclosure, it should be understood that the disclosed devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the modules is only a logical function division. In actual implementation, there may be other division methods, for example, multiple modules can be combined or integrated. to another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or modules may be in electrical, mechanical or other forms.

The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the modules can be selected according to actual needs to implement the solution of this embodiment.

In addition, each functional module in each embodiment of the present disclosure may be integrated into one processing unit, each module may exist separately physically, or two or more modules may be integrated into one unit. The units formed by the above modules can be implemented in the form of hardware, or in the form of hardware plus software functional units.

The above-mentioned integrated modules implemented in the form of software function modules can be stored in a computer-readable storage medium. The above-mentioned software function modules are stored in a storage medium, and include several instructions for enabling a computer device (which may be a personal computer, server, or network device, etc.) or a processor to execute some steps of the methods described in various embodiments of the present disclosure.

It should be understood that the above-mentioned processor may be a central processing unit (Central Processing Unit, referred to as CPU), and may also be other general-purpose processors, digital signal processors (Digital Signal Processor (DSP for short), Application Specific Integrated Circuit (ASIC for short), etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like. The steps of the method disclosed in conjunction with the invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.

The storage may include a high-speed RAM memory, and may also include a non-volatile storage NVM, such as at least one disk storage, and may also be a U disk, a mobile hard disk, a read-only memory, a magnetic disk, or an optical disk.

The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI for short) bus or Extended Industry Standard Architecture (Extended Industry Standard Architecture, EISA for short) bus, etc. The bus can be divided into address bus, data bus, control bus and so on. For ease of representation, the buses in the drawings of the present disclosure are not limited to only one bus or one type of bus.

The above-mentioned storage medium can be realized by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable In addition to programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be a component of the processor. Processors and storage media can be located in application-specific integrated circuits (Application Specific Integrated Circuits, referred to as ASIC). Of course, the processor and the storage medium can also exist in the electronic device or the main control device as discrete components.

Those of ordinary skill in the art can understand that all or part of the steps for implementing the above method embodiments can be completed by program instructions and related hardware. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps including the above-mentioned method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present disclosure, not to limit them; although the present disclosure has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the various embodiments of the present disclosure. scope.

Claims

A blockchain-based smart contract calling method, characterized in that the method is applied to any node of the blockchain, and the node is provided with a scheduler for scheduling and distributing transaction information, for An executor for executing smart contracts and a storage unit for storing smart contracts, the method includes:

receiving the transaction information sent by the client, wherein the transaction information includes path information of the smart contract to be executed corresponding to the transaction information, wherein the path information corresponds to a unique smart contract storage path;

Putting the received transaction information into the scheduler so that the scheduler distributes the transaction information to different executors;

Based on the path information of the smart contract to be executed corresponding to each transaction information, each executor queries the storage unit to obtain the smart contract corresponding to each transaction information, wherein the storage unit contains each smart contract stored according to the tree file directory structure. contract, and the storage path of each smart contract is unique;

Each executor executes the smart contract on the transaction information to obtain an execution result.
The method according to claim 1, wherein the storage unit includes each smart contract stored according to a tree-shaped file directory structure, and the storage path of each smart contract is unique, specifically: in the storage unit Contains directory resources and smart contract resources stored in the form of storage tables; each directory resource contains multiple sub-resources, and smart contract resources of the same type belong to the last sub-resource under the same directory resource, and smart contract resources contain smart contracts Code segment information and status information for .
The method according to claim 2, characterized in that, each executor queries the storage unit to obtain the smart contract corresponding to each transaction information based on the path information of the smart contract to be executed corresponding to each transaction information, including:

Split the path information of the smart contract to be executed corresponding to any transaction information to obtain the names of the storage tables corresponding to the path information;

The corresponding storage tables in the storage unit are sequentially accessed according to the names of the storage tables, so as to obtain the smart contract resources corresponding to the path information.
The method according to claim 3, wherein the sequentially accessing the corresponding storage tables in the storage unit according to the names of the storage tables to obtain the smart contract resources corresponding to the path information includes:

Accessing the cache, sequentially reading the storage tables whose names are the names of the storage tables from the cache; if the storage tables can be read from the cache, then from the cache according to the storage tables The name inquires each storage table in turn until the storage table corresponding to the smart contract resource is determined, so as to obtain the smart contract resource corresponding to the path information from the storage table corresponding to the smart contract resource;

If the storage tables cannot be read from the cache, then query each storage table in turn from the storage unit of the block chain according to the names of the storage tables until the storage table corresponding to the smart contract resource is determined, so as to obtain the corresponding storage table from the smart contract resource. Obtain the smart contract resource corresponding to the path information in the storage table of
The method according to claim 4, wherein the storage tables are inquired in turn according to the names of the storage tables until the storage table corresponding to the smart contract resource is determined, so as to obtain the storage table corresponding to the smart contract resource. Smart contract resources corresponding to path information, including:

According to the level of each storage table name in the path information, query the storage table corresponding to each storage table name one by one to obtain the storage table corresponding to the smart contract resource, so as to obtain the path information from the storage table corresponding to the smart contract resource The corresponding smart contract resource.
The method according to any one of claims 1 to 5, further comprising the step of storing each smart contract according to a tree-shaped file directory structure, as follows:

Identify any catalog resource by creating or querying;

Write the smart contract to be created in the directory resource.
The method according to claim 6, wherein said determining any directory resource by creating or querying comprises:

Generate the storage table name of any directory resource according to the user's input;

Judging whether the name of the storage table of the directory resource already exists;

If it does not exist, create the directory resource, wherein the directory resource includes meta information of the directory;

If it exists, it is judged whether the storage table name is the table name of the smart contract resource, and if not, a prompt that the directory resource already exists is returned.
The method according to claim 6 or 7, wherein the writing the smart contract to be created in the directory resource includes:

Generate the storage table name of any smart contract according to the user's input;

Judging whether the name of the storage table of the smart contract already exists;

If it does not exist, the directory resource is obtained, and the virtual machine is started to execute the smart contract. If the execution is successful, the code segment information and status information of the smart contract are written in the directory resource.
A block chain-based smart contract calling device, characterized in that the device is applied to any node of the block chain, and the node is provided with a scheduler for scheduling and distributing transaction information, for An executor for executing smart contracts and a storage unit for storing smart contracts, the device includes:

The receiving module is used to receive the transaction information sent by the client, wherein the transaction information includes the path information of the smart contract to be executed corresponding to the transaction information, wherein the path information corresponds to a unique smart contract storage path;

A scheduling module, configured to put the received transaction information into a scheduler so that the scheduler distributes the transaction information to different executors;

The dispatching module is used to query the storage unit to obtain the smart contract corresponding to each transaction information through each executor based on the path information of the smart contract to be executed corresponding to each transaction information, wherein the storage unit contains the following information according to the tree file directory Each smart contract stored in the structure, and the storage path of each smart contract is unique;

The execution module is configured to execute the smart contract on the transaction information through each executor to obtain an execution result.
A service device, characterized in that it comprises:

processor and memory;

the memory stores computer-executable instructions;

The processor executes the computer-executed instructions stored in the memory, so that the processor executes the blockchain-based smart contract calling method according to any one of claims 1 to 8.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer-executable instructions, and when the processor executes the computer-executable instructions, the method described in any one of claims 1 to 8 is realized. Blockchain-based smart contract calling method.
A computer program product, comprising a computer program, characterized in that, when the computer program is executed by a processor, the blockchain-based smart contract calling method according to any one of claims 1 to 8 is realized.