-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Add binary deserialization to asterisc's state converter trace function #12238
Add binary deserialization to asterisc's state converter trace function #12238
Conversation
a9e250e
to
d5e9984
Compare
Currently includes diff for #12265, but will be rebase this PR to develop once it's merged. |
d5e9984
to
9a92763
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So good to see knowledge of the specific snapshot format moving out of challenger. Just need to make sure the witness
subcommand in asterisc is giving back what you expect.
55d7533
to
a55aea4
Compare
a55aea4
to
9d908cc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
b02dba0
…on (#12238) * Move serialize from cannon to op-service * Add binary deserialization to asterisc's state converter trace function * Use Asterisc's witness cmd to generate state data * Fix op-challenger tests * remove unnecessary logic from state_converter, and only test witness subcommand
…on (ethereum-optimism#12238) * Move serialize from cannon to op-service * Add binary deserialization to asterisc's state converter trace function * Use Asterisc's witness cmd to generate state data * Fix op-challenger tests * remove unnecessary logic from state_converter, and only test witness subcommand
Description
Adds support for binary serialization of VMState for Asterisc, while preserving compatibility with JSON snapshots. We infer the type of the snapshot by looking at the file type, and dynamically choose whether to use binary representation of json representation.
This is dependency PR of Asterisc PR here: ethereum-optimism/asterisc#82
This is used in Asterisc's op-e2e tests, where a prestate file is converted into VMState instance in op-challenger trace provider