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
Since processing a DR takes computation on the chain side we're charging a base fee of 1Tgas (subject to change) before doing any custom tally logic (filter and/or VM execution). We should reject DRs that do not at least provide this base fee, since the result will always be an out of gas error for the requestor.
Motivation
Prevent requestors from posting DRs that can never produce a valid result since it's guaranteed to run out of gas if the minimum fee is not met.
Implementation
Figure out the best way to sync this value between the chain and the contract. Could be a module query, or if it's better/cheaper we keep it on the contract and the module gets it from there. A possibility would be alongside the list of DRs to be tallied, so we don't have to have an extra query.
The text was updated successfully, but these errors were encountered:
✨ Feature
Since processing a DR takes computation on the chain side we're charging a base fee of 1Tgas (subject to change) before doing any custom tally logic (filter and/or VM execution). We should reject DRs that do not at least provide this base fee, since the result will always be an out of gas error for the requestor.
Motivation
Prevent requestors from posting DRs that can never produce a valid result since it's guaranteed to run out of gas if the minimum fee is not met.
Implementation
The text was updated successfully, but these errors were encountered: