Skip to content

Conversation

@0xDiscotech
Copy link
Contributor

Description

Add new resendMessage feature covering the expired messages scenario on the FMAs were this issue was mentioned.

Metadata

@tynes tynes requested a review from smartcontracts April 14, 2025 20:35
@tynes tynes added this to the Interop RC Beta milestone Apr 14, 2025
If the message is not included within the expiration window, both the message and the underlying action could be considered lost.
- Likelihood: Medium. Block builders/sequencers are generally controlled by a single entity per chain.
- **Mitigations:** From a smart contract perspective, little can be done except allowing calls to `validateMessage` within a deposit context to improve censorship resistance. This is currently under discussion [here](https://github.com/ethereum-optimism/specs/issues/520).
- Potential Impact: High. If the message failure is not related to a time-sensitive operation but is due to the message being incorrect, it could be considered lost.
Copy link
Contributor

Choose a reason for hiding this comment

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

due to the message being incorrect

what do you mean by an "incorrect" message? not sure I am following this failure mode

Copy link
Contributor Author

@0xDiscotech 0xDiscotech Apr 21, 2025

Choose a reason for hiding this comment

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

You're totally right on pointing this out.
The 3rd FMA was reformulated, with the msg being censored being the main risk: e8fd593

Lmk if that works or if any change is needed :)

@mds1 mds1 merged commit c997f6d into ethereum-optimism:main Jun 4, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants