Skip to content

fix: finalize Msg Passing FMA #251

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

Merged

Conversation

agusduha
Copy link
Contributor

@agusduha agusduha commented Apr 2, 2025

Description

Finalize Msg Passing FMA and add tracking monitoring issue

Metadata

Issue: #237

@agusduha
Copy link
Contributor Author

agusduha commented Apr 3, 2025

Missing:

  • FM3: Check for any L2Beat Stage 1 considerations related to the inability to successfully call validateMessage as part of a force-include a transaction.

Not sure if we wanna track this one inside the censorship resistance issue but lmk

Sorry, something went wrong.

@mds1
Copy link
Contributor

mds1 commented Apr 11, 2025

@agusduha Tracking it inside the censorship resistance seems like a good idea, just to make sure we revisit it later. For now I don't think this is a blocker because per L2Beat in the optimism R&D discord here:

it’s not a problem but we’re currently in the process of more precisely defining what’s in scope of the stages framework and what’s not. it’s more relevant to appchains though but we’ll see

Copy link
Contributor

@mds1 mds1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved pending the above comments

@mds1 mds1 merged commit c11e240 into ethereum-optimism:main Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants