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

Update to how session state is managed for EVM #1352

Open
TheNewAutonomy opened this issue Feb 2, 2024 · 0 comments
Open

Update to how session state is managed for EVM #1352

TheNewAutonomy opened this issue Feb 2, 2024 · 0 comments
Labels

Comments

@TheNewAutonomy
Copy link
Member

As a developer I want all unit tests to pass so that we have a high degree of confidence that the functionality is working and repeatable.

Acceptance criteria

All unit tests pass, specifically all unit tests that involve snapshot, storage or session state.

Tasks

    • Storage state and snapshot state is no longer public, instead there's WorldState. However, KVM interacts directly with storage and snapshot state so we need a solution to allow KVM to work, ideally without modifying Nethermind's EVM assembles. Ideally we are able to work without modifying those assemblies then we can merge in future EVM support changes without modifications. Really, we should abstract KVM specific functionality from the underlying EVM assemblies for this reason.
    • Update unit tests relating to KVM state so we can ensure KVM continues to run reliably and we can test over time as we make future modifications to KVM.
@TheNewAutonomy TheNewAutonomy added this to To do in Catalyst Backlog via automation Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

1 participant