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 · Binance
- Sequence
- #12
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 466919193
- Off-chain at
- 2026-11-08T12:42:55.361Z
- Anchored at
- 2026-11-08T12:43:05.000Z
- Block time
- 2026-11-08T12:43:05.000Z
Independent verification
- 1. Database (off-chain)
- BqNiZqBJvjw9M9hnUffUVYNB5Vtjh8eb8ehBMqM1nr8n
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1397 chars)
{"actor":"judge","artifact_identity":"9736bcf3cd15e56645adcbeb14ed146d","band_override":null,"decided_at":"2026-11-08T12:42:55.000Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1111,"investigation_id":"ee0b172d-1fd3-47c7-812a-115748f8108a","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":26,"page_slug":"binance","prev_score":26,"reason":"One of nine checked claims was disputed (about 11%): claim_findings[3] gives April 2026 for the Blumenthal inquiry, while a Tier 1 source and the page's own timeline point to February 2026. Three more findings were only partly supported: an unclear Gambaryan detention date, a duplicated pardon timeline entry, and a section that says two security incidents without mentioning the October 2026 theft. The October 2026 theft figures and attribution match the Chainalysis primary source, and the one omission (Binance has not confirmed the North Korea attribution) is minor. Two high-priority coverage gaps (no primary FBI statement, no independent post-theft reserve audit) and limited reviewer confidence keep this as a small penalty rather than approval.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":12,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}