IXS Launchpad Info

IX Swap is the Uniswap for RWA and bridges the gap between traditional finance and decentralized finance by offering a regulated and innovative platform for trading tokenized Real-World Assets.

IXS Launchpad 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.

8.83
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
N/A
Network N/A
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2025/05/27
Revision date 2025/05/27

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:

  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.


Forked Status
  • The IXS V2 monorepo system, including its core reward function and associated functionalities, is a direct fork of Balancer Labs.

The codebase for the original Balancer Labs contracts can be accessed here:

https://github.com/balancer/balancer-v2-monorepo/tree/master/pkg

Note - This Audit report consists of a security analysis of the IXS Launchpad smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited the mentioned contract for the IXS Launchpad team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing. Moreover, any vulnerabilities or issues inherent in the original Velodrome Finance contracts may also be present in this implementation. 

Files and details

Findings and Audit result

low Issues | 3 findings

Pending

#1 low Issue
Old complier version
All
L2
Description

Adding the latest constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.

Pending

#2 low Issue
Missing zero or dead address check.
PoolFees.sol
L41-43
L155-169
L175-182
Description

Check that the address cannot be zero or dead.

Pending

#3 low Issue
Missing zero or dead address check.
RWARegistry.sol
L65-71
Description

Check that the address cannot be zero or dead.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Potential Gas Exhaustion (DoS) in isRwaBatchSwap
RWARegistry.sol
L81-105
Description

The isRwaBatchSwap function in RwaRegistry.sol is susceptible to a potential gas exhaustion Denial-of-Service (DoS) attack. This vulnerability arises because the function iterates through the swaps array (provided as calldata) using a for loop (for (uint256 i = 0; i < swaps.length; ++i)) to check each swap leg. If an attacker or even a user unintentionally provides an excessively long swaps array, the gas required to execute this loop could surpass the block gas limit.

informational Issues | 1 findings

Pending

#1 informational Issue
Missing Non-reentrant check.
PoolFees.sol
L117-128
L133-138
L155-169
Description

The PoolFees.sol contract mitigates reentrancy in its fee-claiming functions by using the Checks-Effects-Interactions pattern: it updates internal balances before making external calls to transfer tokens. This prevents typical reentrancy attacks. For enhanced security, adding a ReentrancyGuard (like OpenZeppelin's) to these functions would provide an explicit lock against re-entry, offering defense in depth. However, existing linter errors related to compiler version and import paths must be resolved first to ensure the contract can be correctly compiled and analyzed.