Feat: use SlowAdjustingFeeUpdate to update fees based on congestion #1686
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boundless-forest
approved these changes
May 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The template runtime configuration sets FeeMultiplierUpdate to
ConstFeeMultiplier, which does not take into consideration the current usage of the network.While this is a template, it is still good to provide a safe example for anyone integrating frontier in their runtimes.
When using
ConstFeeMultiplier, fees do not reflect congestion, an attacker could cause a DoS against all zero-tip transactions for an extended period of time by just paying the regular transaction fees (and not exponentially raising fees, which would at least limit the duration of that attack).