What 117 audit reports look like
How many blockchain security audits does a large protocol go through? Staking service Lido’s audits page, read on November 12, 2026, listed 117 reports for Lido on Ethereum alone. The oldest two, by Quantstamp and Sigma Prime, date from December 2020, and 30 carry a 2026 date, the latest from September.
Each entry names the commit the auditors reviewed and counts the findings by severity. Certora’s December 2025 audit of Lido V3, at commit 33f2f59, found 84 issues. Seven were rated critical and 14 high, all fixed, and four of the 29 medium findings were acknowledged instead of fixed. The page notes the report was updated in January 2026 to reflect changes to the BLS library the code relies on.
At the other end, MixBytes’ September 2026 review of an Easy Track factory contract recorded no issues at all. Exchange protocol Uniswap published its own tally when its fourth version went live. Its launch post of January 31, 2025 cites nine independent audits, a $2.35 million security competition and a $15.5 million bug bounty, and says no critical bugs were found in the competition or the bounty.
What auditors do
The FBI gave a plain description in a public service announcement of August 29, 2022. A code audit, it said, “typically involves a thorough review and analysis of the platform’s underlying code to identify vulnerabilities or weaknesses.”
The same notice told investors to make sure a DeFi platform had one or more audits by independent auditors, and cited analysis firm Chainalysis for the figure that almost 97% of the $1.3 billion in crypto stolen between January and March 2022 came from DeFi platforms.
Ethereum.org’s security guide treats an audit as one form of independent code review, next to testing, formal verification and bug bounties, which pay outside researchers who report flaws.
Where you see it
Audit claims usually appear as a list of firms on a protocol’s website or documentation, with a link to each report. The useful lines are the commit hash, the count of critical and high findings, and whether each one was fixed or only acknowledged. Compare the commit with the code the protocol says is deployed, since a report on an earlier version says little about a later one.
The mistake: audited means safe
Ethereum.org warns developers to “avoid treating audits as a silver bullet,” because audits “won’t catch every bug.” Treasury officials, writing in an April 2023 assessment of DeFi, found “a lack of standardization in audits” and said several DeFi services “have been exploited even after claiming successful audits.”
LI.FI, a protocol that routes cross-chain swaps, is one documented case. Its incident report of July 18, 2024 lists multiple audits from a variety of firms among its security measures, yet the exploit two days earlier hit a contract component added shortly before the attack, which lacked a validation check the other components had. Treat an audit as evidence about one version of the code, and check its date and commit before relying on it.