External keeper/relayer not redundant
EigenLayer's assessment for RD-F-062 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
EigenPod checkpoint proof submission depends on external parties (typically pod owners or relayers) submitting valid beacon chain proofs. There is no on-chain keeper or automated redundancy enforced at the protocol level. Users must actively submit proofs to checkpoint validator balances and access the withdrawal queue. During the Aug 2025 Pectra fix, rapid manual proof submissions were required. Protocol does not depend on a keeper service for core accounting security, but proof submission liveness has a meaningful dependency on user-side participation. Yellow: liveness dependency without formal redundancy, though economically self-incentivized.
Sources #
- URLEigenPod.sol — verifyCheckpointProofs() callable by pod owner; no automated keeper enforced at protocol levelEigenPod.sol verifyCheckpointProofs()retrieved 2026-04-28
- EigenPods Bug Fix Completed August 29, 2025 — consensus upgrade broke proof format; patched same day; no funds at riskEigenPods Pectra bug fix August 2025retrieved 2026-04-28
Methodology #
Determine whether the protocol depends on a single keeper or relayer (Gelato, Chainlink Automation, custom) with no redundancy or failover.
See the full factor methodology and distribution across all protocols →