stakingContext.auraBooster.deposit boolean return value not handled in Boosted3TokenPoolUtils.sol
stakingContext.auraBooster.deposit boolean return value not handled in Boosted3TokenPoolUtils.sol\\nthe function _joinPoolAndStake in Boosted3TokenPoolUtils.sol is used extensively when handling the token stake.\\nHowever, when entering the stake and interacting with external contract, the logic does not handle the returned boolean value in the code below\\n```\\n        // Transfer token to Aura protocol for boosted staking\\n        stakingContext.auraBooster.deposit(stakingContext.auraPoolId, bptMinted, true); // stake = true\\n```\\n\\nIn the AuraBooster implmenetation, a Boolean is indeed returned to acknowledge that deposit is completely successfully.\\n```\\n    /**\\n     * @notice  Deposits an "_amount" to a given gauge (specified by _pid), mints a `DepositToken`\\n     *          and subsequently stakes that on Convex BaseRewardPool\\n     */\\n    function deposit(uint256 _pid, uint256 _amount, bool _stake) public returns(bool){\\n```\\n
We recommend the project handle the stakingContext.auraBooster.deposit boolean return value explicitly.\\n```\\n  // Transfer token to Aura protocol for boosted staking\\n    bool staked = stakingContext.auraBooster.deposit(stakingContext.auraPoolId, bptMinted, true); // stake = true\\n    require(staked, 'stake failed');\\n```\\n
Notional -> AuraBooster -> BaseRewardPool\\nWithout handling the boolean value explitily, there is risk that transaction may be fail sliently.\\nBecause there are two layers of external call
```\\n        // Transfer token to Aura protocol for boosted staking\\n        stakingContext.auraBooster.deposit(stakingContext.auraPoolId, bptMinted, true); // stake = true\\n```\\n