Project overview - MYLA Metaverse

Type ERC20/BEP20
Language Solidity
Request date 2022/10/28
Latest Revision date 2022/11/11
Description

We have as mission to bring source of income and entertainment for all audiences, we believe that a game of E-sports within the Blockchain need to be more than just a game where you earn money with virtually no effort in a way unsustainable with a minimum longevity, we have as a major goal to develop one of the largest multiverse projects that the Blockchain has ever seen and at the same time please all tastes and please investors and players of the Blockchain market, creating bridges facilitators for all possible audiences.

Price Chart

Audit Summary

Static analysis Dynamic analysis Symbolic Execution SWC check
Network Binance Smart Chain
License & Compiler MIT / v0.8.7+commit.e28d00a7
Contract address 0x3914AE3E50480600921b66e3D7f6356870f6d9AC
No critical 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's not possible to mint new tokens.
Contract owner cannot blacklist addresses. It's not possible to lock user funds by blacklisting addresses.
Contract owner cannot set fees above 25% The fees can be a maximum of 25%. The contract can therefore not be locked.
Contract cannot be locked Owner can't lock any user funds.
Token cannot be burned There is no burn function within the contract.
Ownership is not renounced Contract can be manipulated by owner functions.
C
Critical
No Issues found.
H
High
No Issues found.
M
Medium
No Issues found.
L
Low
3 Issues found. 0 resolved.
I
Informational
4 Issues found. 0 resolved.
O
Optimization
3 Issues found. 0 resolved.
Comment

Ownership Privileges:

  • Exempt accounts from fees and also exempt the fee receiver
  • Set developing wallet addreses
  • Set buy back and hold, but back and hold with decimals, buy back and burn to any arbitrary amount
  • Set WBNB/TOKEN, WBNB/BUSD, pair

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)
The auditing process follows a routine series of steps:
  • 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.

Public functions Public state variables Total lines of code Capabilities
6 2 54

Public functions Public state variables Total lines of code Capabilities
0 0 23

Public functions Public state variables Total lines of code Capabilities
11 0 355

Public functions Public state variables Total lines of code Capabilities
6 0 81

Public functions Public state variables Total lines of code Capabilities
3 0 27

Public functions Public state variables Total lines of code Capabilities
2 0 10

Public functions Public state variables Total lines of code Capabilities
2 0 10

Public functions Public state variables Total lines of code Capabilities
3 0 71

Public functions Public state variables Total lines of code Capabilities
0 0 66

Public functions Public state variables Total lines of code Capabilities
2 0 14

Public functions Public state variables Total lines of code Capabilities
17 10 316

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.

#1 | Missing Zero Address Validation (missing-zero-check)
Severity Location Status
Low MYLA.sol : 65, 66, 311, 312 Pending
Description

Check that the address is not zero.

#2 | Missing Events
Severity Location Status
Low MYLA.sol : All Pending
Description

Emit Events for critical parameter changes. Moreover, there are no events in the cotnract

#3 | Floating Pragma
Severity Location Status
Low MYLA.sol : - Pending
Description

The current pragma Solidity directive is “^0.8.5". 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.

#1 | Functions that are not used (dead-code)
Severity Location Status
Informational Context.sol : 20-22, 20-22 Pending
Description

Remove unused functions.

#2 | Functions that are not used (dead-code)
Severity Location Status
Informational Strings.sol : 39-50, 55-65, 14-34 Pending
Description

Remove unused functions.

#3 | Functions that are not used (dead-code)
Severity Location Status
Informational ERC20.sol : 274-289, 251-261 Pending
Description

Remove unused functions.

#6 | Unused state variables (unused-state)
Severity Location Status
Informational MYLA.sol : 13 Pending
Description

Remove unused state variables.

#1 | Public function that could be declared external (external-function)
Severity Location Status
Optimization Ownable.sol : 53-55, 61-64 Pending
Description

Use the `external` attribute for functions never called from the contract.

#2 | Public function that could be declared external (external-function)
Severity Location Status
Optimization MYLA.sol : 61, 62, 65, 66 Pending
Description

Use the `external` attribute for functions never called from the contract.

#3 | Public function that could be declared external (external-function)
Severity Location Status
Optimization ERC20.sol : 61-63, 69-71, 86-88, 93-95, 100-102, 112-115, 120-122, 131-134, 149-163, 177-180, 196-204 Pending
Description

Use the `external` attribute for functions never called from the contract.

Diagrams

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.