XFactor Intelligence Info

Xfactor Intelligence, a revolutionary platform combines three core elements: Travel and Earn, SocialFi, and Payment Gateway. With XIN, travelling will be extremely flawless by the connect with a vibrant social community, experience secure and efficient payment solutions.

XFactor Intelligence 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.

15.27
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

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0xA935...876E
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2024/03/02
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 not renounced

The owner retains significant control, which could potentially be used to modify key contract parameters.

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
  • The owner can exclude/include wallets in rewards.
  • The owner can exclude/include wallets in fees.
  • The owner can update the dead wallet address.
  • The owner can update the charity wallet address.
  • The owner can update the dev fee wallet address.
  • The owner can update the sum of tax, burn, charity, and dev fees of not more than 25% in the contract.
  • The owner can update the max transaction amount of not more than 10000 tokens.
  • The owner can claim stuck tokens, including contract tokens.

Note - This Audit report consists of a security analysis of the XFactor Intelligent 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 XFactor Intelligent 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

low Issues | 3 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
XIN.sol
L452
L600
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Floating pragma solidity version
XIN.sol
L12
Description

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.

Pending

#3 low Issue
Remove safemath library
XIN.sol
L96-204
Description

The compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow. It is recommended to remove the unwanted code in order to avoid high gas fees.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
XIN.sol
L394
L392
L393
L388
Description

Add the `constant` attributes to state variables that never change.

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
XIN.sol
L245-248
L254-258
L425-427
L429-431
L433-435
L437-439
L447-450
L452-454
L456-459
L461-465
L467-470
L472-475
L477-479
L481-483
L485-494
L528-530
L532-534
L596-598
Description

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