TradeWIX
TradeWix is a German tech rate company. Each of our employees is a specialist in their field. Our crypto experience has allowed us to discover new sides over the years. Many investors, including long-time experienced ones, keep falling for the various scammers in the space. These scammers don't shy away from using the most disgusting tricks to get the money out of investors' pockets. We want to put an end to that and serve as one of the safest platforms to provide the best possible information about each project. Unique score values are only awarded to projects that adhere to our standards and are willing to open up to their investors.
Owner privileges
Comments
Ownership Privileges:
- Include/Exclude wallets from fees, maximum wallet, and maximum transaction limit
- Set fees, maximum wallet, and maximum transaction limit within limitation.
- Set new LP pair and can also remove old one.
- Set marketing wallet address.
- Enable/Disable swap and Liquify
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
97
State variables
public
17
Total lines
of code
994
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.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L556
L566
Rename the local variables that shadow another component.
Pending
#2 Issue
Uninitialized local variables (uninitialized-local)
L835
L850
Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L49-52
Remove unused functions.
Pending
#2 Issue
Function initializing state variables (function-init-state)
L441
L468
L469
L470
Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.
Pending
#3 Issue
Unused return values (unused-return)
L952-965
Ensure that all the return values of the function calls are used.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L449-450
L440
L442
L443
L460
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L76-79
L81-88
L545-553
L566-574
L576-587
L589-601
L743-751
L753-765
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.