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

db: state snapshots #2312

Open
14 of 27 tasks
Tracked by #2313
canepat opened this issue Sep 6, 2024 · 0 comments
Open
14 of 27 tasks
Tracked by #2313

db: state snapshots #2312

canepat opened this issue Sep 6, 2024 · 0 comments
Assignees
Labels
erigon3 Erigon3 feature meta High-level issue for for tracking many implementation issues

Comments

@canepat
Copy link
Member

canepat commented Sep 6, 2024

One of the main features of Erigon3 is moving most of the state content (i.e. account/storage/code) and its validity proof (i.e. commitment) to snapshot flat files. This is accomplished by introducing new abstractions for modelling the common requirements these entities have in terms storage, starting from the kind of queries they must support.

Obviously, some refactoring of the existing snapshot support is required in order to accommodate the new abstractions in the cleanest, most coherent and ultimately most useful way.

This is the main tracking issue. Individual issues are listed below:

@canepat canepat added erigon3 Erigon3 feature meta High-level issue for for tracking many implementation issues labels Sep 6, 2024
@canepat canepat self-assigned this Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
erigon3 Erigon3 feature meta High-level issue for for tracking many implementation issues
Projects
None yet
Development

No branches or pull requests

1 participant