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 · Hossein Ali Zaker Hossein
- Sequence
- #4
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 462279155
- Off-chain at
- 2026-10-28T00:48:07.367Z
- Anchored at
- 2026-10-28T00:48:39.000Z
- Block time
- 2026-10-28T00:48:39.000Z
Independent verification
- 1. Database (off-chain)
- ATyGk79sBWz7gU81xFSxPqGB2zcipWSwzgomr7CuA9v8
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1631 chars)
{"actor":"judge","artifact_identity":"c98c1031ddecdddf5ef7c30e5c33dfb9","band_override":null,"decided_at":"2026-10-28T00:48:07.126Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"f1ace6e8-a8c9-428a-95ef-247f699e7121","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"hossein-ali-zaker-hossein","prev_score":26,"reason":"The core claims hold up against Treasury and OFAC primary sources: the September 17, 2026 designation, the SDN identifiers, his role as a Dot One executive and the co-designees (claim_findings[0], [1], [10]). Of 12 claims, 1 was disputed (the Hormuz Safe Marine Services Authority designation was July 29, not July 24; claim_findings[4]) and 1 could not be verified (the absence of criminal charges; claim_findings[11]), giving a disputed share of about 17%. Several further claims were only partly supported: the page ties his brokering to BitBank and to June-July 2026 more tightly than Treasury does, attributes the 'nearly 60 designations' figure and EU/UK/Gulf coordination to the September 17 action, and uses placeholder timeline dates (claim_findings[2], [3], [5], [6], [7], [8]). The one omission found is minor, the sanctioned status is already stated on the page, and no coverage gap is high priority, so the page needs corrections rather than a larger penalty.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}