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_approve · StakeDAO — vsdCRV Deployer Key Exploit (May 2026)
- Sequence
- #3
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 443517220
- Off-chain at
- 2026-08-25T22:11:12.790Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7f4iLRPWmQ6vrJYmpWGQA9HMBV5mRreEv18ywR3LvhCK
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1469 chars)
{"actor":"judge","decided_at":"2026-08-25T22:11:12.520Z","decision":"review_approve","investigation_id":"1b36e032-1618-4172-a80f-e475afaaf1a7","new_score":38,"page_slug":"stakedao-vsdcrv-deployer-key-exploit-may-2026","prev_score":38,"reason":"Of 30 factual claims checked, 26 were fully confirmed against independent and primary sources, none were disputed, and only 4 had minor qualifications: two were 'partially supported' (claim_findings[15]'s DEX list omits two additional routers named in fuller reporting, and claim_findings[29]'s $770 million industry loss figure is directionally accurate but not found verbatim in the three sources cited for it), and two were 'unverifiable' (claim_findings[26] and [30], both concerning whether the follow-up SDGP-75 governance proposal formally passed and its exact vote-close date, which could not be confirmed from a fetchable primary source but were also not contradicted by any source). That puts disputed_pct at 6.7%, well within the approve range. The reviewer also flagged a high-priority coverage gap about StakeDAO's current TVL and protocol health since the incident; that is a legitimate suggestion for expanding the page, not evidence that anything currently stated is wrong, so it does not by itself justify holding back approval on an otherwise strongly sourced page.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}