Skip to main content
AVOID.NET
← DFX V2reviewed 2026-11-12 · 7 claims checked

Fact-check findings

What an automated fact-checker found when it re-read DFX V2 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 2partially supported 1confirmed 40 corrections pending · 0 applied

unverifiable

2 claims

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

  1. #6[unverifiable][awaiting moderator]in section: Audit Failures — PickAx V2 Audit
    “The V2 codebase underwent a security audit by PickAx (documented in the official DFX Finance GitHub repository under audits/2022-09-DFXv2-Pickax-Audit.pdf), conducted in September 2022 — approximately two months before the hack.”
    reviewerPickAx audit of V2 in Sept 2022 missed the reentrancy bug; the PDF is hosted in DFX GitHubNot checked in this run. The archive record marks the PDF unarchivable (not-found).
  2. #7[unverifiable][awaiting moderator]in the timeline
    “DFX Finance relaunches with improved V2 smart contracts following post-hack security remediation.”
    reviewerDFX relaunched with improved V2 contracts in Feb 2023, sourced to CoinMarketCapA price-tracker page is an unlikely source for a relaunch date. I did not find support.

partially supported

1 claim

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

  1. #5[partially supported][awaiting moderator]in the summary
    “but TVL remains near zero as of 2024.”
    reviewerSummary says TVL remains near zero as of 2024, while the Background section says ~$111,000 as of 2024-2025Internal inconsistency: 'near zero' versus ~$111K. The DefiLlama figure was not fetched, so the correction rests on the page's own section text.

confirmed

4 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Security Exploit — November 2022 Reentrancy Attack
    “The primary attacker extracted approximately $4.3 million, including roughly 2,963 ETH (~$3.8M) and approximately $500,000 in stablecoins.”
    reviewerPrimary attacker extracted about $4.3M (2,963 ETH ~ $3.8M plus ~$500K stablecoins); MEV bot ~$3.2M; total ~$7.5MMatches The Block.
  2. #2[confirmed][no action needed]in section: Security Exploit — November 2022 Reentrancy Attack
    “The DFX Finance team publicly requested the MEV bot operator return those funds; no confirmation of recovery has been reported.”
    reviewerDFX asked the MEV bot operator to return funds; funds remained at the bot addressThe request is confirmed. The absence of later recovery was not independently checked.
  3. #3[confirmed][no action needed]in section: Protocol Response and Reimbursement Plan
    “On January 19, 2023, a community-approved reimbursement proposal was activated: affected users receive one DFX token per one US dollar lost, distributed block-by-block over a three-year period via Sablier streaming to prevent market flooding.”
    reviewerReimbursement activated Jan 19, 2023: 1 DFX per $1 lost, over three years via SablierMatches official docs.
  4. #4[confirmed][no action needed]in the timeline
    “DFX Finance raises $5 million seed round led by Polychain Capital and True Ventures.”
    reviewerSeed round of $5M led by Polychain and True Ventures in Feb 2021Supported.
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.