Assessment reportsPublic findings
Back to Zellic site
↗
Assessment reports>Aura Finance>Threat Models>Function: depositAll(uint256 _pid, bool _stake)
GeneralOverview
DiscussionThe protectAddPool is unsafeWithdrawal of funds from a shut down pool
Threat ModelsWhat are threat models?AuraBalProxyOFT.solAuraBalRewardPool.solAuraOFT.solAuraVestedEscrow.solBaseRewardPool4626.sol
BoosterLite.solFunction: addPool(address _lptoken, address _gauge, uint256 _stashVersion)Function: deposit(uint256 _pid, uint256 _amount, bool _stake)Function: depositAll(uint256 _pid, bool _stake)Function: earmarkRewards(uint256 _pid)Function: withdraw(uint256 _pid, uint256 _amount)
ExtraRewardsDistributor.solL1Coordinator.solPausableOFT.solPausableProxyOFT.solPoolManagerLite.solVirtualBalanceRewardPool.sol
Audit ResultsAudit Results

Function: depositAll(uint256 _pid, bool _stake)

Helper function for depositing the sender's full balance to a gauge (specified by _pid). Optionally stakes the minted DepositToken on BaseRewardPool.

Inputs

  • _pid

    • Control: Arbitrary.

    • Constraints: Must be a valid entry in the poolInfo array, or balanceOf will revert.

    • Impact: Decides the pool to deposit to.

  • _stake

    • Control: Arbitrary.

    • Constraints: Boolean.

    • Impact: Decides if the deposit should be staked after minting.

Branches and code coverage (including function calls)

Intended branches

  • Deposit with stake.

  • Deposit without stake.

Negative behavior

  • Deposit with invalid _pid.

Zellic © 2025Back to top ↑