ethereum-optimism / ethereum-optimism/ecosystem
Move dependency API requests implementation details out of relayer and into a dependency client file
Open
- Dominant language
- TypeScript
- Stars
- 139
- Forks
- 82
- Avg merge
- 44m
- Merged PRs (30d)
- 3
Description
Reference: https://github.com/ethereum-optimism/ecosystem/pull/887#discussion_r2201505585
Contributor guide
Research direction
Start with the relayer implementation and the dependency client file referenced by discussion_r2201505585 in ecosystem#887. Trace where dependency API requests are implemented; done means those implementation details reside in the dependency client rather than the relayer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100