Verify a decision
Every moderation decision on AVOID.NET is anchored to the Solana blockchain. You don't have to trust us — you can verify cryptographically that we committed to a verdict at a specific moment and have not rewritten it.
How verification works
- We commit. When a moderator accepts/rejects a submission, we serialize the decision into deterministic UTF-8 bytes (
payload_canonical_string), hash it with SHA-256, encode the digest as base58, and write it to Solana inside an SPL Memo v2 transaction. - We store the bytes. The exact bytes we hashed are stored alongside the decision in our database. Anyone can read them and recompute the hash in any language.
- You compare three values. Database hash, your independently-recomputed hash, and the hash inside the on-chain memo. If all three match, the decision is authentic and timestamped.
The on-chain memo format is
AVOID.NET|v1|h:<b58-sha256>|d:<id>|t:<iso>Find a signature on any investigation page's decision log, or run python -m src.verify_decision --signature <sig> for a CLI check.
Decision
publish · Spartan Protocol
- Sequence
- #1
- Score
- →
- Cluster
- mainnet-beta
- Slot
- 422206358
- Off-chain at
- 2026-05-26T03:49:36.045Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7DaFbLhZDtJq7feun8ybuKzBMvhDPGUD6A843YJ34Th4
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (6182 chars)
{"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}