ethereum-optimism / ethereum-optimism/optimism

op-service: add `eth.ChainConfig` interface, replace `*params.ChainConfig`

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

Description

We don't want to leak the underlying `*params.ChainConfig` type of geth everywhere, since in most cases we only want to check if a fork is active, and don't need concrete-type access or config mutation.

Contributor guide

Open the contributing guide

Research direction

Start in op-service by locating uses of *params.ChainConfig and reading how callers check fork activation or access configuration. Done means consumers can depend on the proposed eth.ChainConfig interface without leaking the geth concrete type, while preserving the existing fork checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.