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 · DODO AMM
- Sequence
- #14
- Score
- 73 → 73 (0)
- Cluster
- mainnet-beta
- Slot
- 470684820
- Off-chain at
- 2026-11-17T21:29:43.373Z
- Anchored at
- 2026-11-17T21:30:16.000Z
- Block time
- 2026-11-17T21:30:16.000Z
Independent verification
- 1. Database (off-chain)
- 7q58mBag1yyzbUTFVqq1wb5Gxi2nyXQYZoB48fjfXAZk
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1222 chars)
{"actor":"judge","artifact_identity":"37e117573c6702c9b3dc1ea0a9cb28fe","band_override":null,"blocked_count":1,"decided_at":"2026-11-17T21:29:42.922Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"3ff37634-d276-4760-a4b9-2c4b57a50a6d","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":73,"page_slug":"dodo-amm","prev_score":73,"reason":"Of 7 claim findings, 6 were confirmed against The Block and Halborn (exploit amount, affected pools, mechanism, dates, and both recovery figures) and none were disputed. One finding, claim_findings[5] on DeFiLlama TVL figures, could not be read because the source was blocked or too large, so it was excluded from the calculation; that is a coverage limit, not a defect of the page. The calculated disputed share is 0%. The review found no omissions and no contradiction of the page's status, and the open coverage gaps are low or medium priority.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"scored_claims":6,"sequence_num":14,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}