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
Gas does not correspond to ref_time exactly as semantically equivalent code can exhibit totally different gas usage on EVM vs. ref_time usage on PVM.
Right now we ignore it, making all calls unconstrained. But those gas limits are a security feature.
Possible solutions:
Scale the supplied gas limit with a fixed factor
Treat the supplied gas as relative value relative to the EVM block gas limit and convert it to the corresponding relative ref_time limit. Drawback is that the compiler (i.e. the user) needs to know the absolute ref_time limit of the target blockchain. It also largely disconnects the semantic meaning of the value should the block limits in either chain change.
Also add a warning whenever a call with gas limit != 0 is compiled.
The text was updated successfully, but these errors were encountered:
Gas does not correspond to
ref_time
exactly as semantically equivalent code can exhibit totally different gas usage on EVM vs. ref_time usage on PVM.Right now we ignore it, making all calls unconstrained. But those gas limits are a security feature.
Possible solutions:
ref_time
limit. Drawback is that the compiler (i.e. the user) needs to know the absoluteref_time
limit of the target blockchain. It also largely disconnects the semantic meaning of the value should the block limits in either chain change.Also add a warning whenever a call with gas limit != 0 is compiled.
The text was updated successfully, but these errors were encountered: