isthmus: Add hardfork timestamps

[gastonponti]

HF activation overrides for celo networks
(Workaround until having the config in the superchain)

Depends on celo-org/op-geth#388
Depends on celo-org/op-geth#390

Closes https://github.com/celo-org/celo-blockchain-planning/issues/795
Closes https://github.com/celo-org/celo-blockchain-planning/issues/936

[Copilot]

Pull Request Overview

Adds Celo-specific hardfork activation overrides to the rollup configuration and bumps the op-geth replace version.

• Imported params and called applyCeloHardforks in NewRollupConfigFromCLI
• Implemented applyCeloHardforks to set HF timestamps for Celo networks
• Updated go.mod to point the go-ethereum replace directive at a newer op-geth version

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
op-node/service.go	Added applyCeloHardforks function and invocation
go.mod	Updated replace directive for github.com/ethereum/go-ethereum

Comments suppressed due to low confidence (2)

op-node/service.go:293

• [nitpick] The function name applyCeloHardforks is a bit generic; consider renaming it to something like applyCeloHardforkActivationTimes to clarify its purpose.

func applyCeloHardforks(rollupConfig *rollup.Config) {

op-node/service.go:290

• New logic in applyCeloHardforks lacks test coverage; adding unit tests for each supported Celo chain ID would help catch regressions.

// applyCeloHardforks modifies the rollupConfig to apply Celo-specific hardforks.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License

View full report

[palango]

@gastonponti Updated this with latest op-geth.