-
Notifications
You must be signed in to change notification settings - Fork 364
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
Release v26 fixes #1232
base: release-v26
Are you sure you want to change the base?
Release v26 fixes #1232
Conversation
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.
I checked the part for publishing stored batch info and commitment. Looks good to me - I mean I think it should be possible to continue execution using only Ethereum calldata(when gateway calldata and l2 sequencer data are lost). However, some historical fields may have different guarantees after migration on the gateway, like events, bootloader memory commitment, and maybe some system logs, as they are not saved on the l1. But it's not a big issue probably
What ❔
Why ❔
Checklist