ethereum-optimism / ethereum-optimism/optimism

Tracker: Resolve dependency cycles in op-node components.

Open
#17,115 0 comments 0 reactions 0 assignees View on GitHub
A-op-node
Dominant language
Go
Stars
6.5k
Forks
4k
Avg merge
2d 15h
Merged PRs (30d)
145

Description

Description here:

https://github.com/ethereum-optimism/optimism/pull/17101/files#r2282745163

This ticket number will be referenced in TODO comments tracking locations of potential DI dependency cycles in op-node for refactor.

Contributor guide

Open the contributing guide

Research direction

Start with the discussion in PR 17101, comment r2282745163, then inspect the op-node TODO comments that identify potential dependency cycles. Map the affected components and their dependency paths before deciding how the refactor should be structured; done means the tracked cycles are resolved and the TODO references are updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.