Conversation
Illustrate the "max of 10% bump vs. re-estimated fees" rule in the Replacement Underpriced FAQ with concrete numbers, since the rule was previously stated but not demonstrated.
🔗 Preview Mode
|
Contributor
Author
|
Merged into #1468 instead. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Follow-up to #1468 for the lower-level bundler/paymaster path. The "Resolve Replacement Underpriced errors" FAQ already states the rule (bump maxFeePerGas/maxPriorityFeePerGas by the max of a 10% increase or the re-estimated value), but didn't show it worked through with numbers. This adds a concrete example.
No changes to the fee percentages or network buffer table — just an illustration of the existing rule.