Kemonomimi

Smart Contract Audit Report

Audit Summary

Kemonomimi is a new BEP-20 token on the Binance Smart Chain that is an automatic liquidity providing protocol that pays out static rewards to holders.

For this audit, we reviewed the project team's Kemonomimi contract at 0x61d89991916309403688dd4C9b5f2494341a6CC1 on the Binance Smart Chain Mainnet.

Audit Findings

Please ensure trust in the team prior to investing as they have some control in the ecosystem.
Date: April 13th, 2022.

Finding #1 - Kemonomimi - Informational

Description: There are two instances in the _getTValues() function where multiplication is performed on the result of a division. Division can lead to integer truncation, therefore dividing and subsequently multiplying can cause results to lose precision and become less accurate.

function _getTValues {
...
uint256 tFee = tAmount.div(10 ** 2).mul(_taxFee);
uint256 tLiquidity = tAmount.div(10 ** 2).mul(_liquidityFee);
...
}

Recommendation: We recommend modifying these calculations to perform all multiplication before division.

---

Finding #2 - Kemonomimi - Informational

Description: Several state variables can never be modified, but are not declared constant.

_decimals, _name, _symbol, _maxTxAmount, _maxWalletToken

Recommendation: These state variables should be declared constant for additional gas savings on each call.

Contract Overview

