update go-ethereum dependency

[FletcherMan]

Update go-ethereum, and add morph203Time for upgrading testing

Summary by CodeRabbit

• New Features

  • Introduced an optional configuration setting for enhanced upgrade scheduling.

• Chores

  • Updated references for the Ethereum integration to the latest stable release, improving performance and stability across the system.

[coderabbitai]

Walkthrough

This pull request updates the repository's submodule and dependency references for the go-ethereum module. The submodule branch in .gitmodules is changed from “feature/block_context” to “main” and the tracked commit in the go-ethereum project is updated. Several go.mod files (and the Makefile) now reference a new Ethereum target version, updating the dependency from an older commit to a more recent one. Additionally, the genesis configuration is enhanced by introducing an optional Morph203Time field and propagating it through the genesis block creation process.

Changes

File(s)	Change Summary
.gitmodules, go-ethereum	Update submodule branch from “feature/block_context” to “main” and update the subproject commit from 3b9465a03a8cebd3... to de5160c106deeae615de11c6b72dc64109d18767.
Makefile, bindings/go.mod, contracts/go.mod, node/go.mod, ops/.../go.mod, ops/tools/go.mod, oracle/go.mod, tx-submitter/go.mod	Update Ethereum dependency version from v1.10.14-0.20241226065029-3b9465a03a8c to v1.10.14-0.20250218031646-de5160c106de.
ops/.../genesis/config.go, ops/.../genesis/genesis.go	Add new optional field Morph203Time in genesis configuration and integrate it into the genesis block setup.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant C as Config Loader
    participant G as Genesis Builder

    U->>C: Provide deployment config (optional Morph203Time)
    C->>G: Call NewL2Genesis(config)
    G->>G: Check if Morph203Time is set and integrate into genesis config
    G-->>U: Return configured genesis block

Loading

Possibly related PRs

• Move block context to blob #649: Involves modifications to the .gitmodules file changing the "go-ethereum" submodule branch, though with adjustments in the opposite direction.

Suggested reviewers

• songyaoshun

Poem

I'm a bunny with a keen coder's heart,
Hopping through branches with precision and art,
Submodules updated and dependencies leaped,
Genesis tweaks make the protocol deep,
With carrots 🥕 and commits, I cheer and play—
CodeRabbit celebrates changes in a joyful way!

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 golangci-lint (1.62.2)

level=warning msg="[runner] Can't run linter goanalysis_metalinter: buildir: failed to load package zstd: could not load export data: no export data for "morph-l2/node/zstd""
level=error msg="Running error: can't run linter goanalysis_metalinter\nbuildir: failed to load package zstd: could not load export data: no export data for "morph-l2/node/zstd""

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9e1d0de and 41a1d3a.

⛔ Files ignored due to path filters (8)

• bindings/go.sum is excluded by !**/*.sum
• contracts/go.sum is excluded by !**/*.sum
• go.work.sum is excluded by !**/*.sum
• node/go.sum is excluded by !**/*.sum
• ops/l2-genesis/go.sum is excluded by !**/*.sum
• ops/tools/go.sum is excluded by !**/*.sum
• oracle/go.sum is excluded by !**/*.sum
• tx-submitter/go.sum is excluded by !**/*.sum

📒 Files selected for processing (12)

• .gitmodules (1 hunks)
• Makefile (1 hunks)
• bindings/go.mod (1 hunks)
• contracts/go.mod (1 hunks)
• go-ethereum (1 hunks)
• node/go.mod (1 hunks)
• ops/l2-genesis/go.mod (1 hunks)
• ops/l2-genesis/morph-chain-ops/genesis/config.go (1 hunks)
• ops/l2-genesis/morph-chain-ops/genesis/genesis.go (2 hunks)
• ops/tools/go.mod (1 hunks)
• oracle/go.mod (1 hunks)
• tx-submitter/go.mod (1 hunks)

✅ Files skipped from review due to trivial changes (4)

