EverGrow EGC security record

In the contract `LucroStaking` the role `_admin` has authority over the functions shown in the list below. - function `addPackage()`, to create a package, transfer the rewards token to the contract, and set the number per second of token distribution. Users can stake the token in the contract to get the rewards from the package. - function `alterPackage()`, to update the package attributes, such as updating the total distribution reward tokens, and updating the number per second of the token distribution. - function `endPackage()`, to end the package. - function `claimAllRewardsForUser()`, to claim all rewards for the user. - function `claimAllRewardsForUsers()`, to claim all rewards for the users. Any compromise to the `_admin` account may allow the hacker to take advantage of this authority, allowing them to set the package, withdraw all staking and reward tokens from the contract, claim all user rewards, update the total distribution reward tokens, and update the number per second of the token distribution. In the contract `LucroStaking` the role `_owner` has authority over the functions shown in the list below. - function `changeOwner()`, to change the owner. - function `addAdmin()`, to add an admin. The admin possesses the privilege to add or alter packages. - function `removeAdmin()`, to remove an admin. The admin possesses the privilege to add or alter packages. - function `setMaxStakingPerBatch()`, the owner of the contract possessed the privilege to set the max staking amount per batch. - function `setSafeMode()`, to change the safe mode, specifically for protecting users from accidents. - function `setSmallFeeToBoostTotalExcluded()`, the owner of the contract possessed the privilege to set the small fee amount of distribution. - function `setSlippage()`, the owner of the contract possessed the privilege to set the slippage tolerance of swapping tokens when compounding rewards. - function `setExitFee()`, to set the exit fee percentage. - function `setEntryFee()`, to set the entry fee percentage. - function `setFeeRecipient()`, to set the fee recipient address. - function `setDEX()`, to set the DEX address. - function `setSwapPath()`, to set swap paths. - function `setStartIndex()`, to set the start index for package looping. - function `setPause()`, to pause the contact, staking, unstaking, claiming rewards, and compounding rewards. Any compromise to the `_owner` account could potentially enable a hacker to exploit this authority, In the contract `Ownable` the role `_owner` has authority over the functions shown in the diagram below.  Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and transfer the ownership. **The `alterPackage` function is exclusively controlled by the `admin` role, which is responsible for updating crucial state variables like `totalToDistribute`, and `timePeriod`. These variables are pivotal to the project's integrity and impact the number per second of the token distribution and the total distribution of reward tokens. Unauthorized modifications could severely impact certain functionalities, potentially eroding user trust.**

In the `EverGrowStaking.sol` contract, - the role `_owner` has authority over the following functions: - function `addAdmin()`, to add an admin. - function `removeAdmin()`, to remove an admin. - function `setMaxStakingPerBatch()`, to set the max staking amount per batch. - function `setSmallFeeToBoostTotalExcluded()`, to set the small fee amount of distribution. - function `setSlippage()`, to set the slippage tolerance of swapping tokens when compounding rewards. - function `setExitFee()`, to set the exit fee percentage. - function `setEntryFee()`, to set the entry fee percentage. - function `setFeeRecipient()`, to set the fee recipient address. - function `setDEX()`, to set the DEX address. - function `setSwapPath()`, to set swap paths. - function `setStartIndex()`, to set the start index for package looping. - function `setPause()`, to pause the contact, staking, unstaking, claiming rewards, and compounding rewards. - the role `admin` has authority over the following functions: - function `setSafeMode()`, to change the safe mode. - function `addPackage()`, to create a package, transfer the rewards token to the contract, and set the number per second of token distribution. - function `alterPackage()`, to update the package attributes. - function `endPackage()`, to end the package. - function `claimAllRewardsForUser()`, to claim all rewards for the user. - function `claimAllRewardsForUsers()`, to claim all rewards for the users. In the `Ownable` contract, the `owner` role has authority over the following function: - function `changeOwner`, to change the owner. Any compromise of the privileged accounts could potentially enable a hacker to exploit their authority, allowing them to change the fee address, update the fee rate to collect fees, end reward packages to reclaim reward tokens, and ultimately disrupt the project's normal functionalities. **The `alterPackage` function is exclusively controlled by the `admin` role, which is responsible for updating crucial state variables like `totalToDistribute`, and `timePeriod`. These variables are pivotal to the project's integrity and impact the number per second of the token distribution and the total distribution of reward tokens. Unauthorized modifications could severely impact certain functionalities, potentially eroding user trust.**

The lack of restrictions on the `stake` function permits users to stake their tokens even after all packages have concluded. As a result, users may face losses since there are no rewards to distribute, and entry and exit fees will be charged when staking or unstaking their tokens. We would like to confirm with the team whether this is aligned with original design.

The lack of restrictions on the `stake` function permits users to stake their tokens even after all packages have concluded. As a result, users may face losses since there are no rewards to distribute, and entry and exit fees will be charged when staking or unstaking their tokens. We would like to confirm with the team whether this is aligned with original design.