Bridge security record

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.  In the contract `SmartChefFactory` 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.  In the contract `SmartChefInitializable` the role `SMART_CHEF_FACTORY` has authority over the functions shown in the diagram below. Any compromise to the `SMART_CHEF_FACTORY` account may allow the hacker to take advantage of this authority.  In the contract `SmartChefInitializable` 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. 

The contract is serving as the underlying entity to interact with one or more third party protocols. The scope of the audit treats third party entities as black boxes and assume their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of third parties can possibly create severe impacts, such as increasing fees of third parties, migrating to new LP pools, etc. ```solidity=870 IBEP20 public rewardToken; ``` - The contract `SmartChefInitializable` interacts with third party contract with `IBEP20` interface via `rewardToken`. --- ```solidity=873 IBEP20 public stakedToken; ``` - The contract `SmartChefInitializable` interacts with third party contract with `IBEP20` interface via `stakedToken`. --- ```solidity=1031 function recoverWrongTokens(address _tokenAddress, uint256 _tokenAmount) external onlyOwner { ``` - The function `SmartChefInitializable.recoverWrongTokens` interacts with third party contract with `IBEP20` interface via `_tokenAddress`.

For ERC20 token transfer, it is more safe to use SafeERC20 library than standard ERC20 functions. See https://github.com/OpenZeppelin/openzeppelin-contracts/blob/v4.4.2/contracts/token/ERC20/utils/SafeERC20.sol

For Solidity version 0.8.x, native math operations are already safe and cheaper. There is no need to use SafeMath library.

After [EIP-1884](https://eips.ethereum.org/EIPS/eip-1884) was included in the Istanbul hard fork, it is not recommended to use `.transfer()` or `.send()` for transferring ether as these functions have a hard-coded value for gas costs making them obsolete as they are forwarding a fixed amount of gas, specifically `2300`. This can cause issues in case the linked statements are meant to be able to transfer funds to other contracts instead of EOAs.