BNB Tiger
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!
Owner privileges
Comments
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
Audit Scope
This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.
We will verify the following claims:- Correct implementation of Token standard
- Deployer cannot mint any new tokens
- Deployer cannot burn or lock user funds
- Deployer cannot pause the contract
- Overall checkup (Smart Contract Security)
- Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
- Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
- Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
- Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
- Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
- Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
- Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.
A file with a different Hash has been modified, intentionally or otherwise, 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.
Functions
public
101
State variables
public
26
Total lines
of code
788
Capabilities
Hover on items
Audit Details
Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.
Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.
medium Issues
Resolved
#1 Issue
Owner can get back the ownership of contract after transferring it
L139-193
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
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L518
L541
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L561-567
L569-575
L577-583
L585-587
L597-599
L601-603
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L605
L609
Check that the address is not zero.
Pending
#4 Issue
State variable visibility is not set
L408
L440
Provide a state variable visibility
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L119-136
L102-104
L106-108
L110-112
L114-117
L83-92
L94-100
L10-13
L71-73
L75-78
Remove unused functions.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L402
L400
L401
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L161-164
L166-170
L172-174
L176-178
L180-185
L187-192
L498-500
L502-504
L506-508
L510-512
L518-520
L522-525
L527-530
L532-534
L536-539
L549-551
L557-559
L613-616
L618-620
L622-624
L630-647
L652-655
L657-661
Use the `external` attribute for functions never called from the contract.
Diagrams
Disclaimer
SolidProof.io reports are not, nor should be considered, an âendorsementâ or âdisapprovalâ of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any âproductâ or âassetâ created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etcâ...)
SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.
SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProofâs position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.