fix(enm): revert disablePod on stale-beacon silent no-op [audit finding 1, HIGH] - #486
Merged
0xpanicError merged 2 commits intoAug 11, 2026
Conversation
disablePod() returns void, so an un-upgraded EtherFiNode beacon swallows the call via its empty fallback and returns success without disabling the pod. The manager then emitted a false PodDisabled, after which consolidating validators out would cut the pod's beacon-chain slashing factor. Assert pod.restakingDisabled() after the call so a stale-beacon deployment reverts PodNotDisabled instead. Adds a regression test; updates the existing mock-based retirement test to also report restakingDisabled(). Finding 1 (HIGH) from the PR #485 pre-audit review; reproduced on a Tenderly fork carrying real EigenLayer v1.14.0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
Signed-off-by: Yash Saraswat <107622640+0xpanicError@users.noreply.github.com>
0xpanicError
merged commit Aug 11, 2026
d88d52e
into
pankaj/feat/non-eigenpod-withdrawal-credentials
2 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Finding 1 (HIGH) —
disablePodsilent no-opEtherFiNodesManager.disablePodcallsIEtherFiNode(node).disablePod(), which returns nothing. If the EtherFiNode beacon has not been upgraded yet, the old implementation's emptyfallback()swallows the call and returns success — so the manager emits a falsePodDisabledwhile the pod is still live. The runbook's next step (consolidating validators out) would then cut the pod's beacon-chain slashing factor and devalue our claim on the ETH still in it.Fix
After calling
disablePod(), assert the pod actually reportsrestakingDisabled(); otherwise revertPodNotDisabled. A stale-beacon deployment now fails loudly instead of silently succeeding.Tests
test_disablePod_revertsWhenPodNotActuallyDisabled(pod stays enabled → revertsPodNotDisabled).test_disabledPod_retirementRoutesThroughTheNodeAsPodOwnerto mockrestakingDisabled() == truefor the happy path.non-eigenpod-credentialssuite: 77 passing on mainnet fork.Evidence
Empirically reproduced on a Tenderly fork carrying real EigenLayer v1.14.0 (rehearsal test T2): pre-fix,
disablePodsilently succeeds + emitsPodDisabledwhilerestakingDisabledstays 0.Base:
pankaj/feat/non-eigenpod-withdrawal-credentials(fix targets code introduced by PR #485).🤖 Generated with Claude Code
Note
High Risk
Touches irreversible EigenPod retirement on the restaking path; a wrong check could block legitimate retirements or still allow a false success that devalues ETH claims via the beacon slashing factor.
Overview
Fixes a HIGH audit finding where
disablePodcould silently succeed and emitPodDisabledeven though the EigenPod was still live.If the EtherFiNode beacon is stale, the empty
fallbackswallowsdisablePod()and returns success. The manager now asserts the pod exists and reportsrestakingDisabled()before emitting, otherwise revertsPodNotDisabled. That stops the runbook from consolidating validators out of a still-active pod and cutting the beacon-chain slashing factor.Adds a regression test for the silent no-op path and updates the happy-path test to mock
restakingDisabled() == true.Reviewed by Cursor Bugbot for commit 7f7fa64. Bugbot is set up for automated code reviews on this repo. Configure here.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.