Fact-check findings
What an automated fact-checker found when it re-read Yield 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
4 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #4[unverifiable][awaiting moderator]in section: Protocol Shutdown and Wind-Down
“Official support for the protocol ended on February 2, 2024.”
reviewerWind-down announced Oct 4, 2023; operations cease Dec 29, 2023; official support ended Feb 2, 2024Primary announcement returned 403. Search results corroborate the December 2023 cessation and the demand/regulatory rationale, but not the specific Feb 2, 2024 date. - #5[unverifiable][awaiting moderator]in section: ZachXBT Flag
“Yield Protocol has been flagged by on-chain investigator ZachXBT.”
reviewerYield Protocol has been flagged by ZachXBTNo source cited and none found. The section itself admits the basis is unknown and speculates about it; that speculation is not evidence. - #6[unverifiable][awaiting moderator]in section: Abandoned Contract Risk
“CertiK's post-mortem attributed the vulnerability to the same class of pool-balance manipulation previously patched in April 2023, suggesting that not all contract variants received the fix or that analogous vulnerabilities existed in related contracts.”
reviewerCertiK's post-mortem attributed the vulnerability to the same class of pool-balance manipulation patched in April 2023The cited coverage shows only that CertiK confirmed the attack. No post-mortem making this comparison was found, so this looks like the page's inference presented as CertiK's attribution. - #7[unverifiable][awaiting moderator]in section: Abandoned Contract Risk
“The incident is cited in DeFi security literature as a cautionary example of inadequate sunset procedures for permissionless smart contract protocols.”
reviewerThe incident is cited in DeFi security literature as a cautionary exampleNo literature identified.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #3[partially supported][awaiting moderator]in section: Security Incidents
“These funds were ultimately recovered by July 2023 after the Euler hacker, who identified as 'Jacob,' returned the stolen funds following on-chain negotiations.”
reviewerEuler losses were recovered by July 2023 after the hacker, identified as 'Jacob', returned fundsRestoration via Euler recovery is supported, but the hacker returned funds in April 2023, and the July 2023 completion date and the 'Jacob' alias were not verified.
confirmed
3 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Security Incidents
“The whitehat received a bounty of $95,000 USDC, equal to 10% of funds at risk.”
reviewerWhitehat Paludo0x disclosed the burn() logic error on April 28, 2023 via Immunefi; about $950,000 at risk; $95,000 USDC bounty (10%); fixed with cached pool balanceImmunefi bug-fix review matches the page on researcher, amounts, function and fix. - #2[confirmed][no action needed]in section: Security Incidents
“Approximately $181,000 in crypto assets were drained from residual liquidity pools.”
reviewerApril 2024 exploit of ~$181,000 on Arbitrum via flash-loaned assets and pool token balance/total supply mismatch; PeckShield flagged first, CertiK confirmedAmount, mechanism and attribution match. The exact exploit day of April 30 is not stated in the article, which is only dated that day; minor. - #8[confirmed][no action needed]in the timeline
“2023-03-13”
reviewerEuler exploit drained ~$197 million on March 13, 2023; Yield losses under $1.5 millionDate and figures consistent across search results.