-
Notifications
You must be signed in to change notification settings - Fork 1.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
fix(isthmus): include storage updates in l2 withdrawals root computation #14307
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.
this seems right, but would like another review from
@shekhirin or @rkrasiuk
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.
otherwise lgtm
Some(state.database.as_ref().storage_root( | ||
ADDRESS_L2_TO_L1_MESSAGE_PASSER, | ||
hashed_storage_updates.unwrap_or_default(), | ||
)?) |
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.
this most likely does redundant IO because we might traverse this path during state root computation. please, leave a comment saying this. the proper way would be to include state_root
in the MultiProof
struct and call state_provider.multiproof
with the target instead of state_provider.root
when sealing a block
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.
opened an issue #14492
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.
thank you @rkrasiuk !
No description provided.