search

AntelopeIO / leap

C++ implementation of the Antelope protocol
Other
116 stars 70 forks source link

Configurable `max-transaction-time` per contract #434

Open poplexity opened 1 year ago

poplexity commented 1 year ago

There are use cases where it's desired that only certain (trusted) contracts can exceed the default max-transaction-time threshhold.

One specific example is for Telos EVM (and quite possibly TrustEVM once live). On EVM networks, transactions can execute as long as they wish so long as they continue paying for the gas. There are some edge case examples which legitimately need to execute for more than 30ms. On Telos EVM contract it is desirable to let that happen, without letting ALL contracts on the network execute for such a long period of time.

This request is the ability to specify both the current (default) max as well as specify higher values for specific accounts.

stephenpdeos commented 1 year ago

We are not considering configurable max-transaction-time per contract at this time.

For now, our recommendation is increasing max-transaction-time for a given network's specific needs. We'll plan to solve for this issue via documentation of best practices for setting max-transaction-time.