MYLA Metaverse Info

mylametaverse.com

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.

Overall Score
88.44
Poor Excellent
MYLA Metaverse Logo

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

Smart Contract Audit

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x3914...d9AC
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2022/11/11
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 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 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:

  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:

  • 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

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

low Issues | 3 findings

Pending

#1 low Issue
Missing Zero Address Validation (missing-zero-check)
MYLA.sol
L65
L66
L311
L312
Description

Check that the address is not zero.

Pending

#2 low Issue
Missing Events
MYLA.sol
All
Description

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

Pending

#3 low Issue
Floating Pragma
MYLA.sol
-
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.

optimization Issues | 3 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
Ownable.sol
L53-55
L61-64
Description

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

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
MYLA.sol
L61
L62
L65
L66
Description

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

Pending

#3 optimization Issue
Public function that could be declared external (external-function)
ERC20.sol
L61-63
L69-71
L86-88
L93-95
L100-102
L112-115
L120-122
L131-134
L149-163
L177-180
L196-204
Description

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

informational Issues | 4 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
Context.sol
L20-22
L20-22
Description

Remove unused functions.

Pending

#2 informational Issue
Functions that are not used (dead-code)
Strings.sol
L39-50
L55-65
L14-34
Description

Remove unused functions.

Pending

#3 informational Issue
Functions that are not used (dead-code)
ERC20.sol
L274-289
L251-261
Description

Remove unused functions.

Pending

#4 informational Issue
Unused state variables (unused-state)
MYLA.sol
L13
Description

Remove unused state variables.