-
Notifications
You must be signed in to change notification settings - Fork 773
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
Ensure EVM runs when nonce is zero #2054
Conversation
dfd44c5
to
01f3c91
Compare
Codecov Report
Flags with carried forward coverage won't be shown. Click here to find out more. |
Ah right, we cannot update If you recursively call back into the CREATE-ing account, then the nonce never updates, so it always tries to CREATE at the same address. |
@jochem-brouwer I reverted the changes I made around setting the default |
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.
Not sure if there is more work to be done but this looks good to me!
Thanks! |
This PR is based on an old version of master. In here I address the nonce bug in #2009.
I think that pre-EVM calls the state should be exactly as it is pre-EVM. Since we have introduced this "nonce - 1" logic at some point this should be removed (and I think this might be easy). This first version does the depth check and removes the 'nonce - 1' if the depth is zero.
I tried removing it by also moving the "increment nonce" logic in
interpreter.ts
the same way how I moved it now inrunTx
, but this has a failing chainstart testRecursiveCreateContractsCreate4Contracts_d0g0v0_Frontier
which I should look into.