consensus, miner: set the basefee to 0 after London fork #421
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
minh-bq
force-pushed
the
london-hardfork
branch
3 times, most recently
from
59a6ecc
to
039665f
Compare
Currently, we choose to set basefee to 0 after London fork on Ronin, the basefee logic can be changed in future fork. Besides, at the London fork, we don't double the block gas limit.
andicrypt
approved these changes
May 21, 2024
andicrypt
approved these changes
May 21, 2024
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.
Currently, we choose to set basefee to 0 after London fork on Ronin, the basefee logic can be changed in future fork. Besides, at the London fork, we don't double the block gas limit.