Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

alloy-evm cannot be bumped to 0.28 until reth updates its dependency

Open
#154 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
rust

Research direction

Wait for a reth release using alloy-evm >= 0.28, then inspect the dependency updates and crates/ev-precompiles/src/mint.rs. Check crates/ev-revm/src/factory.rs and run the project’s compilation checks; done means reth and alloy-evm resolve to compatible versions without duplicate-type errors and the Precompile API change is addressed.

Written by the indexing model from the issue text.

Description

Description

Dependabot opened a PR to bump alloy-evm from 0.27.2 to 0.28.0, but it cannot be merged because reth v1.11.1 internally depends on alloy-evm 0.27.3.

Having both versions in the dependency graph causes type mismatches — Rust treats alloy-evm 0.27::EthBlockExecutorFactory and alloy-evm 0.28::EthBlockExecutorFactory as completely different types, resulting in compilation errors in crates/ev-revm/src/factory.rs.

Required changes for alloy-evm 0.28

  • Precompile trait breaking change: is_pure() was renamed to supports_caching() (alloy-rs/evm#284). Requires a trivial fix in crates/ev-precompiles/src/mint.rs.
  • Version alignment: alloy-evm must match the version used by reth to avoid duplicate types in the dependency graph.

Action

  • Close the dependabot PR for now
  • Wait for a reth release that depends on alloy-evm >= 0.28
  • Then update reth and alloy-evm together
Dominant language
Rust
Stars
8
Forks
9
Avg merge
3d 17h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from evstack/ev-reth

All issues in evstack/ev-reth

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.