TAPZI Info
Tapzi replaces randomness with real strategy — where skill determines success, not luck. The better player wins. Always. But we're more than just a gaming platform… Tapzi is also a launchpad for the next generation of Web3 skill-based games — empowering game studios and developers to publish, integrate token staking, and reach a global competitive audience. Join the protocol where skills create value and where new games thrive.
Team and KYC Verification
The team has securely submitted their personal information to SolidProof.io for verification.
In the event of any fraudulent activities, this information will be promptly reported to the relevant authorities to ensure accountability and compliance.
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.
Smart Contract Analysis Statement
Contract Analysis
The TAPZI contract implements an ERC20 token with trading control mechanisms for preventing early trading, owner-controlled exclusions, and one-time trading activation. While the overall design follows common patterns on Ethereum, a few areas need attention:
- The hardcoded owner address in the constructor should be reviewed for clarity during deployment coordination.
-
The excludeFromEnable function serves its intended purpose for pre-launch operations and becomes inactive post-launch.
- Additionally, the contract does not support burning, minting post-deployment, or fee mechanisms and restricts blacklisting functionality to trading exclusions only.
Ownership Privileges
The ownership of the contract has been hardcoded to a specific address. The owner retains full privileges including:
- Enable trading permanently (one-time action).
-
Exclude or include addresses from pre-launch trading restrictions (inactive post-launch).
- Transfer ownership to another address.
- Renounce ownership (making the contract ownerless).
- No ability to mint additional tokens.
- No ability to burn tokens from any address.
- No ability to pause or disable trading once enabled.
- No ability to set fees or taxes on transfers.
Security Features
The contract implements several positive security features:
- Trading cannot be disabled once enabled, preventing honeypot behavior.
- Uses custom errors for gas efficiency and better error handling.
- Fixed total supply with no additional minting capability.
- Proper inheritance from OpenZeppelin's battle-tested contracts.
Note - This Audit report consists of a security analysis of the TAPZI smart contract. This analysis did not include economic analysis of the contract's tokenomics. Moreover, we only audited the main contract for the TAPZI 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
optimization Issues | 1 findings
Pending
#1 optimization Issue
Gas optimization opportunity
The boolean logic 'isExcludedFromEnable[from] || isExcludedFromEnable[to]' could be optimized by checking the cheaper condition first or caching the mapping lookups if used multiple times.
informational Issues | 2 findings
Acknowledged
#1 informational Issue
Hardcoded owner address in constructor
The contract hardcodes the owner address (0x497990860D2448dc475DCc1496309C1883cd214b) directly in the Ownable constructor. While ownership can be transferred later, this approach requires careful coordination during deployment to ensure the intended owner receives control.
Acknowledged
#2 informational Issue
Pre-launch exclusion mechanism
The isExcludedFromEnable mapping only functions before trading is enabled, allowing specific addresses (deployer, liquidity setup) to operate during deployment. Once enableTrading() is called, this exclusion mechanism becomes inactive and cannot be used to restrict any user's ability to trade.