Lido Dual Governance audit

OpenZeppelinCode version: not recorded (see the report)

Audit · firm’s term: audit

OpenZeppelin reviewed Lido (Lido Dual Governance audit) on 19 Nov 2024: 10 findings, 0 critical; 6 marked fixed, 3 acknowledged, 1 open.

No open critical findings
Open the reportOpen Lido’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings10

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium001
Low135
LowAbility to Vote Multiple Times on the Same Proposal in Tiebreaker ContractsAcknowledged

The report gives no description here.

LowEscrow.requestNextWithdrawalsBatch Might Be Executed While the Batch Queue Is in a Closed StateAcknowledged

The report gives no description here.

LowIncorrect Comparison Used for Tiebreaker VotingAcknowledged

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.

Tell us