WWF Layer 2 AMM & NFTs on BSC
Unable to find manual contract audit (e.g. Certik, PeckShield, Solidity...)
WWEToken._writeCheckpoint(address,uint32,uint256,uint256) (#1535-1553) uses a dangerous strict equality:
- nCheckpoints > 0 && checkpoints[delegatee][nCheckpoints - 1].fromBlock == blockNumber (#1545)
Don't use strict equality to determine if an account has enough Ether or tokens.
Additional information: link
Contract locking ether found:
Contract WWEToken (#1159-1566) has payable functions:
- WWEToken.receive() (#1268)
But does not have a function to withdraw the ether
Remove the payable attribute or add a withdraw function.
Additional information: link
WWEToken._transfer(address,address,uint256) (#1227-1251) performs a multiplication on the result of a division:
-taxAmount = amount.mul(transferTaxRate).div(10000) (#1232)
-burnAmount = taxAmount.mul(burnRate).div(100) (#1233)
Consider ordering multiplication before division.
Additional information: link
BEP20._approve(address,address,uint256).owner (#902) shadows:
- Ownable.owner() (#63-65) (function)
Rename the local variables that shadow another component.
Additional information: link
WWEToken.delegateBySig(address,uint256,uint256,uint8,bytes32,bytes32) (#1401-1442) uses timestamp for comparisons
Dangerous comparisons:
- require(bool,string)(now <= expiry,WWE::delegateBySig: signature expired) (#1440)
Avoid relying on block.timestamp.
Additional information: link
WWEToken.getChainId() (#1560-1564) uses assembly
- INLINE ASM (#1562)
Do not use evm assembly.
Additional information: link
WWEToken.antiWhale(address,address,uint256) (#1191-1201) compares to a boolean constant:
-_excludedFromAntiWhale[sender] == false && _excludedFromAntiWhale[recipient] == false (#1194-1195)
Remove the equality to the boolean constant.
Additional information: link
Different versions of Solidity is used:
- Version used: ['0.6.12', '>=0.4.0', '>=0.5.0', '>=0.6.0<0.8.0', '>=0.6.2', '>=0.6.2<0.8.0']
- >=0.6.0<0.8.0 (#5)
- >=0.6.0<0.8.0 (#32)
- >=0.4.0 (#102)
- >=0.6.0<0.8.0 (#203)
- >=0.6.2<0.8.0 (#420)
- >=0.4.0 (#612)
- >=0.6.2 (#931)
- >=0.6.2 (#1029)
- >=0.5.0 (#1075)
- >=0.5.0 (#1130)
- 0.6.12 (#1152)
Use one Solidity version.
Additional information: link
WWEToken._transfer(address,address,uint256) (#1227-1251) is never used and should be removed
Remove unused functions.
Additional information: link
Pragma version>=0.5.0 (#1130) allows old versions
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
Low level call in Address.functionDelegateCall(address,bytes,string) (#580-586):
- (success,returndata) = target.delegatecall(data) (#584)
Avoid low-level calls. Check the call success. If the call is meant for a contract, check for code existence
Additional information: link
Variable WWEToken._delegates (#1343) is not in mixedCase
Follow the Solidity naming convention.
Additional information: link
Redundant expression "this (#23)" inContext (#17-26)
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 (#940) is too similar to IUniswapV2Router01.addLiquidity(address,address,uint256,uint256,uint256,uint256,address,uint256).amountBDesired (#941)
Prevent variables from having similar names.
Additional information: link
WWEToken.slitherConstructorConstantVariables() (#1159-1566) uses literals with too many digits:
- BURN_ADDRESS = 0x000000000000000000000000000000000000dEaD (#1167)
Use: Ether suffix, Time suffix, or The scientific notation
Additional information: link
transferOperator(address) should be declared external:
- WWEToken.transferOperator(address) (#1330-1334)
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.
BscScan page for the token does not contain additional info: website, socials, description, etc.
Additional information: link
Unable to find token on CoinGecko
Additional information: link
Unable to find token on CoinMarketCap
Additional information: link
Unable to find token/project description on the website or on BscScan, CoinMarketCap
Unable to find token contract audit
Unable to verify that token and website are owned by the same team (no listings + unable to find contract on website)
Unable to verify token contract address on the website
Unable to find audit link on the website
Unable to find whitepaper link on the website
Unable to find Telegram link on the website
Unable to find Twitter link on the website
Unable to find token on CoinHunt
Additional information: link
Unable to find code repository for the project
Young tokens have high risks of scam / price dump / death
Token has no active CoinGecko listing / rank
Token has no active CoinMarketCap listing / rank
Young tokens have high risks of price dump / death
Unable to find Telegram account
Twitter account link seems to be invalid
Unable to find Blog account (Reddit or Medium)
Unable to find Youtube account
Unable to find Discord account