BNB Tiger Info
BNBTiger is the king of beasts. They are the symbol of victory and strength. Powerful and tough.and our $BNBTIGER community is the same. $BNBTIGER is a decentralized experiment, launched on the January 3, 2022, by the founder, BNBTiger9527, as a fresh opportunity for those who were struggling in the midst of the biggest bear market since. Born out of trials and tribulation, the $BNBTIGER community is the strongest community you'll find, supportive of one another, and pushing each other towards success. We are fed up with the fraud projects in the market! These projects have lowered people's trust, led to suspicion and panic, and finally led to the death of one project after another. No more great projects like Shib can be born! The goal of the birth of BNBTiger is to rebuild the security and trust of the market. Like Shib, Let's complete another 260000 X the task. So we launched a huge number of 10.000.000.000.000.000.000.000.000 tokens, destroyed 50%, and launched fairly! Let's start from zero. This is a new social experiment. We want to see how many zeros can be killed by real trust! Our ultimate goal is to eliminate all zeros and surpass the historical record of shib!
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.
TrustNet DataPulse
0xAC68931B666E086E9de380CFDb0Fb5704a35dc2D
Data provided by We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!
We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.
In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.
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 burning within the contract without any allowances
Ownership is renounced
Contract cannot be manipulated by owner functions.
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.
NOTE:
Ownership is renounced
Owner is not able to regain ownership with lock function because it was not called before the ownership was transferred to the dead address.
Owner Privileges
- update market pair
- update tx limit for holder
- update max tx /maxwallet to 0
- be aware of it. Owner can lock user funds here
- exclude from fee
- exclude from wallet limit
- set buy/sell fees and also the distribution share without limitation
- be aware of it. The owner is able to set the fees to arbitary number
- update minimumTokensBeforeSwap
- update marketing wallet
- update team wallet
- enable/disable swapAndLiquifyEnabled
- enable/disable swapAndLiquifyByLimitOnly
- update router/pair address
- liquidity will be send to the owner address
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 1 findings
Resolved
#1 medium Issue
Owner can get back the ownership of contract after transferring it
The owner is able to regain the ownership. The owner must call the lock function to set own address to the "_previousOwner". After transferring the ownership the owner is able to regain the ownership by calling the unlock function. We recommend the new owner to call the lock function with the time value of 0 that the previousOwner variable will be overwritten by the own address that the previous one is not able to regain the ownership back.
low Issues | 4 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#3 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#4 low Issue
State variable visibility is not set
Provide a state variable visibility
optimization Issues | 2 findings
Pending
#1 optimization Issue
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change.
Pending
#2 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
informational Issues | 1 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.