- Home
- Security Audits
- Unilayer
Web3 · Smart Contract Audit
Unilayer Security Audits
softstack has completed 2 smart contract audits for Unilayer between April 2021 and May 2021, reporting 7 findings in total (1 high, 1 medium, 2 low and 3 informational). Every report is published in the softstack public audit archive.
Key facts
- Client
- Unilayer
- Audits completed
- 2
- First audited
- Latest audit
- Chains
- Ethereum
- Languages
- Solidity
- Market cap
- $3M as of 2026-09-30
About the project
UniLayer is a decentralised trading platform built on top of Uniswap on Ethereum, paired with the LAYER utility token. It offers automated swaps, liquidity management, flash staking and live order books. Charting and analytics tools sit alongside the trading interface.
Findings
Combined across all 2 reviews softstack has completed for Unilayer. Each report is broken out below.
Reports
Newest first. Every report covers its own scope and commit.
LAYERx Farm smart contract audit
0Critical0High0Medium0Low1InformationalScope
Components reviewed
3 modules · 3 files- Farm.sol
- testedfarm.sol
- farm.sol
LAYERx v5 smart contract audit
0Critical1High1Medium2Low2InformationalScope
Components reviewed
4 modules · 4 files- LAYERx_v5.sol
- Layerx_v5.sol
- layerx_v5.sol
- layerx_v4.sol
All 1 findings
ID Title Severity Status 5.1.5Fix Spelling and Grammatical Errors Code Snippet Result/Recommendation Language mistakes were identified in the messages in the codebase.
Informational fixed
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
Unilayer 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 Unilayer between April 2021 and May 2021. The published reports are linked on this page and in the softstack public audit archive.
2 separate reviews, the first in April 2021 and the most recent in May 2021. Each one covers its own scope and commit, and is listed individually on this page.
7 findings across all 2 reviews: 1 high, 1 medium, 2 low and 3 informational.
Each report covers the code as it stood at the commit it names, the most recent in May 2021. 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.