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 · Zaid Issam Ahmed al-Jebouri / El-Kahira General Trading
- Sequence
- #3
- Score
- 0 → 0 (-12)
- Cluster
- mainnet-beta
- Slot
- 443522092
- Off-chain at
- 2026-08-26T20:09:08.919Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- GUjZYwb4ujpX6iUmKPVoDny3P8CBuWYpXkCNLCtkAtw
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1739 chars)
{"actor":"judge","decided_at":"2026-08-26T20:09:08.534Z","decision":"review_revise","investigation_id":"4b55635c-d0aa-47f0-9bb4-c9a40116fd5a","new_score":0,"page_slug":"zaid-issam-ahmed-al-jebouri-el-kahira-general-trading","prev_score":0,"reason":"The core finding on this page holds up: the July 23, 2026 OFAC Specially Designated Global Terrorist designation of Zaid Issam Ahmed al-Jebouri, El-Kahira for General Trading, and the two co-designees is confirmed in detail against Treasury's own press release and OFAC's listing, including an exact date-of-birth match for a co-designee (claim_findings[0], claim_findings[6]). Against that, the reviewer disputed 2 of 25 claims and could not verify 2 more (16% combined), concentrated in two internal dates recorded a full year later than independent sourcing supports — an Israel enforcement action and a related prior U.S. sanctions action (claim_findings[7], claim_findings[15]) — which also breaks the page's own six-month timeline calculation. Most consequential for a screening-oriented platform, seven specific cryptocurrency wallet addresses stated as fact could not be confirmed against any of the page's own cited sources (claim_findings[11]), and a sanctioned entity's name is misspelled in a way that would not match official watchlists (claim_findings[18]). A further ambiguity over whether an underground-banking allegation belongs to one named brother or both (claim_findings[9]) adds identification risk on a page about a living, publicly named individual. These issues call for correction, not removal or unconditional approval.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}