Saffron Lido Vaults audit
Audit competition · firm’s term: public contest
Sherlock reviewed saffron.finance (Saffron Lido Vaults audit) on 21 Sep 2024: 5 findings, 0 critical; 4 marked fixed, 1 acknowledged.
No open critical findings
Open the reportOpen saffron.finance’s security record
Report hosted on GitHub.
Trustblock does not review code.
Findings5
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 2 |
| Medium | 0 | 1 | 2 |
| Low | 0 | 0 | 0 |
HighThe incorrect accounting of protocol fee will cause double charging fee and wrong distribution of earnings for variable usersFixed
The report gives no description here.
HightotalEarnings is incorrect when withdrawing after ending which will withdraw too many funds leaving the Vault insolventFixed
The report gives no description here.
MediumAttacker will DoS LidoVault up to 36 days which will ruin expected apr for all parties involvedFixed
The report gives no description here.
MediumLidoVault::vaultEndedWithdraw doesn't take into consideration income withdrawals before slashing, blocking variable users from withdrwing their incomeFixed
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 saffron.finance’s security record
saffron.financeAudits7 audits by 4 firmsLast audit Mar 2026, by Pashov Audit Group.
Critical findingsNo open critical findingsAcross the 7 reports, 3 critical findings were reported. Each is marked fixed by the firm that reported it.
Open saffron.finance’s security recordSecurity firm
Sherlock46 projects reviewed · 67 reports · latest Sep 2026
See Sherlock’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