Skip to content
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

Handle rereading self-destructed contracts better so we don't need to fall back to sequential #314

Open
hai-rise opened this issue Sep 4, 2024 · 3 comments

Comments

@hai-rise
Copy link
Contributor

hai-rise commented Sep 4, 2024

  • The current difficulty is to write zero to all slots on self-destruction. Perhaps we can add some data structure to track self-destructed accounts to then check at storage.
  • This is quite common in early eras like ISTANBUL and is the only case that causes slow down at the moment.
  • It is not that severe going forward as self-destruction has already been deprecated.
@byhashdong
Copy link
Contributor

@hai-rise Has anyone taken this issue? If not, I would like to take it.

@hai-rise
Copy link
Contributor Author

@byhashdong Not yet and it could be quite challenging 🤔.
My vague plan is to address this with/after #382 which will give us more control at the EVM execution level.
Feel free to have a go still 🙏.

@byhashdong
Copy link
Contributor

Okay, I would like to give it a try. If you have any suggestions, please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants