Fact-check findings
What an automated fact-checker found when it re-read Spartan Protocol against the sources the page cites. Only the most recent review is shown.
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
5 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #2[disputed][awaiting moderator]in section: May 2021 flash loan exploit
“On May 2, 2021, at approximately 04:38 UTC”
reviewerAttack occurred at approximately 04:38 UTC on May 2, 202104:38 UTC is after the project's first public report per CoinDesk, so it cannot be the attack time. Halborn gives no time; PeckShield was blocked (403). Suggested wording is cautious; exact on-chain block time not verified.Proposed correction (not yet applied)On May 2, 2021 (late May 1 in US time zones), shortly before Spartan's first public report at about 00:21 UTC - #8[disputed][awaiting moderator]in section: Anonymous team and governance
“The protocol's GitHub repositories show the last commit to spartan-contracts in March 2024 and the last update to spartan-docs in September 2023, indicating a sharp slowdown in development.”
reviewerRepository activity: last commit to spartan-contracts March 2024; spartan-docs September 2023; development largely stopped since 2024Dates on the org page do not match the page, and the summary's 'development has largely stopped since 2024' is contradicted by 2025-2026 activity in the DApp, API and site repos. Contract-level development does appear dormant.Proposed correction (not yet applied)The protocol's GitHub repositories show spartan-contracts last updated in September 2023 and spartan-docs in April 2023, while the community DApp repository (SpartanProtocol-DAppV2) was updated as recently as October 2026, indicating a sharp slowdown in smart-contract development. - #9[disputed][awaiting moderator]in the summary
“development has largely stopped since 2024”
reviewerSummary says development has largely stopped since 2024Same underlying issue as section 5.Proposed correction (not yet applied)smart-contract development has been dormant since 2023, though front-end repositories were still updated in 2026 - #10[disputed][awaiting moderator]in the timeline
“2024-03”
reviewerTimeline: last commit to spartan-contracts in 2024-03Possible confusion with the 'assets' repo (Mar 7, 2024).Proposed correction (not yet applied)2023-09 - #11[disputed][awaiting moderator]in the timeline
“2023-09”
reviewerTimeline: last update to spartan-docs in 2023-09Sep 2023 matches the spartan-contracts repo date instead.Proposed correction (not yet applied)2023-04
unverifiable
4 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #13[unverifiable][awaiting moderator]in section: Team response and compensation plan
“a snapshot at block 7048833 recording LP positions before the exploit”
reviewerCompensation plan: ~20 million SPARTA, snapshot block 7048833, 1:1 bridge, Code4rena bountySource blocked; no alternative reachable source checked for these specifics. - #14[unverifiable][awaiting moderator]in section: Pre-exploit audit
“Spartan Protocol v1 was audited by CertiK in September–October 2020, before launch.”
reviewerCertiK audited v1 in Sept-Oct 2020 with no critical findingsAudit PDF and Medium statement were not fetched in this review. - #15[unverifiable][awaiting moderator]in section: Fund recovery
“No credible source has reported that any portion of the approximately $30 million stolen was recovered.”
reviewerNo portion of the stolen funds has been reported recoveredNegative claim; searches found no recovery reports, but the cited Halborn article is silent. - #17[unverifiable][awaiting moderator]in section: Anonymous team and governance
“Spartan Protocol V2 launched on BNB Chain mainnet in October 2021”
reviewerV2 launched Oct 2021 on BNB Chain with four poolsNot fetched; plausible given the URL date and the Rebuilding timeline.
partially supported
5 claimsThe cited evidence supports part of the claim but not all of it.
- #4[partially supported][awaiting moderator]in the timeline
“Attacker uses a 100,000 WBNB PancakeSwap flash loan to manipulate calcLiquidityShare() and drain approximately $30 million from Spartan Protocol pools.”
reviewerTimeline entry cites CoinDesk for the flash loan and calcLiquidityShare() manipulationFacts are right (Halborn, Cointelegraph) but the cited CoinDesk article does not state the flash loan or function. Consider citing Halborn or PeckShield. - #5[partially supported][awaiting moderator]in section: May 2021 flash loan exploit
“The attacker routed proceeds through the 1inch aggregator (swapping into BTCB and BETH) and Nerve Finance, then bridged out of BSC via Anyswap.”
reviewerProceeds were routed through 1inch (BTCB, BETH), Nerve Finance, and bridged via AnyswapAnyswap bridging supported; 1inch/BTCB/BETH/Nerve not verified because PeckShield and BscScan were not readable. - #7[partially supported][awaiting moderator]in section: May 2021 flash loan exploit
“The SPARTA token fell by 30–70% within hours of the exploit becoming public.”
reviewerSPARTA fell 30-70% within hours of the exploit30% confirmed; 70% not found in fetched sources. - #12[partially supported][awaiting moderator]in section: Smart contract vulnerability — liquidity share miscalculation
“The function read the pool's live, manipulable token balance rather than the cached reserve values stored in baseAmountPooled and tokenAmountPooled.”
reviewerRoot cause: calcLiquidityShare() read live balance rather than cached valuesGeneral mechanism confirmed; variable names and Amber Group's fix not verified (Medium blocked). - #16[partially supported][awaiting moderator]in section: V2 relaunch and development activity
“As of May 2026 CoinGecko reported a price of approximately $0.0002”
reviewerSPARTA all-time high and price/market cap figures (~$0.0002, ~$15,000 market cap as of May 2026)Order of magnitude consistent; aggregators disagree on supply and ATH. Page already notes ATH divergence.
confirmed
3 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: May 2021 flash loan exploit
“an attacker drained approximately $30 million from Spartan Protocol's liquidity pools on Binance Smart Chain (BSC)”
reviewerExploit drained about $30 million from Spartan Protocol pools on BSC on May 2, 2021Loss figure and chain are consistent across sources. - #3[confirmed][no action needed]in section: May 2021 flash loan exploit
“The attack began with a 100,000 WBNB flash loan from PancakeSwap.”
reviewerAttack began with a 100,000 WBNB flash loan from PancakeSwap, repaid with a 260 WBNB feeLoan size confirmed by Halborn; the 260 fee appears in a search snippet from secondary coverage, not Halborn. - #6[confirmed][no action needed]in section: May 2021 flash loan exploit
“with stolen assets including approximately 2,643,882 SPARTA and 21,555 WBNB”
reviewerStolen assets ~2,643,882 SPARTA and 21,555 WBNB; 933,351 LP tokensFigures match Halborn.