feat: update L2 base fee formula #891
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
omerfirmak
previously approved these changes
Jul 9, 2024
omerfirmak
approved these changes
Jul 9, 2024
roylou
approved these changes
Jul 9, 2024
0xmountaintop
pushed a commit
that referenced
this pull request
Jul 10, 2024
* feat: update L2 base fee formula * update test tx hashes
0xmountaintop
added a commit
that referenced
this pull request
Jul 10, 2024
feat: update L2 base fee formula (#891) * feat: update L2 base fee formula * update test tx hashes Co-authored-by: Péter Garamvölgyi <[email protected]>
lwedge99
pushed a commit
to sentioxyz/scroll-geth
that referenced
this pull request
Aug 27, 2024
* feat: update L2 base fee formula * update test tx hashes
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.
1. Purpose or design rationale of this PR
Update according to new cost estimation.
Note: Follower nodes don't verify the base fee, so this is a compatible change.
2. PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
3. Deployment tag versioning
Has the version in
params/version.gobeen updated?4. Breaking change label
Does this PR have the
breaking-changelabel?