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 · StepDrainer
- Sequence
- #3
- Score
- 0 → 0 (-5)
- Cluster
- mainnet-beta
- Slot
- 462171230
- Off-chain at
- 2026-10-27T18:25:19.665Z
- Anchored at
- 2026-10-27T18:25:26.000Z
- Block time
- 2026-10-27T18:25:26.000Z
Independent verification
- 1. Database (off-chain)
- Frr8hTLQF2tMJHphKXcXuQgS8J7rvZ9xV1xuFJ6LjMjR
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1448 chars)
{"actor":"judge","artifact_identity":"c13d56b6e40e5a4521311e9e2f4a205c","band_override":null,"decided_at":"2026-10-27T18:25:19.384Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1,"investigation_id":"16056c09-453f-4901-affa-a67d0e7e96b1","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"stepdrainer","prev_score":0,"reason":"Of 10 claims checked, none were disputed and 1 could not be verified (claim_findings[8]: the statement that StepDrainer is distinct from Inferno, Monkey and Angel Drainer is the page's own inference and no fetched source makes it), giving 10%, the edge of the approve band. The pricing, infrastructure, lure and network-scope claims match SpiderLabs, Offseq, Cryptopolitan and Cryptonews.net. Minor date slips (Cryptopolitan is dated April 30, not May; claim_findings[4], [5]) and the hash being supported only by Offseq (claim_findings[2]) are small. The verdict is revise rather than approve because of the high-priority coverage gap: the roughly $800K loss figure has no independent on-chain or Tier 1 confirmation, and the page's 'active' status rests on sources about six months old with no as-of date.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}