Ethereum: Is it possible to schedule function calls to an Ethereum smart contract? [closed]

Planned function calls to the intelligent chords of Ethereum: Technical research

The decentralized nature of Ethereum and the growing ecosystem have created new opportunities to interact with various components by program. In this article, we will immerse ourselves on the possibility of calls for the planning of functions on intelligent contracts of Ethereum as a function of the height or horoditing of the current block.

Context and context

Ethereum’s intelligent contracts are self-executing contracts with special terms and terms written in stability, the programming language used to create these contracts. They can perform a variety of tasks, including the management of national changes, logical performance and interaction with external services. To facilitate developers to interact with intelligent contracts by program, Ethereum Virtual Machines (EVM) supports various APIs which allow customers to access the data of the contract and perform functions.

Gas ​​transactions

One way to cause function calls is gas transactions. These include sending a “gas” payment to the Ethereum network to carry out a transaction or call the contractual function. Although gas payments are necessary for transactions, they can be expensive because the network had high transaction costs.

To solve this problem, we will study two strategies:

1
Payment of gas provided : This approach includes a fixed quantity of gas payment at regular intervals (for example, each block). By planning these payments in advance, developers can ensure that their functions are performed in a specific window, even if it is not the current height of the block or horoditing.

  • Function calls based on time : We will study how to plan functions of functions according to the block height or current horoding using previous gas payments for the specific API gas and EVM.

Payments of gas provided

We may use the function of the intelligent contract and the combination of external services to implement the planned gas payments:

  • Activation of planned transactions : Develop a personalized intelligent contract which regularly activates transactions (for example the block). When the current block height is greater than the desired threshold, send the “gas payment” to the network.

2
Gas ​​Payment Mechanism : Introduce Evm to a specific Gas Payment Mechanism Using Apis Such as `,and` `''. This will allow us to calculate the price of gas, which is required for each transaction as a function of the current block height.

Functional calls based on time -tamper

Ethereum: Is it possible to schedule function calls to an Ethereum smart contract? [closed]

We will use APIs specific to the EVM on the functionalities based on the horodatages which allow us to access the data of the contract and to fulfill the functions in certain horodings:

1
Acquisition of contractual data : Use
eth_geteventbyhash () or other similar features to obtain the latest event from Ethereum Blockchain.

  • Call shall functions : When we have the favorite signature of the function, call it viacomplex () ‘,evm_call ()(javaScript) or equivalent api.

Challenges and restrictions

Consider the following challenges and limitations before diving into this subject:

  • Gas ​​efficiency: planned transactions can cause higher gas costs generated by the increase in transaction costs.

  • Block synchronization: The planned function call approach is based on the current height of the block. If the network has congestion or downtime, these functions may not be fulfilled as expected.

  • Security risks: planned transactions can increase the attack surface if it is not properly secure.

Conclusion

Although there are technical problems related to the introduction of calls provided for Ethereum intelligent contracts, it is not impossible. By including gas payments, EVM APIs and contract data, developers can create a stable system for a temporary base.

ETHEREUM CHART THERE

Leave a Reply

Your email address will not be published. Required fields are marked *