Skip to content

FMA: SuperchainERC20 #235

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

Closed
tynes opened this issue Mar 27, 2025 · 7 comments
Closed

FMA: SuperchainERC20 #235

tynes opened this issue Mar 27, 2025 · 7 comments
Assignees

Comments

@tynes
Copy link
Contributor

tynes commented Mar 27, 2025

This ticket will be complete when the SuperchainERC20 FMA is finalized. https://github.com/ethereum-optimism/design-docs/blob/f3aa2db64b1676b5e58ae602acf2ebdba34b617c/security/fma-superchainerc20.md

@tynes
Copy link
Contributor Author

tynes commented Mar 27, 2025

The status of this FMA is implementing actions.

  • add tests for the SuperchainTokenBridge
  • monitoring plan

We need to decide if we want specific monitoring or can leverage a single monitoring solution that is able to check that all executing messages do indeed have initiating messages.

@agusduha
Copy link
Contributor

Review:

  • Adding missing tests links fix: superchain erc20 FMA #245
  • FM1 monitoring does not seem necessary for now, the solution implies tracking for multiple ERC20

@agusduha
Copy link
Contributor

agusduha commented Apr 2, 2025

Finalizing PR: #245

@op-aaron op-aaron assigned mds1 and unassigned agusduha Apr 8, 2025
@tynes
Copy link
Contributor Author

tynes commented Apr 11, 2025

Review:

  • Adding missing tests links fix: superchain erc20 FMA #245
  • FM1 monitoring does not seem necessary for now, the solution implies tracking for multiple ERC20

We agree that monitoring for this is not required, especially since it is possible to create a malicious token that triggers the monitor. We can monitor at a lower layer of the protocol and get all of the benefits without needing to worry about app layer bugs

@tynes tynes closed this as completed Apr 11, 2025
@github-project-automation github-project-automation bot moved this from Backlog to Done in Protocol Team Apr 11, 2025
@mds1 mds1 reopened this Apr 11, 2025
@github-project-automation github-project-automation bot moved this from Done to In Progress in Protocol Team Apr 11, 2025
@mds1
Copy link
Contributor

mds1 commented Apr 11, 2025

Reopening just because I left one comment here: #245 (comment)

@agusduha
Copy link
Contributor

Last action item PR: #265
@mds1

@mds1
Copy link
Contributor

mds1 commented Apr 17, 2025

Merged and marking this as completed, thank you!

@mds1 mds1 closed this as completed Apr 17, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in Protocol Team Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Closed/Done
Status: Done
Development

No branches or pull requests

3 participants