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_revise · AnubisDAO
- Sequence
- #3
- Score
- 2 → 0 (-15)
- Cluster
- mainnet-beta
- Slot
- 461973756
- Off-chain at
- 2026-10-27T06:44:49.745Z
- Anchored at
- 2026-10-27T06:45:25.000Z
- Block time
- 2026-10-27T06:45:25.000Z
Independent verification
- 1. Database (off-chain)
- G5JMLQfJDMaQK49jMaSvQFszN1h9sBn7mCDRe7Zxheq2
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1374 chars)
{"actor":"judge","artifact_identity":"c52e06e164c4868fa3e49e417e891717","band_override":null,"decided_at":"2026-10-27T06:44:49.343Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4,"investigation_id":"14f590e2-8d66-4af0-a96f-2f8b300fef26","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"anubisdao","prev_score":2,"reason":"Of 10 claims checked, 3 were disputed and 1 could not be verified, giving a disputed share of 40%, which falls in the significant-issues band. The three disputed findings (claim_findings[0], [1], [2]) are one error: the page merges the June 2022 laundering of 1,018 ETH with the separate July 15-16, 2023 batches of 100 ETH, creating a false 'reports differ' discrepancy and a misdated timeline entry. The Tornado Cash sanctions framing is out of date because Treasury lifted them in March 2025 (claim_findings[3]), though the review rates that omission as minor. The core account (about $60M raised, pool drained, competing narratives, ZachXBT's attribution, no charges) was supported, so the penalty sits at the low end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}