VoxAI Info
VOX AI is a groundbreaking platform that combines voice-powered AI with advanced crypto management tools, simplifying portfolio tracking, trading, and market analysis. Whether interacting through Telegram or the dedicated VOX AI app, users can effortlessly manage their crypto assets, analyze market trends, and execute trades with precision. At the heart of VOX AI is the integration of cutting-edge features like the VOX DEX for seamless trading and a comprehensive charting tool for traders, positioning VOX AI as a leader in the evolving crypto ecosystem.
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.
Token transfer can be locked
Owner can lock user funds with owner functions.
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 whitelist addresses from fees and limits.
- The owner can set a minimum swap amount not less than 0.1% of the total supply.
- The owner can exempt wallets from limits.
- The owner can enable trading only once.
- The owner can update the max wallet amount to not less than 2% of the total supply.
- The owner can update the buy and sell taxes to not more than 5%.
- The owner can remove limits.
- The owner can toggle anti-mev feature.
- The owner can transfer tokens from the contract to specific destination.
- The owner can swap tokens manually.
- The owner can withdraw stuck ETH from the contract.
- The owner can withdraw tokens from the contract, including the contract's tokens.
Note - This Audit report consists of a security analysis of the VoxAI 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 VoxAI 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
medium Issues | 4 findings
Pending
#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
Missing 'require' check. (Potential honeypot)
The owner can set any arbitrary address to the development wallet address, excluding zero address as this can lead to a potential honeypot if the owner has set the address to a contract address that cannot receive ETH. It is recommended that the address cannot be set to a contract address that cannot receive ETH to avoid these circumstances.
Resolved
#3 medium Issue
Excessive Initial Tax Rates
The smart contract is configured to launch with prohibitively high initial buy and sell taxes of 30% each. This excessive rate is a significant deterrent for potential investors, as it creates an immediate and substantial loss on any trade. Such a high barrier to entry and exit can damage trust, discourage trading activity, and lead potential holders to suspect the project may be a "honeypot" where funds are easily trapped. This ultimately undermines the token's ability to establish a healthy, liquid market.
Pending
#4 medium Issue
Owner Can Drain All Tax Tokens, Bypassing Treasury Mechanism
The contract contains two distinct functions, rescueTokens and removeClog, that both serve as critical backdoors, granting the owner unilateral power to drain the entire balance of accumulated tax tokens. The rescueTokens function can be exploited by using the native token address as its parameter, while the removeClog function is explicitly designed to withdraw a percentage of the contract's tokens. Both functions allow the owner to send these funds to any wallet, completely bypassing the public swapTokensForETH mechanism that is intended to transparently manage project revenue. The presence of two such functions creates a severe and redundant centralization risk, making it trivial for a malicious or compromised owner to steal all project funds.
low Issues | 2 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing events arithmetic
Emit all the critical parameter changes.
informational Issues | 1 findings
Pending
#1 informational Issue
Function that are not used (Dead code).
Remove unused code.