Skip to main content
AVOID.NET
← Dough Financereviewed 2026-11-02 · 12 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Dough Finance against the sources the page cites. Only the most recent review is shown.

Read this first

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 5partially supported 2confirmed 50 corrections pending · 0 applied

unverifiable

5 claims

No source the reviewer could reach confirms or contradicts the claim.

  1. #2[unverifiable][awaiting moderator]in section: July 2024 Flash Loan Exploit
    “The attacker's initial funds were sourced via Railgun, a zero-knowledge privacy protocol.”
    reviewerAttacker's initial funds were sourced via RailgunCertiK does not mention Railgun. Other cited sources (Medium analyses) were not checked for it, so the claim is not confirmed.
  2. #5[unverifiable][awaiting moderator]in section: Compensation Failures and Alleged Abandonment
    “Approximately 2,700 users were impacted.”
    reviewerApproximately 2,700 users were affectedThe 2,700 figure was not found in any readable source. CryptoTimes and ainvest, the likeliest origins, could not be read.
  3. #8[unverifiable][awaiting moderator]in section: ZachXBT Flagging and On-Chain Observations
    “ZachXBT's flagging of the entity has been cited as an indicator of elevated risk for users of the protocol.”
    reviewerZachXBT flagged Dough Finance and hypothesised a private key leakNo source found linking ZachXBT to Dough Finance. The ZachXBT private-key-leak hypothesis appears to belong to the Bittensor incident, so the whole section looks misattributed. The section's quoted sentence about the hypothesis is likewise unsupported. I recommend human review before removing it.
  4. #9[unverifiable][awaiting moderator]in section: ZachXBT Flagging and On-Chain Observations
    “According to reporting, ZachXBT hypothesized that the attack may have originated from a private key leak, though this specific hypothesis was not confirmed by subsequent technical analyses, which attributed the exploit to calldata validation failures in the smart contract.”
    reviewerZachXBT hypothesized the attack may have originated from a private key leakLikely conflation with a different incident on the same cited site.
  5. #11[unverifiable][awaiting moderator]in the timeline
    “Dough Finance website goes offline. Protocol effectively abandoned.”
    reviewerDough website went offline in December 2024No source dates the shutdown to December 2024. The timeline entry has an empty source field.

partially supported

2 claims

The cited evidence supports part of the claim but not all of it.

  1. #10[partially supported][awaiting moderator]in the timeline
    “2025-05”
    reviewerLopez lawsuit was filed in May 2025Press coverage was in May 2025, but the case number and a search summary suggest a January 2025 filing. I could not read the docket, so I propose no correction.
  2. #12[partially supported][awaiting moderator]in the timeline
    “Trial in Lopez v. Herro scheduled; outcome pending as of research date.”
    reviewerTrial in Lopez v. Herro scheduled for April 2026, outcome pendingThe scheduling is correct as of May 2025. Today is November 2026 and I found no reporting on the trial, a motion to dismiss or arbitration, or a settlement. The status is likely out of date. The Current Protocol Status section repeats it.

confirmed

5 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: July 2024 Flash Loan Exploit
    “CertiK's post-incident analysis identified the root cause as a lack of calldata validation in the ConnectorDeleverageParaswap contract's deloop call chain.”
    reviewerExploit on July 12, 2024 drained roughly $2.1 million via missing calldata validation in ConnectorDeleverageParaswapCertiK confirms date, root cause and approximately $2.1M loss.
  2. #3[confirmed][no action needed]in section: July 2024 Flash Loan Exploit
    “By July 13, 2024, approximately 600 ETH of stolen funds had been deposited into Tornado Cash.”
    reviewerAbout 600 ETH of stolen funds was deposited into Tornado Cash by July 13, 2024Matches CertiK.
  3. #4[confirmed][no action needed]in section: July 2024 Flash Loan Exploit
    “yielding a total recovery of approximately 76.17 ETH (roughly $281,000)”
    reviewerWhite-hat returned 69.12 ETH and c0ffeebabe.eth returned 7.05 ETH, totalling about 76.17 ETHETH amounts verified by CertiK.
  4. #6[confirmed][no action needed]in section: Compensation Failures and Alleged Abandonment
    “A governance vote passed with 99.5% support to reimburse token holders.”
    reviewerGovernance vote passed with 99.5% support; about $180,000 of recovered funds went to select addresses; website shut downSupported by CoinAlertNews, a secondary source.
  5. #7[confirmed][no action needed]in section: Founders' Transition to World Liberty Financial
    “WLFI has reportedly generated approximately $550 million in token sales, with Herro and Folkman together earning an alleged $65 million in revenues from the venture.”
    reviewerHerro and Folkman have earned an alleged $65 million from WLFI, which reportedly had about $550 million in token salesThe page hedges appropriately with 'alleged' and 'reportedly'.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.