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 · WaterPlum / Contagious Interview
- Sequence
- #3
- Score
- 0 → 0 (-12)
- Cluster
- mainnet-beta
- Slot
- 462279536
- Off-chain at
- 2026-10-28T00:49:06.105Z
- Anchored at
- 2026-10-28T00:50:00.000Z
- Block time
- 2026-10-28T00:50:00.000Z
Independent verification
- 1. Database (off-chain)
- 9JzMpSGoHwjVxgAprBGQ48i5MA4uJNZFSnHVGYuwPt6N
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1397 chars)
{"actor":"judge","artifact_identity":"37b3f876b1e9e3f744633ec0f063889c","band_override":null,"decided_at":"2026-10-28T00:49:05.861Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"3ff27a94-3426-4ecf-8cd4-fa6a1e524dcb","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"waterplum-contagious-interview","prev_score":0,"reason":"Of 7 checked claims, 1 was disputed (claim_findings[3], the bitFlyer incident dated January 2025 when reporting says May 2025) and 1 could not be found in any source (claim_findings[6], the 2022 and 2023 origin dates), giving about 29%, which is the minor-issues band. The core figures, the 313 General Bureau attribution and the five malware families were confirmed (claim_findings[0], [1], [4]). The exact seven-agency roster (claim_findings[2]) and the attribution of the several hundred million yen (claim_findings[4]) were only partly supported, and the primary government advisories could not be read, so the penalty sits in the upper half of the band. No material omission was found and the group is still reported as operating.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}