CR7 AI Coin Info
Cr7 ai is more than just a typical ai chatbot. It’s a multi-phase initiative that begins with a subscription-based mvp (usd payments) for immediate premium access (text-only chat in the first release) and will later expand to voice capabilities. In parallel, we are developing the cr7 ai coin—a token designed to introduce community governance, rewards, and advanced features. Through this combination of ai innovation and token economics, we are building a dynamic ecosystem that can scale to a worldwide phenomenon.
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.
Security Assessments
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 enable trading only once.
- The owner can set the antibot blocks to not greater than 500.
- The owner can buy back and burn tokens manually.
- The owner can lock the tokens to the beneficiary address for a given release time.
- The user can release the locked amount.
- The owner can update the tax wallets.
- The owner can update the tax percentage to not more than 10%.
- The owner can exclude wallets from tax.
Note - This Audit report consists of a security analysis of the CR7 AI Coin 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 CR7 AI Coin 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
Findings and Audit result
medium Issues | 4 findings
Acknowledged
#1 medium Issue
Transfer of tokens without enabling trade.
The trading needs to be enabled by the owner in order for regular users to transfer tokens. On the contrary, the owner can authorize addresses manually and those addresses will be able to trade tokens. This functionality can be exploited in the following way, For example, there is a presale and the wallets used for the presale can be authorized by the owner. All the tokens obtained can be consolidated into a final wallet address and facilitate trading and selling of the acquired tokens, the last wallet address can be authorized.
Pending
#2 medium Issue
Centralized risk on vesting.
The setVesting function poses a centralization issue, as the owner has unilateral control over locking tokens, setting release times, and transferring tokens without beneficiary consent. This creates a trust dependency, where beneficiaries must rely entirely on the owner’s integrity, exposing them to risks of misuse or mismanagement, such as indefinite token locking or unfair allocations. To mitigate these risks, implementing a multi-signature wallet for ownership actions ensures decisions are collectively made. Adding beneficiary consent for vesting terms and emitting detailed events for transparency enhances accountability. Furthermore, preventing arbitrary extensions of release times once tokens are vested ensures immutable terms, reducing the potential for abuse and increasing trust in the contract.
Pending
#3 medium Issue
Manual buyback and burn
The buyback and burn process in the contract is executed manually by the owner via the buybackAndBurn function, which swaps tokens for BNB on a DEX and sends the BNB to a burn address. This approach raises centralization concerns, as the owner has exclusive control over execution, leading to potential delays, mismanagement, or lack of accountability. To mitigate these risks, automation should be implemented to trigger buyback and burn based on predefined conditions. Multi-signature control can enhance security, and detailed event emissions can improve transparency, ensuring token holders are informed about each buyback and burn action.
Resolved
#4 medium Issue
The owner can lock trading
The setTradingEnabled function allows the owner to enable or disable trading, posing centralization risks. Disabling trading halts all transactions except those involving the owner, which could disrupt liquidity, harm users financially, and damage trust. The lack of transparency or limitations on this control raises concerns about arbitrary or malicious use. To mitigate these risks, a time-lock mechanism can delay changes, providing users with notice. Alternatively, a governance-based or multi-signature approval process can decentralize control. Emitting clear events and maintaining transparency are crucial for ensuring user trust and accountability when exercising such critical functionality.
low Issues | 3 findings
Resolved
#1 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
#2 low Issue
Missing events arithmetic
It is recommended to emit all the critical parameter changes.
Acknowledged
#3 low Issue
Redundant code.
The setTaxPercents function has a redundant require statement. The first require checks if _totalTaxPercent is less than or equal to 10%, while the second ensures the subtaxes sum up to _totalTaxPercent. Since the second require already validates the total tax indirectly, the first check can be removed. Combining them into a single require makes the code more concise and gas-efficient.