fix: Prove block that consumes an L1toL2 msg added on the same L1 block#16375
Merged
spalladino merged 1 commit intonextfrom Sep 3, 2025
Merged
fix: Prove block that consumes an L1toL2 msg added on the same L1 block#16375spalladino merged 1 commit intonextfrom
spalladino merged 1 commit intonextfrom
Conversation
spalladino
force-pushed
the
palla/l1-to-l2-message-proving-v2
branch
from
f935117 to
74e6519
Compare
spalladino
force-pushed
the
palla/l1-to-l2-message-proving-v2
branch
from
74e6519 to
7bfeae4
Compare
Co-authored-by: iLeila Wang <leizciw@gmail.com>
spalladino
force-pushed
the
palla/l1-to-l2-message-proving-v2
branch
from
d903029 to
594f977
Compare
ludamad
pushed a commit
that referenced
this pull request
Dec 16, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes issue where proving fails for a tx that consumes an l1 to l2 message that was bridged on the same block as the tx is mined. The prover was failing to add the messages to the tree before running tx public function simulation, so txs didnt have access to the messages from that block, so their execution reverted, yielding a different end state root.
See also #16704
Fixes #16675