Charlie Unicorn AI Info
In the ever-evolving world of Web3, Charlie Unicorn AI introduces The Entertainment Ecosystem that integrates Artificial Intelligence, DeFi, Game-Fi. Designed for full transparency and regulatory compliance within the European Union restrictions. Charlie Unicorn AI plans to obtain a CASP license to ensure full compliance with MiCA regulations regarding crypto-asset service providers.
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.
Ownership Privileges
- The owner can pause the function.
- The owner can start/strop claim function.
- The owner can change Hashed SK.
- The owner can update the swap enabled.
- The owner can update the max purchase.
- The owner can change the payment wallet.
- The owner can update the token.
- The owner can change the USDT/USDC Interface.
- The owner can update the stage price.
- The owner can set the current stage.
- The owner can update the stage supply.
- The owner can transfer the ownership.
- The owner can rescue funds.
- The owner can buy from TON.
- The owner can rescue tokens.
Note - This Audit report consists of a security analysis of the Charlie Unicorn 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 Charlie Unicorn 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
/
Findings and Audit result
medium Issues | 5 findings
Pending
#1 medium Issue
The owner can lock claim.
The contract contains the functionality in which the owner of the contract can lock the claiming functionality in the contract for an indefinite period of time, which can lock the user funds in the contract. There must be a check where the claiming functionality should not be locked permanently in the contract.
Resolved
#2 medium Issue
The owner can lock the contract.
The contract imports the pausable contract through which the owner of the contract can pause the token transfer for the indefinite period of time.
Resolved
#3 medium Issue
Missing ‘NonReentrant’ check.
The contract imports the reentrancy guard in the contract but the staking or un-staking function does not have the reentrancy guard check. It is recommended to add the check-in function to avoid any reentrancy issues in the contract.
Resolved
#4 medium Issue
Missing threshold for Max purchase.
The contract contains the functionality in which the admin of the contract can update any arbitrary value in the max purchase amount, including zero, which can lock the swapping functionality in the contract if the value is set to zero. There must be a threshold limit so that the value will lie at that range to exclude this risk from the contract.
Resolved
#5 medium Issue
Cannot be changed during Mid-Sale.
The owner can modify crucial sale parameters—pricing, token supply, or stage—while the sale is in progress. Doing so can cause confusion among buyers expecting the original rate, potentially leading to mismatch in token allocations or severe disruptions in user trust. If the stage or price changes unexpectedly, purchasers might pay incorrect amounts for tokens. Similarly, adjusting the supply mid-sale could cause overselling or unexpected shortages. Transferring ownership unexpectedly can also expose the contract to malicious actions if the new owner changes parameters unfairly. These issues can undermine the sale’s overall transparency and fairness.
low Issues | 3 findings
Pending
#1 low Issue
Missing events arithmetic.
It is recommended to emit all the critical parameter changes.
Resolved
#2 low 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.
Resolved
#3 low Issue
Missing zero or dead address check.
It is recommended to check that the address cannot be set to zero or dead address.
informational Issues | 1 findings
Resolved
#1 informational Issue
Public function should be an internal function.
By changing the function’s visibility to internal, we limit who can invoke it, ensuring that only contract functions can update the ETH price. This prevents external callers from spamming or manipulating the price feed unnecessarily.