Lido security record
As of 16 Oct 2026, Lido has 38 audit reports by 11 security firms on Trustblock; the latest is by ack3, dated 24 Jul 2026. Those reports list 1 critical acknowledged and not fixed.
Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.
Audits38
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Lido NEST | Security firm: ack3 | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido Circuit Breaker Audit Report | Security firm: Cyfrin | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido PR 85 - Bytecode Verification | Security firm: Cantina | Date: | Scope: Not recorded. See the report | No open critical findings | Open · cantina.xyz |
| Lido CSM v3 and CM v2 audit | Security firm: Certora | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido Vault Wrapper | Security firm: Ackee Blockchain Security | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido V3 | Security firm: Certora | Date: | Scope: Not recorded. See the report | 1 critical finding, fixed | Open · GitHub |
| Lido security review | Security firm: Sigma Prime | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido Vault Middleware Audit Report | Security firm: Cyfrin | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido Stonks 2. | Security firm: Ackee Blockchain Security | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido V3 Oracle V7 | Security firm: Certora | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido Csm V2 | Security firm: Ackee Blockchain Security | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido Triggerable Withdrawals | Security firm: Ackee Blockchain Security | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido Community Staking Module audit (April 2025) | Security firm: Ackee Blockchain Security | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido Dual Governance re-audit | Security firm: OpenZeppelin | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido DG | Security firm: Certora | Date: | Scope: Not recorded. See the report | 2 critical findings, fixed | Open · GitHub |
| Launchnodes Lido Liquid Staking | Security firm: OXORIO | Date: | Scope: Files named in the report | 6 critical findings, fixed | Open · audits.oxor.io |
| Lido Dual Governance audit | Security firm: OpenZeppelin | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido Community Staking Module audit (October 2024) | Security firm: Ackee Blockchain Security | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Zircuit / Lido / NEW Proposal | Security firm: Quantstamp | Date: | Scope: Files named in the report | No open critical findings | Open · certificate.quantstamp.com |
| Lido Staking Router V2 | Security firm: Ackee Blockchain Security | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido Simple Delegation | Security firm: Ackee Blockchain Security | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| LIP-23: Rebase Check Smart Contracts | Security firm: ChainSecurity | Date: | Scope: Files named in the report | No open critical findings | Open · chainsecurity.com |
| Lido Steth Optimism | Security firm: Ackee Blockchain Security | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido Stonks | Security firm: Ackee Blockchain Security | Date: | Scope: Not recorded. See the report | No open critical findings | Open · GitHub |
| Lido EasyTrack | Security firm: OXORIO | Date: | Scope: Repository at commit 425f4a2 | No open critical findings | Open · audits.oxor.io |
Findings348
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 1 | 11 |
| High | 0 | 0 | 23 |
| Medium | 0 | 7 | 47 |
| Low | 4 | 80 | 175 |
LowCode Quality ImprovementsLido Dual Governance re-audit · OpenZeppelin · 18 Feb 2025Open
The report gives no description here.
Open the reportLowIncorrect InterfacesLido Dual Governance re-audit · OpenZeppelin · 18 Feb 2025Open
The report gives no description here.
Open the reportLowDiscrepancies Between Documentation and ImplementationLido Dual Governance audit · OpenZeppelin · 19 Nov 2024Open
The report gives no description here.
Open the reportLowMissing DocstringsLido Dual Governance audit · OpenZeppelin · 19 Nov 2024Open
The report gives no description here.
Open the reportContracts
No deployed address is recorded for these audits.
The reports name a repository or files. Open a report to see its scope.
Show this on your site
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Content
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
Style
Format
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="lido"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
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