feat(protocol): allow block propose to pass a bytes32 input to L2 anchor #18569
Conversation
This file contains 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
feat(protocol): allow block propose to pass a bytes32 input to L2 anchor
🚨 Report Summary
For more details view the full report in OpenZeppelin Code Inspector |
Closed
myronrotter
reviewed
Dec 9, 2024
dantaik
changed the title
dantaik
changed the title
smtmfft
approved these changes
Dec 15, 2024
davidtaikocha
approved these changes
Dec 16, 2024
dantaik
requested review from
davidtaikocha
and removed request for
myronrotter
davidtaikocha
approved these changes
Dec 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This feature allows the block proposer to pass any bytes32 data as input to L2, which can then be consumed by transactions within the same block.
It is a general-purpose feature, leaving the definition and use of the input data entirely up to the block proposer. If larger data is required, its hash can be passed as the input. The original data can then be included as call data in L2 transactions, enabling the verification of the data’s integrity against the input (the hash).