- Home
- Security Audits
- Investax
Web3 · Smart Contract Audit
Investax Security Audits
softstack has completed 2 smart contract audits for Investax between September 2022 and June 2023, reporting 11 findings in total (2 medium, 3 low and 6 informational). Every report is published in the softstack public audit archive.
Key facts
- Client
- Investax
- Audits completed
- 2
- First audited
- Latest audit
- Chains
- Ethereum
- Languages
- Solidity
About the project
InvestaX is a Singapore platform for tokenising real-world assets and issuing digital securities, operated by IC SG Pte. Ltd. It holds a Capital Markets Services licence from the Monetary Authority of Singapore and is a recognised market operator, covering both issuance and secondary trading. Its offerings include tokenised funds and vaults backed by corporate bonds and treasury instruments.
Findings
Combined across all 2 reviews softstack has completed for Investax. Each report is broken out below.
Reports
Newest first. Every report covers its own scope and commit.
Primary Issuer smart contract audit
0Critical0High2Medium2Low4InformationalScope
Source repositorygithub.com/IX-Swap/ixs-primary-issuer-contractsComponents reviewed
1 module- See the published report for the file list
All 7 findings
ID Title Severity Status 6.2.2Misuse of Low-Level Calls The contract uses send() function for transferring Ether. The send() function only forwards 2300 gas which might not be sufficient after the EIP-1884 update, where gas cost for certain operations was increased.
Medium fixed 6.2.3Excessive Permissions For Certain Functions There are functions which are only restricted by the OPERATOR_ROLE, which can execute critical functionality such as adding or removing from whitelist, forceWithdraw, forceFinalize.
Low acknowledged 6.2.4Misleading Function Naming The function getAmountOut might be misleading since it doesn't actually get an amount out. Instead, it calculates and returns an output amount based on an input amount and a conversion rate.
Low fixed 6.2.5Floating Compiler Version The current pragma Solidity directive is floating. It is recommended to specify a fixed compiler version to ensure that the bytecode produced does not vary between builds.
Informational fixed 6.2.6Missing Natspec Documentation The Solidity contract does not include Natspec documentation, which is a special form of comments used to provide rich documentation for functions, return variables, and other contract elements.
Informational acknowledged 6.2.7No Event Emitted After Changing Role The contract code does not emit an event when the operator role has been changed. While this is not a security issue per se, it's a good practice to do so.
Informational acknowledged 6.2.8Unexpected Behavior of Whitelist Functions The current implementation of addToWhitelist and removeFromWhitelist in XTokenLightDistributionController contract can have some unexpected behavior.
Informational acknowledged IXAPE Token smart contract audit
0Critical0High0Medium1Low2InformationalScope
Source repositorygithub.com/InvestaX/x-token-liteComponents reviewed
1 module · 1 file- InvestaAdmin.sol
All 2 findings
ID Title Severity Status 6.2.1Extensive Owner/Trustee Rights Code Snippet Result/Recommendation The trustee has extensive rights, which effects the owner role. The auditor has recognized kind of role Line: 57 – 81 ( /** * @dev Assigns or changes the trustee wallet.
Low fixed 6.2.2Interface Folder Structure Code Snippet Result/Recommendation The project structure should contain an extra folder for interfaces. NA It is recommended to move the interface into a separate folder called interfaces.
Informational wont-fix
About this engagement
A smart contract audit reviews on-chain code for flaws an attacker could exploit. Engineers trace how assets move through the contracts, check who can call privileged functions, and test the arithmetic, external calls and upgrade paths. Each finding is rated by severity, and fixes are re-checked before the final report.
How softstack runs smart contract auditsMethodology
Review process
Scoping and threat modelling
The commit hash is frozen and the attack surface is mapped: asset flows, trust assumptions, privileged roles and the external systems the code depends on.
Automated analysis
Static analysers sweep the full codebase to surface known weakness patterns, unreachable states and deviations from established conventions.
Manual code review
Independent engineers read the code line by line, concentrating on business logic, access control, arithmetic and the handling of external calls.
Adversarial testing
Property-based fuzzing and invariant tests attack the assumptions the protocol relies on, targeting states that ordinary unit tests never reach.
Reporting
Every finding is documented with a severity rating, its impact, the steps to reproduce it and a concrete remediation the team can act on.
Remediation verification
Submitted fixes are re-reviewed against the original finding, and the final report records the resolved state of each one.
Standards and references
- SWC RegistrySmart Contract Weakness Classification
- CWECommon Weakness Enumeration
FAQ
Investax was audited by softstack GmbH, a German Web3 security and software company based in Flensburg and certified to ISO/IEC 27001 by TÜV SÜD. softstack has completed 2 smart contract audits for Investax between September 2022 and June 2023. The published reports are linked on this page and in the softstack public audit archive.
2 separate reviews, the first in September 2022 and the most recent in June 2023. Each one covers its own scope and commit, and is listed individually on this page.
11 findings across all 2 reviews: 2 medium, 3 low and 6 informational.
Each report covers the code as it stood at the commit it names, the most recent in June 2023. Any code changed after that point is outside the reviewed scope.
Related audits
Browse all security auditsDisclaimer
This audit represents a point-in-time security assessment of the reviewed codebase and is intended for informational purposes only. While Softstack applies industry-standard security review methodologies, no audit can guarantee the absence of vulnerabilities, bugs, or other security risks. This report does not constitute financial, legal, regulatory, or investment advice, nor does it endorse the project, its business model, products, or services. Security is an ongoing process, and we strongly recommend conducting a new assessment following any material code changes or at least every 6 months to address newly emerging threats, vulnerabilities, and ecosystem developments.