-
-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove fee history fallback #4210
Merged
Merged
Conversation
This file contains 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
@metamaskbot publish-preview |
Preview builds have been published. See these instructions for more information about preview builds. Expand for full list of packages and versions.
|
OGPoyraz
approved these changes
Apr 26, 2024
mcmire
approved these changes
Apr 26, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
7 tasks
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.
Explanation
Currently the
GasFeeController
has a series of fallbacks in order to estimate the current gas fees for a network.Broadly speaking, these are currently:
eth_feeHistory
.eth_gasPrice
.Option 2 behaves similar to the gas API itself in that it retrieves the fee history for the last 5 blocks, then uses different percentiles in order to determine a low, medium, and high estimate. This includes validations to ensure a minimum priority fee however unlike the gas API, these constants or "settings" are not chain specific and can therefore be considerably incorrect, especially in the case of layer 2 networks where gas fee values are considerably smaller.
This results in a scenario where MetaMask consistently suggests high values for new networks that are not yet supported by the gas API, when a more suitable value could have been provided had a standard
eth_gasPrice
call been used instead.As such, this PR ultimately removes the fee history logic (option 2) from the
GasFeeController
, meaning if the gas API does not support a network, a standardeth_gasPrice
call is the only fallback.References
Fixes #2385
Changelog
@metamask/gas-fee-controller
eth_gasPrice
call.Checklist