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 · RIVER Token
- Sequence
- #2
- Score
- 18 → 18 (0)
- Cluster
- mainnet-beta
- Slot
- 462056119
- Off-chain at
- 2026-10-27T11:36:45.497Z
- Anchored at
- 2026-10-27T11:37:20.000Z
- Block time
- 2026-10-27T11:37:20.000Z
Independent verification
- 1. Database (off-chain)
- BYBxL7Z5YEwXihkWodorzPm5NKbQuopDVZcXvGAa5MzB
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1556 chars)
{"actor":"reviewer","artifact_identity":"71b2048423b264f82c06efe0f0309335","blocked_count":1,"decided_at":"2026-10-27T11:36:45.061Z","decision":"review","disputed_pct":0.375,"findings_hash":"Di2CVJ4vcBHLTX4depnB1JdqqCe96YQfxQbWC4h48Xru","investigation_id":"e6823a2e-ed01-44dd-a357-e58d2f393aab","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":18,"omissions":{"material":1,"total":1},"page_content_hash":"6ebddfb02845db3d27dabb08855848ca77b4805f40c3a7fd2ea152b741f5bc19","page_slug":"river-token","prev_score":18,"reason":"The core narrative holds: the BuildKey launch dates, the ZachXBT bounty on May 18, 2026, the 80x futures-to-spot figure and the severe post-ATH crash are corroborated. Problems are a flatly wrong statement that no investors are publicly named (Justin Sun's $8M investment is public), internally inconsistent launch price percentages, the rally magnitude, one allegation phrased as established fact, and an official-site domain that does not match the prose. The page also omits the Justin Sun investment and ends in June 2026. No shutdown, exploit or sanction was found. Several key sources were blocked (403), which limits verification of the finer wallet-level claims.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}