Empire security record

The variables `fee`, `buyFee`, and `sellFee` do not have reasonable boundaries, so they can be given arbitrary values.

Function state mutability should be restricted to `view` instead of `pure` for the reason that `_name`, `_symbol`, `_tTotal`, and `_decimals` are all state variables.

There are several typos in the code and comments. 1. In the following code snippet, `tokensIntoLiqudity` should be `tokensIntoLiquidity`. ```solidity= event LogSwapAndLiquify( uint256 tokensSwapped, uint256 ethReceived, uint256 tokensIntoLiqudity ); ``` 2. `recieve` should be `receive` in the line of comment `//to recieve ETH from uniswapV2Router when swapping.

The contract has unlocked compiler version. An unlocked compiler version in the source code of the contract permits the user to compile it at or above a particular version. This, in turn, leads to differences in the generated bytecode between compilations due to different compiler versions. This can lead to an ambiguity when debugging as compiler specific bugs may occur in the codebase that would be hard to identify over a span of multiple compiler versions rather than a specific one.

```solidity=150 event LogSetBurnWallet(address indexed setter, address burnWallet); ``` - `LogSetBurnWallet` is declared in `EmpireToken` but never emitted.

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.