Lido

MixBytesCode version: not recorded (see the report)

MixBytes reviewed Lido on 16 Jun 2026: 10 findings, 0 critical; 6 marked fixed, 4 acknowledged.

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
Low045
LowAllowConsolidationPair - allowlist entries are permanent and not re-validated at consolidation execution timeAcknowledged

The report gives no description here.

LowAllowConsolidationPair - no per-creator/per-pair limit lets an authorized operator exhaust the global motion slots (Easy Track-wide DoS)Acknowledged

The report gives no description here.

LowCreateOrUpdateOperatorGroup - missing cross-group membership pre-check produces motions that always revert at enactmentAcknowledged

The report gives no description here.

LowReportWithdrawalsForSlashedValidators - slashingPenalty is forwarded with only a positivity check and burned verbatim against the operator's bondAcknowledged

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
Audits82 audits by 14 firmsLast audit Oct 2026, by Cyfrin.
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

MixBytes

26 projects reviewed · 81 reports · latest Nov 2026

See MixBytes’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