fix(l1): use ethpandaops as the hoodi checkpoint sync server

[iovoid]

Motivation

Multisync has been failing on hoodi due to a 500 error in stakely.

Description

Switches to the EthPandaOps endpoint.

[github-actions]

🤖 Kimi Code Review

Review: PR #6533 - Update checkpoint sync URLs for Hoodi testnet

Summary: Configuration update to switch checkpoint sync endpoints from Stakely to EthPandaOps for the Hoodi testnet.

Assessment: ✅ No issues found. Change is correct and safe.

Notes:

1. Consistency (Lines 65, 212): Both Lighthouse beacon node instances are updated consistently to use https://checkpoint-sync.hoodi.ethpandaops.io. This maintains uniformity across the multi-sync setup.

2. URL Format: The new URL drops the trailing slash present in the original (...stakely.io/ → ...ethpandaops.io). This is benign—Lighthouse (and standard HTTP libraries) normalize this correctly.

3. Trust Assumptions: EthPandaOps is a reputable community infrastructure provider for Ethereum testnets. This change is operationally sound for Hoodi testing environments.

4. Timeout Retention: The --checkpoint-sync-url-timeout 600 (10 minutes) remains appropriate for the new endpoint.

Suggestion (Optional): Consider parameterizing the checkpoint URL via environment variables to avoid future hardcoded changes:

environment:
  - CHECKPOINT_SYNC_URL=${CHECKPOINT_SYNC_URL:-https://checkpoint-sync.hoodi.ethpandaops.io}

This is non-blocking—current approach is acceptable for testnet tooling.

---

Automated review by Kimi (Moonshot AI) · kimi-k2.5 · custom prompt

[github-actions]

🤖 Claude Code Review

PR #6533 Review: fix(l1): use ethpandaops as the hoodi checkpoint sync server

---

Overview

A minimal infrastructure fix that replaces the broken Stakely checkpoint sync endpoint for the Hoodi testnet with the EthPandaOps endpoint in the multisync Docker Compose configuration. Two identical substitutions are made — one per lighthouse-hoodi service instance.

---

Analysis

Correctness

• Both occurrences of the old URL (https://hoodi-checkpoint-sync.stakely.io/) are correctly updated to the new one (https://checkpoint-sync.hoodi.ethpandaops.io).
• The change is symmetric — both lighthouse-hoodi and lighthouse-hoodi-2 services get the same fix, which is the expected behavior.
• The trailing slash is dropped in the new URL. This is a minor stylistic difference; most HTTP clients handle both forms, but it's worth confirming the endpoint behaves identically without it.

Scope

• The fix is correctly scoped: only the failing checkpoint sync URLs are touched; no surrounding configuration is altered.
• No other files in the codebase reference hoodi-checkpoint-sync.stakely.io, so there are no missed call-sites.

Risk

• Low risk. This is a configuration-only change with no code logic involved.
• EthPandaOps is a well-known, community-trusted infrastructure provider for Ethereum testnets, making this a reasonable fallback.

---

Minor Observations

• If Stakely resumes service in the future, consider leaving a comment in the YAML explaining why the switch was made (e.g., # stakely.io returning 500s as of <date>). This helps future maintainers understand the history without digging through git blame.
• If there is a documented list of approved/preferred checkpoint sync endpoints for each testnet (in a README or CLAUDE.md), it would be worth updating that reference as well.

---

Verdict

The change is correct, minimal, and addresses the stated issue. Ready to merge.

---

Automated review by Claude (Anthropic) · sonnet · custom prompt

[greptile-apps]

Greptile Summary

Replaces the Stakely checkpoint sync endpoint (hoodi-checkpoint-sync.stakely.io) with the EthPandaOps endpoint (checkpoint-sync.hoodi.ethpandaops.io) for both consensus-hoodi and consensus-hoodi-2 services in the multisync compose file, fixing 500 errors that were blocking sync. Both instances are updated consistently, and the new URL pattern matches the existing pattern already used for Sepolia (checkpoint-sync.sepolia.ethpandaops.io).

Confidence Score: 5/5

Safe to merge — a straightforward URL swap with no logic changes.

The PR changes exactly two lines in a single YAML config file, replacing a broken third-party checkpoint sync URL with a working one. Both hoodi service instances are updated consistently, the new URL follows the same pattern already established for Sepolia, and there are no logic, security, or structural concerns.

No files require special attention.

Important Files Changed

Filename	Overview
tooling/sync/docker-compose.multisync.yaml	Checkpoint sync URL for both hoodi services updated from Stakely to EthPandaOps; change is consistent and matches the pattern used for sepolia.

Sequence Diagram

sequenceDiagram
    participant LH as Lighthouse (consensus-hoodi / hoodi-2)
    participant CP as checkpoint-sync.hoodi.ethpandaops.io
    participant EX as ethrex-hoodi / hoodi-2

    LH->>CP: GET /eth/v1/beacon/headers/finalized (checkpoint sync)
    CP-->>LH: finalized checkpoint state
    LH->>EX: engine_newPayloadV* (via authrpc :8551)
    EX-->>LH: VALID

Loading

_{Reviews (1): Last reviewed commit: "fix(tooling): hoodi checkpoint via ethpa..." | Re-trigger Greptile}

[github-actions]

🤖 Codex Code Review

Findings

1. Medium: tooling/sync/docker-compose.multisync.yaml:65 and tooling/sync/docker-compose.multisync.yaml:212 update multisync Hoodi to the new EthPandaOps endpoint, but other Hoodi sync entry points still point at older or different URLs, including the old Stakely endpoint in tooling/sync/Makefile:203. That leaves the repo with inconsistent behavior: multisync uses one checkpoint source, while other supported workflows can still keep using the deprecated one. If the intent is to retire the old Hoodi endpoint, update or centralize the Hoodi checkpoint URL across tooling/sync/docker-compose.yml:26, tooling/sync/Makefile:44, tooling/sync/Makefile:203, and docs/workflows/debug_execution_witness_benchmarking.md:56.

No other findings in the diff itself. This PR only changes operational sync config, so I don’t see any Rust/EVM/consensus, gas-accounting, or memory-safety risk in the changed lines alone.

---

Automated review by OpenAI Codex · gpt-5.4 · custom prompt