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.
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix: BlockCapturer for Created Accounts #1291
fix: BlockCapturer for Created Accounts #1291
Changes from all commits
d95c9bd
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Does taking a storage snapshot insert a storage value ?
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.
Also, at least according to the current EYP, storage does not matter when it comes to checking the possibility of doing a CREATE2
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.
Yeah, but at the end of the day, we are not measuring against the EYP. We are comparing against execution on MAINNET using BESU. What I'm looking at is what BESU does. If that deviates from the EYP ... well, we still have to follow BESU.
However, I agree that it does seem wierd and I can follow up with BESU to see why they do it that way (or even it could be a bug).
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.
Yes, in the replay environment it does. See
ReplayExecutionEnvironment.initWorld()
. One option might be to dropStorageSnapshots
which assign0x0
at the beginning of the conflation. It has the same effect. Maybe you prefer this?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.
But does taking a storage snapshot change the world state ? If so that is a massive problem.
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.
In any case we do want to define storage snapshots even if the target account has empty storage or doesn't even exist yet. Simply because it's possible in Ethereum and we will want to test that, see #1205, but it should be side-effect free
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.
AFAIU the EYP defines for an account$a$
existence
as existence in the state, i.e.EMPTY
as having nontrivial nonce, balance or codeDEAD
as either not existing or being emptyalong with EIP-7610
So maybe a more accurate name would be
accountMayNotBeDeployedAt
/deploymentIsProhibitedAt
or so.