Empire v3

The **require** can be used to check for conditions and throw an exception if the condition is not met. It is better to provide a string message containing details about the error that will be passed back to the caller.

It is recommended to add the max transaction amount check as many other deflation tokens(e.g. Safemoon) do to prevent the big whale.

Potential sandwich attacks could happen if calling `uniswapV2Router.swapExactTokensForETHSupportingFeeOnTransferTokens` and `uniswapV2Router.addLiquidityETH` without setting restrictions on slippage. For example, when we want to make a transaction of swapping 100 A Token for 1 Eth, an attacker could raise the price of Eth by adding A Token into the pool before the transaction so we might only get 0.1 Eth. After the transaction, the attacker would be able to withdraw more than he deposited because the total value of the pool increases by 0.9 Eth.

Solidity version >=0.8.0 includes checked arithmetic operations and underflow/overflow by default, making SafeMath redundant.

The function `deliver` can be called by anyone. It accepts an uint256 number parameter `tAmount`. The function reduces the Empire token balance of the caller by `rAmount`, which is `tAmount` reduces the transaction fee. Then, the function adds `tAmount` to variable `_tFeeTotal`, which represents the contract's total transaction fee.

The contract is serving as the underlying entity to interact with third-party protocol, including: - `uniswapV2Router` The scope of the audit would treat those 3rd party entities as black boxes and assume their functional correctness. However, in the real world, 3rd parties may be compromised that led to assets being lost or stolen.

The return value of an external call is not stored in a local or state variable. ```solidity=809 uniswapV2Router.addLiquidityETH{value: ethAmount}( address(this), tokenAmount, 0, 0, liquidityWallet, block.timestamp ); ```