Fact-check findings
What an automated fact-checker found when it re-read Renzo Protocol against the sources the page cites. Only the most recent review is shown.
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
unverifiable
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #6[unverifiable][awaiting moderator]in section: Current Protocol Status (2025–2026)
“the first burn, on November 5, 2025, destroyed over 114 million tokens, with monthly burns to follow”
reviewerFirst REZ burn on November 5, 2025 destroyed over 114 million tokens, with monthly burns to followThe cited source does not contain the date or amount, and a search found no corroboration. Reported figures differ (about 100M). - #7[unverifiable][awaiting moderator]in the timeline
“Renzo executes its first REZ buyback-and-burn, destroying over 114 million tokens; monthly burns confirmed as an ongoing programme.”
reviewerTimeline: Nov 2025 first buyback-and-burn destroying over 114 million tokens; monthly burns confirmedSame issue as the section claim. 'Confirmed as ongoing' overstates the source, which only promises monthly reports.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #5[partially supported][awaiting moderator]in section: Security Audit: Code4rena Findings
“Because the audit ran concurrently with or after the depeg, some of these vulnerabilities were present in production code at the time of the incident.”
reviewerAudit ran concurrently with or after the depeg, so some vulnerabilities were in production code at the time of the incidentThe audit began six days after the depeg, not concurrently. The inference about production code is the page's own and is not sourced. The summary's 'A concurrent Code4rena audit' has the same issue.
confirmed
4 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: The April 2024 ezETH Depeg
“On April 24, 2024 ezETH lost its peg on Uniswap, falling from about $3,100 (near ETH parity) by roughly 79 percent in under an hour before partially recovering.”
reviewerezETH fell about 79 percent on Uniswap in under an hour on April 24, 2024DL News supports the 79% drop and date. The starting price is approximate. - #2[confirmed][no action needed]in section: The April 2024 ezETH Depeg
“According to DL News, the Renzo team made no public statement addressing user frustration or the price collapse during the depeg.”
reviewerRenzo team made no public statement during the depegCorrectly attributed to DL News. It reflects the state of the article at publication time. - #3[confirmed][no action needed]in section: Liquidation Cascade and User Losses
“On Gearbox Protocol, 115 Credit Accounts were liquidated and about 10,650 ezETH (approximately $33 million) was sold into the Balancer pool”
reviewerLiquidations of $56-65 million across 250+ users; Gearbox 115 accounts, ~10,650 ezETH (~$33M); Morpho 146 users, ~$23MHeadline figures match DL News. Finer details were not independently checked. - #4[confirmed][no action needed]in section: Security Audit: Code4rena Findings
“A Code4rena competitive audit held from April 30 to May 8, 2024, with a $112,500 USDC prize pool, identified 22 unique vulnerabilities: 8 high severity and 14 medium severity.”
reviewerCode4rena audit ran April 30 to May 8, 2024 and found 8 high and 14 medium vulnerabilitiesDates and counts match the report. The $112,500 pool was not verified.