BAO Info
BAO's goal is to be the number one meme token. Our strategy is to rise infinitely, and victory often belongs to the diamond hand. Returning after a year, we made the big decision to change the transaction fee to BYU:0 SELL:3 which leaves a lot of room for growth and we can minimize or even offset investors in the process of trading Costs incurred. As an investor, this is a unique opportunity to be part of an investment with a good career and great potential gains.
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.
On-Chain Insights
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.
Contract cannot be locked
Owner cannot lock any user funds.
Token cannot be burned
There is no burn function within the contract.
Ownership is not renounced
Contract can be manipulated by owner functions.
Scope of Work
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.
The ownership is renounced but the Dev address mentioned on L44 can still make the following changes in the contract:
- Claim Balance of the contract
- Transfer native tokens from the contract
- Setup Liquidity Pool and Marketing pool address and status
We recommend investors/users do their own research before investing
Files and details
Findings and Audit result
low Issues | 2 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
optimization Issues | 4 findings
Pending
#1 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
Pending
#2 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
Pending
#3 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
Pending
#4 optimization Issue
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change.
informational Issues | 3 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#2 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#3 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
This audit covered the following files listed below with a SHA-1 Hash. The Team mentioned above provided us with the files that need to be evaluated.
A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.