Fact-check findings

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 section: Protocol Logic Exploit — March 2026

   “The incident is classified as a protocol logic vulnerability by SmartContractHacking.com, which notes the vulnerability 'could have been caught in audit.'”

   reviewerThe SmartContractHacking.com page says the vulnerability 'could have been caught in audit'Quoted phrase does not appear in the cited source.
   Proposed correction (not yet applied)

   The incident is classified as a protocol logic vulnerability (pool mispricing) by SmartContractHacking.com, which states the root cause is unconfirmed.
   citedsmartcontractshacking.com/hacks/goonfi-hack-2026
2. #3[disputed][awaiting moderator]in section: ZachXBT Flag and Community Warnings

   “per SmartContractHacking.com, 'could have been caught in audit.'”

   reviewerSame 'could have been caught in audit' quote repeated in the audits sectionFabricated or misattributed quote; also 'directly resulted from a protocol logic flaw' overstates an unconfirmed root cause.
   Proposed correction (not yet applied)

   per SmartContractHacking.com, the root cause remains unconfirmed.
   citedsmartcontractshacking.com/hacks/goonfi-hack-2026

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

1. #4[unverifiable][awaiting moderator]in section: Protocol Logic Exploit — March 2026

   “After extracting funds, the attacker is alleged to have moved assets through mixers or cross-chain bridges to obscure the trail, converting proceeds to more liquid or privacy-preserving assets.”

   reviewerAttacker moved funds through mixers or bridges; allegedNo fetched source mentions mixers; looks like generic boilerplate. The timeline repeats it as 'allegedly moved through mixers'.
   citedsmartcontractshacking.com/hacks/goonfi-hack-2026
2. #6[unverifiable][awaiting moderator]in the timeline

   “ZachXBT flags GoonFi following the exploit. No public team response or compensation plan issued.”

   reviewerZachXBT flagged GoonFi following the exploit on 2026-03-28No source found for a ZachXBT flag; the page itself concedes it is unconfirmed yet states it flatly in the summary and timeline with a specific date. Also the cited source says the team reportedly halted the program, which conflicts with 'no public team response'.
3. #7[unverifiable][awaiting moderator]in the summary

   “The protocol has been flagged by ZachXBT and is cited by researchers as representative of a broader Solana centralization concern”

   reviewerSummary states GoonFi has been flagged by ZachXBTUnsupported assertion; the body section admits no primary source.
4. #10[unverifiable][awaiting moderator]in section: Centralization and Systemic Risk

   “GoonFi holds approximately 6% of the Prop AMM market on Solana, processing around $113 million in daily volume at peak.”

   reviewerGoonFi holds ~6% of Prop AMM market and ~$113M daily volume at peakHelius does not support this; other cited sources not checked for it (DeFiLlama blocked with 403).
   citedwww.helius.dev/blog/solanas-proprietary-amm-revolution
5. #11[unverifiable][awaiting moderator]in section: ZachXBT Flag and Community Warnings

   “GoonFi's oracle update frequency is described as 'one of the lowest among competitors,'”

   reviewerOracle update frequency described as one of the lowest among competitorsNot in fetched text; may be in a chart, unverified.
   citedwww.helius.dev/blog/solanas-proprietary-amm-revolution
6. #12[unverifiable][awaiting moderator]in section: Protocol Overview

   “Cumulative DEX volume on DeFiLlama reached approximately $29.8 billion as of May 2026, while measured total value locked (TVL) stands at $0”

   reviewerCumulative DEX volume ~$29.8B per DeFiLlama and TVL $0DeFiLlama returned 403 to the fetcher; not scored.
   citeddefillama.com/protocol/goonfi

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

1. #5[partially supported][awaiting moderator]in section: Protocol Logic Exploit — March 2026

   “According to a post-mortem published on X (Twitter) by the handle 'cetipo' (referenced at https://x.com/cetipo/status/2037892924982038893), the exploit required technical expertise in arbitrage mechanics, Solana programming, and precise transaction timing.”

   reviewerPost-mortem by 'cetipo' on X describes required expertiseSource calls it an alert, not a post-mortem; expertise claim unsupported. Timeline entry repeats 'Post-mortem published by cetipo'.
   citedsmartcontractshacking.com/hacks/goonfi-hack-2026
2. #8[partially supported][awaiting moderator]in section: Protocol Overview

   “By July 2025, aggregator-driven trades through Jupiter accounted for 99.2% of all GoonFi volume, indicating near-total dependence on a single routing source.”

   reviewer99.2% of GoonFi volume in July 2025 came via JupiterFigure is for aggregators in general, not Jupiter alone. Timeline entry for 2025-07 says 'via Jupiter' as well.
   citedwww.helius.dev/blog/solanas-proprietary-amm-revolution
3. #9[partially supported][awaiting moderator]in section: Team Anonymity and Transparency Concerns

   “Helius developer research states GoonFi 'is operated by professional DeFi market-making firms and Solana-native teams that have so far chosen to keep their involvement under the radar.'”

   reviewerHelius says GoonFi is operated by professional market-making firmsSubstance matches, but it applies to the group, not GoonFi specifically.
   citedwww.helius.dev/blog/solanas-proprietary-amm-revolution

The cited evidence supports the claim as written.

1. #1[confirmed][no action needed]in the summary

   “On March 28, 2026, a protocol logic vulnerability was exploited via mispricing arbitrage, resulting in approximately $254,000 in losses with no recovery reported.”

   reviewerOn March 28, 2026 GoonFi was exploited for about $254,000 via a protocol logic flawDate, amount and classification match. 'No recovery reported' not contradicted.
   citedsmartcontractshacking.com/hacks/goonfi-hack-2026