Inuyama

Smart Contract Audit Report

Audit Summary

Inuyama Audit Report Inuyama is a new BEP-20 token on the Binance Smart Chain.

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

Audit Findings

Informational findings were identified and the team may want to review them.
Date: January 24th, 2023.

Finding #1 - INUYAMA - Informational

Description: The _transfer() function requires that the paused state variable is set to false. paused is set to false upon deployment and cannot be modified.
Recommendation: The team should either add a setter function that allows them to toggle the paused state variable or remove this state variable from the contract for additional gas savings on each transfer and to reduce contract size and deployment costs.

Finding #2 - INUYAMA - Informational

Description: The taxAmount state variable can never be modified but is not declared constant.
Recommendation: This state variable could be declared constant for additional gas savings on each reference.

Finding #3 - INUYAMA - Informational

Description: Although the SafeMath library is utilized, the contract is deployed with Solidity v0.8.7 which has built-in overflow/underflow checks.
Recommendation: SafeMath could be safely removed to reduce contract size, deployment costs, and gas costs on all transactions that utilize it.

Contract Overview

  • The total supply of the token is set to 1 billion $YAMA [1,000,000,000].
  • No public mint or burn functions are present, though the circulating supply can be decreased by sending tokens to the 0x..dead address.
  • At the time of writing this report, there are 1,435 total token holders. The token allocation is as follows:
  • Blacklisted accounts are prohibited from initiating transfers.
  • The contract enforces a maximum transaction amount which imposes a limit of 20 million tokens that can be transferred in a single transaction.
  • The contract enforces a maximum wallet amount that prevents a transfer from occurring if the recipient's token balance will exceed 20 million tokens after the transfer occurs.
  • There is a 5% Transfer fee on all transfers via Pancakeswap where neither the sender nor the recipient is excluded from fees.
  • The tokens collected through the Transfer fee are stored in the contract address. The tokens are swapped for BNB when the following conditions are met:
    • The threshold number of 1 million tokens in the contract address has been reached.
    • The contract is not currently performing a swap.
    • The caller is initiating a sell transaction via Pancakeswap.
  • The contract's full BNB balance is split amongst 3 wallets controlled by the team on transfers when its balance exceeds 1 BNB.
  • As the contract is deployed with Solidity v0.8.7, it is protected from overflows/underflows.
  • The contract complies with the BEP-20 token standard.
Ownership Controls:
  • Ownership has been renounced by the team.
  • The owner was previously able to add/remove accounts from the transfer blacklist at any time.
  • The owner was previously able to set the maximum transaction amount to any value at any time.
  • The owner was previously able to set the maximum wallet amount to any value greater than 10 million tokens at any time.
  • The team's "dWallet" can exclude and include accounts from the Transfer fee at any time.
  • The team's dWallet can swap all of the tokens in the contract for BNB at any time.
  • The team's dWallet can send all of the BNB in the contract to the fWallet, mWallet, and dWallet at any time.
  • The team's dWallet can modify the percentage of BNB that is split between the fWallet and mWallet to any percentages at any time.
  • The team's dWallet can withdraw any tokens (besides $YAMA) from the contract at any time.
  • The team's dWallet can update the dWallet, fWallet, and mWallet addresses at any time.

Audit Results

Vulnerability Category Notes Result
Arbitrary Jump/Storage Write N/A PASS
Centralization of Control Ownership has been renounced by the team. The team's "dWallet" retains the Ownership Controls listed above. PASS
Compiler Issues N/A PASS
Delegate Call to Untrusted Contract N/A PASS
Dependence on Predictable Variables N/A PASS
Ether/Token Theft N/A PASS
Flash Loans N/A PASS
Front Running N/A PASS
Improper Events N/A PASS
Improper Authorization Scheme N/A PASS
Integer Over/Underflow N/A PASS
Logical Issues N/A PASS
Oracle Issues N/A PASS
Outdated Compiler Version N/A PASS
Race Conditions N/A PASS
Reentrancy N/A PASS
Signature Issues N/A PASS
Sybil Attack N/A PASS
Unbounded Loops N/A PASS
Unused Code N/A PASS
Overall Contract Safety   PASS

Inheritance Chart

Smart Contract Audit - Inheritance

Function Graph

Smart Contract Audit - Graph

Functions Overview


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

 +  Context 
    - [Int] _msgSender

 + [Int] IERC20 
    - [Ext] totalSupply
    - [Ext] balanceOf
    - [Ext] transfer #
    - [Ext] allowance
    - [Ext] approve #
    - [Ext] transferFrom #

 + [Lib] SafeMath 
    - [Int] add
    - [Int] sub
    - [Int] sub

 +  Ownable (Context)
    - [Pub]  #
    - [Pub] owner
    - [Ext] transferOwnership #
       - modifiers: onlyOwner

 + [Int] IUniswapV2Factory 
    - [Ext] createPair #

 + [Int] IUniswapV2Router02 
    - [Ext] swapExactTokensForETHSupportingFeeOnTransferTokens #
    - [Ext] factory
    - [Ext] WETH
    - [Ext] addLiquidityETH ($)

 +  INUYAMA (Context, IERC20, Ownable)
    - [Pub]  #
    - [Ext] name
    - [Ext] symbol
    - [Ext] decimals
    - [Ext] totalSupply
    - [Pub] balanceOf
    - [Ext] transfer #
    - [Ext] allowance
    - [Ext] approve #
    - [Ext] isWhitelisted
    - [Ext] transferFrom #
    - [Prv] _approve #
    - [Prv] _transfer #
    - [Prv] swapTokensForEth #
       - modifiers: lockTheSwap
    - [Ext] changeMaxTrnx #
       - modifiers: onlyOwner
    - [Ext] changeMaxWallet #
       - modifiers: onlyOwner
    - [Prv] sendETHToFee #
    - [Ext] openTrading #
       - modifiers: onlyOwner
    - [Ext] blacklistBot #
       - modifiers: onlyOwner
    - [Ext] removeFromBlacklist #
       - modifiers: onlyOwner
    - [Prv] _tokenTransfer #
    - [Ext] whitelistAddress #
    - [Ext]  ($)
    - [Ext] transferERC20 #
    - [Ext] changeTaxDistro #
    - [Ext] changeWallet #
    - [Ext] manualswap #
    - [Ext] manualsend #

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 1300+ 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 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.