Owner privileges
Comments
Ownership Privileges
- The owner can start and end the presale in the contract.
- The owner can set any arbitrary value as the price of the token.
- The owner can set any arbitrary value as the price of a dollar in bnb.
- The owner can pause the presale.
- The owner can enable/disable claim functionality in the contract.
- The owner can transfer contract balance to his wallet.
- The owner can claim the stuck tokens including contract's tokens.
Note - This Audit report consists of a security analysis of the WAXCHAIN smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the WAXCHAIN team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.
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
34
State variables
public
12
Total lines
of code
465
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.
high Issues
Pending
#1 Issue
The owner can manipulate the price of token.
L442-444
L447-449
The owner can set any arbitrary value as the price of token in bnb and dollar which is not recommended as this can manipulate the price of tokens. Instead of making it manually, add the functionality to have the price of tokens and according to that the price will be pegged with USDT or BNB in the contract.
medium Issues
Pending
#1 Issue
The owner can lock token.
L454-456
The owner can enable/disable the claim functionality from the contract which is not recommended as this can lock the user funds for an unlimited period of time. It is recommended that the claimed functionality should not be locked in the contract.
low Issues
Pending
#1 Issue
Floating pragma solidity version
L12
Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L58-60
L247-263
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L100-102
L104-107
L141-143
L149-151
L159-161
L164-166
L169-173
L180-184
L186-191
L194-198
L200-209
L331-389
L390-424
L433-435
L437-439
L442-444
L447-449
L451-453
L458-460
L462-464
Use the `external` attribute for functions never called from the contract.
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.