Skip to main content
AVOID.NET
← DODO AMMreviewed 2026-11-17 · 7 claims checked

Fact-check findings

What an automated fact-checker found when it re-read DODO AMM 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 1confirmed 60 corrections pending · 0 applied

unverifiable

1 claim

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

  1. #6[unverifiable][awaiting moderator]in section: Total Value Locked and Market Position
    “DeFiLlama's protocol data report an all-time-high TVL of $451.88 million on January 22, 2022, falling to a low of about $10.82 million on June 5, 2026, and standing at roughly $15.4 million as of November 17, 2026”
    reviewerDeFiLlama TVL ATH $451.88M on Jan 22, 2022; low ~$10.82M June 2026; ~$15.4M on Nov 17, 2026; fees/revenue figures.Could not read the DeFiLlama payload; not scored. Page presents these as point-in-time snapshots.

confirmed

6 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: March 2021 Crowdpooling Exploit
    “In March 2021, attackers drained approximately $3.8 million from four of DODO's V2 Crowdpooling liquidity pools (WSZO, WCRES, ETHA, and FUSI).”
    reviewerAttackers drained about $3.8 million from V2 Crowdpooling pools in March 2021 (WSZO, WCRES, ETHA, FUSI).Amount and pool names corroborated by The Block and by search results summarising contemporaneous coverage.
  2. #2[confirmed][no action needed]in section: March 2021 Crowdpooling Exploit
    “an attacker initialized the contract with a counterfeit token, used sync() to reset the pool's recorded reserve to zero, called init() again pointing at a real pool token, and then used a flash loan to drain genuine assets while bypassing the contract's liquidity checks.”
    reviewerHalborn's init()/sync()/flash-loan mechanism description.Matches Halborn's four-step description.
  3. #3[confirmed][no action needed]in section: March 2021 Crowdpooling Exploit
    “Halborn's analysis dates the underlying attack to March 8, 2021.”
    reviewerHalborn dates attack to March 8, 2021; disclosure March 9, 2021.Both dates confirmed.
  4. #4[confirmed][no action needed]in section: Fund Recovery
    “DODO said it expected to recover about $1.88 million (roughly 1,140,000 USDT and 411 ETH)”
    reviewerDODO's initial update expected about $1.88M recovery (1,140,000 USDT and 411 ETH).Figures confirmed; the 1.88 vs 1.89 rounding difference is minor and disclosed on the page.
  5. #5[confirmed][no action needed]in section: Fund Recovery
    “Halborn says the original attacker kept roughly $700,000 and about $200,000 was frozen on exchanges.”
    reviewerHalborn: about $3.1M recovered, attacker kept ~$700K, ~$200K frozen on exchanges, bots returned funds.Matches Halborn; page appropriately flags discrepancy with earlier figures.
  6. #7[confirmed][no action needed]in section: Regulatory Status
    “No SEC, CFTC, DOJ, or OFAC enforcement action naming DODO, DODO Inc., or its founders was found as of November 2026.”
    reviewerNo SEC/CFTC/DOJ/OFAC action against DODO found.Absence of evidence, correctly hedged on the page. My searches also found nothing.
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.