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
State Receipt Ingestion in RollupOVM #450
State Receipt Ingestion in RollupOVM #450
Conversation
- Moved rollup serialization out of core because it's not useful outside of wallet stuff - Added rollup serialization encode / decode utility functions in place of ABI classes - Changed uni and pigi token types to be numbers
…ytes32 issue for keccak output
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.
Took a quick look through. To me this looks good. I like that you're storing data and handling fraud proofs in the OVM itself. Hiding as much of the exit game complexity inside the OVM vibes with me.
Also, looked it over with @ben-chain and he approves as well!
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.
Overall this looks great! I left one comment that's kinda massive about the wallet structure to make it more in line with the vision of the ovm (what you mentioned at standup).
Lemme know if there are questions!
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.
Let's Get That Money, as they say 💰
Description
MerkleInclusionProofDecider
to the OVM for checking the validity of merkle proofsMetadata
Fixes
Contributing Agreement