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 · Shibarium
- Sequence
- #4
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 464275656
- Off-chain at
- 2026-11-01T23:23:49.817Z
- Anchored at
- 2026-11-01T23:24:10.000Z
- Block time
- 2026-11-01T23:24:10.000Z
Independent verification
- 1. Database (off-chain)
- 6PU86z8TpuYNS1VdESNAHuHTkUPUT8mSWuaCXjvfUTTC
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1525 chars)
{"actor":"judge","artifact_identity":"883ac9149192b0f8819c8255616c9397","band_override":null,"blocked_count":1,"decided_at":"2026-11-01T23:23:49.528Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"c14bc2fb-14f2-4013-827a-ab263a2823a2","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":52,"page_slug":"shibarium","prev_score":52,"reason":"Of 7 checked claims, 1 was excluded because its source could not be reached (claim_findings[2], the official post-mortem), leaving 6; 2 of those 6 (33%) could not be verified (claim_findings[5] and [6]), and none were disputed. The core exploit facts (claim_findings[0], [3]) are confirmed by The Block, and the $4.1M total (claim_findings[1]) is supported by a later report although several cited sources still carry the early $2.4M figure. The SEC/CFTC commodity classification (claim_findings[4]) rests only on crypto media, and the review flags primary-source verification as a high-priority coverage gap. No omissions or subject-status contradictions were found. The penalty sits at the low end of the band because the unverified items reflect limited reviewer coverage rather than contradicted claims, and reviewer confidence is low (0.45).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}