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 · Abdelhakim Boukich
- Sequence
- #3
- Score
- 0 → 0 (-5)
- Cluster
- mainnet-beta
- Slot
- 464359726
- Off-chain at
- 2026-11-02T04:23:56.203Z
- Anchored at
- 2026-11-02T04:24:19.000Z
- Block time
- 2026-11-02T04:24:19.000Z
Independent verification
- 1. Database (off-chain)
- Hx7hb1SKGavb8NxKSEXD8SkmymdjaKUgvjBesBd1ev9u
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1418 chars)
{"actor":"judge","artifact_identity":"d6d22d22eee18b3d9a3f0702b55017c2","band_override":null,"decided_at":"2026-11-02T04:23:55.909Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1111,"investigation_id":"cfdf5a44-2df6-4901-9ea8-c6fafad47ef8","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"abdelhakim-boukich","prev_score":0,"reason":"The core facts on the page (OFAC designation on June 22, 2026, legal authority, SDGT tag, identifiers, aliases, and Bitcoin Xchange's founding) match Treasury and OFAC sources (claim_findings[0], [1], [7]). One of nine claims could not be verified (claim_findings[8], the FinCEN advisory and ICSVE/West Point reports), which puts the disputed share at about 11%. Several claims need wording fixes: 'holds Dutch nationality' conflicts with Treasury's 'formerly' (claim_findings[2]), the $10 million figure is TRM Labs' estimate rather than processed volume (claim_findings[4]), and the fee range is generic rather than specific to Bitcoin Xchange (claim_findings[3]). The omission of the Turkish co-designees is minor, and the subject is correctly shown as sanctioned.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}