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 · Pishtaz Simorgh Electronic Trade Company
- Sequence
- #4
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 462173059
- Off-chain at
- 2026-10-27T18:31:27.166Z
- Anchored at
- 2026-10-27T18:31:56.000Z
- Block time
- 2026-10-27T18:31:56.000Z
Independent verification
- 1. Database (off-chain)
- 8Sdu4Smbw3aq4JJwuzn2TZvBLs723cjfB53rCrACDzRh
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1523 chars)
{"actor":"judge","artifact_identity":"075eaca27d5cda6b69abaef581176cb8","band_override":null,"decided_at":"2026-10-27T18:31:26.782Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4375,"investigation_id":"f773b798-c1e2-4616-8a76-3c4a30269449","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"pishtaz-simorgh-electronic-trade-company","prev_score":0,"reason":"Of 16 claims checked, 5 were disputed and 2 could not be verified (7 of 16, about 44%), which falls in the significant-issues band. The core allegations hold up: the Sept 17, 2026 OFAC designation, the identifiers, the Dot One subsidiary link and the BitBank allegations were confirmed by Tier 1 sources (claim_findings[0], [1], [9], [12]). The errors are in secondary context: the sectoral determination is dated Sept 17 in three places but Treasury issued it on Aug 24, 2026 (claim_findings[2]-[4]); the designation is called the 'fourth' action when the page lists three (claim_findings[5]); the $94 billion Zedcex figure is not in the cited source (claim_findings[6]); and a timeline date is a placeholder (claim_findings[7]). Because the core claims are sound and the reviewer's confidence is 0.8, the penalty sits at the lenient end of the band.","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}