Description: The _beforeTokenTransfer() function enforces a restriction that limits each address, including those designated as approved DEX addresses, to participate in only one transfer per block.

if (from != address(0)) {
    require(_lastTradeBlock[from] != block.number, "Cannot trade twice in one block");
    _lastTradeBlock[from] = block.number;
}


if (to != address(0)) {
    require(_lastTradeBlock[to] != block.number, "Cannot trade twice in one block");
    _lastTradeBlock[to] = block.number;
}

Risk/Impact: This restriction can impede trading on DEXes where high-frequency trading is typical, resulting in failed buy and sell transactions.

Recommendation: The block-restriction logic in the _beforeTokenTransfer() function should be modified to exclude addresses that have been added as a _dexAddresses.

Resolution: The team has not yet addressed this issue.

Description: In the _beforeTokenTransfer() function, the _maxSellToken value does not enforce a limit on the number of tokens that can be sold in a single transaction but rather prevents any non-buy transfer from occurring if the sender's balance before the transfer occurs exceeds its value.

function _beforeTokenTransfer(address from, address to, uint256 amount) internal virtual {
...

    if (!_dexAddresses[from]){
        require(_balances[from] <= _maxSellToken, "trasaction failed.");
    }

Risk/Impact: The _maxSellToken restriction is potentially misleading and may not operate as the team intended as it does not act as a maximum sell limit. Non-buy transactions may fail if the sender's balance exceeds the _maxSellToken value.

Recommendation: The maximum sell limit logic in the _beforeTokenTransfer() function should be modified to ensure that amount does not exceed _maxSellToken when transferring tokens to an approved DEX to properly enforce a maximum sell limit.

Resolution: The team has not yet addressed this issue.

Description: In the _beforeTokenTransfer() function, the _lastTradeBlock for the recipient of a transfer is updated to the current block number. The recipient is then prohibited from transferring tokens within the same block.

Risk/Impact: A malicious user could exploit this feature by repeatedly transferring a small amount of tokens to the same recipient each block. This repetitive action could result in a denial-of-service, effectively preventing the recipient from selling their tokens, as they would be unable to initiate a transfer within the same block.

Recommendation: The _lastTradeBlock logic should only be updated for the tx.origin of the transaction. Alternatively, the team could increase the contract's minimum transfer amount to a value that would discourage users from engaging in such activity.

Resolution: The team has not yet addressed this issue.

Description: The following two conditions in the _beforeTokenTransfer() function are redundant as the _transfer() function, which triggers the _beforeTokenTransfer() function, already enforces that the sender and the recipient cannot be address(0).

if (from != address(0)) {
...
if (to != address(0)) {

Recommendation: The above if-statements could be removed from the _beforeTokenTransfer() function for additional gas savings on each call.

Description: The _tokenTotalSupply state variable is redundant as it serves as a maximum supply cap but is set equal to the total supply, and additionally, no minting functionality is permitted beyond deployment.

Recommendation: The _tokenTotalSupply state variable should either be removed to reduce contract size and deployment costs or utilized in a way that fits the project team's intended functionality.

Description: The taxAddress and owner state variables are not used in the contract.

Recommendation: The taxAddress and owner state variables should either be removed to reduce contract size and deployment costs or utilized in a way that fits the project team's intended functionality.

• The owner can add any address to the transfer blacklist at any time.
• The owner can set the max sell token value to any value at any time.

• The _beforeTokenTransfer() function enforces a restriction that limits each address, including those designated as approved DEX addresses, to participate in only one transfer per block.
• In the _beforeTokenTransfer() function, the _maxSellToken value does not enforce a limit on the number of tokens that can be sold in a single transaction but rather prevents any non-buy transfer from occurring if the sender's balance before the transfer occurs exceeds its value.
• In the _beforeTokenTransfer() function, the _lastTradeBlock for the recipient of a transfer is updated to the current block number. The recipient is then prohibited from transferring tokens within the same block.