Meta Tower
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.
Owner privileges
Comments
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.
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
31
State variables
public
3
Total lines
of code
663
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.
medium Issues
Pending
#1 Issue
Owner can Lock Funds
LL648
L660
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
Pending
#1 Issue
Local variables shadowing
L583
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Zero Address Validation
L641
Check that the address is not zero and is valid.
informational Issues
Pending
#1 Issue
Functions that are not used
L118-120
L114-116
L399-404
Remove unused functions.
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.