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

Output processing stages #1898

Open
rakita opened this issue Dec 6, 2024 · 0 comments
Open

Output processing stages #1898

rakita opened this issue Dec 6, 2024 · 0 comments

Comments

@rakita
Copy link
Member

rakita commented Dec 6, 2024

There are multiple use cases where users what to do something with the output state, problem with that is there are footguns or unneeded state that are not easy to consume. The returned state reflects the internal JournaledState that in good amount of cases needs to be filtered in one way or another.

Examples:

  • Filter only the changed data.
  • Filter all read data.
  • Nulify self-destructed account.
  • Commit to the database (aka Context)

We can see a few types of stages that we can have:

  • Modification applying changes to data (Applying selfdestruct to remove the footgun, and prepare for next tx)
  • Transformation from internal type to something that is easier to consume ( Commit to db and return TransitionAccount)
  • Filtering of the data (Filter only the changed accounts).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant