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

Fact-check findings

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

disputed

3 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. #1[disputed][awaiting moderator]in section: 2023 Rebase Vulnerability (Unexecuted)
    “In March 2023, a vulnerability was discovered in Vesper's rebalance mechanism by the Dedaub security research team and disclosed responsibly.”
    reviewerThe Dedaub rebase vulnerability was disclosed in March 2023The Immunefi postmortem was published May 7, 2021, so the March 16 discovery was in 2021.
    Proposed correction (not yet applied)
    In March 2021, a vulnerability was discovered in Vesper's rebalance mechanism by the Dedaub security research team and disclosed responsibly.
  2. #2[disputed][awaiting moderator]in the timeline
    “2023-03-16”
    reviewerDedaub discovered the vulnerability on 2023-03-16Same year error as in the section text.
    Proposed correction (not yet applied)
    2021-03-16
  3. #3[disputed][awaiting moderator]in the timeline
    “Vesper joins Immunefi with a $200,000 maximum bug bounty program for smart contract vulnerabilities.”
    reviewerVesper joined Immunefi with a $200,000 bounty in 2023Bounty launched in 2021 following the rebase fix. Date field is stored as 2023; the exact 2021 month is not given, so no precise replacement is proposed. Correct date field to 2021.

unverifiable

1 claim

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

  1. #6[unverifiable][awaiting moderator]in section: Security Posture and Audits
    “As of early 2026, Vesper Finance continues to operate with approximately $48 million in TVL, its highest level since 2022, supported by expansion to Base and Optimism.”
    reviewerTVL of approximately $48 million, highest since 2022DefiLlama blocked. Also, the summary says $48-55M and the timeline says ~$55M in Nov 2025, so the figures are internally inconsistent.

partially supported

1 claim

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

  1. #4[partially supported][awaiting moderator]in the timeline
    “Vesper governance approves $156,833 treasury allocation to remediate Sonne-related pool debt; all Optimism pools restored to operation.”
    reviewerGovernance approved the $156,833 treasury allocation on 2024-05-21Amount and date confirmed, but the cited thread is a discussion and shows no approval or restoration. The section's 'approved via a community governance proposal' and OP/USDC/wstETH pool names were not verified.

confirmed

1 claim

The cited evidence supports the claim as written.

  1. #5[confirmed][no action needed]in section: November 2021 Oracle Manipulation Exploit ($3.37 Million)
    “The attacker funded the attack with 100 ETH sourced from Tornado Cash.”
    reviewerExploit date, attacker address, Tornado Cash funding and approx $3.5M lossCore facts match. Fairyproof says about 56.82 ETH swapped (page says 58 ETH) and does not mention TWAP or the 0.05% pool; the Vesper Medium post (403) could not be read. The $3.37M net figure was not independently 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.