WO2022077186A1

WO2022077186A1 - Execution method and apparatus for smart contract in blockchain, and electronic device

Info

Publication number: WO2022077186A1
Application number: PCT/CN2020/120487
Authority: WO
Inventors: 刘海峰; 郭三彬; 陈复星; 李腾; 卓越; 雷宇
Original assignee: 北京和联共识科技有限公司
Priority date: 2020-10-12
Filing date: 2020-10-12
Publication date: 2022-04-21
Also published as: CN112400182A

Abstract

An execution method and apparatus for a smart contract in a blockchain, and an electronic device. The method comprises: receiving a first transaction submitted by a user, wherein the first transaction carries a first contract address of a logic contract needing to be called for service execution (310); in response to the first transaction, calling the logic contract corresponding to the first contract address, and acquiring a service logic maintained in a contract account corresponding to the logic contract (320); determining a field name of status data which is lacking in execution of the service logic (330); calling a routing contract of a blockchain, and querying a second contract address mapped from the first contract address in a mapping table maintained in a contract account corresponding to the routing contract (340); calling a data contract corresponding to the second contract address, and acquiring status data of the field name maintained in a contract account corresponding to the data contract (350); and supplementing the status data, which is lacking in the service logic, with the status data, so as to execute the service logic (360).

Description

Execution method and device and electronic device of smart contract in blockchain

technical field

One or more embodiments of this specification relate to the field of blockchain technology, and in particular, to a method and apparatus for executing a smart contract in a blockchain, and an electronic device.

Background technique

Blockchain technology, also known as distributed ledger technology, is an emerging technology in which several computing devices jointly participate in "bookkeeping" and jointly maintain a complete distributed database. Due to the characteristics of decentralization, openness and transparency of blockchain technology, each computing device can participate in database records, and data synchronization between computing devices can be performed quickly, blockchain technology has been widely used in many fields. to apply.

SUMMARY OF THE INVENTION

The embodiments of this specification provide a method, device, and electronic device for creating, upgrading, and executing a smart contract in a blockchain.

According to a first aspect of the embodiments of this specification, a method for executing a smart contract in a blockchain is provided, the method comprising:

Receive the first transaction submitted by the user; wherein, the first transaction carries the first contract address of the logical contract that needs to be invoked for business execution;

In response to the first transaction, call the logic contract corresponding to the first contract address to obtain the business logic maintained in the contract account corresponding to the logic contract;

determining the field name of the state data missing from the execution of the business logic;

Invoke the routing contract of the blockchain, and query the second contract address mapped to the first contract address in the mapping table maintained in the contract account corresponding to the routing contract;

calling the data contract corresponding to the second contract address to obtain the status data of the field name maintained in the contract account corresponding to the data contract;

The state data is supplemented to the missing state data in the business logic to execute the business logic.

Optionally, the method further includes:

After executing the business logic to generate the new state data of the target field, the data contract corresponding to the second contract address is called to update the state data of the target field maintained in the contract account corresponding to the data contract, so that the The state data of the target field is modified to new state data.

Optionally, the method further includes:

Receive the second transaction submitted by the user; wherein, the second transaction carries the business logic of the smart contract to be created;

In response to the second transaction, a logic contract is created, and the business logic is written in a contract account corresponding to the logic contract;

Create a data contract, and write the initial state data of each field in the business logic into the contract account corresponding to the data contract;

Call the routing contract in the blockchain, update the mapping table maintained in the contract account corresponding to the routing contract, and write the first contract address corresponding to the logic contract and the second contract address of the data contract the mapping table.

Optionally, the method further includes:

Receive the third transaction submitted by the user; wherein, the third transaction carries the first contract address of the old logic contract to be upgraded and the new business logic to be upgraded;

In response to the third transaction, a new logic contract is created, and the new business logic is written in the contract account corresponding to the new logic contract;

Invoke the routing contract in the blockchain, update the mapping table maintained in the contract account corresponding to the routing contract, to modify the first contract address of the old logical contract in the mapping table to the new logical contract 's first contract address.

Optionally, the method further includes:

If the new business logic adds a new field compared to the old business logic, a new data contract is created, and the initial state data of the new field is written in the contract account corresponding to the new data contract;

Call the routing contract in the blockchain, update the mapping table maintained in the contract account corresponding to the routing contract, to add the first contract address and the second contract address of the new data contract in the mapping table. Mapping relations.

Optionally, if the first transaction also carries business-related status data, in response to the first transaction, call the logical contract corresponding to the first contract address to obtain the contract account corresponding to the logical contract The business logic maintained in , specifically includes:

In response to the first transaction, call the routing contract of the blockchain, and query the second contract address mapped to the first contract address in the mapping table maintained in the contract account corresponding to the routing contract;

Further call the data contract corresponding to the second contract address, and update the state data of the target field maintained in the contract account corresponding to the data contract, so as to record the state data carried by the first transaction;

Further call the logic contract corresponding to the first contract address to obtain the business logic maintained in the contract account corresponding to the logic contract.

Optionally, the state data maintained by the contract account corresponding to the data contract is located in an asset mapping table, and the asset mapping table stores the state data of user accounts and user assets;

The invoking the data contract corresponding to the second contract address to update the state data of the target field maintained in the contract account corresponding to the data contract includes:

If the first transaction is a credit transaction of user assets, call the data contract corresponding to the second contract address, and record the status data of the user account and user assets in the asset mapping table;

If the first transaction is an outgoing transaction of user assets, call the data contract corresponding to the second contract address to verify whether the user account indicated by the first transaction is located in the asset mapping table;

The logic contract corresponding to the first contract address is called, and the business logic maintained in the contract account corresponding to the logic contract is obtained,

When the user account is located in the asset mapping table, the logic contract corresponding to the first contract address is further invoked to obtain business logic maintained in the contract account corresponding to the logic contract.

According to a second aspect of the embodiments of this specification, a method for creating a smart contract in a blockchain, the method includes:

According to a third aspect of the embodiments of this specification, a method for upgrading a smart contract in a blockchain, the method includes:

Optionally, the method further includes:

According to a fourth aspect of the embodiments of this specification, a device for executing a smart contract in a blockchain, the device includes:

The receiving unit receives the first transaction submitted by the user; wherein, the first transaction carries the first contract address of the logical contract that needs to be invoked for business execution;

The response unit, in response to the first transaction, invokes the logic contract corresponding to the first contract address, and obtains the business logic maintained in the contract account corresponding to the logic contract;

A determining unit, determining the field name of the state data lacking in the execution of the business logic;

A routing unit, calling the routing contract of the blockchain, and querying the second contract address mapped to the first contract address in the mapping table maintained in the contract account corresponding to the routing contract;

an obtaining unit, calling the data contract corresponding to the second contract address to obtain the status data of the field name maintained in the contract account corresponding to the data contract;

An execution unit, supplementing the state data to the state data missing in the business logic, so as to execute the business logic.

Optionally, the device further includes:

The updating unit, after executing the business logic to generate the new state data of the target field, invokes the data contract corresponding to the second contract address to update the state data of the target field maintained in the contract account corresponding to the data contract , to modify the state data of the target field to new state data.

Optionally, the device further includes:

The first receiving subunit receives the second transaction submitted by the user; wherein, the second transaction carries the business logic of the smart contract to be created;

The first response subunit, in response to the second transaction, creates a logic contract, and writes the business logic in the contract account corresponding to the logic contract;

The first creation sub-unit, creates a data contract, and writes the initial state data of each field in the business logic in the contract account corresponding to the data contract;

The first update sub-unit calls the routing contract in the blockchain, and updates the mapping table maintained in the contract account corresponding to the routing contract, so as to convert the first contract address corresponding to the logical contract to the data contract's address. The second contract address is written into the mapping table.

Optionally, the device further includes:

The second receiving subunit receives the third transaction submitted by the user; wherein, the third transaction carries the first contract address of the old logic contract to be upgraded and the new business logic to be upgraded;

The second response subunit, in response to the third transaction, creates a new logic contract, and writes the new business logic in the contract account corresponding to the new logic contract;

The second update subunit invokes the routing contract in the blockchain to update the mapping table maintained in the contract account corresponding to the routing contract, so as to modify the first contract address of the old logical contract in the mapping table to The first contract address of the new logical contract.

Optionally, the device further includes:

The second creation sub-unit, if the new business logic adds a new field compared to the old business logic, a new data contract is created, and the new field is written in the contract account corresponding to the new data contract. initial state data;

The third update subunit calls the routing contract in the blockchain, and updates the mapping table maintained in the contract account corresponding to the routing contract, so as to add the first contract address and the new data contract to the mapping table The mapping relationship of the second contract address.

Optionally, the response unit includes:

If the first transaction also carries business-related status data, in response to the first transaction, call the routing contract of the blockchain, and query the mapping table maintained in the contract account corresponding to the routing contract. The second contract address mapped by the first contract address; further call the data contract corresponding to the second contract address to update the status data of the target field maintained in the contract account corresponding to the data contract to record the first Status data carried by the transaction; further call the logic contract corresponding to the first contract address to obtain the business logic maintained in the contract account corresponding to the logic contract.

In the response unit, the data contract corresponding to the second contract address is called to update the status data of the target field maintained in the contract account corresponding to the data contract, including:

In the response unit, the logic contract corresponding to the first contract address is invoked, and the business logic maintained in the contract account corresponding to the logic contract is obtained, including:

According to a fifth aspect of the embodiments of this specification, an apparatus for creating a smart contract in a blockchain, the apparatus includes:

The receiving unit receives the second transaction submitted by the user; wherein, the second transaction carries the business logic of the smart contract to be created;

a response unit, in response to the second transaction, creating a logic contract, and writing the business logic in a contract account corresponding to the logic contract;

The creation unit creates a data contract, and writes the initial state data of each field in the business logic into the contract account corresponding to the data contract;

An update unit, calling the routing contract in the blockchain, and updating the mapping table maintained in the contract account corresponding to the routing contract, so as to convert the first contract address corresponding to the logical contract to the second contract of the data contract address is written to the mapping table.

According to a sixth aspect of the embodiments of the present specification, a device for upgrading a smart contract in a blockchain, the device includes:

The receiving unit receives the third transaction submitted by the user; wherein, the third transaction carries the first contract address of the old logic contract to be upgraded and the new business logic to be upgraded;

The response unit, in response to the third transaction, creates a new logical contract, and writes the new business logic in the contract account corresponding to the new logical contract;

The upgrading unit calls the routing contract in the blockchain, and updates the mapping table maintained in the contract account corresponding to the routing contract, so as to modify the first contract address of the old logical contract in the mapping table to the new one The first contract address of the logical contract.

