Martian Doge Info
Maritan Doge is the meta-universe of the Mars modal cryptocurrency space. It is inspired by Musk's Mars mania: the future economic model of Mars will be based on cryptocurrency. In tribute to Musk and DOGE, Martian doge was born, aiming to be the necessary economic application tool for future human landing on Mars. Martian doge ecological model is divided into three main parts: Martian doge NFT, Martian doge mining ecology and Martian doge wallet, and will develop NFT GAMEFI in the future
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.
Contract cannot be locked
Owner cannot lock any user funds.
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.
Owner Privileges
- exclude/include from fee
- exclude/include from regimental list
- exclude from dividends
- set numTokensSellToAddLiquidity
- can be set to any value (0-max uint256)
- set market address
- update minimum token balance for dividends
- can be set to any value (0-max uint256)
- if value is set to 0 nobody will have dividends because it will be set to 0 in the dividendPayingToken
- can be set to any value (0-max uint256)
- can be set to any value (0-max uint256)
- if value is set to 0 nobody will have dividends because it will be set to 0 in the dividendPayingToken
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 1 findings
Pending
#1 medium Issue
Anyone is able to change tokenHoldersMap
We highly recommend you to prevent the function calling from the outside. Otherwise anyone is able to change values of the map.
low Issues | 7 findings
Pending
#1 low Issue
Missing Zero Address Validation
We recommend you to check the zero address before setting the owner. Additionally we recommend you to add a renounceOwnership function here if you are going to check for the zero address.
Pending
#2 low Issue
Unused state variables
Remove unused state variables.
Pending
#3 low Issue
Missing Events Arithmetic
Emit an event for critical parameter changes.
Pending
#4 low Issue
Missing Zero Address Validation
Check that the address is not zero.
Pending
#5 low Issue
A floating pragma is set
The current pragma Solidity directive is „“>=0.8.0"".
Pending
#6 low Issue
State variables that could be declared immutable
Add the `immutable` attribute to state variables that never change or are set only in the constructor.
Pending
#7 low Issue
Remove SafeMath library
Since you are using pragma version above 0.8.x we recommend you to remove the library and replace functions with raw mathematical operations.
informational Issues | 2 findings
Pending
#1 informational Issue
State variables that could be declared constant
Add the `constant` attribute to state variables that never change.
Pending
#2 informational Issue
Wrong comment
1 hour is 3600 in seconds. In the require condition the contract is checking above 100 and lower/equal to 86400. We recommend you to change the value to 3600 or adjust the comment