Handle a case where priorityFee > maxFee in the task loop #655
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automatic transactions in the task loop fail when the user-inputted
priorityFee
is greater than the oracle basedmaxFee
. This PR addresses this case by settingpriorityFee
tomin(priorityFee, 25% of the oracle based maxFee
) whenpriorityFee > maxFee
for transactions in the node task loop.For example: automatically initializing vote power, defending pDAO proposals, bond reductions and so on.
The change is also applied to watchtower task
process-penalties.go