Optionally, the device further includes:

The creation unit, if the new business logic adds a new field compared to the old business logic, create a new data contract, and write the initial state data of the new field in the contract account corresponding to the new data contract ;

The updating unit calls the routing contract in the blockchain, and updates the mapping table maintained in the contract account corresponding to the routing contract, so as to add the first contract address and the second address of the new data contract to the mapping table. The mapping relationship of contract addresses.

According to a seventh aspect of the embodiments of this specification, a smart contract of a blockchain, the smart contract is composed of a logic contract, a routing contract, and a data contract;

Business logic is maintained in the contract account corresponding to the logic contract;

A mapping table is maintained in the contract account corresponding to the routing contract, and the mapping table stores the mapping relationship between the first contract address of the logic contract and the second contract address of the data contract;

The state data generated by the execution of the logic contract is maintained in the contract account corresponding to the data contract.

According to an eighth aspect of the embodiments of the present specification, an electronic device is provided, including:

processor;

memory for storing processor-executable instructions;

Wherein, the processor is configured to execute, create, and upgrade the smart contracts in any of the above-mentioned blockchains.

The embodiments of this specification provide a solution for executing, creating, and upgrading smart contracts in the blockchain, by dividing smart contracts into logical contracts, routing contracts, and data contracts. The logic contract that maintains business logic no longer maintains state data, so there are no restrictions on asset security and data migration, making business logic upgradeable and pluggable. When the business logic is upgraded, the logic contract that writes the new business logic is directly created, and the mapping relationship between the data contract that stores the state data and the old logic contract is modified to the new logic contract by updating the mapping table maintained by the routing contract.

Description of drawings

1 is a schematic diagram of a smart contract of a blockchain provided by an exemplary embodiment;

2 is a flow chart of a method for creating a smart contract in a blockchain provided by an exemplary embodiment;

3 is a flow chart of a method for upgrading a smart contract in a blockchain provided by an exemplary embodiment;

4 is a flow chart of a method for executing a smart contract in a blockchain provided by an exemplary embodiment;

5 is a schematic structural diagram of an electronic device provided by an exemplary embodiment;

FIG. 6 is a block diagram of an apparatus for executing a smart contract in a blockchain provided by an exemplary embodiment.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. Where the following description refers to the drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments are not intended to represent all implementations consistent with one or more embodiments of this specification. Rather, they are merely examples of apparatus and methods consistent with some aspects of one or more embodiments of this specification, as recited in the appended claims.

It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may also be combined into a single step in other embodiments. describe. The first, the second, the third, etc. in this specification are for distinguishing the difference, rather than limiting the sequence.

For the convenience of understanding, the following first introduces some technical concepts in the blockchain.

Blockchains are generally divided into three types: Public Blockchain, Private Blockchain and Consortium Blockchain. In addition, there can also be a combination of the above-mentioned types, such as private chain + alliance chain, alliance chain + public chain, etc.

Among them, the most decentralized is the public chain. The public chain is represented by Bitcoin and Ethereum. Participants who join the public chain (also called nodes in the blockchain) can read the data records on the chain, participate in transactions, and compete for the accounting rights of new blocks, etc. . Moreover, each node can freely join or leave the network and perform related operations.

The private chain is on the contrary, the write permission of the network is controlled by an organization or institution, and the data read permission is regulated by the organization. In simple terms, a private chain can be a weakly centralized system with strict restrictions on nodes and a small number of nodes. This type of blockchain is more suitable for internal use within a specific institution.

The consortium chain is a blockchain between the public chain and the private chain, which can achieve "partial decentralization". Each node in the alliance chain usually has a corresponding entity or organization; the node joins the network through authorization and forms a stakeholder alliance to jointly maintain the operation of the blockchain.

Based on the basic characteristics of the blockchain, the blockchain is usually composed of several blocks. Timestamps corresponding to the creation time of the blocks are respectively recorded in these blocks, and all blocks form a time-ordered data chain strictly according to the timestamps recorded in the blocks.

For the real data generated in the physical world, it can be constructed into a standard transaction format supported by the blockchain, and then published to the blockchain, and the node devices in the blockchain will perform consensus processing on the received transactions , and after reaching a consensus, the node device in the blockchain as the accounting node will package the transaction into the block and store the certificate persistently in the blockchain.

In the field of blockchain, an important concept is Account; taking Ethereum as an example, Ethereum usually divides accounts into external accounts and contract accounts; external accounts are accounts directly controlled by users, also known as It is a user account; and a contract account is an account (ie, a smart contract) that is created by the user through an external account and contains the contract code.

For an account in the blockchain, a structure is usually used to maintain the account state of the account. When a transaction in a block is executed, the state of the account associated with that transaction in the blockchain usually changes as well.

Taking Ethereum as an example, the structure of an account usually includes fields such as Balance, Nonce, Code, and Storage. in:

The Balance field is used to maintain the current account balance of the account;

The Nonce field is used to maintain the number of transactions of the account; it is a counter used to ensure that each transaction can be processed only once, effectively avoiding replay attacks;

The Code field is used to maintain the contract code of the account; in practical applications, the Code field usually only maintains the hash value of the contract code; therefore, the Code field is usually also called the Codehash field.

