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

perf(continuations): Hash initial accounts at the beginning of the execution #412

Open
hratoanina opened this issue Jul 19, 2024 · 0 comments
Assignees
Labels
crate: evm_arithmetization Anything related to the evm_arithmetization crate. performance Performance improvement related changes

Comments

@hratoanina
Copy link
Contributor

Currently, we hold in memory a copy of the original payloads of all initial accounts and initial storage slots, which is kept all the way to the initial trie hashing at the end of the execution.
What we could do instead is to hash them in the beginning so that we only need to store the initial accounts in the form of hash nodes.

@hratoanina hratoanina added performance Performance improvement related changes crate: evm_arithmetization Anything related to the evm_arithmetization crate. labels Jul 19, 2024
@hratoanina hratoanina added this to the zk-continuations - Q3 2024 milestone Jul 19, 2024
@LindaGuiga LindaGuiga self-assigned this Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crate: evm_arithmetization Anything related to the evm_arithmetization crate. performance Performance improvement related changes
Projects
Status: Backlog
Development

No branches or pull requests

2 participants