ethereum-optimism / ethereum-optimism/optimism
`revm` update cadence
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 145
Description
We've been maintaining OP stack support in Hardhat using `op-revm`. With the [transfer](https://github.com/bluealloy/revm/pull/3568) of `op-revm` from the `revm` monorepo to https://github.com/ethereum-optimism, will `op-revm` stay in sync with new `revm` releases?
If so, is there a timeline by which you aim to integrate new releases of REVM (bug fix, new EIPs, etc.)?
Contributor guide
Research direction
Start by reading the linked op-revm transfer pull request and the current issue discussion. Determine whether op-revm is expected to track revm releases and what integration timeline can be stated; done means the maintenance policy and release cadence are clearly documented or answered.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100