The Storage field is used to maintain the state data of the account (the default field value is empty); for the contract account, an independent storage space is usually allocated to store the state data of the contract account; the independent storage space is usually Call it the account storage for this contract account. The state data of the contract account is usually constructed as a data structure of the MPT (Merkle Patricia Trie) tree and stored in the above-mentioned independent storage space; among them, the MPT tree constructed based on the state data of the contract account is usually also called the Storage tree. . The Storage field usually only maintains the root node of the Storage tree; therefore, the Storage field is usually also called the StorageRoot field.

Wherein, for the external account, the field values of the Code field and the Storage field shown above are all null values.

In practical applications, whether it is a public chain, a private chain or a consortium chain, it is possible to provide the function of smart contracts. A smart contract on the blockchain is a contract that can be triggered and executed by a transaction on the blockchain. Smart contracts can be defined in the form of code.

Taking Ethereum as an example, users are supported to create and invoke some complex logic in the Ethereum network. As a programmable blockchain, the core of Ethereum is the Ethereum Virtual Machine (EVM), and each Ethereum node can run the EVM. EVM is a Turing-complete virtual machine through which various complex logics can be implemented. Users publish and invoke smart contracts in Ethereum that run on the EVM. In fact, EVM directly runs virtual machine code (virtual machine bytecode, hereinafter referred to as "bytecode"), so smart contracts deployed on the blockchain can be bytecodes.

For the security of the blockchain, the smart contracts in the existing blockchain are designed to be immutable and non-upgradable. Taking Ethereum as an example, once a smart contract is created in the blockchain, the contract code of the business logic declared in the smart contract cannot be modified. However, any business logic needs to be changed to adapt to different needs, that is to say, there is a need to modify or upgrade smart contracts in practice. To this end, the business side needs to continuously release smart contracts with new business logic. However, doing so has the following problems:

The contract account corresponding to the smart contract not only maintains the contract code of the business logic (Code field), but also maintains stateful data (Storage field). Although the newly created smart contract can write the contract code of the new business logic, it cannot directly create the state data in the old smart contract. This requires additional operations to obtain, and the operation of synchronizing state data is more complicated. In addition, although the old smart contract can no longer be used, the maintained state data is no longer updated, but these state data are always recorded, which additionally occupies the resources of the blockchain. With the continuous iterative upgrade of smart contracts, the state data maintained in the old smart contracts will occupy more and more blockchain resources, thus continuously squeezing the available resources of the existing blockchain.

For this reason, this manual is mainly aimed at improving traditional smart contracts. Please refer to the smart contract of the blockchain provided by an exemplary embodiment of FIG. 1, the smart contract can be divided into a logic contract, a routing contract and a data contract; wherein:

As shown in Fig. 1, the logic contract can be upgraded (an embodiment of the logic contract upgrade will be described in detail later), and the data contract can be expanded (an embodiment of the data contract extension will be described in detail later). Users can initiate transactions to logic contracts or data contracts. The logic contract can read and write data to the data contract. Routing contracts are used to provide routing services to logic contracts or data contracts.

By dividing smart contracts into logical contracts, routing contracts and data contracts. The logic contract that maintains business logic no longer maintains state data, so there are no restrictions on asset security and data migration, making business logic upgradeable and pluggable. When the business logic is upgraded, the logic contract that writes the new business logic is directly created, and the mapping relationship between the data contract that stores the state data and the old logic contract is modified to the new logic contract by updating the mapping table maintained by the routing contract.

The subsequent examples of the creation, upgrade, and execution of smart contracts in the blockchain are all based on the improved smart contract architecture.

The following further describes an embodiment of the method for creating the smart contract shown in FIG. 2 . The method includes:

Step 110: Receive the second transaction submitted by the user; wherein, the second transaction carries the business logic of the smart contract to be created;

Step 120: In response to the second transaction, create a logic contract, and write the business logic in a contract account corresponding to the logic contract;

Step 130: Create a data contract, and write the initial state data of each field in the business logic into the contract account corresponding to the data contract;

Step 140: Invoke the routing contract in the blockchain, and update the mapping table maintained in the contract account corresponding to the routing contract, so as to link the first contract address corresponding to the logical contract with the second contract of the data contract. address is written to the mapping table.

In this embodiment, the user can send a transaction including the creation of a smart contract to the blockchain, and the transaction carries the contract code of the business logic. When the nodes in the blockchain reach an agreement through a consensus mechanism, the smart contract can be created.

Different from the existing creation of a smart contract, this embodiment not only creates a logic contract for storing business logic contract codes, but also creates a data contract for storing state data.

After the logical contract is created, a contract account corresponding to the logical contract appears on the blockchain, and the contract account has a unique contract address (called the first contract address). The contract code of the business logic carried in the transaction will be stored in the Code of the contract account corresponding to the logical contract (in some cases, the Code stores the hash pointer of the contract code, which is addressed to the contract code through the hash pointer). The Storage of the contract account corresponding to the logic contract is empty, that is, the logic contract only maintains business logic and does not store state data.

After the data contract is created, a contract account corresponding to the data contract appears on the blockchain, and the data account has a unique contract address (called the second contract address). The initial state data (usually 0) of each business field is written into the Storage of the contract account corresponding to the data contract. The code of the contract account corresponding to the data contract is empty, that is, the data contract only maintains state data and does not store business logic.

After both the logical contract and the data contract are created, the routing contract needs to update the mapping table maintained in its corresponding contract account to map the mapping relationship between the first contract address corresponding to the logical contract and the second contract address of the data contract Write the mapping table.

