GameM Info
GameM Global is a cutting-edge blockchain-powered GameFi ecosystem that seamlessly merges gaming, decentralized finance (DeFi), and blockchain technology into a unified platform. Designed for players, developers, and investors, it leverages Multi-dimensional Encryption Technology (MET) and the GameM Token (GMT) to ensure a secure, transparent, and scalable environment where every interaction—whether gaming, staking, or trading—is rewarded.
TrustNet Score
The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.
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.
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 burning within the contract without any allowances
Ownership is not renounced
The owner retains significant control, which could potentially be used to modify key contract parameters.
Contract is not upgradeable
The contract does not use proxy patterns or other mechanisms to allow future upgrades. Its behavior is locked in its current state.
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:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- 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 submit transactions for various operations through multisig. -
The owner can confirm transactions that have been submitted. -
The owner can revoke their confirmation for pending transactions. - The owner can submit a proposal to add a new owner.
- The owner can execute the addition of a new owner with multisig.
- The owner can execute the removal of an existing owner with multisig.
-
The owner can submit and add new owners through multisig approval. -
The owner can submit and remove existing owners through multisig approval. -
The owner can submit and transfer tokens to the private sale contract (13% of the total supply). - The owner can execute the private sale token transfer with multisig approval.
-
The owner can submit and transfer tokens to an airdrop (10% of the total supply). -
The owner can submit and transfer tokens to the farming pool (42% of the total supply). - The owner can execute an airdrop token transfer with multisig approval.
-
The owner can submit and transfer tokens to the liquidity pool (20% of the total supply). - The owner can execute liquidity pool token transfer with multisig approval.
-
The owner can submit and transfer tokens to the teamdex wallet (10% of total supply, vested over 25 months after a 2-year lock). - The owner can execute the teamdex token transfer with multisig approval.
-
The owner can submit and transfer tokens to a partner's wallet (5% of total supply, vested over 25 months after a 2-year lock). - The owner can execute a partner token transfer with multisig approval.
- The owner can submit a proposal to withdraw accumulated USDT from the contract.
-
The owner can submit and withdraw accumulated USDT from the contract.
Note - This Audit report consists of a security analysis of the GameM 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 GameM team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.
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
/
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
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 1 findings
Pending
#1 medium Issue
submitTransferPartners Function Issue.
The submitTransferPartners function incorrectly uses TEAM_DEX_CODE (value 4) instead of PARTNERS_CODE (value 5) when submitting the transaction. This mismatch will cause execution failures when attempting to call the corresponding TransferToPartners function, as that function specifically checks for PARTNERS_CODE. The code should be changed to use the correct functionality code. This will ensure that transactions submitted for partner token distribution can be properly executed by the TransferToPartners function.
informational Issues | 4 findings
Pending
#1 informational Issue
Floating pragma solidity version.
Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.
Pending
#2 informational Issue
Functions that are not used (dead-code).
Remove unused functions.
Pending
#3 informational Issue
Remove signedmath library.
The 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.The 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 informational Issue
Remove math library.
The 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.