KAI [CryptoKAI] Token

Unable to find manual contract audit (e.g. Certik, PeckShield, Solidity...)

Contract locking ether found:
Contract CryptoKAI (CryptoKAI.sol#9-119) has payable functions:
- CryptoKAI.receive() (CryptoKAI.sol#86)
But does not have a function to withdraw the ether
Remove the payable attribute or add a withdraw function.

Additional information: link

KaiERC20.constructor(string,string).symbol (KaiERC20.sol#25) shadows:
- ERC20.symbol() (ERC20.sol#72-74) (function)
Rename the local variables that shadow another component.

Additional information: link

CryptoKAI.antiBot(uint256) (CryptoKAI.sol#110-117) should emit an event for:
- antiBotAmount = amount (CryptoKAI.sol#114)
Emit an event for critical parameter changes.

Additional information: link

Reentrancy in CryptoKAI.constructor(string,string) (CryptoKAI.sol#23-36):
External calls:
- uniswapV2Pair = IUniswapV2Factory(_uniswapV2Router.factory()).createPair(address(this),_uniswapV2Router.WETH()) (CryptoKAI.sol#31-32)
State variables written after the call(s):
- _approve(address(this),address(uniswapV2Router),~ uint256(0)) (CryptoKAI.sol#35)
- _allowances[owner][spender] = amount (ERC20.sol#276)
- uniswapV2Router = _uniswapV2Router (CryptoKAI.sol#34)
Apply the check-effects-interactions pattern.

Additional information: link

Reentrancy in CryptoKAI.constructor(string,string) (CryptoKAI.sol#23-36):
External calls:
- uniswapV2Pair = IUniswapV2Factory(_uniswapV2Router.factory()).createPair(address(this),_uniswapV2Router.WETH()) (CryptoKAI.sol#31-32)
Event emitted after the call(s):
- Approval(owner,spender,amount) (ERC20.sol#277)
- _approve(address(this),address(uniswapV2Router),~ uint256(0)) (CryptoKAI.sol#35)
Apply the check-effects-interactions pattern.

Additional information: link

CryptoKAI._transfer(address,address,uint256) (CryptoKAI.sol#48-76) uses timestamp for comparisons
Dangerous comparisons:
- antiBotTime > block.timestamp && amount > antiBotAmount && bots[sender] (CryptoKAI.sol#54-56)
Avoid relying on block.timestamp.

Additional information: link

Different versions of Solidity is used:
- Version used: ['>=0.6.0<0.8.0', '^0.7.6']
- >=0.6.0<0.8.0 (Context.sol#3)
- ^0.7.6 (CryptoKAI.sol#2)
- >=0.6.0<0.8.0 (ERC20.sol#3)
- >=0.6.0<0.8.0 (IERC20.sol#3)
- ^0.7.6 (KaiERC20.sol#2)
- ^0.7.6 (ManagerInterface.sol#3)
- >=0.6.0<0.8.0 (Ownable.sol#3)
- >=0.6.0<0.8.0 (ReentrancyGuard.sol#3)
- >=0.6.0<0.8.0 (SafeMath.sol#3)
- ^0.7.6 (Uniswap.sol#2)
Use one Solidity version.

Additional information: link

SafeMath.trySub(uint256,uint256) (SafeMath.sol#35-38) is never used and should be removed
Remove unused functions.

Additional information: link

Pragma version>=0.6.0<0.8.0 (SafeMath.sol#3) is too complex
Deploy with any of the following Solidity versions: 0.5.16 - 0.5.17, 0.6.11 - 0.6.12, 0.7.5 - 0.7.6 Use a simple pragma version that allows any of these versions. Consider using the latest version of Solidity for testing.

Additional information: link

Function IUniswapV2Router01.WETH() (Uniswap.sol#143) is not in mixedCase
Follow the Solidity naming convention.

Additional information: link

Redundant expression "this (Context.sol#21)" inContext (Context.sol#15-25)
Remove redundant statements if they congest code but offer no value.

Additional information: link

Variable IUniswapV2Router01.addLiquidity(address,address,uint256,uint256,uint256,uint256,address,uint256).amountADesired (Uniswap.sol#148) is too similar to IUniswapV2Router01.addLiquidity(address,address,uint256,uint256,uint256,uint256,address,uint256).amountBDesired (Uniswap.sol#149)
Prevent variables from having similar names.

Additional information: link

KaiERC20.amountPlayToEarn (KaiERC20.sol#12) should be constant
Add the constant attributes to state variables that never change.

Additional information: link

transferOwnership(address) should be declared external:
- Ownable.transferOwnership(address) (Ownable.sol#63-67)
Use the external attribute for functions never called from the contract.

Additional information: link

Average PancakeSwap trading volume, liqudity, number of swaps are extremely low. Token seems to be dead.

Number of Binance Smart Chain (BSC) token holders is low.

Token is deployed only at one blockchain

Token has only one trading pair

Unable to find PancakeSwap trading pair to compute liquidity.

Unable to find PancakeSwap trading pair to compute volume.

Unable to find PancakeSwap trading pair to compute number of swaps.

Unable to find website, listings and other project-related information

Token has no active CoinGecko listing / rank

Token has no active CoinMarketCap listing / rank

Young tokens have high risks of price dump / death