The following further introduces an embodiment of the method for upgrading the smart contract shown in FIG. 3 . The method includes:

Step 210: Receive a third transaction submitted by the user; wherein, the third transaction carries the first contract address of the old logic contract to be upgraded and the new business logic to be upgraded;

Step 220: In response to the third transaction, create a new logical contract, and write the new business logic in the contract account corresponding to the new logical contract;

Step 230: Invoke the routing contract in the blockchain to update the mapping table maintained in the contract account corresponding to the routing contract, so as to modify the first contract address of the old logical contract in the mapping table to the new one. The first contract address of the logical contract.

In this embodiment, the user can send a transaction including the upgraded smart contract to the blockchain, and the transaction carries the first contract address of the old logic contract and the contract code of the new business logic to be upgraded. When the nodes in the blockchain reach an agreement through a consensus mechanism, the smart contract can be upgraded.

Different from the existing upgraded smart contract, since the logic contract in this embodiment no longer maintains state data, there is no need to synchronize the state data maintained by the old contract.

After a new logical contract is created, a contract account corresponding to the new logical contract appears on the blockchain, and the contract account has a unique contract address (called the first contract address of the new logical contract). The contract code of the new business logic carried in the transaction will be saved in the Code of the contract account corresponding to the new logical contract (in some cases, the Code saves the hash pointer of the contract code, which is addressed to the contract code through the hash pointer) . The Storage of the contract account corresponding to the new logical contract is also empty, that is, the new logical contract only maintains business logic and does not store state data.

Since the state data is stored in the contract data, there is no need to synchronize the state to the new logical contract. In order for the new logic contract to obtain the required state data, the mapping table maintained by the routing contract needs to be updated. That is, the first contract address of the old logical contract in the mapping table is modified to the first contract address of the new logical contract, so as to invalidate the connection between the old logical contract and the data contract and establish a new logical contract and Links between data contracts.

Although the logic contract in this manual is modifiable and upgradeable, the data contract adheres to the concept of traditional smart contracts and cannot be modified or upgraded. Once the data contract is deployed on the chain, it cannot be modified, and the data structure (the current business field) will be locked in this data contract. However, in practical applications, if the business logic is iteratively upgraded, the corresponding data structure often also has iterations. For example, the business logic adds some business fields. But data contracts cannot be upgraded. Therefore, the smart contracts in the above-mentioned blockchain still have the problem of data expansion.

In response to this problem, this specification also proposes a solution for data expansion. On the basis of Figure 3, it can also include:

In this embodiment, if business logic needs to add new fields, these fields will be stored in a brand new data contract. At the same time, the second contract address and the included field names of the new data contract will be updated to the mapping table of the routing contract. The logic contract obtains the second contract address of the data contract corresponding to the new field by querying the mapping table. Thereby routing reads and writes.

It should be noted that, for the case where the logical contract maps multiple data contracts, in order to improve the query efficiency, the form of the mapping table maintained in the above routing contract may also include:

The first mapping relationship between the first contract address of the logical contract and each field, and the second mapping relationship between each field and the second contract address of the data contract to which it belongs.

In this way, through the two-layer mapping relationship, the state data corresponding to each field required for the execution of the logical contract can be finally determined.

The following further introduces an embodiment of the execution method of the smart contract shown in FIG. 4 . The smart contract is divided into a logical contract, a routing contract and a data contract; the contract account corresponding to the logical contract maintains business logic; the contract account corresponding to the routing contract maintains a mapping table, and the mapping table stores the logic The mapping relationship between the first contract address of the contract and the second contract address of the data contract; the contract account corresponding to the data contract maintains the state data generated by the execution of the logic contract; the method includes:

Step 310: Receive the first transaction submitted by the user; wherein, the first transaction carries the first contract address of the logical contract to be invoked for business execution;

Step 320: In response to the first transaction, call the logic contract corresponding to the first contract address to obtain the business logic maintained in the contract account corresponding to the logic contract;

Step 330: Determine the field name of the state data lacking in the execution of the business logic;

Step 340: Invoke the routing contract of the blockchain, and query the second contract address mapped to the first contract address in the mapping table maintained in the contract account corresponding to the routing contract;

Step 350: Invoke the data contract corresponding to the second contract address to obtain the status data of the field name maintained in the contract account corresponding to the data contract;

Step 360: Supplement the state data to the missing state data in the business logic to execute the business logic.

