Skip to main content
AVOID.NET

Fact-check findings

What an automated fact-checker found when it re-read Vesu Protocol (Pragma Oracle Malfunction — September 2026) 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. #3[disputed][awaiting moderator]in section: Recovery and Refund Process
    “reported recovering approximately 95% of lost value at September 13 prices”
    reviewer95% recovery measured at September 13 pricesBoth primary sources give 11 September as the pricing date, not 13 September. The 93% at incident-morning prices is correct.
    Proposed correction (not yet applied)
    reported recovering approximately 95% of lost value at September 11 prices
  2. #7[disputed][awaiting moderator]in the timeline
    “Multisig migration to 3-of-5 structure is initiated.”
    reviewerPragma multisig migration to 3-of-5 initiated on Sept 15The multisig migration is dated 22 September and the Foundation publisher activation 16 September. Neither belongs on 15 September. Suggest moving the multisig to a new 2026-09-22 timeline entry; a pure text swap is a minimal fix.
    Proposed correction (not yet applied)
    Multisig migration to 3-of-5 structure is not part of this entry; it was completed on 2026-09-22.

unverifiable

2 claims

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

  1. #12[unverifiable][awaiting moderator]in section: Oracle Dependency Risk
    “Vesu had no independent circuit breaker capable of detecting the two-minute price anomaly before liquidations executed.”
    reviewerVesu had no independent circuit breakerAnalytical assertion not found in the cited sources. Pragma's note that Vesu's source check may not see weak conversion inputs is only tangential.
  2. #14[unverifiable][awaiting moderator]in section: Distinction from September 17 Nostra Finance Incident
    “an attacker allegedly manipulated the market price of Nostra's native NSTR token approximately 8,000-fold”
    reviewerNostra Finance September 17 ~$3.5M loss, NSTR manipulation about 8,000-foldNot fetched, so unchecked. The cited URL slug mentions a 'Pragma oracle exploit', which sits awkwardly with the page's statement that this incident is unrelated to Pragma. Mechanism and any Pragma link should be checked.

partially supported

4 claims

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

  1. #4[partially supported][awaiting moderator]in section: Recovery and Refund Process
    “Liquidated borrowers receive a direct refund in their original collateral asset at approximately 95% of losses.”
    reviewerLiquidated borrowers receive a direct refund (page omits that they must open a Discord ticket with their curator)The page implies a passive refund. The source says borrowers must contact their curator, which matters given the page's scam warning.
  2. #8[partially supported][awaiting moderator]in section: Remediation and Protocol Changes
    “Pragma's multisig administration was migrated to a 3-of-5 multisig structure.”
    reviewerPragma's multisig administration was migrated to 3-of-5 (remediation section, undated and presented alongside Sept 13)True but overbroad. It omits the scope limitation and the date.
  3. #11[partially supported][awaiting moderator]in section: Oracle Dependency Risk
    “A comparable upstream oracle failure occurred in Aave in March 2026, reportedly resulting in approximately $26-27 million in unintended wstETH liquidations”
    reviewerAave March 2026 failure was an upstream oracle failure with ~$26-27M wstETH liquidationsAmounts match reporting. The cause was Aave's own CAPO configuration, not an upstream data provider. The claim has no cited source on the page. I did not fetch the page, so the correction rests on search-result summaries only.
  4. #13[partially supported][awaiting moderator]in the timeline
    “At approximately 04:40 UTC, Pragma's price feeds normalize without manual intervention.”
    reviewerTimeline: feeds normalize ~04:40; SDK 2.13.1 at 07:59 on Sept 4Time is supported. 'Without manual intervention' is not confirmed.

confirmed

6 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Incident Overview
    “Total collateral seized across the incident amounted to approximately $3,077,500. Borrower equity lost was approximately $783,905, and bad debt absorbed by the affected pools reached approximately $618,884.”
    reviewerLoss figures: 47 positions, 42 wallets, seven pools, $3,077,500 collateral, $783,905 borrower equity, $618,884 bad debtMatches the Pragma post-mortem exactly.
  2. #2[confirmed][no action needed]in section: Root Cause: Pragma Oracle Pipeline Failure
    “With only two data points, the median calculation returned their average: $2.036576.”
    reviewerRoot cause: USDC mapped to USDC.e, $3.073203 stale value, median $2.036576 from two observationsMatches the post-mortem.
  3. #5[confirmed][no action needed]in section: Recovery and Refund Process
    “Total assets recovered were stated as $1,330,278.93, with $1,324,085.08 distributable after conversion costs, against total claims of $1,395,300.76 from both lenders and borrowers.”
    reviewerRecovery amounts and total claimsMatches the Vesu refund post.
  4. #6[confirmed][no action needed]in section: Recovery and Refund Process
    “On September 7, 2026, the principal liquidator voluntarily returned seized assets, less their liquidation reward and costs, to the Vesu Security Council multisig.”
    reviewerPrincipal liquidator returned assets on September 7 (Pragma post-mortem)Date supported by Pragma.
  5. #9[confirmed][no action needed]in section: Remediation and Protocol Changes
    “Minimum source-count requirements for USDT/USDC feeds were strengthened to four sources.”
    reviewerMinimum source count of four for USDT/USDC; source-count reporting for composed prices pendingSupported. The pending-reporting caveat is also supported.
  6. #10[confirmed][no action needed]in section: Remediation and Protocol Changes
    “The Starknet Security Council temporarily restricted six addresses associated with the incident as part of its standard governance response; all restrictions were subsequently lifted after the investigation concluded.”
    reviewerStarknet Security Council temporarily restricted six addresses, later liftedSupported.
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.