[Fix] EIP-1559 Integrity check #600
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
…ain when we detect inconsistency between the value and the baseFee.
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.
Name of the feature/issue
EIP-1559 Integrity check
Description
Added new EIP1559 integrity check to force fetching the value again when we detect inconsistency between the value and the stored baseFee. We detected this situation on some old states from users which tried to perform an operation and received an error.
After checking the state, we noticed that some chains had the EIP-1559 flag with a
falsevalue when it should be true. The situation was automatically fixed after switching networks but it seems some users only operate with one network so this check should prevent this situation from happening again (i.e. a non EIP network upgrades to EIP-1559)