Dollarmoon Info
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.
TrustNet Score
The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.
Real-Time Threat Detection
Real-time threat detection, powered by Cyvers.io,
is currently not
activated
for this project.
This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks.
For more information, click here.
Summary and Final Words
No crucial issues found
The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.
Contract owner cannot mint
It is not possible to mint new tokens.
Contract owner cannot blacklist addresses.
It is not possible to lock user funds by blacklisting addresses.
Contract owner cannot set high fees
The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.
Token transfer can be locked
Owner can lock user funds with owner functions.
Token cannot be burned
There is no burning within the contract without any allowances
Ownership is not renounced
The owner retains significant control, which could potentially be used to modify key contract parameters.
Scope of Work
This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.
The auditing process consists of the following systematic steps:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.
A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.
Final Words
The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.
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
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
low Issues | 5 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#3 low Issue
Local variables used prior their declaration (variable-scope)
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 low 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 low 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 | 2 findings
Pending
#1 informational Issue
Unused return values (unused-return)
Ensure that all the return values of the function calls are used.
Pending
#2 informational Issue
Uninitialized local variables (uninitialized-local)
Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.