BabyBoomToken (BBT) security record

In the contract `BBT` the role `_owner` has authority over the following functions: - `mint()` allows function owner to mint BBT tokens when total supply is less than the max supply. - `stop()` and `start()` function allows the owner to pause/unpause the contract Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and mint tokens to arbitrary accounts.

All of the `Baby Boom` tokens are sent to the contract deployer on deployment. This is a centralization risk because the contract deployer can distribute tokens without obtaining the consensus of the community. Any compromise to these addresses may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.

As the function `setMaxSupply()` is set as `internal` and can only be called from the constructor function, the use of the `onlyOwner` modifier is redundant. ```solidity=34 function setMaxSupply(uint256 amount) internal onlyOwner { _maxSupply = amount; } ```

The linked variables assigned in the constructor can be declared as `immutable`. Immutable state variables can be assigned during contract creation but will remain constant throughout the lifetime of a deployed contract. A big advantage of immutable variables is that reading them is significantly cheaper than reading from regular state variables since they will not be stored in storage.