Meta Tower Info

Meta Tower is not just a platform; it's a lifestyle and gaming revolution. Our mission is to empower people to forge new social connections, engage with top brands, and craft their very own digital universe, all while sharing these experiences both within and outside our metaverse.

Meta Tower Logo

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.

76.68
PoorExcellent

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

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Select the audit
Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0x0505...4436
Network
Polygon - Mumbai Testnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2024/02/23
Revision date In progress

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 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

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:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. 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 blacklist wallet addresses manually, and the addresses that are blacklisted will not be able to transfer their tokens.
  • The owner can authorize unauthorized addresses that can make transfers in the pre-listing phase. Moreover, it is also possible to enable/disable pre-listing phase at any time. Is it is done after the pre-listing time is over then the contract will be locked for normal users.

Note - This Audit report consists of a security analysis of the Meta Tower Token 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 Meta Tower team. Our team did not audit other contracts associated with the project. We recommend investors to do their research before investing.

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
Owner can Lock Funds
MetaTowerV2.sol
LL648
L660
Description

The owner can manually blacklist addresses from transferring their tokens. Moreover, it is also possible to enable/disable the pre-listing phase at any time. Thus, while the pre-listing phase is active, only the authorized addresses can transfer their tokens. So, in that case, if it is enabled after the trading starts for normal users then their funds would be locked.

low Issues | 2 findings

Pending

#1 low Issue
Local variables shadowing
MetaTowerV2.sol
L583
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Zero Address Validation
MetaTowerV2.sol
L641
Description

Check that the address is not zero and is valid.

informational Issues | 1 findings

Pending

#1 informational Issue
Functions that are not used
MetaTowerV2.sol
L118-120
L114-116
L399-404
Description

Remove unused functions.