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

Reduce main minimal trace by recording only memory reads #177

Open
fractasy opened this issue Nov 28, 2024 · 0 comments
Open

Reduce main minimal trace by recording only memory reads #177

fractasy opened this issue Nov 28, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@fractasy
Copy link
Contributor

fractasy commented Nov 28, 2024

Today we are recording [a,b] for every step.
If we store only memory reads that are not memory-mapped registers, we would create a vector of read values, in read order, which is deterministic. Since 90% of the memory usage is for registers, this would reduce the length of the trace, and therefore the memory requirements.
This is similar to the zkEVM input db concept, but storing [value] in execution read order instead of the initial set of [key, value].

@fractasy fractasy self-assigned this Nov 28, 2024
@fractasy fractasy added the enhancement New feature or request label Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant