Lido NEST

ack324 Jul 2026Code version: not recorded (see the report)

ack3 reviewed Lido (Lido NEST) on 24 Jul 2026: 9 findings, 0 critical; 5 marked fixed, 4 acknowledged.

No open critical findings

Open the report Open Lido’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings9

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	4	5

LowAllocationStatus enum desynchronizationFixed

The report gives no description here.

LowFailed revenue source recoveryFixed

The report gives no description here.

LowIncomplete Stonks switch wind-downFixed

The report gives no description here.

LowRecovered revenue reweighted by increased surplus shareFixed

The report gives no description here.

LowUnfillable buyback order slotFixed

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

ack3

1 project reviewed · 1 report · latest Jul 2026

See ack3’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.