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

superchain-registry changes - Design and implement the mechanism for mapping release versions to an OPCM #13082

Open
Tracked by #13069
maurelian opened this issue Nov 25, 2024 · 0 comments
Open
Tracked by #13069

superchain-registry changes - Design and implement the mechanism for mapping release versions to an OPCM #13082

maurelian opened this issue Nov 25, 2024 · 0 comments

Comments

@maurelian
Copy link
Contributor

maurelian commented Nov 25, 2024 •
edited
Loading

The address of the OPCM corresponding to each upgrade will be stored in the superchain-registry,
and op-deployer will ensure that upgrades conform to the specified ordering.
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
@maurelian