Assessment reportsPublic findings
Back to Zellic siteBack
↗
Assessment reports>EtherFi>Informational findings>Admin could not revert exit request on behalf of LiquidityPool
GeneralOverview
Findings
Critical (5)
High (1)
Medium (3)
Low (1)
Informational (1)Admin could not revert exit request
DiscussionUnused variables could be removed
Threat ModelWhat are threat models?EtherFiNode.solEtherFiNodesManager.solLiquidityPool.solStakingManager.sol
Audit ResultsSummary
Category: Code Maturity

Admin could not revert exit request on behalf of LiquidityPool

Informational Impact
Informational Severity
N/A Likelihood

Description

There is a sendExitRequests function to send exit requests when the TNFT holder is LiquidityPool, which calls batchSendExitRequest, but there is no function to call batchRevertExitRequest when the TNFT holder is LiquidityPool.

Impact

There is no function to call batchRevertExitRequest on behalf of LiquidityPool.

Recommendations

We recommend adding a function to call batchRevertExitRequest on behalf of LiquidityPool.

Remediation

This issue has been acknowledged by EtherFi, and a fix was implemented in commit 405b37cc↗.

Zellic © 2025Back to top ↑