feat(ethereum): add hoodi testnet support

[cjorge-graphops]

feat(ethereum): update to erigon 3

feat(ethereum): default to erigon caplin for consensus

Summary by CodeRabbit

• New Features

  • Added support for the new "hoodi" flavor in the Ethereum namespace, including configuration options and dedicated settings for Erigon, Lighthouse, and Nimbus clients.

• Documentation

  • Updated documentation to reflect changes in default features and allowed options for the Polygon namespace.

• Refactor

  • Removed the "heimdall-ha-svc" feature from the Polygon namespace configuration and schema for improved consistency.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This change introduces a new "hoodi" flavor to the Ethereum namespace across configuration, schema, and Helmfile definitions. It adds corresponding configuration files for Erigon, Lighthouse, and Nimbus clients under the new "hoodi" network. The schema and CUE definitions are updated to recognize "hoodi" as a valid flavor, including its default properties and namespace settings. Additionally, the Polygon namespace documentation and schema are updated to remove the "heimdall-ha-svc" feature, consolidating references to "heimdall" only.

Changes

File(s)	Change Summary
ethereum/helmfile.yaml, schema.json, src/schemas/ethereum.cue	Added support for the new "hoodi" flavor in the Ethereum namespace, including default configurations, schema enum values, and target namespace "eth-hoodi".
ethereum/values/hoodi/erigon.yaml, ethereum/values/hoodi/lighthouse.yaml, ethereum/values/hoodi/nimbus.yaml	Added new configuration files for the "hoodi" network for Erigon, Lighthouse, and Nimbus clients, specifying network-specific arguments and resource requirements.
ethereum/values/holesky/lighthouse.yaml, ethereum/values/sepolia/lighthouse.yaml	Added Lighthouse client configuration files for the "holesky" and "sepolia" networks, each specifying the appropriate network argument.
polygon/README.md	Updated documentation to remove "heimdall-ha-svc" from the list of allowed and default features in the Polygon namespace.
schema.json	Removed all references to the "heimdall-ha-svc" feature from the Polygon namespace schema, including enums, defaults, and feature definitions.

Sequence Diagram(s)

sequenceDiagram
    participant Operator
    participant Helmfile
    participant Schema
    participant Erigon
    participant Lighthouse
    participant Nimbus

    Operator->>Helmfile: Deploy Ethereum with flavor "hoodi"
    Helmfile->>Schema: Validate "hoodi" flavor and namespace settings
    Helmfile->>Erigon: Apply "hoodi" configuration (extraArgs, storage)
    Helmfile->>Lighthouse: Apply "hoodi" configuration (extraArgs)
    Helmfile->>Nimbus: Apply "hoodi" configuration (extraArgs)

Loading

Suggested labels

type:feature

Suggested reviewers

• i0n
• calinah

---

📜 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 77bf94d and 4415548.

📒 Files selected for processing (9)

• ethereum/helmfile.yaml (1 hunks)
• ethereum/values/holesky/lighthouse.yaml (1 hunks)
• ethereum/values/hoodi/erigon.yaml (1 hunks)
• ethereum/values/hoodi/lighthouse.yaml (1 hunks)
• ethereum/values/hoodi/nimbus.yaml (1 hunks)
• ethereum/values/sepolia/lighthouse.yaml (1 hunks)
• polygon/README.md (1 hunks)
• schema.json (8 hunks)
• src/schemas/ethereum.cue (2 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
• @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.