← Levyathan1 decision on this page
Audit log
Every state-changing event for Levyathan: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions carry three independent witnesses — the original source, an Internet Archive snapshot taken at submission time, and a Solana memo signed by our publicly-disclosed publisher key.
- #1publishby system:backfill2026-05-28 17:55:09ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 422,769,721
- sig
3cF2UfpFXLTC…oKgUUY9Eexplorer ↗- hash
FW6ZfGAffwA1…L2SdCNQRsha256 → base58
verifying row…full verify ↗canonical bytes (4495 B) ▸
{"actor":"system:backfill","investigation_id":"6ed9c996-80dd-4693-94c7-3a0ca2c16e79","kind":"publish","page_slug":"levyathan","published_at":"2026-05-28T17:55:09.062Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Levyathan","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://rekt.news/levyathan-rekt","type":"other","url":""},{"credibility":3,"name":"https://levyathan-index.medium.com/post-mortem-levyathan-c3ff7f9a6f65","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://rekt.news/levyathan-rekt","type":"other","url":""},{"credibility":3,"name":"https://levyathan-index.medium.com/post-mortem-levyathan-c3ff7f9a6f65","type":"other","url":""},{"credibility":3,"name":"https://levyathan-index.medium.com/levyathan-our-past-and-future-396b8e6f164b","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://levyathan-index.medium.com/levyathan-our-past-and-future-396b8e6f164b","type":"other","url":""},{"credibility":3,"name":"https://rekt.news/levyathan-rekt","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://rekt.news/levyathan-rekt","type":"other","url":""},{"credibility":3,"name":"https://levyathan-index.medium.com/post-mortem-levyathan-c3ff7f9a6f65","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://levyathan-index.medium.com/levyathan-our-past-and-future-396b8e6f164b","type":"other","url":""},{"credibility":3,"name":"https://levyathan-index.medium.com/post-mortem-levyathan-c3ff7f9a6f65","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://rekt.news/levyathan-rekt","type":"other","url":""},{"credibility":3,"name":"https://levyathan-index.medium.com/post-mortem-levyathan-c3ff7f9a6f65","type":"other","url":""}]}],"sources_used":[],"summary":"Levyathan was a Binance Smart Chain DeFi protocol billing itself as the first crypto index fund on BSC, launching in mid-2021. On July 30, 2021, the project collapsed after private keys controlling the token minting contract were left exposed in a public GitHub repository for approximately four months, enabling an attacker to mint and dump a quadrillion LEV tokens. A concurrent bug in the emergencyWithdraw() function compounded losses for stakers, and stolen funds were bridged to Ethereum and routed through Tornado Cash; the project never recovered and effectively disbanded.","timeline":[{"date":"2021-06-01","event":"Levyathan launches on Binance Smart Chain as an alleged first crypto index fund protocol on BSC; LEV token distributed via airdrop and sale.","source":""},{"date":"2021-07-01","event":"CertiK completes security audit of Levyathan smart contracts, identifying 18 issues with none labeled Critical.","source":""},{"date":"2021-07-28","event":"An unknown party submits a Timelock transaction to transfer ownership of the MasterChef contract, using private keys that had been left in Levyathan's public GitHub repository.","source":""},{"date":"2021-07-30","event":"Timelock delay expires; attacker executes ownership transfer, mints approximately 100 quintillion LEV tokens, dumps them on market, and bridges proceeds to Ethereum. LEV price collapses to near zero. Concurrent emergencyWithdraw bug allows early stakers to drain additional funds from the protocol.","source":""},{"date":"2021-07-30","event":"Levyathan team publishes initial post-mortem on Medium acknowledging the private key exposure and emergencyWithdraw bug. Recovery wallet address published.","source":""},{"date":"2021-08-05","event":"Rekt.news publishes detailed analysis of the exploit, questioning whether the public key story was a cover for an inside job and criticizing the team's communications.","source":""},{"date":"2021-08-01","event":"CertiK formally acknowledges audit failure via statement to the Levyathan team, accepting responsibility for missing the emergencyWithdraw vulnerability in the post-audit code review.","source":""},{"date":"2021-08-10","event":"Levyathan publishes final Medium post announcing project dissolution, confirming development funds are depleted, new developers have withdrawn, and all recovered funds will be distributed to victims. Official channels to be shut down.","source":""}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision 17750b3b-f1bb-4101-be3d-5139f01740da
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>.