ICOPAX Info
ICOPAX is a decentralized trading platform built natively for Telegram. No KYC, no downloads, no unnecessary steps. Just fast, secure, and permissionless trading in the environment users already know. With ICOPAX, users can swap tokens directly inside Telegram, challenge others in 1v1 token battles to win $IPAX, and access perpetual futures with 0% fees when paying with IPAX. The platform also offers copy trading from top traders, competitive Battle Royale trading tournaments, and a task and referral system designed to reward user activity and growth. ICOPAX is built to make crypto trading simpler, more affordable, and fully in the hands of users. By combining DeFi principles with a lightweight Telegram-based interface, it removes the friction that often blocks adoption. Whether you’re a pro trader or just exploring the space, ICOPAX gives you the tools to trade confidently and effortlessly.
Team and KYC Verification
The KYC verification for this project is currently in progress.
The team has submitted their information and verification is pending.
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 renounced
The contract does not include owner functions that allow post-deployment modifications.
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 ownership of the contract is renounced. Hence, the owner cannot make any changes in the contract's settings.
Note - This Audit report consists of a security analysis of the ICOPAX 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 ICOPAX 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
high Issues | 1 findings
Resolved
#1 high Issue
Owner's Unilateral Authority to Burn Tokens from Any Account.
The burn function is protected by the onlyOwner modifier, which allows the contract owner to destroy tokens from any user's wallet by simply providing their address and an amount. This function does not require any prior approval or allowance from the token holder, giving the owner unchecked power to reduce any user's balance to zero. This capability represents a severe centralization risk and fundamentally undermines the principles of self-custody and trust. A malicious or compromised owner could selectively or indiscriminately burn user tokens, leading to a direct and irreversible loss of funds for the holders.
medium Issues | 1 findings
Resolved
#1 medium Issue
The owner can pause token transfer.
The smart contract grants the owner the exclusive and unrestricted ability to pause all token transfers at any time by calling the pause() function. This functionality is controlled by the onlyOwner modifier, centralizing a critical operational control into a single address. While intended as a security feature for emergencies, this creates a significant risk. If the owner's account is compromised, or if the owner acts maliciously or loses access to their keys, the token transfers could be frozen indefinitely. This would trap all user funds within the contract, making them untransferable and effectively useless.
informational Issues | 1 findings
Acknowledged
#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.