Jerry Inu security record

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

In the traditional deflationary token the function `swapAndLiquify()` will use the token for liquidity fees to add liquidity. However, there is no liquidity fee in the Jerry Inu token, and there is no added liquidity operation in `swapAndLiquify()` as well. All fee tokens (`marketingFee`) will be swapped to the BNB and sent to the marketing wallet.

A sandwich attack may happen when an attacker observes a transaction swapping tokens or adding liquidity without setting restrictions on slippage or minimum output amount. The attacker can manipulate the exchange rate by frontrunning (executing before the target) a transaction to purchase one of the assets and make profits by backrunning (executing after the target) a transaction to sell the asset. The following functions are called without setting restrictions on slippage or minimum output amount, so transactions triggering these functions are vulnerable to sandwich attacks, especially when the input amount is large: ```solidity=500 router.swapExactTokensForETHSupportingFeeOnTransferTokens( tokenAmount, 0, // accept any amount of ETH path, address(this), block.timestamp ); ```

State variables that never change should be declared as `constant` to save gas. ```solidity=128 uint256 private _tTotal = 420 *10**15 * 10**_decimals; ``` - `_tTotal` should be declared `constant`. --- ```solidity=131 uint256 public swapTokensAtAmount = 1e14 * 10**_decimals; ``` - `swapTokensAtAmount` should be declared `constant`. --- ```solidity=133 address public deadWallet = 0x000000000000000000000000000000000000dEaD; ``` - `deadWallet` should be declared `constant`. --- ```solidity=134 address public marketingWallet = 0x6f7B7C560D748e264B61035eC97Da8D74a896c6d; ``` - `marketingWallet` should be declared `constant`.