← Spartan Protocol4 decisions on this page
Audit log
Every state-changing event for Spartan Protocol: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.
- #1publishby system:backfill2026-05-26 03:49:36ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 422,206,358
- sig
5xaSPkAX1NtK…qnqryUKXexplorer ↗- hash
7DaFbLhZDtJq…3YJ34Th4sha256 → base58
verifying row…full verify ↗canonical bytes (6182 B) ▸
{"actor":"system:backfill","investigation_id":"831828e5-711a-4123-a4ac-a35a12746d72","kind":"publish","page_slug":"spartan","published_at":"2026-05-26T03:49:35.903Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Spartan Protocol","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://peckshield.medium.com/the-spartan-incident-root-cause-analysis-a0324cb4b42a","type":"other","url":""},{"credibility":3,"name":"https://medium.com/amber-group/exploiting-spartan-protocols-lp-share-calculation-flaws-391437855e74","type":"other","url":""},{"credibility":3,"name":"https://www.halborn.com/blog/post/explained-the-spartan-protocol-hack-may-2021","type":"other","url":""},{"credibility":3,"name":"https://www.coindesk.com/markets/2021/05/02/binance-smart-chains-spartan-protocol-loses-30m-in-exploit","type":"other","url":""},{"credibility":3,"name":"https://cointelegraph.com/news/spartan-protocol-exploit-results-in-loss-of-30m","type":"other","url":""},{"credibility":3,"name":"https://bscscan.com/address/0x3b6e77722e2bbe97c1cfa337b42c0939aeb83671","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://github.com/spartan-protocol/resources/blob/master/certik-audit.pdf","type":"other","url":""},{"credibility":3,"name":"https://www.certik.com/projects/spartanprotocol","type":"other","url":""},{"credibility":3,"name":"https://spartanprotocol.medium.com/today-spartan-protocol-was-subject-to-an-exploit-targeting-the-liquidity-pools-8589b2069cef","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://medium.com/spartanprotocol/announcing-the-spartan-protocol-e15af93a8a8f","type":"other","url":""},{"credibility":3,"name":"https://blog.spartanprotocol.org/announcing-the-spartan-protocol/","type":"other","url":""},{"credibility":3,"name":"https://medium.com/spartanprotocol/spartan-protocol-faqs-339c6ee6bf0","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://spartanprotocol.medium.com/rebuilding-spartan-protocol-25a2901e4637","type":"other","url":""},{"credibility":3,"name":"https://blog.spartanprotocol.org/rebuilding-spartan-protocol/","type":"other","url":""},{"credibility":3,"name":"https://spartanprotocol.medium.com/spartan-protocol-road-to-v2-cont-a1f7b431b4e","type":"other","url":""},{"credibility":3,"name":"https://github.com/spartan-protocol","type":"other","url":""},{"credibility":3,"name":"https://x.com/spartanprotocol/status/1388654212024705024","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://coinmarketcap.com/currencies/spartan-protocol/","type":"other","url":""},{"credibility":3,"name":"https://www.coingecko.com/en/coins/spartan-protocol","type":"other","url":""},{"credibility":3,"name":"https://coincodex.com/crypto/spartan-protocol/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://protos.com/bsc-binance-smart-chainflash-loan-attacks-crypto-may/","type":"other","url":""},{"credibility":3,"name":"https://beincrypto.com/spartan-defi-suffers-30m-loss-bsc-flash-loan-attack/","type":"other","url":""},{"credibility":3,"name":"https://www.benzinga.com/markets/cryptocurrency/21/05/20909436/another-day-another-defi-hack-spartan-protocol-exploited-for-over-30m","type":"other","url":""}]}],"sources_used":[],"summary":"Spartan Protocol is a decentralized liquidity and synthetic-asset protocol that launched on Binance Smart Chain (BSC) in 2020 and was operated by a fully anonymous, community-driven team. On May 2, 2021, a critical vulnerability in the protocol's liquidity-share calculation logic was exploited via flash loan, resulting in approximately $30 million in stolen funds — ranking it among the largest DeFi exploits of that era. The protocol attempted a v2 rebuild with re-audited contracts but has since fallen to near-zero TVL and market cap, with no meaningful development activity recorded after 2024.","timeline":[{"date":"2020-09-18","event":"CertiK begins audit of Spartan Protocol v1 smart contracts; audit revised October 5, 2020. No critical vulnerabilities reported.","source":""},{"date":"2020-10-05","event":"CertiK audit finalized with no critical findings. Protocol proceeds toward launch on Binance Smart Chain.","source":""},{"date":"2021-02-01","event":"Spartan Protocol publicly operational on BSC with SPARTA token distributed via Proof-of-Burn mechanism.","source":""},{"date":"2021-05-02","event":"Flash loan exploit drains approximately $30 million from Spartan Protocol liquidity pools. Attacker uses 100,000 WBNB flash loan from PancakeSwap to exploit calcLiquidityShare() vulnerability. Attacker address: 0x3b6e77722e2bbe97c1cfa337b42c0939aeb83671.","source":""},{"date":"2021-05-02","event":"PeckShield and Amber Group publish independent root cause analyses. SPARTA token falls 30–70% within hours of news.","source":""},{"date":"2021-05-02","event":"Spartan Protocol team publishes post-mortem and recovery roadmap via Twitter and Medium, announcing plans to work with Binance on fund recovery and resume v2 development.","source":""},{"date":"2021-05-03","event":"Over $100,000 in additional user funds reported still at risk across multiple BSC pairs (WBNB, BUSD, CREAM, ETH, BURGER, XRP, DOT, LINK, RAVEN).","source":""},{"date":"2022-01-01","event":"Code4rena competitive audit of Spartan Protocol v2 contract suite completed, funded in part by Binance BUIDL grant.","source":""},{"date":"2023-09-25","event":"Last recorded update to spartan-docs GitHub repository, signaling slowdown in documentation maintenance.","source":""},{"date":"2024-03-07","event":"Last recorded commit to spartan-contracts GitHub repository, indicating near-cessation of active development.","source":""},{"date":"2025-04-19","event":"CoinLore reports no price data received for SPARTA after this date, suggesting possible delisting or abandonment. Market cap falls to approximately $13,000.","source":""}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision 8eed15d7-60cb-4b77-a910-b7da6cebea71 - #2rescoreby systemsystem2026-10-10 18:49:02ZScore: 12 → 59 (+47)Rescored under Scoring v2, the published formula (avoid.net/scoring): 12 → 59. Problems weighed by who is responsible: incidents the subject suffered −6.4, concerns that are not fraud −6.4, problems around the subject, caused by others −1.6; legitimacy credit long-running +8.anchoranchored
- chain
- ●mainnet-betaslot 455,368,989
- sig
4abbuNyihqQs…mtqe2TPqexplorer ↗- hash
G3hw1oA9yj5V…Tug3sErEsha256 → base58
verifying row…full verify ↗canonical bytes (638 B) ▸
{"actor":"system","decided_at":"2026-10-10T18:49:02.148Z","decision":"rescore","investigation_id":"831828e5-711a-4123-a4ac-a35a12746d72","new_score":59,"page_slug":"spartan","prev_score":12,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 12 → 59. Problems weighed by who is responsible: incidents the subject suffered −6.4, concerns that are not fraud −6.4, problems around the subject, caused by others −1.6; legitimacy credit long-running +8.","score_delta":47,"score_model":"v2","sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 56ef0c4b-de64-4d6f-8a88-4b65d1e9bf79 - #3reviewby reviewerreviewer2026-10-27 06:39:35ZScore: 59 → 59 (no score change)The core incident (about $30M flash loan exploit of the liquidity share calculation on BSC, May 2021) is well supported. Problems: the stated 04:38 UTC attack time conflicts with CoinDesk's report that the team disclosed the exploit around 00:21 UTC; GitHub dates and the 'development stopped since 2024' claim do not match the org page, which shows contracts last updated September 2023 and DApp/API repos updated in 2026; the timeline CoinDesk citation does not say what the entry claims. Many team-statement and audit details could not be checked because Medium returned 403.anchoranchored
- chain
- ●mainnet-betaslot 461,972,224
- sig
3oG99b3pLVwg…6Xvke4Xqexplorer ↗- hash
3PNzXy8fhnS9…3fy8aSxCsha256 → base58
verifying row…full verify ↗canonical bytes (1424 B) ▸
{"actor":"reviewer","artifact_identity":"b02fb6c5463ac9fd791b5e69b382f686","blocked_count":2,"decided_at":"2026-10-27T06:39:35.644Z","decision":"review","disputed_pct":0.4667,"findings_hash":"GiAHnTLaKhrjTuf63pqMHwj67ERYCcRmaAPzjuSvxuKU","investigation_id":"831828e5-711a-4123-a4ac-a35a12746d72","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":59,"page_content_hash":"c898ab2d9c6ff848684320b59c9bcafe42acd1ecebde00c048046117f70ca90c","page_slug":"spartan","prev_score":59,"reason":"The core incident (about $30M flash loan exploit of the liquidity share calculation on BSC, May 2021) is well supported. Problems: the stated 04:38 UTC attack time conflicts with CoinDesk's report that the team disclosed the exploit around 00:21 UTC; GitHub dates and the 'development stopped since 2024' claim do not match the org page, which shows contracts last updated September 2023 and DApp/API repos updated in 2026; the timeline CoinDesk citation does not say what the entry claims. Many team-statement and audit details could not be checked because Medium returned 403.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":15,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 70b429a0-7490-4882-917b-c826796c16d1 - #4review reviseby judgejudge2026-10-27 06:39:35ZScore: 59 → 59 (no score change)Of 17 checked claims, 2 could not be assessed because the source blocked the reviewer and are left out. Of the remaining 15, 5 were disputed and 2 were unverifiable, which is about 47% and falls in the significant-issues band. The core allegation, a roughly $30 million flash loan exploit on BSC in May 2021, is confirmed (claim_findings[0], [2], [5]). The disputes are the stated 04:38 UTC attack time, which CoinDesk's report of a 00:21 UTC disclosure contradicts (claim_findings[1]), and the GitHub activity dates and the claim that development stopped in 2024, which the organisation page contradicts (claim_findings[7]-[10]). Because the disputes are peripheral to the core allegation and the reviewer's confidence is modest (0.55), the penalty sits at the low end of the band.anchoranchored
- chain
- ●mainnet-betaslot 461,972,227
- sig
4bsLaMdPNQc8…oeTsMEQxexplorer ↗- hash
ESFmF6ZB85hx…9R4cvpkxsha256 → base58
verifying row…full verify ↗canonical bytes (1871 B) ▸
{"actor":"judge","artifact_identity":"b02fb6c5463ac9fd791b5e69b382f686","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T06:39:35.644Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4667,"investigation_id":"831828e5-711a-4123-a4ac-a35a12746d72","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":59,"page_slug":"spartan","prev_score":59,"reason":"Of 17 checked claims, 2 could not be assessed because the source blocked the reviewer and are left out. Of the remaining 15, 5 were disputed and 2 were unverifiable, which is about 47% and falls in the significant-issues band. The core allegation, a roughly $30 million flash loan exploit on BSC in May 2021, is confirmed (claim_findings[0], [2], [5]). The disputes are the stated 04:38 UTC attack time, which CoinDesk's report of a 00:21 UTC disclosure contradicts (claim_findings[1]), and the GitHub activity dates and the claim that development stopped in 2024, which the organisation page contradicts (claim_findings[7]-[10]). Because the disputes are peripheral to the core allegation and the reviewer's confidence is modest (0.55), the penalty sits at the low end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":15,"sequence_num":4,"severity_override":{"applied":false,"band":null,"from_band":"significant","reason":"subject_status.contradicts_page is true, but only because the page says development has largely stopped since 2024 while front-end repositories were updated in 2026. No shutdown, exploit or sanction is left unmentioned and there are no omission findings. The percentage band already reflects this issue (claim_findings[7])."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 804b84d1-3340-436b-910e-ab80e9e98011
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine —
python -m src.verify_decision <event_id>.