BugsBunny Info
The Bugs Bunny Token ($BUGS) was born out of a shared vision among a group of crypto enthusiasts who are drawn together by their love of the childhood cartoon show „Looney Tunes“ and crypto. With this new cryptocurrency, the main character of the popular childhood series comes back to life and brings all his joy and nostalgia under the stressful life of a crypto investor. To that end, the currency manages to achieve price growth due to its large community and appeal, putting its followers financially in a great direction.
TrustNet Score
The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.
Real-Time Threat Detection
Real-time threat detection, powered by Cyvers.io,
is currently not
activated
for this project.
This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks.
For more information, click here.
Summary and Final Words
No crucial issues found
The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.
Contract owner cannot mint
It is not possible to mint new tokens.
Contract owner cannot blacklist addresses.
It is not possible to lock user funds by blacklisting addresses.
Contract owner cannot set high fees
The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.
Token transfer can be locked
Owner can lock user funds with owner functions.
Token cannot be burned
There is no burning within the contract without any allowances
Ownership is not renounced
The owner retains significant control, which could potentially be used to modify key contract parameters.
Scope of Work
This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.
The auditing process consists of the following systematic steps:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.
A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.
Final Words
The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.
Ownership Privileges
- Create and Update presale in which the owner can set/update the token's selling price, total amount of tokens to sell, start/end time, and the active/inactive status
- End the presale at any time
- Change the Fund wallet address and USDT token address (which will be used to buy tokens apart from ETH).
- Change the Sale token address, which means that it is possible for the owner to set this address to any other random token address, and then, in that case, the users may not be able to claim the tokens for which they have paid. Thus, they may get a different token instead of what they paid for
- The owner has complete authority to start/stop the presale at any time
- There is an extreme possibility of the owner locking the user tokens either by 1. Not adding the tokens to the presale contract balance, or 2. Withdrawing all the tokens from the presale contract address at any time.
It is possible for the owner to withdraw all the tokens from the contract's balance, in which case the claim function will not work.
Note - This Audit report consists of a security analysis of the BugsBunny Presale smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the BugsBunny team. Our team did not audit other contracts associated with the project. We recommend investors to do their own research before investing.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
low Issues | 1 findings
Pending
#1 low Issue
Missing Zero Address Validation
Check that the address is not zero.
optimization Issues | 1 findings
Pending
#1 optimization Issue
Public function that could be declared external
Use the `external` attribute for functions never called from the contract.
informational Issues | 1 findings
Pending
#1 informational Issue
Functions that are not used
We recommend removing unused functions.