-
Notifications
You must be signed in to change notification settings - Fork 633
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
Optimism execution #781
Comments
Thank you for reporting this! Will take a look, reproduce, and get back to you! As a side note, if you make a PR, it would be preferable to split it up to make reviewing and adding the relevant unit tests easier. |
@Wollac thank you!
revm/crates/revm/src/evm_impl.rs Line 418 in 02d85ac
For the future, the idea is to create the The Second point I will leave for @refcell, for the third point we definitely should not panic. |
I have created a PR that addresses these issues. It has been validated in It does not yet include specific unit tests, as @refcell mentioned. None of the affected functions had tests before, so designing relevant tests would require more thought. |
Left a couple of nits, but besides those, you're pr looks great! Really exciting that you were able to test this against Optimism Blocks!! On the topic of unit tests, I think pushing those into other prs is totally reasonable. |
Very exciting news that you guys are successfully executing Optimism blocks! Thanks a ton for fixing these up :) |
Fixed with #789 |
When I tried to use the Optimism execution behind the
optimism
feature flag of versionv3.5.0
, I ran into the following problems:Handler::optimism()
is never used. So even ifenv.cfg.optimism
istrue
, the Optimism specific fee handling is not applied.env.block.basefee * (gas.spend() - gas_refund)
should be used instead.optimism
feature is enabled whileenv.cfg.optimism
isfalse
for Ethereum transactions, thetx_l1_cost
is still computed, which can lead to a panic as obviously theenveloped_tx
is not provided in this case.If the above observations are indeed correct and it would be helpful, I can provide a PR for these issues.
The text was updated successfully, but these errors were encountered: