5 comments (5 comments)0 reactions (0 reactions)0 assignees (0 assignees)Rust212 stars (212 stars)37 forks (37 forks)user submission
good first issue
Description
the project is still using ethers
Contributor guide
- Tech stack
- rust
- Domain
- backend
- Issue type
- refactor
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 4
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- over 1 week
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- active
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- mostly clear
- Prerequisites
- Rust programmingethers rsalloy SDKMEV share
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 30
- Research direction
- Examine the current usage of ethers rs in the codebase, focusing on key modules like provider, contract calls, and error handling. Review the issue comments for any specific migration paths discussed. Compare ethers rs and alloy APIs to plan the migration, possibly starting with smaller crates or modules.