- Home
- Security Audits
- Lossless
Web3 · Smart Contract Audit
Lossless Security Audit
softstack completed a smart contract audit of Lossless's Wrapped ERC20 in April 2023, reporting 8 findings (3 medium, 3 low and 2 informational), of which 5 were resolved or mitigated before the final report. The full report is published in the softstack public audit archive.
Key facts
- Client
- Lossless
- Completed
- Chains
- Ethereum
- Languages
- Solidity
- Commit
66984d9a529c- Market cap
- $68,292 as of 2026-09-30
About the project
Lossless is a Web3 security project that adds a transaction-level protection layer to token contracts. Its protocol freezes flagged malicious transfers for investigation through a stake-based community reporting system, while its Aegis product monitors contracts for threats. Lossless is built around LERC-20, an extension of the ERC-20 standard, and supports Ethereum and other EVM chains.
Scope
Components reviewed
1 module · 1 file- LosslessWrappedERC20.sol
Findings
5 of 8 findings resolved before the final report.
| ID | Title | Severity | Status |
|---|---|---|---|
6.2.1 | Overwriting Pending Withdrawal Requests In the LosslessWrappedERC20 contract, when users request a withdrawal using the requestWithdraw function, there is no check for an existing pending withdrawal request. | Medium | fixed |
6.2.2 | Missing Reentrancy Guard The withdrawTo function in the LosslessWrappedERC20 contract is vulnerable to reentrancy attacks as it does not have any reentrancy protection mechanisms. | Medium | fixed |
6.2.3 | Optimization of Blacklisted Funds Handling The LosslessWrappedERC20 contract has a function, transferOutBlacklistedFunds, that may become expensive to execute as the number of blacklisted addresses increases. | Medium | acknowledged |
6.2.4 | Insecure Default Admin Role Many important functions can be only called by the admin, which could create a single point of failure if the admins private key is compromised. | Low | acknowledged |
6.2.5 | Front-running The LosslessWrappedERC20 contract may be vulnerable to front-running attacks, where attackers can observe pending withdrawal requests, specifically in the requestWithdraw function, and manipulate transactions before they are executed. | Low | acknowledged |
6.2.6 | Missing Withdrawal Request Cancellation Function In the LosslessWrappedERC20 contract, there is no function to cancel a withdrawal request. Users may want to cancel a withdrawal request in certain situations, such as if they made a mistake or changed their mind. | Low | fixed |
6.2.7 | Floating Pragma Set The current pragma Solidity directive is "^0.8.0". It is recommended to specify a fixed compiler version to ensure that the bytecode produced does not vary between builds. | Informational | fixed |
6.2.8 | Spelling Mistakes in Comments and Error Messages There are a few spelling mistakes found in the comments and error messages of the smart contract. These mistakes do not impact the functionality of the contract but could lead to confusion or misunderstanding when reading the contract. | 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
Lossless 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 completed a smart contract audit for Lossless in April 2023. The full report is linked on this page and published in the softstack public audit archive.
The review reported 8 findings: 3 medium, 3 low and 2 informational. 5 of 8 were resolved or mitigated before the final report.
1 source files were reviewed at commit 66984d9. The published report lists every file covered.
This report covers the code as reviewed in April 2023 at commit 66984d9. 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.