Web3 · Smart Contract Audit

UNCX Network Security Audits

softstack has completed 11 smart contract audits for UNCX Network between November 2020 and July 2023, reporting 60 findings in total (9 medium, 23 low and 28 informational). Every report is published in the softstack public audit archive.

Key facts

Client
UNCX Network
Audits completed
11
First audited
Latest audit
Languages
Solidity, Rust
Market cap
$1M as of 2026-09-30

About the project

UNCX Network, formerly UniCrypt, provides DeFi infrastructure for token teams, including liquidity pool locking, token vesting, staking and farming pools, a no-code token minter and a launchpad. Founded in June 2020, it is known for early liquidity-locking contracts for Uniswap on Ethereum. Its tooling spans multiple chains, including Ethereum and Solana, and UNCX serves as the governance token.

Findings

Combined across all 11 reviews softstack has completed for UNCX Network. Each report is broken out below.

0Critical
0High
9Medium
23Low
28Informational

Reports

Newest first. Every report covers its own scope and commit.

  1. ENMTv2 smart contract audit

    · commit 936ab73 · 9 files

    PDF
    0Critical
    0High
    4Medium
    7Low
    8Informational
    ScopeSource repositorygithub.com/Boka44/enmt-v2

    Components reviewed

    9 modules · 9 files
    1. TaxToken.sol
    2. Antibot.sol
    3. Constructor.sol
    4. Lossless.sol
    5. Multicall.sol
    6. Settings.sol
    7. Storage.sol
    8. Tax.sol
    9. Wallets.sol
    All 18 findings
    IDTitleSeverityStatus
    6.2.3High Gas Consumption For Token Creation

    In the current implementation, the compiler optimizer is configured to one run for the MintGenerator.sol. This is probably done to reduce the contracts byte code size but increases the used gas on each function call significantly.

    Mediumfixed
    6.2.4Bad Test Coverage

    In the current implementation, several functions are never tested and other functions are rarely tested.

    Mediumfixed
    6.2.5Missing Implementations For Diamond Standard

    According to the EIP-2535 specification “all diamonds must implement the IDiamond interface” and “diamonds must emit DiamondCut event” on functions modification.

    Lowacknowledged
    6.2.6Missing Batch Function For Adding Facets And Function Selectors

    The current implementation is missing a batch add function to add function selectors for a facet. For every function of every facet the addFacet and addSelector function has to be called once.

    Lowacknowledged
    6.2.7Missing Remove And Replace Facet Functions

    The current implementation is missing a remove and replace function for facet functions. If one facet should be removed, all facets must be reset and for every other function the addFacet and addSelector has to be called.

    Lowacknowledged
    6.2.8Redundant Byte Code

    Some functions are defined multiple times in different facets with exact the same byte code. This produces redundant byte code for the diamond contract.

    Lowacknowledged
    6.2.9Unnecessary If Statement

    In the current implementation are several if statements returning true if the statement is true. This is redundant and consumes more gas than returning just the statement.

    Lowacknowledged
    6.2.10Missing Value Validation

    Several functions lack value safety checks. Therefore, only values that are consistent with the logic of the contract should be permitted. Missing address validation checks could lead to contract deployment without properly set addresses.

    Lowacknowledged
    6.2.11Duplicated Storing Of Variables

    In the current implementation the MinFactory stores the referencing addresses for taxHelpers duplicated in a mapping and array. This produces storage overhead.

    Lowacknowledged
    6.2.12Missing Inheritance

    The LPWallet implements exactly the same functions as BuyBackWallet with some additional functions.

    Informationalacknowledged
    6.2.13Missing Natspec Documentation

    Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more. This special form is named the Ethereum Natural Language Specification Format (NatSpec).

    Informationalacknowledged
    6.2.14Wrong Function Returning Parameter

    The current implementation of the isMaxBalanceWhitelisted function returns a value of the swapWhitelist variable.

    Informationalacknowledged
    6.2.15Redundant Getter Functions

    The current implementation has getter functions for public state variables. Public state variables automatically generate getter functions.

    Informationalfixed
    6.2.16Unexplicit State Variable Visibility

    In the current implementation several state variables are leaking explicit visibility. Implicitly these variables are defined as public.

    Informationalacknowledged
    6.2.17Unexplicit Variable Declaration

    In the current implementation unexplicit types of unsigned integer variables are used several times.

    Informationalacknowledged
    6.2.18Misleading Contract Name

    The MintFactory is capable of storing several different references of deployed tokens, token generators and references to other smart contracts. Its only function is to register tokens and token generators.

    Informationalacknowledged
    6.2.19Naming Conventions Violation

    In the current implementation several variable names are violating best practice naming convention rules. This leads to bad code readability.

    Informationalacknowledged
    6.2.2Wrong Implementation Of Ownable For Diamond Patterns

    See the published report for the full description.

    Mediumacknowledged
  2. Locker v3 smart contract audit

    PDF
    0Critical
    0High
    3Medium
    5Low
    4Informational
    All 10 findings
    IDTitleSeverityStatus
    6.2.3Bad Test Coverage

    In the current implementation, several functions are rarely tested.

    Mediumacknowledged
    6.2.4Potential Loss Of Contract Ownership

    The owner of the contract can be changed by calling transferOwnership function of OpenZeppelin Ownable implementation. This function directly sets the owner to the given address, if the address is not the zero address.

    Lowfixed
    6.2.5Potential Loss of Token Lock Ownership

    The owner of the token lock can be changed by calling transferLockOwnership function. This function directly sets the token lock owner to the given address, if the address is not the current owner address.

    Lowfixed
    6.2.6Missing Value Validation

    Several onlyOwner functions lack value safety checks. Therefore, only values that are consistent with the logic of the contract should be permitted.

    Lowacknowledged
    6.2.7Incorrect Return Value of getLocksLength Function

    The function getLocksLength is meant to represent the number of all unique locks in the contract but it only returns the number of all ever created locks including the deleted ones.

    Lowfixed
    6.2.8Insecure Adjustment of Hash Prefix Value

    In the current implementation the signatures to allow a custom fee for NFTs is including a HASH_PREFIX to prevent signature replay attacks on other contracts or blockchains.

    Lowfixed
    6.2.9Floating 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.

    Informationalfixed
    6.2.10Missing Natspec Documentation

    Solidity contracts can use a special form of comments to provide rich documentation for function, return variables, and more. This special form is named Ethereum Natural Language Specification Format(NatSpec).

    Lowacknowledged
    6.2.11Redundant Zero Address Checking

    The _collect function first checks if the caller is the userLock.additionalCollector and afterwards if the userLock.additionalCollector is not the zero address.

    Informationalfixed
    6.2.12Missing Unlock Date Time Check

    The caller passed a unlock date into the lock function. This unlock date is checked for the format and if it is forever, but not if it is in the future.

    Informationalfixed
  3. ENMTv2 smart contract audit

    · commit 936ab73 · 9 files

    PDF

    Earlier issue of the same review. Its findings are counted once in the combined total above.

    0Critical
    0High
    4Medium
    7Low
    8Informational
    ScopeSource repositorygithub.com/Boka44/enmt-v2

    Components reviewed

    9 modules · 9 files
    1. TaxToken.sol
    2. Antibot.sol
    3. Constructor.sol
    4. Lossless.sol
    5. Multicall.sol
    6. Settings.sol
    7. Storage.sol
    8. Tax.sol
    9. Wallets.sol
    All 18 findings
    IDTitleSeverityStatus
    6.2.3High Gas Consumption For Token Creation

    In the current implementation, the compiler optimizer is configured to one run for the MintGenerator.sol. This is probably done to reduce the contracts byte code size but increases the used gas on each function call significantly.

    Mediumfixed
    6.2.4Bad Test Coverage

    In the current implementation, several functions are never tested and other functions are rarely tested.

    Mediumfixed
    6.2.5Missing Implementations For Diamond Standard

    According to the EIP-2535 specification “all diamonds must implement the IDiamond interface” and “diamonds must emit DiamondCut event” on functions modification.

    Lowacknowledged
    6.2.6Missing Batch Function For Adding Facets And Function Selectors

    The current implementation is missing a batch add function to add function selectors for a facet. For every function of every facet the addFacet and addSelector function has to be called once.

    Lowacknowledged
    6.2.7Missing Remove And Replace Facet Functions

    The current implementation is missing a remove and replace function for facet functions. If one facet should be removed, all facets must be reset and for every other function the addFacet and addSelector has to be called.

    Lowacknowledged
    6.2.8Redundant Byte Code

    Some functions are defined multiple times in different facets with exact the same byte code. This produces redundant byte code for the diamond contract.

    Lowacknowledged
    6.2.9Unnecessary If Statement

    In the current implementation are several if statements returning true if the statement is true. This is redundant and consumes more gas than returning just the statement.

    Lowacknowledged
    6.2.10Missing Value Validation

    Several functions lack value safety checks. Therefore, only values that are consistent with the logic of the contract should be permitted. Missing address validation checks could lead to contract deployment without properly set addresses.

    Lowacknowledged
    6.2.11Duplicated Storing Of Variables

    In the current implementation the MinFactory stores the referencing addresses for taxHelpers duplicated in a mapping and array. This produces storage overhead.

    Lowacknowledged
    6.2.12Missing Inheritance

    The LPWallet implements exactly the same functions as BuyBackWallet with some additional functions.

    Informationalacknowledged
    6.2.13Missing Natspec Documentation

    Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more. This special form is named the Ethereum Natural Language Specification Format (NatSpec).

    Informationalacknowledged
    6.2.14Wrong Function Returning Parameter

    The current implementation of the isMaxBalanceWhitelisted function returns a value of the swapWhitelist variable.

    Informationalacknowledged
    6.2.15Redundant Getter Functions

    The current implementation has getter functions for public state variables. Public state variables automatically generate getter functions.

    Informationalfixed
    6.2.16Unexplicit State Variable Visibility

    In the current implementation several state variables are leaking explicit visibility. Implicitly these variables are defined as public.

    Informationalacknowledged
    6.2.17Unexplicit Variable Declaration

    In the current implementation unexplicit types of unsigned integer variables are used several times.

    Informationalacknowledged
    6.2.18Misleading Contract Name

    The MintFactory is capable of storing several different references of deployed tokens, token generators and references to other smart contracts. Its only function is to register tokens and token generators.

    Informationalacknowledged
    6.2.19Naming Conventions Violation

    In the current implementation several variable names are violating best practice naming convention rules. This leads to bad code readability.

    Informationalacknowledged
    6.2.2Wrong Implementation Of Ownable For Diamond Patterns

    See the published report for the full description.

    Mediumfixed
  4. Token smart contract audit

    · 1 file

    PDF
    0Critical
    0High
    0Medium
    0Low
    0Informational

    No security findings reported.

    Scope

    Components reviewed

    1 module · 1 file
    1. UNCX_Token.sol
  5. Uniswap LP Token Locker v3 smart contract audit

    · commit 3f08f36 · 27 files

    PDF
    0Critical
    0High
    0Medium
    6Low
    6Informational

    12 of 12 resolved

    ScopeSource repositorygithub.com/Boka44/unicrypt-uniswap-v3-lp

    Components reviewed

    14 modules · 27 files
    1. contracts/interfaces/pool/IUniswapV3PoolImmutables.sol
    2. contracts/interfaces/pool/IUniswapV3PoolDerivedState.sol
    3. contracts/interfaces/pool/IUniswapV3PoolOwnerActions.sol
    4. contracts/interfaces/pool/IUniswapV3PoolState.sol
    5. contracts/interfaces/pool/IUniswapV3PoolEvents.sol
    6. contracts/interfaces/pool/IUniswapV3PoolActions.sol
    7. contracts/interfaces/IUniswapV3LPFactory.sol
    8. contracts/interfaces/IUniswapV3LPToken.sol
    9. contracts/interfaces/IUniswapV3Pool.sol
    10. contracts/interfaces/ITickHelper.sol
    11. contracts/interfaces/IWETH9.sol
    12. contracts/interfaces/IUniswapV3MintCallback.sol
    13. contracts/interfaces/IUniswapV3Factory.sol
    14. contracts/libraries/FixedPoint96.sol
    All 12 findings
    IDTitleSeverityStatus
    5.1.1Checking for boolean equality

    Code Snippet Result/Recommendation In the current implementation several require checks are using a comparison to a Boolean constant. This leads to unnecessary gas consumption.

    Lowfixed
    5.1.2Missing natspec documentation

    Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more.

    Lowfixed
    5.1.3Missing Zero address validation

    Code Snippet Result/Recommendation In the current implementation several functions are not UniswapV3LPFactory Line 30: It is recommended to check addresses for the zero address before setting them. checking for zero addresses.

    Lowfixed
    5.1.4Division before multiplication

    Code Snippet Result/Recommendation In the current implementation several functions are not checking for zero addresses. Setting an address to the zero address can result in loosing funds by sending it to the zero address.

    Lowfixed
    5.1.5Unchecked transfer

    Code Snippet Result/Recommendation In the current implementation several functions ignore return values of external function calls. Execution will resume even if the called contract throws an exception.

    Lowfixed
    5.1.6Redundant override function

    Code Snippet Result/Recommendation In the current implementation the decimals function of UniswapV3LPToken.sol is overriding the decimal function of ERC20.sol with the exact

    Lowfixed
    5.1.7Different Compiler version used

    Code Snippet Result/Recommendation In the current implementation, several pragma versions have been identified, which can lead to inconsistency and further problems while deployment.

    Informationalfixed
    5.1.8A floating pragma is set.

    Code Snippet Result/Recommendation The current pragma Solidity Line 1: It is recommended to follow the latter example, as directive is "^>=0.8.3". It is recommended to specify a fixed compiler version to

    Informationalfixed
    5.1.9SafeMath for pragma version higher than 0.8.0

    Code Snippet Result/Recommendation

    Informationalfixed
    5.1.10ABIEncoder v2

    Code Snippet Result/Recommendation The second change since solidity 0.8.0 that is very visible is that the ABI coder v2 is activated by default.

    Informationalfixed
    5.1.11Public function could be declared external

    Code Snippet Result/Recommendation In the current implementation several functions are declared as public where they could be external.

    Informationalfixed
    5.1.12Unused state variable

    Code Snippet Result/Recommendation In the current implementation is a declared state variable, which is never used by any contract.

    Informationalfixed
  6. Farms v2 smart contract audit

    · 21 files

    PDF
    0Critical
    0High
    0Medium
    1Low
    2Informational

    0 of 3 resolved

    Scope

    Components reviewed

    14 modules · 21 files
    1. IStakeFactory.sol
    2. IStakeSettings.sol
    3. PoolRewardMappings.sol
    4. StakeFactory.sol
    5. StakeSettings.sol
    6. StakeFactoryPager.sol
    7. IRewardPool.sol
    8. StakePool.sol
    9. StakePoolPager.sol
    10. IEcosystemWhitelist.sol
    11. ICountryList.sol
    12. RewardPoolGenerator.sol
    13. RewardPool.sol
    14. IStakePool.sol
    All 3 findings
    IDTitleSeverityStatus
    5.1.1Hardcoded address

    Code Snippet Result/Recommendation The contract contains hardcoded addresses. Line: 30 SETTINGS.UNCL_FEE_ADDRESS = payable( 0x0da797beF1F3C234204aA3EF3A50a67B7aAeCB49 Line: 45 .UNICRYPT_DEV_ADDRESS =…

    Lowacknowledged
    5.1.2OpenZeppelin libraries are not correctly imported

    Code Snippet Result/Recommendation In the current implementation, OpenZeppelin files are not correctly imported.

    Informationalacknowledged
    5.1.3A floating pragma is set.

    Code Snippet Result/Recommendation The current pragma Solidity directive is "^0.8.0". It is recommended to specify a fixed compiler version to Line 1: pragma solidity ^0.8.0; It is recommended to follow the latter example, as future…

    Informationalacknowledged
  7. LP Locker smart contract audit

    · 4 files

    PDF
    0Critical
    0High
    0Medium
    1Low
    1Informational

    0 of 2 resolved

    Scope

    Components reviewed

    4 modules · 4 files
    1. totallp-locker-main/programs/country-list/src/lib.rs
    2. lp-locker-main/programs/locker/src/lib.rs
    3. programs/country-list/src/lib.rs
    4. programs/locker/src/lib.rs
    All 2 findings
    IDTitleSeverityStatus
    5.1.1Missing rustdoc documentation

    Code Snippet Result/Recommendation rust can use a special form of comments to provide rich documentation for functions, return variables and more. This special form is named as rustdoc.

    Lowacknowledged
    5.1.2Outdated anchor versions

    Code Snippet Result/Recommendation Locker is using anchor-spl and anchor-lang dependency version 0.18 which is not the latest version.

    Informationalacknowledged
  8. LP Locker v2 (Safemoon AMM) smart contract audit

    · 7 files

    PDF
    0Critical
    0High
    0Medium
    0Low
    3Informational

    0 of 3 resolved

    Scope

    Components reviewed

    7 modules · 7 files
    1. ICountryList.sol
    2. MigrateLP.sol
    3. TransferHelper.sol
    4. UniswapV2Locker.sol
    5. Context.sol
    6. Ownable.sol
    7. ReentrancyGuard.sol
    All 3 findings
    IDTitleSeverityStatus
    5.1.1Interfaces are not correctly implemented

    Code Snippet Result/Recommendation Interfaces and functions are inside the same contract file, this can be hard to read.

    Informationalacknowledged
    5.1.2OpenZeppelin libraries are not correctly imported

    Code Snippet Result/Recommendation In the current implementation, OpenZeppelin files are not correctly imported.

    Informationalacknowledged
    5.1.3A floating pragma is set.

    Code Snippet Result/Recommendation The current pragma Solidity directive is "^0.8.0". It is recommended to specify a fixed compiler version to

    Informationalacknowledged
  9. Unicrypt Token Vesting smart contract audit

    · 8 files

    PDF
    0Critical
    0High
    0Medium
    0Low
    1Informational
    Scope

    Components reviewed

    8 modules · 8 files
    1. contracts/FullMath.sol
    2. contracts/TokenBlacklist.sol
    3. contracts/TokenVesting.sol
    4. contracts/TransferHelper.sol
    5. contracts/UnicryptAdmin.sol
    6. contracts/VestingMathLibrary.sol
    7. FullMath.sol
    8. TokenVesting.sol
  10. Unicrypt.Network Presale Contracts smart contract audit

    · 7 files

    PDF
    0Critical
    0High
    0Medium
    1Low
    1Informational
    Scope

    Components reviewed

    7 modules · 7 files
    1. Presale01.sol
    2. PresaleFactory.sol
    3. PresaleGenerator01.sol
    4. PresaleHelper.sol
    5. PresaleLockForwarder.sol
    6. PresaleSettings.sol
    7. PresaleLockerForwarder.sol
  11. Uniswap LP Token Locking Contract v2 smart contract audit

    · 1 file

    PDF
    0Critical
    0High
    1Medium
    1Low
    1Informational

    3 of 3 resolved

    Scope

    Components reviewed

    1 module · 1 file
    1. UniswapV2Locker.sol
    All 3 findings
    IDTitleSeverityStatus
    5.1.1Wrong import of OpenZeppelin library

    Code Snippet Result/Recommendation In the current implementation, OpenZeppelin files are added to the repo. This violates OpenZeppelin’s MIT license, which requires the license and copyright notice to

    Mediumfixed
    5.1.2Checks-effects-interactions pattern

    Code Snippet Result/Recommendation Potential violation of Checks- Effects-Interaction pattern in UniswapV2Locker.lockLPToke n(address,uint256,uint256,addr ess payable,bool,address payable): Could potentially lead to re-entrancy…

    Lowfixed
    5.1.3Fix Spelling and Grammatical Errors

    Code Snippet Result/Recommendation Language mistakes were identified in the messages in the codebase.

    Informationalfixed
  12. Unicrypt Farm Contracts smart contract audit

    · 3 files

    PDF
    0Critical
    0High
    1Medium
    1Low
    1Informational

    3 of 3 resolved

    Scope

    Components reviewed

    3 modules · 3 files
    1. Farm01.sol
    2. FarmFactory.sol
    3. FarmGenerator01.sol
    All 3 findings
    IDTitleSeverityStatus
    5.1.1Wrong import of OpenZeppelin library

    Code Snippet Result/Recommendation In the current implementation, OpenZeppelin files are added to the repo. This violates OpenZeppelin’s MIT license, which requires the license and copyright notice to

    Mediumfixed
    5.1.2Improved Logic in getMultiplier

    Code Snippet Result/Recommendation The function getMultiplier takes two arguments, i.e., _from and _to, and calculates the reward multiplier for the given block range ([_from, _to]).

    Lowfixed
    5.1.3Missing natspec documentation

    Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more.

    Informationalfixed

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 audits

Methodology

Review process

  1. 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.

  2. Automated analysis

    Static analysers sweep the full codebase to surface known weakness patterns, unreachable states and deviations from established conventions.

  3. Manual code review

    Independent engineers read the code line by line, concentrating on business logic, access control, arithmetic and the handling of external calls.

  4. Adversarial testing

    Property-based fuzzing and invariant tests attack the assumptions the protocol relies on, targeting states that ordinary unit tests never reach.

  5. 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.

  6. 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

UNCX Network 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 11 smart contract audits for UNCX Network between November 2020 and July 2023. The published reports are linked on this page and in the softstack public audit archive.

11 separate reviews, the first in November 2020 and the most recent in July 2023. Each one covers its own scope and commit, and is listed individually on this page.

60 findings across all 11 reviews: 9 medium, 23 low and 28 informational.

Each report covers the code as it stood at the commit it names, the most recent in July 2023. Any code changed after that point is outside the reviewed scope.

Related audits

Browse all security audits

Disclaimer

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.