Luminex Defi Finance Info

Luminex DeFi Finance is a decentralized finance protocol focused on enabling stable value digital asset transfers, swaps, and cross-chain interoperability across supported blockchain networks. At the core of the protocol is LFUSD, a stablecoin designed to facilitate predictable value exchange and efficient on-chain settlement within decentralized applications.

Luminex Defi Finance 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.

70.95
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
0x313E...2B2F
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2026/01/26
Revision date 2026/01/26

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.


Ownership Privileges
  • The owner can rescue tokens and native coin from the contract.
  • The owner can transfer or renounce the ownership.

Note - This Audit report consists of a security analysis of the Luminex Defi Finance 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 Luminex Defi Finance 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

informational Issues | 3 findings

Pending

#1 informational Issue
Floating pragma solidity version.
LFUSDCoin.sol
L7
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

#2 informational Issue
Missing Explicit Inheritance from IERC20 Interface
LFUSDCoin.sol
L35
Description

The LuminexDefiFinance contract does not explicitly inherit from the IERC20 interface, even though it implements the standard ERC-20 functions. By not declaring is IERC20, the code bypasses the Solidity compiler's automatic validation. This increases the risk of human error, such as misspelled function names, incorrect return types, or missing standard functions, which could lead to integration issues with wallets, exchanges, and other DeFi protocols that rely on strict standard compliance.

Pending

#3 informational Issue
Use of Non-Standard SafeERC20 Implementation
LFUSDCoin.sol
L23-33
Description

The contract utilizes a simplified, custom implementation of the SafeERC20 library instead of the industry-standard OpenZeppelin version. This custom implementation strictly requires the transfer and transferFrom calls to return a boolean value. However, several major tokens (most notably USDT on Ethereum) do not adhere to the ERC-20 standard's return value requirement and return void instead. Consequently, attempting to interact with or rescue such non-compliant tokens using this contract will cause transactions to revert, potentially resulting in funds being permanently stuck in the contract.