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

Export minimal pre-execution state from a fraudulent block instead of a post-execution state #257

Closed
Tracked by #245 ...
Manav-Aggarwal opened this issue Aug 10, 2022 · 1 comment
Assignees
Labels
block-fraud-proofs Block Fraud Proofs (Generation and verification) C: Cevmos Changes related to the cevmos branches C:Store

Comments

@Manav-Aggarwal
Copy link
Member

Manav-Aggarwal commented Aug 10, 2022

We'd like to be able to revert to a previous state of a cosmos-sdk baseapp and use logs from a trace to filter down to the minimal set of state needed in a fraudproof.

Parts covered from the cycle of a fraudproof:

Optimint Full Node (Producer of fraudproof)
3. The cosmos-sdk will simply execute the fraudulent block while logging all the states touched by the transaction. Then, it will revert to a previous state again, and then snapshot the state while using the contents of the log to filter down to the minimal set of state needed. This minimial snapshot will be packaged as a fraudproof and passed back to optimint.

Parent issue: #245

@Manav-Aggarwal
Copy link
Member Author

Closed by: rollkit#1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
block-fraud-proofs Block Fraud Proofs (Generation and verification) C: Cevmos Changes related to the cevmos branches C:Store
Projects
No open projects
Archived in project
1 participant