• The total supply of the token is set to 1 quadrillion $MIMI [1,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 217 total token holders. The token allocation is as follows:
  • 30.84% of the total supply has been sent to the 0x..dead address.
  • 4.05% of the total supply is in Pancakeswap liquidity.
  • Of that liquidity, 99.96% of the LP tokens have been sent to the 0x..dead address.
  • The next five holders own a cumulative 10.16% of the total supply.
  
  
• The contract enforces a maximum transaction amount of 20 trillion tokens on all transfers besides sells via Pancakeswap.
• The contract enforces a maximum wallet amount that prevents a transfer from occurring if the recipient's token balance will exceed 20 trillion tokens after the transfer occurs.
• There is a Tax fee and a Liquidity fee on all transfers where neither the sender nor the recipient is excluded from fees.
• The tokens collected through the Tax fee are removed from the circulating supply; This serves as a frictionless fee redistribution that automatically benefits all token holders at the time of each transaction.
• The Liquidity fee charged during transfers is stored in the contract address. The tokens are swapped for BNB for the purpose of funding Pancakeswap liquidity and the team's Marketing wallet when the following conditions are met:
  • The threshold number of tokens (determined by the owner) in the contract address has been reached.
  • The contract is not currently performing an automatic liquidity add.
  • The caller is not initiating a buy transaction via Pancakeswap.
• Liquidity-adds are automatically performed by selling a portion of the tokens collected as fees, pairing the received BNB with the token, and adding it as liquidity to the BNB pair.
• The LP tokens received through this process are sent to the 0x..dead address.
• A percentage (determined by the owner) of the BNB received through the token swapping process is sent to the team's Marketing wallet.
• The contract utilizes the SafeMath library to protect against overflows/underflows.
• The contract complies with the BEP-20 token standard.

Ownership Controls:

• The owner can set the Tax fee up to 5% and the Liquidity fee up to 19% at any time.
• The owner can exclude and include accounts from transfer fees.
• The owner can exclude accounts from the maximum transaction amount and maximum wallet amount restrictions at any time.
• The owner can set the threshold number of tokens that triggers an automatic liquidity add to any value at any time.
• The owner can set the Marketing divisor to any value greater than 1.
• The owner can withdraw any tokens (besides $MIMI) from the contract at any time.
• The owner can withdraw up to 94% of the BNB from the contract in a single transaction at any time.
• The owner can update the team's Marketing wallet to any address at any time.

Audit Results

Inheritance Chart

Function Graph

Functions Overview

 ($) = payable function
 # = non-constant function
 
 Int = Internal
 Ext = External
 Pub = Public

 + [Int] IBEP20 
    - [Ext] totalSupply
    - [Ext] decimals
    - [Ext] symbol
    - [Ext] name
    - [Ext] balanceOf
    - [Ext] transfer #
    - [Ext] allowance
    - [Ext] approve #
    - [Ext] transferFrom #

 + [Int] Token 
    - [Ext] transferFrom #
    - [Ext] transfer #

 +  Context 
    - [Int]  #
    - [Int] _msgSender
    - [Int] _msgData

 + [Lib] SafeMath 
    - [Int] add
    - [Int] sub
    - [Int] sub
    - [Int] mul
    - [Int] div
    - [Int] div
    - [Int] mod
    - [Int] mod

 +  Ownable (Context)
    - [Int]  #
    - [Pub] owner
    - [Pub] renounceOwnership #
       - modifiers: onlyOwner
    - [Pub] transferOwnership #
       - modifiers: onlyOwner
    - [Int] _transferOwnership #

 + [Int] IPancakeRouter01 
    - [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] IPancakeRouter02 (IPancakeRouter01)
    - [Ext] removeLiquidityETHSupportingFeeOnTransferTokens #
    - [Ext] removeLiquidityETHWithPermitSupportingFeeOnTransferTokens #
    - [Ext] swapExactTokensForTokensSupportingFeeOnTransferTokens #
    - [Ext] swapExactETHForTokensSupportingFeeOnTransferTokens ($)
    - [Ext] swapExactTokensForETHSupportingFeeOnTransferTokens #

 + [Int] IPancakeFactory 
    - [Ext] feeTo
    - [Ext] feeToSetter
    - [Ext] getPair
    - [Ext] allPairs
    - [Ext] allPairsLength
    - [Ext] createPair #
    - [Ext] setFeeTo #
    - [Ext] setFeeToSetter #
    - [Ext] INIT_CODE_PAIR_HASH

 + [Int] IPancakePair 
    - [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] mint #
    - [Ext] burn #
    - [Ext] swap #
    - [Ext] skim #
    - [Ext] sync #
    - [Ext] initialize #

 +  Kemonomimi (Context, IBEP20, 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] totalFees
    - [Pub] reflect #
    - [Pub] reflectionFromToken
    - [Pub] tokenFromReflection
    - [Prv] _approve #
    - [Prv] removeAllFee #
    - [Prv] restoreAllFee #
    - [Prv] _transfer #
    - [Prv] _transferStandard #
    - [Prv] _reflectFee #
    - [Prv] _getValues
    - [Prv] _getTValues
    - [Prv] _getRValues
    - [Prv] _getRate
    - [Prv] _getCurrentSupply
    - [Prv] _takeLiquidity #
    - [Prv] swapAndLiquify #
       - modifiers: lockTheSwap
    - [Prv] swapTokensForBNB #
    - [Prv] addLiquidity #
    - [Ext] setLiquidityFeePercent #
       - modifiers: onlyOwner
    - [Ext] setReflectFee #
       - modifiers: onlyOwner
    - [Ext] setAutoLpDivisor #
       - modifiers: onlyOwner
    - [Ext] setMarketingDivisor #
       - modifiers: onlyOwner
    - [Pub] excludeFromFee #
       - modifiers: onlyOwner
    - [Pub] includeInFee #
       - modifiers: onlyOwner
    - [Ext] setExcludedFromAntiWhale #
       - modifiers: onlyOwner
    - [Pub] isExcludedFromFee
    - [Pub] isExcludedFromAntiWhale
    - [Pub] transferBEPTokens #
       - modifiers: onlyOwner
    - [Ext] clearStuckBalance #
       - modifiers: onlyOwner
    - [Ext] changeFeeReceivers #
       - modifiers: onlyOwner
    - [Ext]  ($)
    - [Ext]  ($)

About SourceHat

SourceHat has quickly grown to have one of the most experienced and well-equipped smart contract auditing teams in the industry. Our team has conducted 1800+ 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!
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 SourceHat Audit?

Typically, a smart contract audit is a comprehensive review process designed to discover logical errors, security vulnerabilities, and optimization opportunities within code. A SourceHat 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.

• Go Home