Renzo Protocol audit reports

Renzo Protocol has 4 public audit reports from Nethermind Security, HashEx and Sigma Prime; the latest is Nethermind Security, 1 May 2025; 1 critical finding, marked fixed by the firm. It also holds 1 deployed contract on 1 chain.

Critical findings
No open critical findings
Across the 4 reports, 1 critical finding was reported. It is marked fixed by the firm that reported it. See the findings
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm6

Statuses are the security firms’ own

6 findings are still open or acknowledged in the firms’ reports: 1 high, 2 medium, 3 low (all acknowledged).

High
1
Medium
2
Low
3
  • High Acknowledged

    Malicious Validator Frontrunning Attack

    Renzo Protocol · Sigma Prime · 1 Jun 2024 · Report ↗

  • Medium Acknowledged

    Double Use Of Validator Public Key Can Re-introduce Security Issues

    Renzo Protocol · Sigma Prime · 1 Jun 2024 · Report ↗

  • Medium Acknowledged

    Incorrect stakedButNotVerifiedEth Accounting Can Overinflate TVL

    Renzo Protocol · Sigma Prime · 1 Jun 2024 · Report ↗

  • Low Acknowledged

    Checkpoint system can be DoSed when currentCheckpointTimestamp loses synchronization

    Renzo security review · Nethermind Security · 14 Apr 2025 · Report ↗

  • Low Acknowledged

    Price Updates DOS After Price Staleness

    Renzo Protocol · Sigma Prime · 1 Jun 2024 · Report ↗

  • Low Acknowledged

    Remove Collateral DOS By Transfer Of Dust Amount

    Renzo Protocol · Sigma Prime · 1 Jun 2024 · Report ↗

Audits4

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Renzo BridgeSecurity firm: Nethermind SecurityDate: Scope: Not recorded; see the reportNone openFindings: None listedGitHub ↗
Renzo security reviewSecurity firm: Nethermind SecurityDate: Scope: Not recorded; see the reportNone openFindings: 2 high · 1 medium · 3 low
5 fixed · 1 acknowledged
GitHub ↗
RenzoSecurity firm: HashExDate: Scope: 1 address on EthereumNone openFindings: None listedhashex.org ↗
Renzo ProtocolSecurity firm: Sigma PrimeDate: Scope: Not recorded; see the report1 critical finding, fixedFindings: 1 critical · 5 high · 4 medium · 5 low
10 fixed · 5 acknowledged
GitHub ↗

Findings35

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

SeverityOpenAcknowledgedFixed
Critical001
High016
Medium023
Low035

No open finding in these reports.

Contracts1

AddressChainSource code
0x3b50805453023a91a8bf641e279401a0b23fa6f9Chain: EthereumSource code: Verified source

Renzo Protocol: questions

Is Renzo Protocol audited?

Trustblock holds 4 public audit reports for Renzo Protocol, dated 1 Jun 2024 to 1 May 2025. The latest is by Nethermind Security (“Renzo Bridge”).

Who audited Renzo Protocol?

3 security firms wrote the reports Trustblock holds for Renzo Protocol: Nethermind Security, HashEx and Sigma Prime.

Are there open findings in Renzo Protocol’s audits?

6 findings are still open or acknowledged in the firms’ reports: 1 high, 2 medium, 3 low (all acknowledged). Of 1 critical finding: marked fixed by the firm. Statuses are the security firms’ own.

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

Facts

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.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="renzo"
></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