Dollarmoon
The first part of the name refers to the US Dollar, a symbol of wealth and power, and the most dominant fiat currency. As for the second part, it refers to the moon, a symbol of wealth in the crypto world. For these reasons, we have decided that our cryptocurrency would combine the two names, on its journey to the moon. We believe in our dream, and we are going to make it happen with the help of our unique roadmap. What makes our roadmap very special is that it relies on a completely new system called âValue Leading Systemâ, and that very specific aspect would make our project the first of its kind in the field of Cryptocurrencies.
Owner privileges
Comments
Ownership Privileges:
- Set max sell transaction to any arbitrary value
- Update the minimum token balance for dividends to any arbitrary value and exclude wallets from dividends
- Update the claim wait within limitations.
- Update uniswap router address, AMM Pair
- Exclude accounts from fees
- Change Liquidity wallet, amd marketing wallet
- Update dividend tracker address
- Set balance of accounts in the dividend contract which will be done by minting of tokens to that particular account.
- Update gas for processing, and process account for dividends
- Set trade fee and fees status
- Enable Transfer before trading is enabled for any wallet/contract
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
158
State variables
public
32
Total lines
of code
2046
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)
L1071
L1071
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L1382-1384
L1386-1388
L1453-1456
L1458-1461
L1463-1466
L1468-1471
L1473-1476
L1478-1481
L1483-1486
L1488-1491
L1493-1503
Emit an event for critical parameter changes.
Pending
#3 Issue
Local variables used prior their declaration (variable-scope)
L1709
L1709
L1709
Move all variable declarations prior to any usage of the variable, and ensure that reaching a variable declaration does not depend on some conditional if it is used unconditionally.
Pending
#4 Issue
Floating Pragma
-
The current pragma Solidity directive is â^0.6.2". Contracts should be deployed with the same compiler version and flags that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions.
Pending
#5 Issue
Old Compiler Version
-
The contract is using an old compiler version which is not recommended for deployment because it is prone to known vulnerabilities.
informational Issues
Pending
#1 Issue
Unused return values (unused-return)
L1591-1593
L1607-1716
L1807-1822
Ensure that all the return values of the function calls are used.
Pending
#2 Issue
Uninitialized local variables (uninitialized-local)
L1709
L1709
L1709
Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.
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.