Skip to content

tracers/prestate: always remove empty accounts from pre-state #31427

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.

Sign up for GitHub

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

Merged
s1na merged 4 commits into from
Jun 16, 2025
Merged

tracers/prestate: always remove empty accounts from pre-state #31427

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6e813f6
tracers/prestate: always remove empty accounts from pre-state
jsign Mar 18, 2025
1c13317
resolve merge conflict
s1na Jun 16, 2025
e57ca8a
fix tests
s1na Jun 16, 2025
9c2336c
minor
s1na Jun 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions eth/tracers/native/prestate.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -177,11 +177,9 @@ func (t *prestateTracer) OnTxEnd(receipt *types.Receipt, err error) {
if t.config.DiffMode {
t.processDiffState()
}
// the new created contracts' prestate were empty, so delete them
for a := range t.created {
// the created contract maybe exists in statedb before the creating tx
if s := t.pre[a]; s != nil && s.empty {
delete(t.pre, a)
for addr, s := range t.pre {
if s.empty {
delete(t.pre, addr)
}
Comment on lines +192 to 195
Copy link
Contributor Author

@jsign jsign Mar 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is just a potential variant that avoids to include all empty state accesses, since the client can assume if it isn't in the result then it is empty.

The variant that I would personally prefer is actually the opposite: always including empty accesses. Althought they are redundant as mentioned before, I like knowing those accesses actually happened. But this is more useful for some use cases that I want, and might be a bit unjustified for what the API tries to provide.

}
}
Expand Down
Loading