The first meme coin in the history, Doge was launched in 2013. 8 years later, the Red Team is launching Red Doge, the Doppelgänger of Doge. RedDoge will be a utility token as we are building an ecosystem that encompasses gaming and NFTs.
Unable to find manual contract audit (e.g. Certik, PeckShield, Solidity...)
RedDoge.sendETHToFee(uint256) (#392-395) sends eth to arbitrary user
Dangerous calls:
- _FeeAddress.transfer(amount.div(2)) (#393)
- _marketingWalletAddress.transfer(amount.div(2)) (#394)
Ensure that an arbitrary user cannot withdraw unauthorized funds.
Additional information: link
Reentrancy in RedDoge.openTrading() (#397-422):
External calls:
- uniswapV2Pair = IUniswapV2Factory(_uniswapV2Router.factory()).createPair(address(this),_uniswapV2Router.WETH()) (#404-405)
- uniswapV2Router.addLiquidityETH{value: address(this).balance}(address(this),balanceOf(address(this)),0,0,owner(),block.timestamp) (#406-413)
External calls sending eth:
- uniswapV2Router.addLiquidityETH{value: address(this).balance}(address(this),balanceOf(address(this)),0,0,owner(),block.timestamp) (#406-413)
State variables written after the call(s):
- tradingOpen = true (#417)
Apply the check-effects-interactions pattern.
Additional information: link
Combination 1: Reentrancy vulnerabilities + Functions that send Ether to arbitraty destination. Usual for scams. May be justified by some complex mechanics (e.g. rebase, reflections). DYOR & manual audit are advised.
RedDoge.openTrading() (#397-422) ignores return value by IERC20(uniswapV2Pair).approve(address(uniswapV2Router),type()(uint256).max) (#418-421)
Ensure that all the return values of the function calls are used.
Additional information: link
RedDoge._approve(address,address,uint256).owner (#317) shadows:
- Ownable.owner() (#115-117) (function)
Rename the local variables that shadow another component.
Additional information: link
RedDoge.constructor(address,address).marketingWalletAddress (#208) lacks a zero-check on :
- _marketingWalletAddress = marketingWalletAddress (#211)
Check that the address is not zero.
Additional information: link
Reentrancy in RedDoge.transferFrom(address,address,uint256) (#269-284):
External calls:
- _transfer(sender,recipient,amount) (#274)
- uniswapV2Router.swapExactTokensForETHSupportingFeeOnTransferTokens(tokenAmount,0,path,address(this),block.timestamp) (#383-389)
External calls sending eth:
- _transfer(sender,recipient,amount) (#274)
- _FeeAddress.transfer(amount.div(2)) (#393)
- _marketingWalletAddress.transfer(amount.div(2)) (#394)
State variables written after the call(s):
- _approve(sender,_msgSender(),_allowances[sender][_msgSender()].sub(amount,ERC20: transfer amount exceeds allowance)) (#275-282)
- _allowances[owner][spender] = amount (#323)
Apply the check-effects-interactions pattern.
Additional information: link
Reentrancy in RedDoge.transferFrom(address,address,uint256) (#269-284):
External calls:
- _transfer(sender,recipient,amount) (#274)
- uniswapV2Router.swapExactTokensForETHSupportingFeeOnTransferTokens(tokenAmount,0,path,address(this),block.timestamp) (#383-389)
External calls sending eth:
- _transfer(sender,recipient,amount) (#274)
- _FeeAddress.transfer(amount.div(2)) (#393)
- _marketingWalletAddress.transfer(amount.div(2)) (#394)
Event emitted after the call(s):
- Approval(owner,spender,amount) (#324)
- _approve(sender,_msgSender(),_allowances[sender][_msgSender()].sub(amount,ERC20: transfer amount exceeds allowance)) (#275-282)
Apply the check-effects-interactions pattern.
Additional information: link
RedDoge._transfer(address,address,uint256) (#327-376) uses timestamp for comparisons
Dangerous comparisons:
- require(bool)(cooldown[to] < block.timestamp) (#347)
Avoid relying on block.timestamp.
Additional information: link
RedDoge._previousteamFee (#189) is set pre-construction with a non-constant function or state variable:
- _teamFee
Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.
Additional information: link
solc-0.8.6 is not recommended for deployment
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
Variable RedDoge._FeeAddress (#190) is not in mixedCase
Follow the Solidity naming convention.
Additional information: link
Reentrancy in RedDoge.transferFrom(address,address,uint256) (#269-284):
External calls:
- _transfer(sender,recipient,amount) (#274)
- _FeeAddress.transfer(amount.div(2)) (#393)
- _marketingWalletAddress.transfer(amount.div(2)) (#394)
State variables written after the call(s):
- _approve(sender,_msgSender(),_allowances[sender][_msgSender()].sub(amount,ERC20: transfer amount exceeds allowance)) (#275-282)
- _allowances[owner][spender] = amount (#323)
Event emitted after the call(s):
- Approval(owner,spender,amount) (#324)
- _approve(sender,_msgSender(),_allowances[sender][_msgSender()].sub(amount,ERC20: transfer amount exceeds allowance)) (#275-282)
Apply the check-effects-interactions pattern.
Additional information: link
Variable RedDoge._transferStandard(address,address,uint256).rTransferAmount (#452) is too similar to RedDoge._getValues(uint256).tTransferAmount (#502)
Prevent variables from having similar names.
Additional information: link
RedDoge.slitherConstructorConstantVariables() (#166-575) uses literals with too many digits:
- DEAD_ADDRESS = 0x000000000000000000000000000000000000dEaD (#179-180)
Use: Ether suffix, Time suffix, or The scientific notation
Additional information: link
RedDoge._tOwned (#169) is never used in RedDoge (#166-575)
Remove unused state variables.
Additional information: link
Ownable._previousOwner (#103) should be constant
Add the constant attributes to state variables that never change.
Additional information: link
delBot(address) should be declared external:
- RedDoge.delBot(address) (#430-432)
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.
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
Token was delisted (assigned to inactive / untracked listing) from 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 find audit link on the website
Unable to find whitepaper link on the website
Unable to find token on CoinHunt
Additional information: link
Young tokens have high risks of scam / price dump / death
Young tokens have high risks of scam / price dump / death
Token has no active CoinMarketCap listing / rank
Young tokens have high risks of price dump / death
Token has relatively low CoinGecko rank
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