Lido security review

Sigma Prime1 Jan 2026Code version: not recorded (see the report)

Audit · firm’s term: security assessment

Sigma Prime reviewed Lido (Lido security review) on 1 Jan 2026: 1 finding, 0 critical; it is marked fixed.

No open critical findings

Open the report Open Lido’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings1

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	0	1

Marked Informational by the firm. Not counted as findings.

InformationalContract Requires Cancun EVM Version For mcopy OpcodeFixed

The report gives no description here.

InformationalError Cases Not Returned To CallerFixed

The report gives no description here.

InformationalLack Of returndatasize Validation In Precompile CallsFixed

The report gives no description here.

InformationalRedundant Memory Write In Gas Optimized FunctionFixed

The report gives no description here.

InformationalUndocumented Working Memory Allocation In AssemblyFixed

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

Sigma Prime

16 projects reviewed · 37 reports · latest Aug 2026

See Sigma Prime’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.