Lido V1

ChainSecurityFiles named in the report

Audit · firm’s term: code assessment

ChainSecurity reviewed Lido (Lido V1) on 23 Aug 2022: 9 findings, 0 critical; all acknowledged, none fixed.

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

Report hosted on chainsecurity.com.

Trustblock does not review code.

Findings9

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium000
Low090

No open finding in this report.

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.

Repository and files the report names (15)

  • LidoOracle.sol
  • Lido.sol
  • StakeLimitUtils.sol
  • SelfOwnedStETHBurner.sol
  • CompositePostRebaseBeaconReceiver.sol
  • NodeOperatorsRegistry.sol
  • LidoExecutionLayerRewardsVault.sol
  • OrderedCallbacksArray.sol
  • DepositSecurityModule.sol
  • ReportUtils.sol
  • MemUtils.sol
  • WstETH.sol
  • ECDSA.sol
  • StETH.sol
  • Pausable.sol

Part of Lido’s security record

Lido
Audits84 audits by 15 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

ChainSecurity

81 projects reviewed · 290 reports · latest Nov 2026

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