CAT Musk Coin
Smart Contract Audit Report
CAT Musk Coin is a new BEP-20 token on the Binance Smart Chain that pays out static rewards to holders.
For this audit, we reviewed the project team's CATMuskCoin contract at 0x67680Dcb3248fD5ACd51780891567F96d18395C3 on the Binance Smart Chain Mainnet.
Please ensure trust in the team prior to investing as they have substantial control in the ecosystem.
Date: March 25th, 2022.
Finding #1 - CATMuskCoin - LowDescription: The owner can use the lock() function to temporarily set ownership to address(0). Ownership is restored after the duration of time determined by the owner has passed and they use the unlock() function.
Risk/Impact: The unlock function has the potential to be used after ownership has been set to address(0), which will restore ownership to the original owner that initially created the ownership lock. This can be used in a nefarious way by the project team to restore ownership and change fee structures.
Recommendation: We recommend that the unlock function be modified to set the previous owner variable equal to address(0) at the end of the unlock function to prevent it from being used more than once per lock.
Resolution: The team has not yet addressed this issue.
Finding #2 - CATMuskCoin - InformationalDescription: Several functions are declared public, but are never called internally.Recommendation: These functions should be declared external for additional gas savings on each call.
name, symbol, decimals, totalSupply, transfer, allowance, approve, transferFrom, increaseAllowance, decreaseAllowance, isExcludedFromReward, totalFees, minimumTokensBeforeSwapAmount, buyBackSellLimitAmount, deliver, reflectionFromToken, excludeFromReward, isExcludedFromFee, excludeFromFee, includeInFee, GetBuyBackTimeInterval, GetSwapMinutes, setBuyBackEnabled, setAutoBuyBackEnabled, changeRouterVersion, transferForeignToken
Finding #3 - CATMuskCoin - InformationalDescription: Several state variables can never be modified, but are not declared constant.Recommendation: These state variables should be declared constant for additional gas savings on each call.
_decimals, isEnabledBuyBackAndBurn, _name, _symbol, _tTotal, deadAddress
Finding #4 - CATMuskCoin - InformationalDescription: The
_isEnabledBuyBackAndBurnstate variable, and
SwapAndLiquifyevents are not used in the contract.
Recommendation: These should all be removed or utilized in a way that fits the project team's intended functionality.
Finding #5 - CATMuskCoin - InformationalDescription: Although the SafeMath library is utilized, the contract is deployed with Solidity v0.8.4 which has built-in overflow checks.
Recommendation: SafeMath could be safely removed to reduce contract size and deployment costs.
- The total supply of the token is set to 100 quadrillion $CATM [100,000,000,000,000,000].
- No mint or burn functions exist, though the circulating supply can be decreased by sending tokens to the 0x..dead address.
- At the time of writing this report, there are 500 total token holders. The token allocation is as follows:
- 43.67% of the total supply has been sent to the 0x..dead address.
- 9.01% of the total supply belongs is stored in a PinkSale token locking contract and will unlock on April 20th, 2022.
- 8.42% of the total supply is in Pancakeswap liquidity.
- Of that liquidity, 99% of the LP tokens are locked in a UniCrypt token locking contract for 50 years.
- The next five wallet addresses own a cumulative 19.21% of the total supply.
- The contract enforces a maximum transaction amount (determined by the owner) which imposes a limit to the number of tokens that can be transferred during a single transaction.
- When users sell tokens via PancakeSwap, the transaction details are stored in the "SellHistory" array which will be used to determine the average sell amount in the calculations for the buyback functionality.
- There is a Tax fee and a Liquidity fee on all transfers where neither the sender nor the recipient is excluded from fees. A separate fee structure can be set by the team to apply different fee percentages depending on whether the user is buying or selling during the transfer.
- The owner can manually add accounts to a special fee list; these accounts will be charged separate fee percentages (determined by the owner) on all transfers.
- The tokens collected through the Tax fee are removed from the circulating supply; This serves as a frictionless fee redistribution which automatically benefits all token holders at the time of each transaction.
- The tokens collected through the Liquidity fee are swapped for BNB once the contract token balance reaches the threshold number of tokens. A percentage (determined by the owner) of the received BNB is sent to the team's Marketing wallet.
- On each transfer that occurs while the minimum threshold (determined by the owner) is met, the protocol will determine an amount of BNB to apply towards buying $CATM tokens that will subsequently be sent to the 0x..dead address.
- The team has some control regarding the amount of BNB that is used during buybacks as they can update the variables that are used when determining the minimum and maximum buyback ranges.
- The amount of BNB is calculated based on the average BNB value per token sale since a Buyback has previously occurred. An amount between the minimum and maximum buyback ranges is Psuedo-randomly chosen.
- As the contract is deployed with Solidity v0.8.4, it is protected from overflows/underflows.
- The contract complies with the BEP-20 token standard.
- The owner can modify the Tax fee and Liquidity fee for both fee structures to any percentages at any time.
- The owner can exclude and include accounts from transfer fees and reward distribution.
- The owner can assign different fee percentages that will apply to specified accounts on all token transfers at any time.
- The owner can update the maximum transaction amount to any value at any time.
- The owner can enable/disable the automatic token swapping functionality at any time.
- The owner can update the threshold number of tokens needed to trigger the token swapping functionality to any value at any time.
- The owner can set the percentage of BNB that is transferred to the Marketing wallet to any value at any time.
- The owner can update the team's Marketing wallet to any address at any time.
- The owner can withdraw all of the BNB or tokens (besides $CATM) from the contract address at any time.
- The owner can enable/disable the Buyback mechanism at any time.
- The owner can set the amount of time that must pass between Buybacks to any value at any time.
- The owner can set the amount of time that sell transactions histories are stored for to any value at any time.
- The owner can set the minimum and maximum Buyback range values to any values at any time.
- The owner can set the Buyback divisor to any value at any time.
- The owner can set the Buyback sell limit to any value at any time.
- The owner can utilize the PrepareForPresale() function to set fees to 0 and set the max transaction amount to 100% of the total token supply.
- The owner can utilize the afterPresale() function to restore the transfer fees and set the maximum transaction amount to 0.3% of the total supply.
- The owner can update the Pancakeswap Router address at any time.
|Arbitrary Jump/Storage Write||N/A||PASS|
|Centralization of Control||WARNING|
|Delegate Call to Untrusted Contract||N/A||PASS|
|Dependence on Predictable Variables||N/A||PASS|
|Front Running||The Buyback system may be susceptible to front running however, this is unlikely to occur as the contract is deployed on Binance. The team must monitor and if suspicious activity is detected, the team should disable the Buyback functionality.||WARNING|
|Improper Authorization Scheme||N/A||PASS|
|Outdated Compiler Version||N/A||PASS|
|Unused Code||The ||PASS|
|Overall Contract Safety||PASS|
($) = payable function # = non-constant function Int = Internal Ext = External Pub = Public + Context - [Int] _msgSender - [Int] _msgData + [Int] IERC20 - [Ext] totalSupply - [Ext] balanceOf - [Ext] transfer # - [Ext] allowance - [Ext] approve # - [Ext] transferFrom # + [Lib] SafeMath - [Int] add - [Int] sub - [Int] sub - [Int] mul - [Int] div - [Int] div - [Int] mod - [Int] mod + [Lib] Address - [Int] isContract - [Int] sendValue # - [Int] functionCall # - [Int] functionCall # - [Int] functionCallWithValue # - [Int] functionCallWithValue # - [Prv] _functionCallWithValue # + Ownable (Context) - [Pub]
# - [Pub] owner - [Pub] renounceOwnership # - modifiers: onlyOwner - [Pub] transferOwnership # - modifiers: onlyOwner - [Pub] getUnlockTime - [Pub] getTime - [Pub] lock # - modifiers: onlyOwner - [Pub] unlock # + [Int] IUniswapV2Factory - [Ext] feeTo - [Ext] feeToSetter - [Ext] getPair - [Ext] allPairs - [Ext] allPairsLength - [Ext] createPair # - [Ext] setFeeTo # - [Ext] setFeeToSetter # + [Int] IUniswapV2Pair - [Ext] name - [Ext] symbol - [Ext] decimals - [Ext] totalSupply - [Ext] balanceOf - [Ext] allowance - [Ext] approve # - [Ext] transfer # - [Ext] transferFrom # - [Ext] DOMAIN_SEPARATOR - [Ext] PERMIT_TYPEHASH - [Ext] nonces - [Ext] permit # - [Ext] MINIMUM_LIQUIDITY - [Ext] factory - [Ext] token0 - [Ext] token1 - [Ext] getReserves - [Ext] price0CumulativeLast - [Ext] price1CumulativeLast - [Ext] kLast - [Ext] burn # - [Ext] swap # - [Ext] skim # - [Ext] sync # - [Ext] initialize # + [Int] IUniswapV2Router01 - [Ext] factory - [Ext] WETH - [Ext] addLiquidity # - [Ext] addLiquidityETH ($) - [Ext] removeLiquidity # - [Ext] removeLiquidityETH # - [Ext] removeLiquidityWithPermit # - [Ext] removeLiquidityETHWithPermit # - [Ext] swapExactTokensForTokens # - [Ext] swapTokensForExactTokens # - [Ext] swapExactETHForTokens ($) - [Ext] swapTokensForExactETH # - [Ext] swapExactTokensForETH # - [Ext] swapETHForExactTokens ($) - [Ext] quote - [Ext] getAmountOut - [Ext] getAmountIn - [Ext] getAmountsOut - [Ext] getAmountsIn + [Int] IUniswapV2Router02 (IUniswapV2Router01) - [Ext] removeLiquidityETHSupportingFeeOnTransferTokens # - [Ext] removeLiquidityETHWithPermitSupportingFeeOnTransferTokens # - [Ext] swapExactTokensForTokensSupportingFeeOnTransferTokens # - [Ext] swapExactETHForTokensSupportingFeeOnTransferTokens ($) - [Ext] swapExactTokensForETHSupportingFeeOnTransferTokens # + CATMuskCoin (Context, IERC20, Ownable) - [Pub] # - [Pub] name - [Pub] symbol - [Pub] decimals - [Pub] totalSupply - [Pub] balanceOf - [Pub] transfer # - [Pub] allowance - [Pub] approve # - [Pub] transferFrom # - [Pub] increaseAllowance # - [Pub] decreaseAllowance # - [Pub] isExcludedFromReward - [Pub] totalFees - [Pub] minimumTokensBeforeSwapAmount - [Pub] buyBackSellLimitAmount - [Pub] deliver # - [Pub] reflectionFromToken - [Pub] tokenFromReflection - [Pub] excludeFromReward # - modifiers: onlyOwner - [Ext] includeInReward # - modifiers: onlyOwner - [Prv] _approve # - [Prv] _transfer # - [Prv] swapTokens # - modifiers: lockTheSwap - [Prv] buyBackTokens # - modifiers: lockTheSwap - [Prv] swapTokensForEth # - [Prv] swapETHForTokens # - [Prv] addLiquidity # - [Prv] _tokenTransfer # - [Prv] _transferStandard # - [Prv] _transferToExcluded # - [Prv] _transferFromExcluded # - [Prv] _transferBothExcluded # - [Prv] _reflectFee # - [Prv] _getValues - [Prv] _getTValues - [Prv] _getRValues - [Prv] _getRate - [Prv] _getCurrentSupply - [Prv] _takeLiquidity # - [Prv] calculateTaxFee - [Prv] calculateLiquidityFee - [Prv] removeAllFee # - [Prv] restoreAllFee # - [Pub] isExcludedFromFee - [Pub] excludeFromFee # - modifiers: onlyOwner - [Pub] includeInFee # - modifiers: onlyOwner - [Prv] _getSellBnBAmount - [Prv] _removeOldSellHistories # - [Ext] SetBuyBackMaxTimeForHistories # - modifiers: onlyOwner - [Ext] SetBuyBackDivisor # - modifiers: onlyOwner - [Pub] GetBuyBackTimeInterval - [Ext] SetBuyBackTimeInterval # - modifiers: onlyOwner - [Ext] SetBuyBackRangeRate # - modifiers: onlyOwner - [Pub] GetSwapMinutes - [Ext] SetSwapMinutes # - modifiers: onlyOwner - [Ext] setTaxFeePercent # - modifiers: onlyOwner - [Ext] setBuyFee # - modifiers: onlyOwner - [Ext] setSellFee # - modifiers: onlyOwner - [Ext] setLiquidityFeePercent # - modifiers: onlyOwner - [Ext] setBuyBackSellLimit # - modifiers: onlyOwner - [Ext] setMaxTxAmount # - modifiers: onlyOwner - [Ext] setMarketingDivisor # - modifiers: onlyOwner - [Ext] setNumTokensSellToAddToBuyBack # - modifiers: onlyOwner - [Ext] setMarketingAddress # - modifiers: onlyOwner - [Pub] setSwapAndLiquifyEnabled # - modifiers: onlyOwner - [Pub] setBuyBackEnabled # - modifiers: onlyOwner - [Pub] setAutoBuyBackEnabled # - modifiers: onlyOwner - [Ext] prepareForPreSale # - modifiers: onlyOwner - [Ext] afterPreSale # - modifiers: onlyOwner - [Prv] transferToAddressETH # - [Pub] changeRouterVersion # - modifiers: onlyOwner - [Ext] ($) - [Pub] transferForeignToken # - modifiers: onlyOwner - [Ext] Sweep # - modifiers: onlyOwner - [Ext] setAddressFee # - modifiers: onlyOwner - [Ext] setBuyAddressFee # - modifiers: onlyOwner - [Ext] setSellAddressFee # - modifiers: onlyOwner
About Solidity Finance
Solidity Finance was founded in 2020 and quickly grew to have one of the most experienced and well-equipped smart contract auditing teams in the industry. Our team has conducted 1000+ solidity smart contract audits covering all major project types and protocols, securing a total of over $50 billion U.S. dollars in on-chain value across 1500 projects!.
Our firm is well-reputed in the community and is trusted as a top smart contract auditing company for the review of solidity code, no matter how complex. Our team of experienced solidity smart contract auditors performs audits for tokens, NFTs, crowdsales, marketplaces, gambling games, financial protocols, and more!
Contact us today to get a free quote for a smart contract audit of your project!
What is a Solidity Audit?
Typically, a smart contract audit is a comprehensive review process designed to discover logical errors, security vulnerabilities, and optimization opportunities within code. A Solidity Audit takes this a step further by verifying economic logic to ensure the stability of smart contracts and highlighting privileged functionality to create a report that is easy to understand for developers and community members alike.
How Do I Interpret the Findings?
Each of our Findings will be labeled with a Severity level. We always recommend the team resolve High, Medium, and Low severity findings prior to deploying the code to the mainnet. Here is a breakdown on what each Severity level means for the project:
- High severity indicates that the issue puts a large number of users' funds at risk and has a high probability of exploitation, or the smart contract contains serious logical issues which can prevent the code from operating as intended.
- Medium severity issues are those which place at least some users' funds at risk and has a medium to high probability of exploitation.
- Low severity issues have a relatively minor risk association; these issues have a low probability of occurring or may have a minimal impact.
- Informational issues pose no immediate risk, but inform the project team of opportunities for gas optimizations and following smart contract security best practices.