Skip to main content
AVOID.NET
← Convergencereviewed 2026-11-02 · 11 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Convergence 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.

disputed

2 claims

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #2[disputed][awaiting moderator]in the summary
    “a successor project called Tangent Finance (TGN)”
    reviewerSuccessor project ticker is TGNSummary says TGN while the sections and timeline say TAN; cited source says TAN.
    Proposed correction (not yet applied)
    a successor project called Tangent Finance (TAN)
  2. #4[disputed][awaiting moderator]in section: Audit Failures and Operational Security Concerns
    “yet none of these audits covered the specific code that was later modified.”
    reviewerAudits did not flag the gap because audited code contained the check, yet later section says none of the audits covered the modified codeContradicts section 2 of the page, which says the audited codebase contained the check. Sources say the contract was audited and the line removed afterwards.
    Proposed correction (not yet applied)
    yet the audited code contained the validation check, which was removed in a later gas-optimization change.

unverifiable

4 claims

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

  1. #5[unverifiable][awaiting moderator]in section: Token Impact and Market Consequences
    “routed approximately 65.8 ETH through Tornado Cash, an on-chain privacy mixer, in an apparent attempt to obscure the trail of funds”
    reviewerAttacker routed about 65.8 ETH through Tornado CashCited CoinDesk and Cointelegraph do not mention it; the cryptotimes negotiation article returned 403. Plausible but not confirmed by what I could read.
  2. #7[unverifiable][awaiting moderator]in section: ZachXBT Flag and Community Intelligence
    “Convergence Finance has been flagged by on-chain investigator ZachXBT.”
    reviewerZachXBT flagged ConvergenceThe page itself admits the flag is not verifiable, and the cited CoinDesk article is an exploit report. The following speculation about ZachXBT's 'documented pattern' is unsourced.
  3. #8[unverifiable][awaiting moderator]in section: Team Response and Attacker Negotiations
    “On August 6, 2024, approximately five days after the exploit, Convergence Finance transmitted an on-chain message to the attacker's Ethereum address.”
    reviewerTeam sent on-chain message to attacker on Aug 6 requesting return of 65.8 ETH within 48 hoursSource blocked; article date of Aug 7 is consistent with an Aug 6 message.
  4. #11[unverifiable][awaiting moderator]in the timeline
    “Convergence team announces pivot to Tangent Finance (TAN), a new DeFi lending protocol. CVG token deprecated.”
    reviewerTimeline: CVG protocol launched 2023; vote Sept 2024; pivot announced Oct 2024; CVG deprecatedTimeline dates 2023, 2024 (audits), 2024-09 and 2024-10 are placeholder-like (date_original 01-01 / 09-01 / 10-01) and have no sources; I found nothing confirming them.

stale

1 claim

The claim was accurate when written but events since have overtaken it.

  1. #6[stale][awaiting moderator]in section: ZachXBT Flag and Community Intelligence
    “an OFAC-sanctioned mixer as of August 2022”
    reviewerTornado Cash described as OFAC-sanctioned mixer as of August 2022, implying a current compliance dimensionSanction was lifted in March 2025, after the Fifth Circuit ruling in Nov 2024. At the time of the Aug 2024 exploit it was sanctioned, but the page implies a present regulatory dimension. Based on search results, not a fetched page.
    Proposed correction (not yet applied)
    a mixer that OFAC sanctioned in August 2022 and delisted in March 2025

partially supported

2 claims

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

  1. #3[partially supported][awaiting moderator]in section: Protocol Background
    “The protocol was audited four times prior to its exploit by Halborn, Sherlock (Contest #126), and Hats Finance (two separate competitions covering bonds/vesting and the Convex integration respectively).”
    reviewerProtocol audited four times by Halborn, Sherlock #126 and two Hats competitionsFour audits confirmed; auditor names and Sherlock contest number not independently verified (docs not fetched).
  2. #9[partially supported][awaiting moderator]in the timeline
    “2024-08-02”
    reviewerPost-mortem published 2024-08-02Post-mortem slug suggests Aug 1; exact publication date not confirmed. Also the timeline source fields are all empty.

confirmed

2 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in the summary
    “mint 58 million CVG tokens and sell them for approximately $212,000, collapsing the token price by 99%”
    reviewerAttacker minted 58 million CVG and sold for about $212,000 on Aug 1, 2024 via missing validation in CvxRewardDistributorCore exploit facts match Cointelegraph. Minor nuance: roughly $210k from token sales plus ~$2k rewards.
  2. #10[confirmed][no action needed]in section: Protocol Wind-Down and Successor Project
    “Over 97% of participating DAO voters chose the Tangent path.”
    reviewerDAO vote over 97% for Tangent, with Tangent a lending protocol with 10M fixed TAN supplyConfirmed by a tier-3 source; the primary Medium vote post returned 403 and the figures for treasury ($353k, $510k) were not verified.
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.