Eternis Death Match

Smart Contract Audit Report

Eternis Death Match Audit Report

Executive Summary

This report presents the outcomes of our collaborative engagement with the Eternis Death Match team, focusing on the comprehensive evaluation of the MyToken contract.

Our team conducted an initial security assessment from July 23rd to July 25th, 2024.

Eternis Death Match is developing a new ERC-20 token that allows users to lock tokens in the contract for any specified number of days.


Audit Scope

Name

Source Code

Visualized

MyToken

3b99ef3

Inheritance Chart.  Function Graph.

Name

Address/Source Code

Visualized

MyToken

3b99ef3

Inheritance Chart.  Function Graph.


Audit Findings

An Informational finding was identified and the team may want to review it.

Finding #1

MyToken

Informational Open

Finding #1 - MyToken
Informational Open

Description: The MyToken contract inherits the Ownable contract however, no owner-restricted functions are present.

Recommendation: The Ownable contract could be removed to reduce contract size and deployment costs.


System Overview

TOKEN ATTRIBUTES

The initial supply of the token is set by the deployer and is minted to the specified initial owner address. No mint functions are accessible beyond deployment. Any user can burn their own tokens to reduce the total supply at any time.

The contract complies with the ERC-20 standard. As the contract is implemented with Solidity v0.8.x, it is protected from overflows/underflows.

STAKING

Any user can initiate a stake at any time by specifying a number of tokens to transfer to the contract and a desired stake duration in days. Each individual stake is recorded in the platform on behalf of the caller's address.

Any user who has previously staked tokens can reclaim their tokens by specifying a valid stake ID, provided the associated end time has been reached. The original stake amount is transferred from the contract to the caller's address. There is no logic included for distributing rewards within the contract.


Vulnerability Analysis

Vulnerability Category Notes Result
Arbitrary Jump/Storage Write N/A PASS
Centralization of Control N/A PASS
Compiler Issues N/A PASS
Delegate Call to Untrusted Contract N/A PASS
Dependence on Predictable Variables N/A PASS
Ether/Token Theft N/A PASS
Flash Loans N/A PASS
Front Running N/A PASS
Improper Events N/A PASS
Improper Authorization Scheme N/A PASS
Integer Over/Underflow N/A PASS
Logical Issues N/A PASS
Oracle Issues N/A PASS
Outdated Compiler Version N/A PASS
Race Conditions N/A PASS
Reentrancy N/A PASS
Signature Issues N/A PASS
Sybil Attack N/A PASS
Unbounded Loops N/A PASS
Unused Code The MyToken contract inherits the Ownable contract however, no owner-restricted functions are present. PASS
Overall Contract Safety   PASS

About SourceHat

SourceHat has quickly grown to have one of the most experienced and well-equipped smart contract auditing teams in the industry. Our team has conducted 1800+ solidity smart contract audits covering all major project types and protocols, securing a total of over $50 billion U.S. dollars in on-chain value!
Our firm is well-reputed in the community and is trusted as a top smart contract auditing company for the review of solidity code, no matter how complex. Our team of experienced solidity smart contract auditors performs audits for tokens, NFTs, crowdsales, marketplaces, gambling games, financial protocols, and more!

Contact us today to get a free quote for a smart contract audit of your project!

What is a SourceHat Audit?

Typically, a smart contract audit is a comprehensive review process designed to discover logical errors, security vulnerabilities, and optimization opportunities within code. A SourceHat Audit takes this a step further by verifying economic logic to ensure the stability of smart contracts and highlighting privileged functionality to create a report that is easy to understand for developers and community members alike.

How Do I Interpret the Findings?

Each of our Findings will be labeled with a Severity level. We always recommend the team resolve High, Medium, and Low severity findings prior to deploying the code to the mainnet. Here is a breakdown on what each Severity level means for the project:

  • High severity indicates that the issue puts a large number of users' funds at risk and has a high probability of exploitation, or the smart contract contains serious logical issues which can prevent the code from operating as intended.
  • Medium severity issues are those which place at least some users' funds at risk and has a medium to high probability of exploitation.
  • Low severity issues have a relatively minor risk association; these issues have a low probability of occurring or may have a minimal impact.
  • Informational issues pose no immediate risk, but inform the project team of opportunities for gas optimizations and following smart contract security best practices.