Monoland Info
Monoland is a revolutionary project that bridges the exciting world of real-world assets (RWA) with the immersive, playful nature of the metaverse. Designed as a fun and gamified experience, Monoland brings the concept of Monopoly to life, where users can own, play, and profit from virtual land and real-world assets. In Monoland, every piece of land is unique, just like the rare Mono token that powers the ecosystem, and users can turn their in-game experiences into real-world rewards
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.
TrustNet DataPulse
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 can blacklist addresses
It is possible to lock user funds by blacklisting addresses.
Contract owner can set high fees
Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.
Token transfer can be locked
Owner can lock user funds with owner functions.
Token cannot be burned
There is no burn function within the contract.
Ownership is not renounced
Contract can be manipulated by owner functions.
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
- The owner can add/remove the liquidity minter.
- The owner can add/remove the farming minter .
- The owner can set a fee receiver address.
- The owner can add/remove the blacklist the wallet.
- The owner can burn his tokens.
- The owner can set anti-whale.
- The owner can set buy/sell cooldown duration.
- The owner can set the max buy/sell amount.
- The owner can set the liquidity pair.
- The owner can add/remove multiple addresses from the whitelist.
- The owner can get the liquidity/farmingminter/feereceiver addresses.
- The owner can set a buy/sell fee of more than 100%.
Note - This Audit report consists of a security analysis of the Monoland 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 Monoland team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 4 findings
Pending
#1 medium Issue
Missing ‘require’ check (Potential honeypot).
The owner can set any arbitrary address to the fee receiver address, Including zero address as this can lead to a potential honeypot if the owner has set the address to a contract address that cannot receive ETH. It is recommended that the address cannot be set to a contract address that cannot receive ETH to avoid these circumstances.
Pending
#2 medium Issue
The owner can blacklist wallets.
The owner can blacklist wallets from transferring tokens for an unlimited period of time which is not recommended as this can lock the user's funds indefinitely. There must be a locking period in the contract so that the user should not be locked for an unlimited period of time.
Pending
#3 medium Issue
The owner can lock funds.
The owner can set any arbitrary amount in the max buy and max sell amount, including zero, which is not recommended as this can lock the transfer function for an unlimited period of time. There must be a threshold amount so that the amount cannot be set to zero. Add a 'require' check in the contract so that the amount cannot be less than at least 0.1% of the total supply of tokens.
Pending
#4 medium Issue
The owner can set fees more than 25%.
The owner can set buy and sell fees of more than 100% in the contract, which is not recommended. The fees in the contract should be no more than 25% so that the user does not lose his token values.
low Issues | 4 findings
Pending
#1 low Issue
Floating pragma solidity version.
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.
Pending
#2 low Issue
Remove safemath library.
The compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow. It is recommended to remove the unwanted code in order to avoid high gas fees.
Pending
#3 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#4 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
optimization Issues | 1 findings
Pending
#1 optimization Issue
Public function that could be declared external (external-function).
Use the `external` attribute for functions never called from the contract.
informational Issues | 2 findings
Pending
#1 informational Issue
Remove unused functions.
Functions that are not used (dead code).
Pending
#2 informational Issue
Remove unused functions.
Functions that are not used (dead code).