Cheap GM Info

CheapGM is a fun, lightweight Web3 dApp where users say "GM" on-chain to earn XP, climb leaderboards, and get rewards. It’s simple, social, and powered by smart contracts with built-in referral payouts.

Cheap GM Logo

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.

47.08
Poor Excellent

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.

Security Assessments

Select the audit
"Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review"
Contract address
0x8F81...83f4
Network
Unichain Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2025/08/07
Revision date 2025/08/07

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 can set high fees

Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.

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:

  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 the treasury wallet address.
  • The owner can set the fees to any arbitrary value, excluding zero.
  • The owner can set the referral fees up to 99.99%. 

Note - This Audit report consists of a security analysis of the Cheap GM smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited the mentioned contract for the Cheap GM 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

/

Findings and Audit result

medium Issues | 2 findings

Acknowledged

#1 medium Issue
Owner Can Set Arbitrarily High Fees
GMCounter.sol
L90-93
L95-98
Description

The contract owner holds a centralized power to set the sayGM fee to any amount without an upper limit, as the setFee function only checks that the fee is not zero. This creates a significant risk: a malicious or compromised owner could make the application unusable by setting an extremely high fee, effectively blocking users.

Acknowledged

#2 medium Issue
Missing Non-reentrant check.
GMCounter.sol
L35-72
Description

The sayGM function contains a re-entrancy vulnerability because it does not follow the recommended Checks-Effects-Interactions security pattern. Specifically, it performs external calls to the referral and treasury addresses (the "Interactions") before all of its state changes (the "Effects") are completed. The totalGMs counter is only incremented on line 70, after the ETH transfers have already been made. If the referral address were a malicious smart contract, it could execute a callback to the sayGM function. While the check on lastGM would prevent a simple second "GM" from the same user, the re-entrant call would execute while the contract is in an inconsistent state (totalGMs would not yet be incremented), which is a dangerous anti-pattern that could be exploited in more complex scenarios.

low Issues | 1 findings

Acknowledged

#1 low Issue
Missing events arithmetic
GMCounter.sol
L85-88
L90-93
L95-98
Description

Emit all the critical parameter changes.

informational Issues | 1 findings

Acknowledged

#1 informational Issue
Floating pragma solidity version
GMCounter.sol
L2
Description

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.