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
review · KelpDAO
- Sequence
- #7
- Score
- 25 → 25 (0)
- Cluster
- mainnet-beta
- Slot
- 457714198
- Off-chain at
- 2026-10-16T17:04:48.559Z
- Anchored at
- 2026-10-16T17:04:51.552Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- MApN32m2fZKffgnYax1uP7dKD7sTVhg4j4fJr4uG341
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1919 chars)
{"actor":"reviewer","artifact_identity":"2afa9543342000946c2364be9b15afe1","decided_at":"2026-10-16T17:04:48.414Z","decision":"review","disputed_pct":0.2273,"findings_hash":"ADQP5j9pHfp5CWK91iMYH4g3xy3DDirumh1Bggqrnk38","investigation_id":"b3201664-21f2-4b65-b4dc-a85ecb74262d","mode":"findings_only","new_score":25,"page_content_hash":"5ecd59fe5d640651be63fda07c6d9f6739d831d32cefa1d21b80284e98050068","page_slug":"kelpdao","prev_score":25,"reason":"The page is a detailed, well-sourced account of the April 2026 KelpDAO/LayerZero exploit, and the large majority of claims I checked -- the exploit mechanics, dollar figures, DVN configuration dispute, LayerZero's public apology, the Arbitrum freeze and SDNY terrorism-judgment litigation, and the DeFi United recovery timeline -- are confirmed against the cited primary sources (LayerZero's own incident report and statement, fetched directly) and independent reporting (CoinDesk, Chainalysis, The Defiant, Yahoo Finance, TRM Labs). Two defects stand out: the page's own cited Yahoo Finance source directly contradicts its claim that AAVE fell 'approximately 10%' (the source says 'over 20%'), an error repeated in both a section and the timeline; and the claim that 'the same threat actor' was behind both the Drift Protocol and KelpDAO hacks is contradicted by the very TRM Labs submission used to source the $575M/18-day figure, which describes the two as distinct North Korea-linked groups. The Mantle 30,000 ETH 'DeFi United' contribution is also mischaracterized as a peer pledge when independent reporting describes it as an interest-bearing loan earmarked specifically for Aave bad debt. None of the three accepted community submissions contained adversarial instructions directed at the reviewer; all were bare URLs.","score_delta":0,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}