-
Notifications
You must be signed in to change notification settings - Fork 284
fix: add sload/sstore witness when calculating dynamic gas #1157
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
Conversation
WalkthroughThe changes involve modifications across three files. In the core module, the Changes
Suggested labels
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (1)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
LGTM
1. Purpose or design rationale of this PR
This PR gets the witness of
SLOADandSSTOREimmediately before calculating their dynamic gas, to align withreth's witness implementation.Another place that needs to change for
SLOADwitness loading is when calculating the gas cost after Frontier and before EIP-2929. Frontier gas cost simply usesparams.SloadGasFrontier(i.e. 50 gas), so changing the gas cost there might affect code cleanliness. Usually, this won't be a problem because EIP-2929 is enabled by default, thus leaving addingSLOADwitness before EIP-2929 as a TODO.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?Summary by CodeRabbit
Summary by CodeRabbit
Refactor
Chore