Reentrancy guard on external-calling functions
EigenLayer's assessment for RD-F-014 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Confirmed: StrategyManager uses ReentrancyGuardUpgradeable with nonReentrant on queueWithdrawal and depositIntoStrategyWithSignature. DelegationManager has nonReentrant on queueWithdrawals. EigenPodManager has nonReentrant on createPod and recordBeaconChainETHBalanceUpdate. Olympix analysis confirmed these as correctly implemented. StrategyBase functions only callable via StrategyManager, blocking cross-contract reentrancy.
Sources #
- EtherscanEigenLayer StrategyManager ImplementationStrategyManager implementation 0x5d25eef8cfedaa47d31fe2346726de1c21e342fb — verified sourceretrieved 2026-04-28
- Olympix EigenLayer Analysis — reentrancy confirmationOlympix/Slither comparative analysis — reentrancy guards correctly implementedretrieved 2026-04-28
Methodology #
Determine whether all state-mutating functions that perform external calls carry `nonReentrant` or an equivalent reentrancy guard.
See the full factor methodology and distribution across all protocols →