Crypticorn Info
In today‘s dynamic and ever-evolving world of cryptocurrencies, seizing opportunities and maximizing profits requires cutting-edge tools and insights. We proudly present Crypticorn, a revolutionary cryptocurrency trading ecosystem that harnesses the power of artificial intelligence (AI) for accurate price predictions and an array of invaluable services. Our mission is to empower both active traders and passive investors with unparalleled opportunities for growth and success in the crypto market.
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.
TrustNet DataPulse
0x68777912fFCc93340F04eBCb58e9B53B2b4452D8
0x8E3F0b0b604bC69ea98A8039fF7884047bC3BD55
Data provided by We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!
We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.
In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.
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 can be burned
There is a function to burn tokens in the contract without any allowances.
Ownership is not renounced
Contract can be manipulated by owner functions.
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.
Contract Analysis
The Crypticorn token contract implements a deflationary ERC20 token with fee mechanisms for liquidity, marketing, and burning. While the overall design follows common patterns on BSC, a few areas need attention:
- The unconventional
_mintimplementation and burn parameter multiplication should be reviewed for clarity. - Reentrancy protections should be added around fee processing.
- Administrative functions would benefit from event logging to ensure transparency.
- Additionally, the contract does not support token locking, minting post-deployment, or blacklisting and restricts fees to a maximum of 10%, contrary to a potential claim of 25%.
Ownership Privileges
The ownership of the contract has not been renounced. The owner retains full privileges including:
- Enabling trading.
- Updating the threshold amount for fee processing.
- Setting buy and sell taxes (with a cap at 10% total fee).
- Updating the marketing wallet address.
- Managing fee exemption addresses (both individually and in bulk).
- Rescuing ETH and ERC20 tokens accidentally sent to the contract.
- Calling the burn function to reduce the token supply.
- Transferring or renouncing ownership.
Note - This Audit report consists of a security analysis of the Crypticorn 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 Crypticorn 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
/
Findings and Audit result
medium Issues | 1 findings
Resolved
#1 medium Issue
Lack of Reentrancy Protection in Fee Handling
The handle_fees function makes external calls to the router (for swapping tokens and adding liquidity) without employing a reentrancy guard.
optimization Issues | 2 findings
Acknowledged
#1 optimization Issue
Redundant Function Overrides
Functions such as approve, transferFrom, increaseAllowance, and decreaseAllowance are overridden in the main contract without adding any custom behavior, leading to unnecessary code duplication.
Acknowledged
#2 optimization Issue
Lack of Event Emission on Critical Updates
Administrative functions (e.g. updating threshold, fees, or the marketing wallet) do not emit events. This reduces on‑chain transparency for stakeholders monitoring key parameter changes.
informational Issues | 2 findings
Acknowledged
#1 informational Issue
Non‑Standard _mint Implementation
The _mint function assigns the balance directly without updating the _totalSupply. While acceptable in the constructor (given a fixed total supply), it deviates from standard ERC20 patterns and could lead to issues if additional minting were ever introduced.
Acknowledged
#2 informational Issue
Burn Function Multiplication Ambiguity
The burn function multiplies the input value by 10^decimals(), which may lead to unexpectedly large burns if the owner does not account for this factor.