Lulo
Audit · firm’s term: security assessment
Certora reviewed Lulo on 10 Feb 2025: 19 findings, 7 critical; all marked fixed.
Findings28
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 7 |
| High | 0 | 0 | 4 |
| Medium | 0 | 0 | 8 |
| Low | 0 | 0 | 0 |
Marked Informational by the firm. Not counted as findings.
InformationalUsers might not be able to update oracles in withdraw_protected_poolOpen
The report gives no description here.
InformationalUsers earn more by setting themselves as a referrerAcknowledged
The report gives no description here.
InformationalIncorrect design of the arbitrage prevention mechanismFixed
The report gives no description here.
InformationalIncorrect implementation of math::adjust_by_bps functionFixed
The report gives no description here.
InformationalMissing program ownership check on user_account in deposit_pool instructionFixed
The report gives no description here.
InformationalProtocol::try_into panics if protocol name is more than 8 bytesFixed
The report gives no description here.
InformationalRequirement of unused accounts and writable unmodified accountsFixed
The report gives no description here.
InformationalThe initiate_regular_withdraw and withdraw_protected_poolFixed
The report gives no description here.
InformationalUsers can bypass minimum transfer check by making post-withdrawal balanceFixed
The report gives no description here.
Contracts in scope
No deployed address is recorded for this audit.
The report names a repository or files. Open the report to see its scope.
Part of Lulo’s security record
LuloSecurity firm
Certora29 projects reviewed · 56 reports · latest Aug 2026
See Certora’s auditsSomething wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us