Smart Contract Audit Report
Be happy is a new BEP-20 token on the Binance Smart Chain.
For this audit, we reviewed the project team's BEP20Token contract at 0x8db8e6a13b0364d2f13aff5c3b75f61df45f16c2 on the Binance Smart Chain Mainnet.
Informational findings were identified and the team may want to review them.
Date: October 25th, 2022.
Finding #1 - BEP20Token - InformationalDescription: The internal _burn() and _burnFrom() functions are never called in the contract.
Recommendation: These functions could be removed to reduce contract size and deployment costs.
Finding #2 - BEP20Token - InformationalDescription: 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.
- The total supply of the token is set to 300 million $HAP [300,000,000].
- No mint or burn functions are accessible, though the circulating supply can be decreased by sending tokens to the 0x..dead address.
- At the time of writing this report, 100% of the total supply belongs to the deployer.
- There are no fees associated with transferring tokens.
- As the contract is deployed with Solidity v0.8.7, it is safe from any possible overflows/underflows.
- The contract complies with the BEP-20 token standard.
|Arbitrary Jump/Storage Write||N/A||PASS|
|Centralization of Control||The team currently owns 100% of the total supply.||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|
|Unused Code||The internal _burn() and _burnFrom() functions are never called in the contract.||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 - [Pub]
# - [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] _transferOwnership # + BEP20Token (Context, IBEP20, Ownable) - [Pub] # - [Ext] getOwner - [Ext] decimals - [Ext] symbol - [Ext] name - [Ext] totalSupply - [Ext] balanceOf - [Ext] transfer # - [Ext] allowance - [Ext] approve # - [Ext] transferFrom # - [Pub] increaseAllowance # - [Pub] decreaseAllowance # - [Int] _transfer # - [Int] _burn # - [Int] _approve # - [Int] _burnFrom #
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 $10 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 Solidity Audit?
Typically, a smart contract audit is a comprehensive review process designed to discover logical errors, security vulnerabilities, and optimization opportunities within code. A Solidity 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.