Suilend
Audit · firm’s term: security assessment · Includes formal verification
Certora reviewed Suilend on 31 Jan 2026: 14 findings, 0 critical; 12 marked fixed, 2 acknowledged.
No open critical findings
Open the reportOpen Suilend’s security record
Report hosted on GitHub.
Trustblock does not review code.
Findings14
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 1 | 3 |
| Low | 0 | 1 | 9 |
MediumLack of check allows a malicious relayer to steal user's obligation by substituting the ObligationOwnerCapAcknowledged
The report gives no description here.
LowInsufficient full liquidation thresholdAcknowledged
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 Suilend’s security record
SuilendAudits3 audits by 2 firmsLast audit Jan 2026, by Certora.
Critical findingsNo open critical findingsAcross 3 reports.
Open Suilend’s security recordSecurity firm
Certora9 projects reviewed · 17 reports · latest Jun 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