Skip to main content
Sign in
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · Levyathan
View on Solana ↗
Sequence
#1
Score
Cluster
mainnet-beta
Slot
422769721
Off-chain at
2026-05-28T17:55:09.114Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
FW6ZfGAffwA1VRBG8a4z5bpAYE7L9W5zwtEUL2SdCNQR
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (4495 chars)
{"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}