Owner privileges
Comments
- Liquidity will be send to the owner
- owner is able to
- take out tokens
- take out bnb
- set fees without any limitation
- It can be set above 100%
- We recommend you to restrict the setting to a certain value for every fees
- It can be set above 100%
- lock user funds by
- setting "maxSellTransactionAmount" to 0
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
115
State variables
public
26
Total lines
of code
2210
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
Pending
#1 Issue
Owner can take out native tokens
L1734
We recommend you to prevent passing the own contract address to the function. Otherwise the owner is able to take out native tokens.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L1373
L1373
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L1824-1831
L1833-1840
L1842-1844
L1963-1965
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L1730
L1846
Check that the address is not zero.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L699-701
L1472-1478
L2192-2194
L593-596
L647-650
L629-632
L611-614
L665-668
L488-491
L548-551
L473-476
L533-536
L518-521
L563-566
L503-506
L409-418
L369-371
L435-444
L386-395
L240-246
L282-287
L294-299
L265-275
L253-258
L191-193
L177-179
Remove unused functions.
Pending
#2 Issue
Missing error messages
-
Add missing error messages to the require statements
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L1760
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L855-857
L863-865
L880-882
L906-909
L925-928
L943-957
L971-974
L990-998
L1197-1199
L1205-1208
L1226-1228
L1230-1235
L1237-1239
L1243-1245
L1410-1412
L1438-1440
L1452-1454
L1619-1636
L1663-1708
L1730-1732
L1824-1831
L1833-1840
L1842-1844
L1846-1848
L1926-1930
L1939-1941
L1943-1947
L1949-1955
L1957-1961
L1963-1965
L1978-1983
L1997-1999
L2001-2003
L2005-2007
L2009-2011
L2061-2064
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.