• .gitmodules
• go-ethereum
• Makefile
• ops/tools/go.mod

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: test
• GitHub Check: test
• GitHub Check: test

🔇 Additional comments (8)

ops/l2-genesis/morph-chain-ops/genesis/genesis.go (1)

38-41: LGTM! Clean implementation of the Morph203Time feature.

The changes correctly handle the optional Morph203Time configuration by conditionally assigning the value and including it in the chain configuration.

Also applies to: 63-63

ops/l2-genesis/morph-chain-ops/genesis/config.go (1)

129-130: LGTM! Well-structured addition of the Morph203Time configuration.

The field is correctly implemented as an optional configuration with proper documentation and JSON handling.

contracts/go.mod (1)

9-9:

❓ Verification inconclusive

Verify the go-ethereum dependency update.

The go-ethereum dependency has been updated to a newer version. Please ensure that:

1. The new version is stable and compatible with the codebase.
2. All tests pass with the new version.
3. The changes in the new version have been reviewed for potential breaking changes.

Run the following script to check the changes between the versions:

---

🏁 Script executed:

#!/bin/bash
# Description: Check the changes between go-ethereum versions.

# Clone the repository
git clone https://github.com/morph-l2/go-ethereum.git
cd go-ethereum

# Compare the changes between the old and new versions
git log --oneline 3b9465a03a8c..de5160c106de

Length of output: 164

---

Action: Please manually verify the go-ethereum dependency update.

The initial git log command did not yield any output, so it's unclear whether the diff between commit 3b9465a03a8c and de5160c106de was correctly produced. To gain further confidence, please run additional checks—especially to confirm that the old commit exists and that any changes from it to the new commit don't introduce breaking changes. For example, you can run:

#!/bin/bash
cd go-ethereum || exit 1

echo "Verifying existence of commits:"
echo -n "Old commit (3b9465a03a8c): "
git cat-file -t 3b9465a03a8c 2>/dev/null || echo "not found"
echo -n "New commit (de5160c106de): "
git cat-file -t de5160c106de 2>/dev/null || echo "not found"

echo -e "\nAttempting to show diff between commits (if both exist):"
git diff 3b9465a03a8c de5160c106de || echo "Diff not produced. Manual check required."

Next steps:

• Verify that commit 3b9465a03a8c exists in the upstream repository.
• Confirm that changes between 3b9465a03a8c and de5160c106de are well understood and won’t break the codebase.
• Ensure that all tests run successfully with the new version.

Once these steps are confirmed manually, you can be confident the dependency update is safe.

bindings/go.mod (1)

7-7: LGTM! Consistent go-ethereum dependency update.

The go-ethereum dependency version update matches the one in contracts/go.mod, maintaining consistency across the codebase.

ops/l2-genesis/go.mod (1)

9-9: Dependency Version Update Verified
The go-ethereum dependency has been updated to v1.10.14-0.20250218031646-de5160c106de, replacing the previous commit. This change appears consistent with the goal of using the latest version. Please ensure that this update does not introduce breaking changes—especially if there are any API differences in the new commit.

tx-submitter/go.mod (1)

10-10: Updated go-ethereum Dependency in tx-submitter Module
The dependency for github.com/morph-l2/go-ethereum has been updated to v1.10.14-0.20250218031646-de5160c106de in the tx-submitter module. Make sure that this update is compatible with any build or runtime expectations (for example, linking or API calls) in this module.

oracle/go.mod (1)

10-10: Consistent Dependency Update in Oracle Module
The oracle module now also references the updated go-ethereum dependency version (v1.10.14-0.20250218031646-de5160c106de). This aligns with the broader update across the project. It would be prudent to run integration tests to confirm that no interface changes adversely affect this module’s functionality.

node/go.mod (1)

13-13: go-ethereum Version Update in Node Module
The node module has been updated to use the latest go-ethereum version (v1.10.14-0.20250218031646-de5160c106de), ensuring consistency with other modules. Please verify that all components interacting with go-ethereum (e.g., submodules or dependent libraries) continue to operate as expected after this update.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.