Smart Contract Audit Report
ODON is a new BEP-20 token on the Binance Smart Chain.
For this audit, we reviewed the project team's ODON contract at 0x04486A7b832c5270B24d1c4B4E86F17b74B88549 on the Binance Smart Chain Mainnet.
Informational findings were identified and the team may want to review them. In addition, centralized aspects are present.
Date: August 12th, 2022.
Updated: September 6th, 2022 to reflect the project's newly deployed Mainnet address.
Finding #1 - ODON - Medium (Resolved)Description: Although logic for automatic liquidity adds exists in the _transfer() function, it will never execute as the
swapAndLiquifyEnabledboolean variable is permanently set to false.
Risk/Impact: The contract will never perform an automatic liquidity add.
Recommendation: The team should either add a setter function that toggles the
swapAndLiquifyEnabledvariable or remove all logic regarding automatic liquidity adds to reduce contract size, deployment costs, and gas costs on all transfers.
Resolution: The team has removed all logic regarding automatic liquidity adds from the contract.
Finding #2 - ODON - InformationalDescription: Although the SafeMath library is used, the contract is implemented with Solidity v0.8.x which has built-in overflow checks.
Recommendation: SafeMath could safely be removed to reduce contract size, deployment costs, and gas costs on all transactions that utilize it.
Finding #3 - ODON - Informational (Resolved)Description: The
teamWalletstate variable can never be modified but is not declared constant.
Recommendation: This state variable can be declared constant for additional gas savings on each reference.
Resolution: The team has implemented the above recommendation.
- The total supply of the token is currently 30 million [30,000,000] $ODON.
- The maximum supply of the token is set to 40 million.
- The owner can mint any number of tokens to any address up to the maximum supply at any time.
- Any user can burn their own tokens to reduce the total supply.
- At the time of writing this report, 100% of the total supply belongs to the owner.
- The contract enforces a maximum transaction amount (determined by the owner) which imposes a limit to the number of tokens that can be transferred in a single transaction.
- There is a Liquidity fee, Team fee, and Burn fee on all transfers via an approved DEX where neither the sender nor the recipient is excluded from fees.
- The tokens collected through the Liquidity fee are sent to the contract address and cannot be withdrawn.
- The tokens collected through the Team fee are sent to a wallet controlled by the team.
- The tokens collected through the Burn fee are removed from the total supply.
- The contract utilizes the SafeMath library to protect against overflows/underflows.
- The contract complies with the BEP-20 token standard.
- The owner can modify the Liquidity fee, Team fee, and Burn fee to any percentages as long as the total combined fee percentage does not exceed 25%.
- The owner can exclude and include accounts from transfer fees and the maximum transaction amount restriction at any time.
- The owner can update the maximum transaction amount to any value greater than 1% of the current total supply at any time.
- The owner can add/remove addresses as an Automated Market Maker Pair at any time.
|Arbitrary Jump/Storage Write||N/A||PASS|
|Centralization of Control||
|Delegate Call to Untrusted Contract||N/A||PASS|
|Dependence on Predictable Variables||N/A||PASS|
|Improper Authorization Scheme||N/A||PASS|
|Outdated Compiler Version||N/A||PASS|
|Overall Contract Safety||PASS|
($) = payable function # = non-constant function Int = Internal Ext = External Pub = Public + [Int] IERC20 - [Ext] totalSupply - [Ext] balanceOf - [Ext] transfer # - [Ext] allowance - [Ext] approve # - [Ext] transferFrom # + [Int] IERC20Metadata (IERC20) - [Ext] name - [Ext] symbol - [Ext] decimals + Context - [Int] _msgSender - [Int] _msgData + [Lib] SafeMath - [Int] add - [Int] sub - [Int] sub - [Int] mul - [Int] div - [Int] div - [Int] mod - [Int] mod + Ownable (Context) - [Pub]
# - [Pub] owner - [Pub] renounceOwnership # - modifiers: onlyOwner - [Pub] transferOwnership # - modifiers: onlyOwner + [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 # + ODON (Context, IERC20, IERC20Metadata, Ownable) - [Pub] # - [Pub] name - [Pub] symbol - [Pub] decimals - [Pub] totalSupply - [Pub] balanceOf - [Pub] transfer # - [Pub] allowance - [Pub] approve # - [Ext] transferFrom # - [Pub] increaseAllowance # - [Pub] decreaseAllowance # - [Int] _transfer # - [Ext] updateFees # - modifiers: onlyOwner - [Ext] ExcludeOrIncludeFromFee # - modifiers: onlyOwner - [Ext] isExcludedFromFee - [Ext] isAutomaticMarketMaker - [Ext] SetAutomaticMarketMaker # - modifiers: onlyOwner - [Ext] setMaxTxPercentage # - modifiers: onlyOwner - [Pub] _mint # - modifiers: onlyOwner - [Ext] _burn # - [Int] _approve # - [Int] _beforeTokenTransfer #
SourceHat (formerly Solidity Finance - founded in 2020) 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.