Floppa

All **FLOP** tokens are sent to the contract deployer when deploying the contract. This is a potential centralization risk as the deployer can distribute **FLOP** tokens without the consensus of the community.

In the contract `BigFloppaToken` the role `_owner` has authority over the functions shown in the diagram and list below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and control the token transfers.  - `blacklist()`: Owner can blacklist addresses from transferring tokens. - `setRules()`: Owner can set configurations of the contract. In the contract `Ownable` the role `_owner` has authority over the functions shown in the diagram and list below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and transfer ownership to other addresses.  - `transferOwnership()`: Owner can transfer contract ownership. - `renounceOwnership()`: Owner can give up contract ownership.

The condition `super.balanceOf(to) + amount >= minHoldingAmount` in the `_beforeTokenTransfer` function enforces a minimum holding requirement for any address receiving tokens from the Uniswap pair. From the way this condition is written, it would require that the balance of tokens in the recipient's (`to`) address after the transfer is at least the `minHoldingAmount`. This means that a recipient must either already have enough tokens to meet the `minHoldingAmount` or the amount they are receiving should be enough to take their balance to the `minHoldingAmount` or above.

The following areas are missing checks on input parameters to ensure that the inputs are appropriate. ### blacklist() * `_isBlacklisting` - No checks that the value contained in `blacklists[_address]` is not equal to the value of `_isBlacklisting` before setting a new value to `blacklists[_address]` ### setRule() * `_minHoldingAmount` - No checks to ensure that `_minHoldingAmount` is less than `_maxHoldingAmount`