PancakeSwap Audit

Whenever new SYRUP tokens are minted, new delegates are moved from the zero address to the recipient of the minting process. However, whenever tokens are burned, new delegates are once again moved from the zero address to the recipient whereas delegates should be moved on the opposite way.

The `transfer` and `transferFrom` functions of the YAM project transfer delegates as well via overridence. The PancakeSwap implementation does not, leading to an inconsistency in the delegates of each `address`.

The first linked `if` block pushes a new `address` to the `addressList` array in the case the `userInfo` mapping lookup yields `0` on the `amount` member. This case is possible even after the user has already been added to the array, either by invoking `emergencyWithdraw` or withdrawing the full amount held by the user.

The linked statement will only yield a different output stored to `totalAllocPoint` only if the condition of L146 yields true.

The function `updateMultiplier` can alter the `BONUS_MULTIPLIER` variable and consequently the output of `getMultiplier` which is directly utilized for the minting of new cake tokens.

The linked comment statement contains a typo in its body, namely `poitns`.

The `SousChef` contract tracks a reward schedule based on the deposited SYRUP tokens, however, the variables of the `UserInfo` struct are never actually utilized to provide any reward.

The `emergencyWithdraw` function is meant to "reset" a user's state and withdraw his deposited tokens. In this case, the `rewardPending` variable of the `user` struct is not zeroed out.