GamoFi Info

gamofi.io

Gamofi is a no-code video game maker that empowers a non-tech, non-gamer audience to create, share & monetize their own video games with no code and at lightning speed. Everyone can create snackable games for entertainment, educational, marketing, and training purposes with ease.

Overall Score
63.40
Poor Excellent
GamoFi 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.

On-Chain Insights

Smart Contract Audit

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x37A9...2B4A
Network
Ethereum - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/12/03
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.

Token transfer can be locked

Owner can lock user funds with owner functions.

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
  • The owner can set buy and sell fees of not more than 25%.
  • The owner can update the value in the max transaction and max wallet amount, which will lock the contract if the value is set to zero.
  • The owner can set a swap threshold percent that cannot be more than 10000, which means the maximum swap threshold value can be set up to the total supply of the contract.
  • The owner can remove the limits from the contract.
  • The owner can enable/disable Transfer delay.
  •  The owner can claim stuck tokens and ETH from the contract. Also, The owner can claim the contract's tokens from the contract.
  • The owner can enable trading only once.

Note - This Audit report consists of a security analysis of the GamoFi 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 GamoFi team, other contracts associated with the project were not audited by our team. We recommend investors to do their own 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 | 2 findings

Pending

#1 medium Issue
Liquidity is added to external owner account
GAMO.sol
L605-640
Description

The contract's liquidity is automatically added to the 'owner' address, which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.

Pending

#2 medium Issue
The owner can lock contract
GAMO.sol
L522-537
Description

The owner can update the value in the max transaction and max wallet amount, which will lock the contract if it is set to zero. It is recommended to add the 'require' check so that the value cannot be less than that particular amount present in the contract.

low Issues | 4 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
GAMO.sol
L382
L416
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Dangerous usage of `tx.origin` (tx-origin)
GAMO.sol
L429-478
Description

Do not use `tx.origin` for authorization.

Pending

#3 low Issue
Remove safemath library.
GAMO.sol
L87-160
Description

Compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow. It is recommended to remove the unwanted code in order to avoid high gas fees.

Pending

#4 low Issue
Owner can claim contract's own tokens.
GAMO.sol
L590-598
Description

The owner can claim the stuck tokens including contract's own tokens from the contract which is not recommended. There must be a 'require' check so that the owner cannot claim the contract's token form the contract.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
GAMO.sol
L198-201
L328-330
L336-338
L344-346
L352-354
L371-374
L382-384
L392-395
L404-408
Description

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