Litedex audit 3

In the contract `LitedexFarmer` the role `_owner` has authority over the functions shown in the diagram below.  --- In the contract `LitedexStakePool.BEP20` the role `_owner` has authority over the functions shown in the diagram below.  In the contract `LitedexStakePool.Litedex` the role `_owner` has authority over the functions shown in the diagram below.  In the contract `LitedexStakePool.LitedexSP` the role `_owner` has authority over the functions shown in the diagram below.  --- In the contract `LitedexSmartStakeFactory.LitedexSmartStake` the role `SMART_STAKE_FACTORY` has authority over the functions shown in the diagram below.  In the contract `LitedexSmartStakeFactory.LitedexSmartStake` the role `_owner` has authority over the functions shown in the diagram below.  In the contract `LitedexSmartStakeFactory` the role `_owner` has authority over the functions shown in the diagram below.  --- In the contract `LitedexVault` the role `_owner` has authority over the functions shown in the diagram below.  In the contract `LitedexVault` the role `admin` has authority over the functions shown in the diagram below.  Any compromise to the privileged account may allow the hacker to take advantage of this authority and update the sensitive settings and execute sensitive functions of the project.

The LitedexFarmer contract operates as the main entry for interaction with staking users. The staking users deposit LP tokens into the Litedex pool and in return get a proportionate share of the pool’s rewards. Later on, the staking users can withdraw their assets from the pool. In this procedure, `deposit()` and `withdraw()` are involved in transferring users’ assets into (or out of) the Litedex protocol. When transferring standard ERC20 deflationary tokens, the input amount may not be equal to the received amount due to the charged (and burned) transaction fee. As a result, this may not meet the assumption behind these low-level asset-transferring routines and will bring unexpected balance inconsistencies.