CN111813999A - A method to improve the scalability of Ethereum smart contract fields - Google Patents

Abstract

The invention discloses a method for improving the expansibility of an Ether house intelligent contract field, which comprises the following steps: defining fields needing to be stored on a block chain; classifying and integrating fields needing to be linked up, and extracting similar fields; the front-end server integrates the similar fields and carries out Json formatting conversion, so that an object or an array consisting of a plurality of fields is converted into a character string of a single field; calling an intelligent contract Api interface on the block chain to transmit a corresponding character string, and storing the character string on one field of the block chain after the intelligent contract is verified; when the front-end server needs to acquire data, Json analysis is needed on the character strings, and therefore the original storage fields are obtained. The invention makes some standardized designs to the format of the field, and converts a plurality of pieces of information according to a certain rule, thereby improving the data volume stored in a single field, improving the expansibility of the field, and meeting the updating requirement of intelligent contract on business.

Description

A method to improve the scalability of Ethereum smart contract fields

technical field

The invention relates to the technical field of blockchain, in particular to a method for improving the field scalability of an Ethereum smart contract.

Background technique

Solidity is a broad, open programming language mainly used for the development of smart contracts in the underlying blockchain system of Ethereum. At present, blockchain technology is widely used in many fields such as finance, food safety, medical care and real estate. And because the number of variables in Solidity language cannot exceed 16 during development and the underlying data contract update will be too cumbersome, it is expensive to develop and modify the underlying system of Ethereum for specific business, and the contract storage content is too large, and the contract storage content is too large. caused restrictions.

SUMMARY OF THE INVENTION

The purpose of the present invention is to provide a method for improving the extensibility of the field of the Ethereum smart contract, to standardize the design of the field format, to improve the extensibility of the field, to reduce the repeated construction of the system, and to ensure the update requirements of the contract in business.

For this purpose, the present invention adopts the following technical solutions:

Provide a method to improve the scalability of Ethereum smart contract fields, including the following steps:

S10. Define the fields that need to be stored on the blockchain;

S20, classifying and integrating the fields that need to be uploaded, and extracting similar fields;

S30, the front-end server integrates the similar fields and performs Json format conversion, so that an object or an array composed of multiple fields is converted into a string of a single field;

S40, calling the smart contract Api interface on the blockchain to pass in the corresponding string, and after verification by the smart contract, store the string in a field of the blockchain;

S50. When the front-end server needs to obtain data, the string needs to be parsed by Json, so as to obtain the original storage field.

As a preferred solution of the method for improving the scalability of the Ethereum smart contract field, in the step S40, the front-end server accesses the smart contract Api interface in Post mode through the HTTP network protocol according to the URL link provided by the interface.

As a preferred solution of the method for improving the scalability of the Ethereum smart contract field, in the step S40, the smart contract Api interface performs a transfer according to the URL link and then calls the corresponding smart contract, and the smart contract Api interface calls the corresponding smart contract. The contract verifies the identity of the call, and after the verification is passed, the storage logic on the smart contract is executed. After the storage logic is confirmed by the consensus mechanism of the blockchain, the blockchain stores the request.

As a preferred solution of the method for improving the field extensibility of the Ethereum smart contract, when a new field needs to be added to the string, it is only necessary to add the new field to the original field on the front-end server.

Beneficial effects of the present invention: the present invention makes some standardized designs for the format of the fields, so that multiple pieces of information are converted according to certain rules, thereby increasing the amount of data stored in a single field, improving the expansibility of the field, and reducing the amount of data stored in the field. The variables generated by the storage in a single function enable the contract to complete the business requirement update under the constraints of the system, reduce the repeated construction of the system, and reduce the required fields for storage in the contract implementation. The setting is the string size. When the data format before conversion needs to be added or deleted, it will not have any effect on the storage format, making the storage content more flexible, without modifying the underlying storage contract, and increasing the flexibility of the contract storage structure.

Description of drawings

In order to describe the technical solutions of the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings that need to be used in the embodiments of the present invention. Obviously, the drawings described below are only some embodiments of the present invention, and for those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative efforts.

FIG. 1 is a flowchart of a method for improving the field scalability of an Ethereum smart contract according to an embodiment of the present invention.

FIG. 2 is a schematic structural diagram (1) of a method for improving the field scalability of an Ethereum smart contract according to an embodiment of the present invention.

FIG. 3 is a schematic structural diagram (2) of a method for improving the field scalability of an Ethereum smart contract according to an embodiment of the present invention.

