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.
- Sequence
- #2
- Score
- 5 → 5 (0)
- Cluster
- mainnet-beta
- Slot
- 443521967
- Off-chain at
- 2026-08-26T20:06:04.952Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BxxciP6Yc3J2QdANRobRoWFXG4AvM33WYFuuU3C7eBXN
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1212 chars)
{"actor":"reviewer","decided_at":"2026-08-26T20:06:04.583Z","decision":"review","investigation_id":"02dd591c-879c-4f2f-b0a7-2f84a0be2243","new_score":5,"page_slug":"interpol-operation-first-light-2026-123m-romance-scam-crypto-network","prev_score":5,"reason":"The page's core Operation First Light 2026 statistics (arrests, dollar figures, victim counts, case metrics, funding, and the headline Thailand $122.5M crypto-wallet case) are strongly confirmed against INTERPOL's own primary press release, and the page correctly avoids merging the 2024 and 2026 editions' figures. However, the page's treatment of the parallel Operation Red Card 2.0 sub-operation contains a significant, load-bearing attribution error: INTERPOL's own official release for Red Card 2.0 does not mention Binance or AFRIPOL at all and credits different technical partners and a different funder, contradicting both the page's framing and its own cited tier-1 source; the Red Card 2.0 country list also incorrectly includes South Africa in place of several other nations INTERPOL actually named.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}