Assessment reportsPublic findings
Back to Zellic siteBack
↗
Assessment reports>Polygon Staking>Threat Model>deposit
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.solPolygonFundFlowController.solPolygonStrategy.sol
PolygonVault.soldepositrestakeRewardsunbondwithdrawwithdrawRewards
Audit ResultsAssessment Results

Function: deposit(uint256 _amount)

This function deposits tokens from the vault controller into the validator pool.

Inputs

  • _amount

    • Control: Fully controlled by the caller.

    • Constraints: N/A.

    • Impact: Amount of tokens to deposit.

Branches and code coverage

Intended branches

  • Receive the amount of tokens to deposit.

  • Call the buyVoucherPOL function on the validator pool.

  • Send any remaining tokens back to the vault controller.

Zellic © 2025Back to top ↑