ethereum-optimism / ethereum-optimism/optimism
Testing to detect when a release has occurred and any non-empty `upgrade()` methods should be reset. (OPCM - Upgrade 13)
Open
@AmadiMichael is already working on this.
Since Mar 17, 2025.
T-evm-safety
T-upgrades
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 134
Description
**Context:**
Certain aspects of the repository will need to change when a release has occured:
- ie. `Releases.release()` value
- `upgrade()` methods on contracts receiving new state vars can be deleted.
- `opcm.upgrade()` of method will need to change to a no-op (fork testing will still pass, but it should be reset for development of the next upgrade.
**Todo:**
We will need a mechanism to identify when an L1 release has occurred which causes these functions to become a 'no-op'. They should be reset at that time.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.