Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Infer other addresses from SystemConfig once MCP L1 is launched #71

Open
zchn opened this issue Jan 30, 2024 · 0 comments
Open

Infer other addresses from SystemConfig once MCP L1 is launched #71

zchn opened this issue Jan 30, 2024 · 0 comments

Comments

@zchn
Copy link
Contributor

zchn commented Jan 30, 2024 

          The goal of this file to serve as a reference and source of truth, which we verify in the `CheckSecurityConfigs` script? I ask because as of https://github.com/ethereum-optimism/optimism/pull/6555, we can now only define a chain's `SystemConfig` and then discover everything else. Wondering if we can leverage that in this repo (once everyone is on MCP L1 contracts)

Originally posted by @mds1 in #69 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zchn