Assessment reportsPublic findings
Back to Zellic site
↗
Assessment reports>Polygon Staking>Threat Model>withdrawVaults
GeneralOverview
Findings
High (1)
Medium (1)
Low (4)
Informational (7)
DiscussionThe logic in _updateStrategyRewards may not need to update all the strategiesThe LSTRewardsSplitter's splitting is not path-independent, which may have cross-protocol implicationsCalling checkUpkeep on chain is against the automation documentation and may revert or waste gas
Threat ModelWhat are threat models?LSTRewardsSplitter.solLSTRewardsSplitterController.sol
PolygonFundFlowController.solrestakeRewardsunbondVaultswithdrawVaults
PolygonStrategy.solPolygonVault.sol
Audit ResultsAssessment Results

Function: withdrawVaults(uint256[] _vaultIds)

This function withdraws from vaults and then performs upkeep if needed.

Inputs

  • _vaultIds

    • Control: Fully controlled by the caller.

    • Constraints: N/A.

    • Impact: Array of vaults to withdraw from.

Branches and code coverage

Intended branches

  • Call unstakeClaim for each vault.

  • Call performUpkeep to perform upkeep if upkeep is needed.

Zellic © 2025Back to top ↑