In this embodiment, the user sends a transaction containing the calling logic contract to the blockchain, and the From field of the transaction is used to record the address of the user who initiated the calling logic contract (that is, the address of the user's user account on the blockchain) , the To field is used to record the contract address of the called logical contract (that is, the first contract address of the logical contract on the blockchain), and the Data field of the transaction is used to record the method and parameters for calling the logical contract.

The node device in the blockchain executes the transaction in the local EVM, calls the logic contract corresponding to the first contract address, and obtains the contract code of the business logic maintained in the contract account corresponding to the logic contract.

Because the logic contract does not store state data, after determining the field name of the state data lacking in the execution of the business logic, by calling the routing contract of the blockchain, query the mapping table maintained in the contract account corresponding to the routing contract The second contract address mapped to the first contract address.

The data contract corresponding to the second contract address is further called to obtain the status data of the field name maintained in the contract account corresponding to the data contract.

At this time, the node device obtains the contract code of the business logic and the missing state data in the business logic, supplements the state data in the EVM to the missing state data in the business logic, and runs the business logic contract in the EVM code.

As can be seen from the above process, the execution of the smart contract provided in this embodiment obtains the contract code of the business logic from the logic contract, and obtains the data corresponding to the business logic from the routing contract through the mutual cooperation between the logic contract, the routing contract and the data contract. contract, and obtain relevant state data from the data contract, and finally assemble the contract code and state data into a complete executable code to run in the EVM.

In practical applications, after calling the smart contract, the corresponding state data will change, so the state data needs to be updated. Therefore, on the basis of the above Figure 4, it can also include:

After the execution of the business logic generates new state data of the target field, the data contract corresponding to the second contract address is called to update the state data of the target field maintained in the contract account corresponding to the data contract, so as to convert the The state data of the target field is modified to the new state data.

In this embodiment, after the execution of the logic contract generates new state data, since the second contract address of the corresponding data contract has been obtained before, the data contract corresponding to the second contract address is directly called, and the contract corresponding to the data contract is called directly. The state data of the target field maintained in the account is modified to the new state data.

The invocation method of the smart contract shown in Figure 4 above is that the first transaction does not carry business-related status data, and the logical contract can be directly invoked.

And if the first transaction also carries service-related status data; the above step 320 specifically includes:

Step 321, in response to the first transaction, call the routing contract of the blockchain, and query the second contract address mapped to the first contract address in the mapping table maintained in the contract account corresponding to the routing contract;

Step 322, further calling the data contract corresponding to the second contract address, and updating the state data of the target field maintained in the contract account corresponding to the data contract to record the state data carried by the first transaction;

Step 323, further calling the logic contract corresponding to the first contract address to obtain the business logic maintained in the contract account corresponding to the logic contract.

In this embodiment, for a user's direct transaction of state data, such transaction is directly sent to its data contract, and after the state data is recorded by the data contract, the logic contract is invoked to process and record the business logic. Since the original state data (state data specified in the transaction) is not transferred by the logical contract, but is directly recorded by the data contract, and the data contract cannot be modified or upgraded, the original state data directly recorded by the data contract can be Trusted, so as to maximize data security.

For this manual, if the logic contract can be upgraded and the data contract can be expanded, then there will be the issues of user data ownership and asset security.

For traditional smart contracts, all of the user's assets are locked in the contract. The function of the smart contract to extract assets or modify the asset balance also assures the user through code disclosure that no other person or program can obtain the user's assets locked in the contract except the user himself. Furthermore, the immutability of traditional smart contracts ensures that once the contract is deployed, there will be no code changes, thus ensuring that the user assets maintained in the smart contract are absolutely safe.

However, this specification uses the separation of duties to divide traditional smart contracts into two separate contracts: logical contracts and data contracts. The user assets in the data contract are determined by the mapping relationship maintained by the routing contract, but this mapping relationship can be modified, that is to say, the user assets do not directly correspond to users, which poses the problem of user asset security. For example, map user A's assets to user B.

To this end, the contract account corresponding to the data contract can also maintain an asset mapping table of the mapping relationship between user accounts and user assets. The mapping table is inside the data contract, and it only provides two interfaces for the user's asset entry and exit, and no other interface has the right to write and update the asset mapping table.

In the above step 322, the data contract corresponding to the second contract address is called to update the status data of the target field maintained in the contract account corresponding to the data contract, including:

In the above step 323, the logic contract corresponding to the first contract address is called to obtain the business logic maintained in the contract account corresponding to the logic contract;

The above-mentioned user assets may refer to virtual tokens or virtual assets.

The virtual tokens may refer to converting real-world currency into virtual tokens that can be circulated on the chain. For example, Bitcoin is a typical virtual token.

The virtual assets may refer to converting some non-monetary physical assets in the real world into virtual assets that can be circulated on the blockchain.

Among them, it should be noted that converting non-monetary physical assets in the real world into virtual assets on the blockchain usually refers to "anchoring" the physical assets with the virtual assets on the blockchain, as The value support of these virtual assets, and then the process of generating virtual assets (hereinafter referred to as user assets) that match the value of physical assets on the blockchain and can be circulated between blockchain accounts on the blockchain.

During implementation, the state data of user assets can be maintained in the contract account corresponding to the data contract, so that non-monetary physical assets in the real world can be used as value support.

Specifically, the Nonce of the contract account of the data contract, the field value of the Code field can be null (or not); the field value of the Storage field can no longer be null; the Storage field can be used to maintain and user accounts. The asset status of the corresponding user asset. Among them, the specific method of maintaining the asset state of the user's assets in the Storage field can be flexibly designed based on requirements, such as an asset mapping table of the mapping relationship between the user account and the asset state of the user's assets.

The specific form of the above-mentioned user assets can be non-monetary physical assets such as real estate, stocks, loan contracts, bills, accounts receivable, etc., and such physical assets are converted into user assets with matching value and circulated on the blockchain.

Returning to this embodiment, when the user puts in the asset, he directly calls the account entry interface on the data contract. After the user's assets are locked into the data contract, the corresponding relationship between the address of the user's account and the user's assets is recorded in the asset mapping table.

When users retrieve assets, they still directly call the outgoing interface on the data contract. The data contract will verify whether the address of the user account exists in the asset mapping table, call the logic contract to perform the next steps if it exists, and finally transfer the user's assets directly to the user's request address.

For any user account that is not in the asset mapping table, the outbound interface will not respond to its operation request for user assets. This ensures that any user assets that are issued belong to the address of the original user account that was originally entered, which ensures the user's binding of asset ownership and improves the security of user assets.

To sum up, the technical solutions provided in this manual divide smart contracts into logical contracts, routing contracts and data contracts. The logical contracts that maintain business logic no longer maintain state data, so there are no restrictions on asset security and data migration, and smart contracts can be upgraded. On the other hand, the data contract is set to be non-upgradable, but extensible to meet the needs of business logic upgrades. On the other hand, the user account to which each user asset belongs is managed through the asset mapping table maintained within the data contract, and the user assets are managed based on the asset mapping table, so as to completely protect the user assets and not be affected by the contract. Asset security risks due to upgrades.

Corresponding to the above method embodiments, the present specification also provides embodiments of an apparatus for executing, creating and upgrading smart contracts in a blockchain.

The embodiments of the apparatus for executing, creating and upgrading smart contracts in the blockchain of this specification can be applied to electronic devices. The apparatus embodiment may be implemented by software, or may be implemented by hardware or a combination of software and hardware. Taking software implementation as an example, a device in a logical sense is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory for operation by the processor of the electronic device where the device is located.

From the perspective of hardware, as shown in Figure 5, a hardware structure diagram of the electronic equipment where the execution device of the smart contract in the blockchain of this specification (the creation and upgrading device of the smart contract in the blockchain is not shown) is located , in addition to the processor, memory, network interface, and non-volatile memory shown in FIG. 5 , the electronic device in which the device is located in the embodiment may also include other hardware, usually according to the actual function of the electronic device. Repeat.

Fig. 6 is a block diagram of a smart contract execution device in a blockchain according to an exemplary embodiment of the present specification. The apparatus can be applied to the aforementioned electronic equipment shown in FIG. 5 , and the apparatus includes:

The receiving unit 410 receives the first transaction submitted by the user; wherein, the first transaction carries the first contract address of the logical contract to be invoked for service execution;

The response unit 420, in response to the first transaction, invokes the logic contract corresponding to the first contract address, and obtains the business logic maintained in the contract account corresponding to the logic contract;

Determining unit 430, determining the field name of the state data lacking in the execution of the business logic;

The routing unit 440 invokes the routing contract of the blockchain to query the second contract address mapped to the first contract address in the mapping table maintained in the contract account corresponding to the routing contract;

The obtaining unit 450 calls the data contract corresponding to the second contract address, and obtains the status data of the field name maintained in the contract account corresponding to the data contract;

The execution unit 460 supplements the state data to the missing state data in the business logic, so as to execute the business logic.

Optionally, the device further includes:

The second response subunit, in response to the third transaction, creates a new logical contract, and writes the new business logic in the contract account corresponding to the new logical contract;

Optionally, the device further includes:

Optionally, the response unit 420 includes:

In the response unit 420, the data contract corresponding to the second contract address is called to update the status data of the target field maintained in the contract account corresponding to the data contract, including:

In the response unit 420, the logic contract corresponding to the first contract address is invoked, and the business logic maintained in the contract account corresponding to the logic contract is obtained, including:

The following describes an apparatus for creating a smart contract in a blockchain according to an exemplary embodiment of this specification. The device can also be applied to the aforementioned electronic equipment shown in FIG. 5 , and the device includes:

An apparatus for upgrading a smart contract in a blockchain shown in an exemplary embodiment of this specification is described below. The device can also be applied to the aforementioned electronic equipment shown in FIG. 5 , and the device includes:

Optionally, the device further includes:

The systems, devices, modules or units described in the above embodiments may be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementing device is a computer, which may be in the form of a personal computer, laptop computer, cellular phone, camera phone, smart phone, personal digital assistant, media player, navigation device, email sending and receiving device, game control desktop, tablet, wearable device, or a combination of any of these devices.

In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include forms of non-persistent memory, random access memory (RAM) and/or non-volatile memory in computer readable media, such as read only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media includes both persistent and non-permanent, removable and non-removable media, and storage of information may be implemented by any method or technology. Information may be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Flash Memory or other memory technology, Compact Disc Read Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cartridges, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.

It should also be noted that the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device comprising a series of elements includes not only those elements, but also Other elements not expressly listed, or which are inherent to such a process, method, article of manufacture, or apparatus are also included. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, article of manufacture, or device that includes the element.

The foregoing describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that in the embodiments and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some implementations, multitasking and parallel processing are also possible or may be advantageous.

The terminology used in one or more embodiments of this specification is for the purpose of describing a particular embodiment only and is not intended to limit the one or more embodiments of this specification. As used in the specification or embodiments and the appended claims, the singular forms "a," "the," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It will also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

It will be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, such information should not be limited by these terms. These terms are only used to distinguish the same type of information from each other. For example, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information without departing from the scope of one or more embodiments of the present specification. Depending on the context, the word "if" as used herein can be interpreted as "at the time of" or "when" or "in response to determining."

The above descriptions are only preferred embodiments of one or more embodiments of this specification, and are not intended to limit one or more embodiments of this specification. All within the spirit and principles of one or more embodiments of this specification, Any modifications, equivalent replacements, improvements, etc. made should be included within the protection scope of one or more embodiments of this specification.

Claims

A method for executing a smart contract in a blockchain, wherein the method comprises:

Receive the first transaction submitted by the user; wherein, the first transaction carries the first contract address of the logical contract that needs to be invoked for business execution;

In response to the first transaction, call the logic contract corresponding to the first contract address to obtain the business logic maintained in the contract account corresponding to the logic contract;

determining the field name of the state data missing from the execution of the business logic;

Invoke the routing contract of the blockchain, and query the second contract address mapped to the first contract address in the mapping table maintained in the contract account corresponding to the routing contract;

calling the data contract corresponding to the second contract address to obtain the status data of the field name maintained in the contract account corresponding to the data contract;

The state data is supplemented to the missing state data in the business logic to execute the business logic.
The method according to claim 1, wherein the method further comprises:

After executing the business logic to generate the new state data of the target field, the data contract corresponding to the second contract address is called to update the state data of the target field maintained in the contract account corresponding to the data contract, so that the The state data of the target field is modified to new state data.
The method according to claim 1, wherein the method further comprises:

Receive the second transaction submitted by the user; wherein, the second transaction carries the business logic of the smart contract to be created;

In response to the second transaction, a logic contract is created, and the business logic is written in a contract account corresponding to the logic contract;

Create a data contract, and write the initial state data of each field in the business logic into the contract account corresponding to the data contract;

Call the routing contract in the blockchain, update the mapping table maintained in the contract account corresponding to the routing contract, and write the first contract address corresponding to the logic contract and the second contract address of the data contract the mapping table.
The method according to claim 1, wherein the method further comprises:

Receive the third transaction submitted by the user; wherein, the third transaction carries the first contract address of the old logic contract to be upgraded and the new business logic to be upgraded;

In response to the third transaction, a new logic contract is created, and the new business logic is written in the contract account corresponding to the new logic contract;

Invoke the routing contract in the blockchain, update the mapping table maintained in the contract account corresponding to the routing contract, to modify the first contract address of the old logical contract in the mapping table to the new logical contract The first contract address of .
The method according to claim 4, wherein the method further comprises:

If the new business logic adds a new field compared to the old business logic, a new data contract is created, and the initial state data of the new field is written in the contract account corresponding to the new data contract;

Call the routing contract in the blockchain, update the mapping table maintained in the contract account corresponding to the routing contract, and add the first contract address and the second contract address of the new data contract to the mapping table. Mapping relations.
The method according to claim 1, wherein if the first transaction also carries business-related status data, the logic contract corresponding to the first contract address is invoked in response to the first transaction, Obtain the business logic maintained in the contract account corresponding to the logic contract, including:

In response to the first transaction, call the routing contract of the blockchain, and query the second contract address mapped to the first contract address in the mapping table maintained in the contract account corresponding to the routing contract;

Further call the data contract corresponding to the second contract address, and update the state data of the target field maintained in the contract account corresponding to the data contract, so as to record the state data carried by the first transaction;

Further call the logic contract corresponding to the first contract address to obtain the business logic maintained in the contract account corresponding to the logic contract.
The method according to claim 6, wherein the state data maintained by the contract account corresponding to the data contract is located in an asset mapping table, and the asset mapping table stores the state data of user accounts and user assets;

The invoking the data contract corresponding to the second contract address and updating the state data of the target field maintained in the contract account corresponding to the data contract includes:

If the first transaction is a credit transaction of user assets, call the data contract corresponding to the second contract address, and record the status data of the user account and user assets in the asset mapping table;

If the first transaction is an outgoing transaction of user assets, call the data contract corresponding to the second contract address to verify whether the user account indicated by the first transaction is located in the asset mapping table;

The logic contract corresponding to the first contract address is called, and the business logic maintained in the contract account corresponding to the logic contract is obtained,

When the user account is located in the asset mapping table, the logic contract corresponding to the first contract address is further invoked to obtain business logic maintained in the contract account corresponding to the logic contract.
A method for creating a smart contract in a blockchain, the method comprising:

Receive the second transaction submitted by the user; wherein, the second transaction carries the business logic of the smart contract to be created;

In response to the second transaction, a logic contract is created, and the business logic is written in a contract account corresponding to the logic contract;

Create a data contract, and write the initial state data of each field in the business logic into the contract account corresponding to the data contract;

Call the routing contract in the blockchain, update the mapping table maintained in the contract account corresponding to the routing contract, and write the first contract address corresponding to the logic contract and the second contract address of the data contract the mapping table.
A device for executing a smart contract in a blockchain, characterized in that the device comprises:

The receiving unit receives the first transaction submitted by the user; wherein, the first transaction carries the first contract address of the logical contract that needs to be invoked for business execution;

The response unit, in response to the first transaction, invokes the logic contract corresponding to the first contract address, and obtains the business logic maintained in the contract account corresponding to the logic contract;

A determining unit, determining the field name of the state data lacking in the execution of the business logic;

a routing unit, calling the routing contract of the blockchain, and querying the second contract address mapped to the first contract address in the mapping table maintained in the contract account corresponding to the routing contract;

an obtaining unit, calling the data contract corresponding to the second contract address, and obtaining the status data of the field name maintained in the contract account corresponding to the data contract;

An execution unit, supplementing the state data to the state data missing in the business logic, so as to execute the business logic.
An electronic device, comprising:

processor;

memory for storing processor-executable instructions;

Wherein, the processor implements the method of any one of claims 1-8 by executing the executable instructions.