Detailed ways

The technical solutions of the present invention are further described below with reference to the accompanying drawings and through specific embodiments.

Among them, the accompanying drawings are only used for exemplary description, and they are only schematic diagrams, not physical drawings, and should not be construed as restrictions on this patent; in order to better illustrate the embodiments of the present invention, some parts of the accompanying drawings will be omitted, The enlargement or reduction does not represent the size of the actual product; it is understandable to those skilled in the art that some well-known structures and their descriptions in the accompanying drawings may be omitted.

The same or similar numbers in the drawings of the embodiments of the present invention correspond to the same or similar components; in the description of the present invention, it should be understood that if the terms "upper", "lower", "left" and "right" appear The orientation or positional relationship indicated by , "inside", "outside", etc. is based on the orientation or positional relationship shown in the drawings, and is only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the indicated device or element must be It has a specific orientation, is constructed and operated in a specific orientation, so the terms describing the positional relationship in the accompanying drawings are only used for exemplary illustration, and should not be construed as a limitation on this patent. situation to understand the specific meaning of the above terms.

In the description of the present invention, unless otherwise expressly specified and limited, if the term "connection" or the like appears to indicate a connection relationship between components, the term should be understood in a broad sense, for example, it may be a fixed connection or a detachable connection It can be connected or integrated; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, and it can be an internal connection between two components or an interaction relationship between the two components. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood in specific situations.

As shown in FIG. 1 , the method for improving the field scalability of an Ethereum smart contract in an embodiment of the present invention includes the following steps:

S10. Define the fields that need to be stored on the blockchain;

S20, classify and integrate the fields that need to be uploaded, and extract similar fields;

S30, the front-end server integrates similar fields and performs Json format conversion, so that an object or array composed of multiple fields is converted into a string of a single field;

S40. Call the smart contract Api interface on the blockchain to pass in the corresponding string, and after verification by the smart contract, store the string in a field of the blockchain;

S50. When the front-end server needs to obtain data, the string needs to be parsed by Json, so as to obtain the original storage field.

In this embodiment, some standardized designs are made on the format of the fields, so that multiple pieces of information are converted according to certain rules, thereby increasing the amount of data stored in a single field, improving the expansibility of the field, and reducing the need for a single function. The variables generated by storage enable the contract to complete the update of business requirements under the constraints of the system, reduce the repeated construction of the system, and reduce the fields required for storage in the contract implementation. At the same time, because the setting of the storage field is a string When the data format before conversion needs to be added or deleted, it will not have any impact on the storage format, making the storage content more flexible, without modifying the underlying storage contract, and increasing the flexibility of the contract storage structure.

In this embodiment, in step S40, the front-end server accesses the smart contract Api interface in Post mode through the HTTP network protocol according to the URL link provided by the interface.

In this embodiment, in step S40, the smart contract Api interface performs a transfer according to the URL link and then calls the corresponding smart contract, the smart contract verifies the identity of the call, and executes the storage logic on the smart contract after the verification is passed. After the consensus mechanism of the blockchain is confirmed, the blockchain stores the request.

In this embodiment, when a new field needs to be added to the string, it is only necessary to add the new field to the original field on the front-end server.

As shown in Figure 2 and Figure 3, for example, the information that needs to be uploaded to the chain includes the mailing destination, logistics company, logistics order number, user name on the chain and time of the chain. According to the defined fields, the above information is classified and integrated, and the extracted Information under the same category, such as mailing destination, logistics company and logistics order number, the front-end server converts the mailing destination, logistics company and logistics order number information into Json string by Json format, and then converts the Json string, on-chain Strings such as username and on-chain time are passed into the smart contract Api interface on the blockchain together. The smart contract Api interface calls the corresponding smart contract. The smart contract verifies the identity of the call. After the verification is passed, the storage logic on the contract is executed. After being confirmed by the consensus mechanism of the blockchain, the blockchain stores the request, thereby reducing the generation of multiple variables during the execution of the smart contract to receive the information. When a new field needs to be added to the express information as shown in Figure 1, it is only necessary to add the new field to the conversion before the front-end server conversion. For the chain, it is still stored in a field, so when receiving information, it is also Only one variable is needed to store, and there is no need to change the field format of the storage contract.

