You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Current core does not properly limit the gas usage with its params.MaxContractGas. It is only asserted per each messages, not including its sub-messages.
Ex) when we execute msg1 which is executing msg2, msg3, ... msgn, the limit is applied per each messages. It is supposed to be applied to sum of all gas usages of the messages to properly limit the gas.
To Reproduce
execute wasm message which is executing sub-messages
Context & versions
v0.4.0 + v0.5.0-beta4
(if applicable) suggested solution
Set new gas meter with limit at msg server
The text was updated successfully, but these errors were encountered:
Describe the bug
Current core does not properly limit the gas usage with its
params.MaxContractGas
. It is only asserted per each messages, not including its sub-messages.Ex) when we execute
msg1
which is executingmsg2, msg3, ... msgn
, the limit is applied per each messages. It is supposed to be applied to sum of all gas usages of the messages to properly limit the gas.To Reproduce
execute wasm message which is executing sub-messages
Context & versions
v0.4.0 + v0.5.0-beta4
(if applicable) suggested solution
Set new gas meter with limit at msg server
The text was updated successfully, but these errors were encountered: