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.

Sign up for GitHub

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

Jump to bottom

Optimize state reversion in a SMT multistore #259

Closed
Tracked by #514
Manav-Aggarwal opened this issue Aug 11, 2022 · 1 comment
Closed
Tracked by #514

Optimize state reversion in a SMT multistore #259

Manav-Aggarwal opened this issue Aug 11, 2022 · 1 comment
Labels
C: Cevmos Changes related to the cevmos branches C:Store

Comments

@Manav-Aggarwal
Copy link
Member

Manav-Aggarwal commented Aug 11, 2022 •
edited
Loading

In #249, state reversion is done by creating a new baseapp instead and setting over the entire state for the app manually by viewing a previous version of the state using the structure view_store.

We'd like to explore optimizing this by potentially reverting the same app instead to a previous version. Currently it is not clear how to do that.

One issue with it is that if you have a fresh baseapp. and execute a block but do not commit, doing a state reversion throws an error. This is relevant post activating fraudproof generation mode described in #249
@Manav-Aggarwal Manav-Aggarwal added C: Cevmos Changes related to the cevmos branches C:Store labels Aug 11, 2022
@Manav-Aggarwal Manav-Aggarwal mentioned this issue Aug 14, 2022
Closed
19 tasks
@Manav-Aggarwal
Copy link
Member Author

We use IAVL tree now. Closed by: rollkit#1

@tzdybal tzdybal mentioned this issue Nov 17, 2022
Closed
38 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: Cevmos Changes related to the cevmos branches C:Store
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Manav-Aggarwal