Lido Dual Governance re-audit

OpenZeppelin18 Feb 2025Code version: not recorded (see the report)

Audit · firm’s term: re-audit

Version of Lido Dual Governance audit: counted once with it

OpenZeppelin reviewed Lido (Lido Dual Governance re-audit) on 18 Feb 2025: 3 findings, 0 critical; 1 marked fixed, 2 acknowledged.

No open critical findings

Open the report Open Lido’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings3

Statuses are the security firm’s own, from its report.

Severity	Open	Acknowledged	Fixed
Critical	0	0	0
High	0	0	0
Medium	0	0	0
Low	0	2	1

Marked Note by the firm. Not counted as findings.

NoteCode Quality ImprovementsOpen

The report gives no description here.

NoteIncorrect InterfacesOpen

The report gives no description here.

NoteUse calldata Instead of memoryAcknowledged

The report gives no description here.

NoteIncomplete DocstringsFixed

The report gives no description here.

NoteMisleading DocumentationFixed

The report gives no description here.

NoteTypographical ErrorsFixed

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 Lido’s security record

Lido

Audits53 audits by 13 firmsLast audit Sep 2026, by Composable Security.

Critical findings2 criticals acknowledged, not fixedReported in 2 reports, the latest by Statemind, Apr 2023. The team acknowledged both.

Open Lido’s security record

Security firm

OpenZeppelin

67 projects reviewed · 184 reports · latest Aug 2026

See OpenZeppelin’s audits

Something 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.