Smart Contract Audit Report
Meta Fame is building a new BEP-20 token with a Liquidity Generation Event.
For this audit, we reviewed the BMF token contract using code provided to us by the project team.
Please ensure trust in the team prior to investing as they have substantial control in the ecosystem. The team receives 100% of total supply upon deployment.
Date: April 8th, 2022.
Finding #1 - BMF - InformationalDescription: Although the SafeMath library is utilized, the contract is implemented with Solidity v0.8.x 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 1 million $BMF [1,000,000] and will be minted to the owner upon deployment.
- The owner can mint any amount of tokens to any address at any time, as long as the amount minted does not exceed the cap of 10 billion $BMF.
- The owner can burn any tokens that they hold to reduce the total supply.
- The owner can burn tokens on another user's behalf if an allowance has been granted.
- The contract includes a calculation for the "circulating supply" of BMF that excludes tokens held by "official accounts".
- The contract supports a Liquidity Generation Event (LGE) consisting of one or many rounds as determined by the owner.
- Each round has a set duration, a maximum amount of coin that can be purchased per user, and a whitelist of addresses that are able to participate.
- The values for each LGE Whitelist Round is determined by the LGE Whitelister address, which is initially the owner.
- After the rounds are created and the Pair address is set, anyone may kick off the Liquidity Generation Event by transferring tokens to the Pair address.
- Only whitelisted users may participate in the Liquidity Generation Event by purchasing tokens from the Pair; there may be a different set of whitelisted users for every round.
- During the Liquidity Generation Event, the amount of purchased tokens is recorded to ensure it does not exceed the maximum allowed amount per user per round.
- The LGE Whitelister address can set the Pair address, delete the round data, modify the round duration, maximum contribution amount, and list of whitelisted users for any round at any time.
- The LGE Whitelister address can transfer their role to any address at any time or renounce their ownership at any time.
- There are no fees associated with transferring tokens.
- The owner can add any address as an official account at any time. This effectively allows the owner to control the circulating supply displayed to users.
- 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.
|Arbitrary Jump/Storage Write||N/A||PASS|
|Centralization of Control||100% of total supply will be minted to the deployer.||PASS|
|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] IBEP20 - [Ext] totalSupply - [Ext] decimals - [Ext] symbol - [Ext] name - [Ext] getOwner - [Ext] balanceOf - [Ext] transfer # - [Ext] allowance - [Ext] approve # - [Ext] transferFrom # + Context - [Int] _msgSender - [Int] _msgData + Ownable (Context) - [Pub]
# - [Pub] owner - [Pub] renounceOwnership # - modifiers: onlyOwner - [Pub] transferOwnership # - modifiers: onlyOwner + [Lib] SafeMath - [Int] add - [Int] sub - [Int] sub - [Int] mul - [Int] div - [Int] div - [Int] mod - [Int] mod + LGEWhitelisted (Context) - [Pub] # - [Ext] renounceWhitelister # - modifiers: onlyWhitelister - [Ext] transferWhitelister # - modifiers: onlyWhitelister - [Int] _transferWhitelister # - [Ext] createLGEWhitelist # - modifiers: onlyWhitelister - [Ext] modifyLGEWhitelist # - modifiers: onlyWhitelister - [Pub] getLGEWhitelistRound - [Int] _applyLGEWhitelist # + BMF (Context, IBEP20, Ownable, LGEWhitelisted) - [Pub] # - [Ext] addOfficialAccount # - modifiers: onlyOwner - [Ext] mint # - modifiers: onlyOwner - [Ext] burn # - modifiers: onlyOwner - [Ext] burnFrom # - modifiers: onlyOwner - [Ext] getOwner - [Ext] decimals - [Ext] symbol - [Ext] name - [Pub] totalSupply - [Ext] getCirculation - [Pub] balanceOf - [Ext] transfer # - [Ext] allowance - [Ext] approve # - [Ext] transferFrom # - [Ext] increaseAllowance # - [Ext] decreaseAllowance # - [Int] _beforeTokenTransfer # - [Int] _transfer # - [Int] _mint # - [Int] _burn # - [Int] _approve #
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 1700+ 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.