-
Notifications
You must be signed in to change notification settings - Fork 86
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
Ethereum Execution Tests failing only when run inside the guest #52
Comments
@Wollac I want to try this issue, May I claim this? |
@dyxushuai Sorry for the late reply. This is a pretty tricky issue, but feel free to check it out! |
Will be fixed when |
This was referenced Jan 17, 2024
This issue was fixed by #76, I think it's time to close it. |
Yes thanks! |
johntaiko
pushed a commit
to johntaiko/zeth
that referenced
this issue
Mar 19, 2024
Sp1 stuff + re-enable risc0 + invalid tx support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently,
zeth
is tested against theGeneralStateTests
of ethereum/tests. However, while each of these tests is tested for correct execution on the host, only a handful of them are actually executed on the guest by default.If you manually run all of them in the guest, some of them will fail due to a
SlotNotFound
panic. This happens when the EVM inside the guest tries to access storage slots that are not part of the guest's input.Steps to reproduce
For example, the following test fails because of this issue:
returndatacopy_initial_big_sum.json
. To run this exact test, change the following linezeth/testing/ef-tests/tests/executor.rs
Line 34 in eed232b
to
#[files("testdata/BlockchainTests/GeneralStateTests/stReturnDataTest/returndatacopy_initial_big_sum.json")]
This returns
This indicates, that for this artificial case, when
revm
is run on the host it does not access storage slot0x0
of account0x0f572e5295c57f15886f9b263e2f6d2d6c7b5ec6
. However, when running in the guest, it does.The text was updated successfully, but these errors were encountered: