MYSTERY

Smart Contract Audit Report

Audit Summary

MYSTERY is a new BEP-20 token on the Binance Smart Chain that is an automatic liquidity providing protocol.

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

Audit Findings

Please ensure trust in the team prior to investing as they have substantial control in the ecosystem.
The team has successfully completed KYC procedures with KYC capital.
Date: March 2nd, 2022.
Updated: March 4th, 2022 to reflect the contract's Mainnet address.

Contract Overview

• The total supply of the token is set to 1 billion $MYST [1,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 2,710 total token holders. The token allocation is as follows:
  • 20.5% of the total supply is in an upgradeable token vesting contract and will fully vest to the team on March 23rd, 2022.
  • 16.76% of the total supply is in Pancakeswap liquidity.
  • Of that liquidity, 86.84% of the LP tokens are stored in the upgradeable token vesting contract and will vest to the team on March 2nd, 2023.
  • 12.83% of the LP tokens belong to the team's Liquidity wallet.
  • 12.77% of the total supply belongs to an unverified contract.
  • 10.55% of the total supply has been sent to the 0x..dead address.
  • 4.83% of the total supply belongs to the team's Liquidity wallet.
  
  
• The owner must manually enable trading in order for all trading to take place on the platform. Only accounts specified by the owner can transfer tokens before trading has been enabled. Once trading has been enabled, it can never be disabled.
• Users who are attempting to buy tokens within the same block that trading was enabled will be taxed at a 99.9% rate.
• 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 any given transaction.
• The contract enforces a maximum wallet amount that prevents a transfer from occurring when the following conditions are met:
  • The recipient is not the Pair address or the 0x..dead address.
  • The recipient is not excluded from the limit.
  • The recipient's token balance will exceed the limit number of tokens (determined by the owner) after the transfer occurs.
• The contract enforces an antidump mechanism that increases total fees by a percentage (determined by the owner) when selling tokens if the price impact that the number of tokens a user has sold (within the last 30 minutes) will have on the liquidity pool is more than the antidump threshold value (also determined by the owner).
• There is a Liquidity fee, Giveaway fee, and DevMarketing fee on all transfers where neither the sender nor the recipient is excluded from fees.
• Fees will not be charged on transfers while the contract is currently performing an automatic liquidity add.
• Total fees are increased by a value (determined by the owner) when selling tokens to Pancakeswap (or any other approved DEX). Total fees are decreased by this same value on all other transactions.
• If a user is attempting to sell tokens after having bought tokens for the first time within 24 hours, total fees will be increased by a percentage (determined by the owner).
• 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 when the following conditions are met:
  • The automatic liquidity add functionality is enabled by the team.
  • The threshold number of tokens in the contract address (determined by the owner) has been reached.
  • The contract is not currently performing an automatic liquidity add.
  • The sender is not performing a buy transaction via Pancakeswap.
  • The sender is not excluded from fees.
  • The sum of the current transfer fees is greater than 0.
• Liquidity-adds are automatically performed by selling 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 Liquidity address controlled by the team. We recommend that the team lock these newly acquired LP tokens.
• The tokens collected from the DevMarketing fee and Giveaway fee are swapped for BNB and are sent to the team's DevMarketing wallet and Giveaway wallet respectively.


• As the contract is implemented with Solidity v0.8.x, it is protected from overflows/underflows.
• The contract complies with the BEP-20 token standard.

Ownership Controls:

• The owner can modify the Liquidity fee, Giveaway fee, and DevMarketing fee to any percentages as long as the total percentage combined does not exceed 25%.
• The owner can exclude and include accounts from transfer fees.
• The owner can update the maximum transaction amount and maximum wallet amount at any time.
• The owner can exclude/include accounts from the maximum transaction amount and maximum wallet amount limits.
• The owner can enable/disable automatic liquidity adds at any time.
• The owner can update the threshold number of tokens needed to trigger an automatic liquidity add to any value at any time.
• The owner can set the maximum amount of tokens from the contract that will be used for automatic liquidity adds to any value at any time.
• The owner can add accounts to a whitelist that will allow them to participate in transfers before trading has been enabled.
• The owner can update the sell percent to any value greater than 100 as long as the percent does not exceed the antidump tax and the product of this value and total fees divided by 100 does not exceed 400.
• The owner can set the sell period to any value up to 7 days.
• The owner can update the antidump period to any value up to 1 hour.
• The owner can update the antidump tax to any value up to 400. If set to 400, total fees will be increased by 4x their current value.
• The owner can enable/disable the antisniper mechanism at any time.
• The owner can add any address as an approved DEX at any time.

Audit Results

Inheritance Chart

Function Graph

Functions Overview

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

 + [Lib] Address 
    - [Int] isContract
    - [Int] sendValue #
    - [Int] functionCall #
    - [Int] functionCall #
    - [Int] functionCallWithValue #
    - [Int] functionCallWithValue #
    - [Prv] _functionCallWithValue #

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

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

 + [Int] IDEXPair 
    - [Ext] getReserves

 + [Int] IDEXFactory 
    - [Ext] createPair #

 + [Int] IDEXRouter 
    - [Ext] factory
    - [Ext] WETH
    - [Ext] addLiquidity #
    - [Ext] addLiquidityETH ($)
    - [Ext] swapExactTokensForTokensSupportingFeeOnTransferTokens #
    - [Ext] swapExactETHForTokensSupportingFeeOnTransferTokens ($)
    - [Ext] swapExactTokensForETHSupportingFeeOnTransferTokens #

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

 + [Int] IAntiSnipe 
    - [Ext] setTokenOwner #
    - [Ext] onPreTransferCheck #

 +  Mystery (IERC20, Ownable)
    - [Pub]  #
    - [Ext]  ($)
    - [Ext] totalSupply
    - [Ext] decimals
    - [Ext] symbol
    - [Ext] name
    - [Ext] getOwner
    - [Pub] balanceOf
    - [Ext] allowance
    - [Pub] approve #
    - [Ext] increaseAllowance #
    - [Ext] decreaseAllowance #
    - [Int] _approve #
    - [Ext] approveMax #
    - [Ext] transfer #
    - [Ext] transferFrom #
    - [Int] _transferFrom #
    - [Int] _basicTransfer #
    - [Int] checkWalletLimit
    - [Int] checkTxLimit
    - [Int] shouldTakeFee
    - [Pub] getTotalFee
    - [Int] takeFee #
    - [Int] shouldSwapBack
    - [Int] swapBack #
       - modifiers: swapping
    - [Int] launched
    - [Pub] getCirculatingSupply
    - [Pub] getLiquidityBacking
    - [Pub] isOverLiquified
    - [Pub] transferOwnership #
       - modifiers: onlyOwner
    - [Pub] renounceOwnership #
       - modifiers: onlyOwner
    - [Ext] setProtectionEnabled #
       - modifiers: onlyOwner
    - [Ext] setProtection #
       - modifiers: onlyOwner
    - [Ext] disableProtection #
       - modifiers: onlyOwner
    - [Ext] setLiquidityProvider #
       - modifiers: onlyOwner
    - [Ext] setSellPeriod #
       - modifiers: onlyOwner
    - [Ext] setAntiDumpTax #
       - modifiers: onlyOwner
    - [Ext] launch #
       - modifiers: onlyOwner
    - [Ext] setTxLimit #
       - modifiers: onlyOwner
    - [Ext] setMaxWallet #
       - modifiers: onlyOwner
    - [Ext] setIsFeeExempt #
       - modifiers: onlyOwner
    - [Ext] setIsTxLimitExempt #
       - modifiers: onlyOwner
    - [Ext] setFees #
       - modifiers: onlyOwner
    - [Ext] setSwapBackSettings #
       - modifiers: onlyOwner
    - [Ext] setTargetLiquidity #
       - modifiers: onlyOwner
    - [Ext] addLiquidityPool #
       - modifiers: onlyOwner

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 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 occuring 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