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 · FEGex
- Sequence
- #4
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 464275206
- Off-chain at
- 2026-11-01T23:22:13.058Z
- Anchored at
- 2026-11-01T23:22:32.000Z
- Block time
- 2026-11-01T23:22:32.000Z
Independent verification
- 1. Database (off-chain)
- 7L5cFHVpSZAfJ2FMsAqKq9pe2qycjJt9rbZ7HdbtdgRA
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1284 chars)
{"actor":"judge","artifact_identity":"18d01d06c212fa63494082370c96e200","band_override":null,"blocked_count":1,"decided_at":"2026-11-01T23:22:12.801Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4545,"investigation_id":"371a48cc-77ea-4fda-beae-4efc4fc12f75","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"page_slug":"fegex","prev_score":53,"reason":"Of 12 countable claim findings (one blocked source excluded), 2 were disputed and 3 could not be verified, giving about 42% disputed or unverifiable. The December 2024 bridge loss is stated as $1.3 million on the page, but the cited CertiK and Protos reports give about $1 million (claim_findings[0], [1]). The $3.6 million cumulative total has no source (claim_findings[2]). The paused-status, Hotbit listing and ZachXBT claims could not be sourced (claim_findings[7], [8], [9]). The three exploit narratives themselves were confirmed by primary analyses, so the penalty sits at the lenient end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}