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 (OPCM - Upgrade 13) #13082

Open
Tracked by #13069
maurelian opened this issue Nov 25, 2024 · 1 comment
Open
Tracked by #13069

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

maurelian opened this issue Nov 25, 2024 · 1 comment
Labels
T-evm-safety Team: EVM Safety T-upgrades

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.
@maurelian maurelian mentioned this issue Nov 25, 2024
Open
42 tasks
@maurelian
Copy link
Contributor Author

maurelian commented Dec 5, 2024 •
edited
Loading

Update: this will be done in the existing standard-versions-X.toml files.

Codeowners must be strictly enforced on that file as any incorrect OPCM addresses present a risk.

This was referenced Dec 5, 2024
Closed
Closed
@BlocksOnAChain BlocksOnAChain changed the title superchain-registry changes - Design and implement the mechanism for mapping release versions to an OPCM superchain-registry changes - Design and implement the mechanism for mapping release versions to an OPCM (Upgrade 12) Jan 10, 2025
@maurelian maurelian changed the title superchain-registry changes - Design and implement the mechanism for mapping release versions to an OPCM (Upgrade 12) superchain-registry changes - Design and implement the mechanism for mapping release versions to an OPCM (Upgrade 13) Jan 30, 2025
@maurelian maurelian added T-upgrades T-evm-safety Team: EVM Safety labels Feb 4, 2025
@maurelian maurelian changed the title superchain-registry changes - Design and implement the mechanism for mapping release versions to an OPCM (Upgrade 13) superchain-registry changes - Design and implement the mechanism for mapping release versions to an OPCM (OPCM - Upgrade 13) Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T-evm-safety Team: EVM Safety T-upgrades
Projects
OP Stack Upgrades
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@maurelian