- Home
- Security Audits
- Lendefi
Web3 · Smart Contract Audit
Lendefi Security Audits
softstack has completed 4 smart contract audits for Lendefi between August 2021 and April 2022, reporting 9 findings in total (2 low and 7 informational), of which 1 were resolved or mitigated before the final reports. Every report is published in the softstack public audit archive.
Key facts
- Client
- Lendefi
- Audits completed
- 4
- First audited
- Latest audit
- Languages
- Solidity
About the project
Lendefi is a decentralised finance protocol for secured lending against crypto collateral. Its design is intended to give lenders protection in volatile markets and to let traditional and private lenders earn interest without taking direct exposure to token price movements. The protocol's contracts were audited across Ethereum and BNB Chain in 2022.
Findings
Combined across all 4 reviews softstack has completed for Lendefi. Each report is broken out below.
1 of 9 findings resolved before the final reports.
Reports
Newest first. Every report covers its own scope and commit.
Protocol smart contract audit
0Critical0High0Medium1Low7Informational0 of 8 resolved
Scope
Source repositorygithub.com/lendefi/contractsComponents reviewed
14 modules · 30 files- TokenHolder.sol
- LoanTokenBase.sol
- FastGasFeedMock.sol
- TmpAdmin.sol
- TmpAdminInterestSettlement.sol
- ProtocolSettings.sol
- Proxy0_5.sol
- Upgradeable_0_5.sol
- StakingInterimState.sol
- SwapImplKyber.sol
- LoanTokenLogicStandard.sol
- LoanTokenSettings.sol
- FeesEvents.sol
- LoanClosingEvents.sol
All 8 findings
ID Title Severity Status 5.2.1Wrong import of OpenZeppelin library Code Snippet Result/Recommendation In the current implementation, some OpenZeppelin files are part of the repository.
Low acknowledged 5.2.2Different pragma versions identified Code Snippet Result/Recommendation In the current implementation, several pragma versions have been identified, which can lead to inconsistency and further problems while deployment.
Informational acknowledged 5.2.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.
Informational acknowledged 5.2.4Remove unused code Code Snippet Result/Recommendation The chances that the unused
Informational acknowledged 5.2.5Rename bzx branding Code Snippet Result/Recommendation There are still brandings from bzx included, which would lead to confusion. NA It is recommended to rename files / functions / variables and keep the branding consistent to lendefi or LDFI.
Informational acknowledged 5.2.6Error or require messages are not clear Code Snippet Result/Recommendation User won’t understand the error messages or correctly interpret it while debugging.
Informational acknowledged 5.2.7Constant name must be capitalized Code Snippet Result/Recommendation Linter: Constant name must be in capitalized SNAKE_CASE [const- name-snakecase] Line: 32 (TokenRegistry.sol) address public constant bZxContract = 0xe638C33001a7e403F560946ff3279F9B07b6AD29; // bsc…
Informational acknowledged 5.2.8Merge commit from original source Code Snippet Result/Recommendation Some useful commits from the original source are not merged. https://github.com/bZxNetwork/contractsV2/commits/development Merging the commits and monitoring from the original source would actively…
Informational acknowledged Vesting smart contract audit
0Critical0High0Medium0Low0InformationalNo security findings reported.
LP Lockup smart contract audit
0Critical0High0Medium1Low0Informational1 of 1 resolved
All 1 findings
ID Title Severity Status 5.1.1Wrong import of OpenZeppelin library Code Snippet Result/Recommendation In the current implementation, OpenZeppelin files are part of the codebase. This violates OpenZeppelin’s MIT license, which requires the license and copyright notice to
Low fixed Token (LDFI) smart contract audit
0Critical0High0Medium0Low0InformationalNo security findings reported.
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
Lendefi 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 4 smart contract audits for Lendefi between August 2021 and April 2022. The published reports are linked on this page and in the softstack public audit archive.
4 separate reviews, the first in August 2021 and the most recent in April 2022. Each one covers its own scope and commit, and is listed individually on this page.
9 findings across all 4 reviews: 2 low and 7 informational. 1 of 9 were resolved or mitigated before the final reports.
Each report covers the code as it stood at the commit it names, the most recent in April 2022. 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.