In this embodiment, multiple pieces of information are recorded on a single string field by using the string type supported by the Solidity language, and before being passed into storage, the information is converted according to the rules, thereby increasing the amount of data stored in a single field and reducing the amount of data stored in a single function. The variables generated by storage in the contract solve the problem that a single function exceeds the limit of 16 variables at the bottom layer, thereby preventing the "stack too deep" error caused by using too many variables, so that the logic in the contract can be used when implementing There are more variables, the effect is more flexible and provides more design ideas.

Explanation of proper nouns:

Json: A lightweight data storage format independent of development language, the full name is JavaScript ObjectNotation, a standard specification of data format, originally derived from the JavaScript language, and later with the widespread use, almost every development language There are APIs for handling Json.

Smart contract Api interface: A set of Api interfaces conforming to the Restful Api specification developed by the underlying extension of the blockchain, providing convenience for invocation.

Restful Api Specification: It is a set of specifications for front-end and back-end separation.

Smart Contract: A computer protocol designed to informatively propagate, verify, or execute a contract, a smart contract allows for trusted transactions that are traceable and irreversible without a third party.

URL link: It is a representation method used to specify the location of information on the World Wide Web service program of the Internet.

HTTP network protocol: It is the standard for client and server requests and responses. It is mainly used by the client to initiate an HTTP request to the specified port in the server through a web browser or other tools. After the server receives the request, it returns the corresponding response. content.

Post method: refers to one of the common basic methods of HTTP request, which is mainly used to submit data to the server.

Consensus mechanism: refers to an algorithm in the blockchain, mainly to ensure the correctness of a transaction. In the blockchain, each user will check whether the operation meets the requirements every time the chain is uploaded, and then all users will vote on this operation, and finally reach a consensus to determine whether this operation is wrong or not. If it is correct, it will be recorded on the blockchain.

Solidity: is a high-level programming language for smart contracts running on the Ethereum Virtual Machine.

Ethereum: Ethereum is an open-source public blockchain platform with smart contract capabilities that provides a decentralized Ethereum virtual machine to process peer-to-peer contracts through its dedicated cryptocurrency, Ethereum.

Ethereum Virtual Machine: The Ethereum Virtual Machine is the runtime environment for smart contracts on Ethereum. The Ethereum virtual machine runs in a sandbox, which is completely separate from the main chain of the blockchain. The code runs in the Ethereum virtual machine without a network, and the file system or smart contracts of other processes will be restricted from accessing other smart contracts. contract.

"stack too deep" error: This error is due to the fact that the ether virtual machine restricts the stack to get to stack[15] at most, that is, the content of the 16th stack element from the top of the stack down, which leads to the fact that if the input parameter of a function method , the return value, and the number of parameters in the function are likely to trigger this error if the number is greater than a certain amount. If the contract business logic is complex, it may trigger the "stack too deep" error.

It should be stated that the above-mentioned specific embodiments are only preferred embodiments of the present invention and applied technical principles. It should be understood by those skilled in the art that various modifications, equivalent substitutions, changes and the like can also be made to the present invention. However, as long as these transformations do not depart from the spirit of the present invention, they should all fall within the protection scope of the present invention. In addition, some terms used in the specification and claims of the present application are not limiting, but are only for convenience of description.

Claims (4)

1. A method for improving the expansibility of an Ethernet intelligent contract field is characterized by comprising the following steps:

s10, defining fields needing to be stored on the block chain;

s20, classifying and integrating the fields needing to be linked, and extracting similar fields;

s30, the front-end server integrates the similar fields and carries out Json formatting conversion, so that an object or an array consisting of a plurality of fields is converted into a character string of a single field;

s40, calling an intelligent contract Api interface on the block chain to transmit the corresponding character string, and storing the character string to a field of the block chain after the character string is verified by the intelligent contract;

and S50, when the front-end server needs to acquire data, the character string needs to be subjected to Json analysis, so that an original storage field is obtained.

2. The method of improving ethernet intelligent contract field expandability of claim 1, wherein in the step S40, the front-end server accesses the intelligent contract Api interface in a Post manner through a network protocol of HTTP according to a URL link provided by the interface.

3. The method of improving the expandability of the smart contract field of the ethernet according to claim 2, wherein in step S40, the Api interface calls the corresponding smart contract after performing a transfer according to the URL link, the smart contract verifies the identity of the call, and executes the storage logic on the smart contract after the verification is passed, and the storage logic stores the request after being confirmed by the consensus mechanism of the blockchain.

4. The method for improving the expandability of the fields of the intelligent contracts of the etherhouses according to claim 3, wherein when a new field needs to be added to the character string, the new field is added to an original field on the front-end server.

Images