XRender AI Info

XRender AI deployed on a platform that supports all EVM and Non-EVM blockchains. The XRender platform offers users the best on-chain and cross-chain experience.

XRender AI Logo

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.

72.57
Poor Excellent

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

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x617B...8AD1
Network
Arbitrum - Testnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/10/10
Revision date In progress

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.

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:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. 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 (Not Applicable after Renouncement)
  • The owner can exclude/include wallets from the max buy/sell and fee whitelist.
  • The owner can set buy and sell fees up to 100% or more as there are no restrictions.
  • The owner can enable/disable antibot.
  • The owner can claim the stuck tokens.
  • The owner can change the LP address
  • The owner can change the anti bot start/end time

Note - This Audit report consists of a security analysis of the XRender AI Token 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 XRender AI  team. Our team did not audit other contracts associated with the project. We recommend investors to do their 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 | 2 findings

Resolved

#1 medium Issue
The owner can set fees upto 100%.
XRenderAI.sol
L979
L983
Description

The owner can lock the user funds by setting the fees above 100%. When the tax is subtracted from the amount, the fees will be higher than the amount. The TX will be reverted then.

Resolved

#2 medium Issue
Owner can Lock Tokens
XRenderAI.sol
L950
L955
Description

The owner can set the maximum buy and sell token amount to an arbitrary value. For example, if the owner decides to set these values to zero then no user will be able to buy/sell the tokens.

low Issues | 1 findings

Pending

#1 low Issue
Missing Events
XRenderAI.sol
L979-981
L983-985
Description

Emitting events are necessary for any critical parameter change in the contract. The events are necessary to track the state changes in the contract, which increases the transparency.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external
XRenderAI.sol
L203-205
L211-213
L235-237
L242-244
L254-258
L277-281
L299-308
L322-326
L342-351
L539-541
L554-557
L612-614
L620-623
L975-977
L979-981
L983-985
Description

Use the `external` attribute for functions never called from the contract.

informational Issues | 2 findings

Pending

#1 informational Issue
Functions that are not used
XRenderAI.sol
L144-146
L723-725
L821-830
L781-783
L847-856
L798-807
L652-658
L694-699
L706-711
L677-687
L665-670
Description

The Functions that are present in the code but are not used (called) anywhere are considered as "Dead-Code" and we recommend removing them as it decreases the lines of code and increases readability.

Pending

#2 informational Issue
Function initializing state variables
XRenderAI.sol
L862
L865
L866
Description

Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.