PEPEAICEO security record

Tokens are sent to the contract deployer when deploying the contract, and according to the whitepaper available on the official website (https://whitepaper.pepeaiceo.com/tokenomics), the token allocation plan is as follows: `Burn: 50%` `Presale: 25%` `Liquidity: 14.24%` `CEX & Marketing: 10.75%` While we have confirmed that the `Burn: 50%` distribution aligns with the plan, we kindly request the team to provide us with the precise transaction hashes for the other distribution plans. This will enable us to verify if the token allocation is in accordance with the outlined plan.

```solidity=698 function internalSwap(uint256 contractTokenBalance) internal inSwapFlag { address[] memory path = new address[](2); path[0] = address(this); path[1] = swapRouter.WETH(); if (_allowances[address(this)][address(swapRouter)] != type(uint256).max) { _allowances[address(this)][address(swapRouter)] = type(uint256).max; } try swapRouter.swapExactTokensForETHSupportingFeeOnTransferTokens( contractTokenBalance, 0, path, address(this), block.timestamp ) {} catch { return; } bool success; if(address(this).balance > 0) {(success,) = marketingAddress.call{value: address(this).balance, gas: 35000}("");} } ``` The `internalSwap()` function calls the `uniswapV2Router.swapExactTokensForETHSupportingFeeOnTransferTokens()` function to swap the `PEPEAICEO` tokens to BNB and send the BNB to the `marketingAddress` address. As a result, over time the `marketingAddress` address will accumulate a significant portion of BNB. If the `marketingAddress` is an EOA (Externally Owned Account), the mishandling of its private key can have devastating consequences for the project as a whole. For the common deflationary token, the entire tokenomic requires certain liquidity to support. However, in the current implementation, the swapped BNB is transferred to `marketingAddress` and is not being used for adding liquidity. Therefore, the entire tokenomic may crash due to lacking enough liquidity in the BNB-PEPEAICEO pool.