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 · Bitcoin Xchange (Syria-based, ISIS-Linked)
- Sequence
- #3
- Score
- 0 → 0 (-7)
- Cluster
- mainnet-beta
- Slot
- 443504928
- Off-chain at
- 2026-08-08T00:23:51.974Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AcAtvrQj2QMiTAM25NBKZY8e2Jxyyh1TjvtFujTSU3La
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1539 chars)
{"actor":"judge","decided_at":"2026-08-08T00:23:51.051Z","decision":"review_revise","investigation_id":"3e49786b-944c-4251-9a0d-7dac931261b9","new_score":0,"page_slug":"bitcoin-xchange-syria-based-isis-linked","prev_score":0,"reason":"The page's core factual claims are well-supported by Tier 1 sources. The June 22, 2026 OFAC designation date, formal entity names, Syrian locations, individual designees, network entity count, and the $10 million transaction volume figure were all confirmed verbatim against the Federal Register (FR Doc. 2026-13102). The single disputed finding — claim_findings[17] — is not a factual inaccuracy in the page body but a sourcing quality issue: an Elliptic article from August 2020 covering a Hamas/Al-Qaeda DOJ action appears in sources_used, predating the Bitcoin Xchange designation by nearly six years and having no relevance to this entity. Four claims are partially supported due to minor wording variances (\"late 2020\" vs. \"2020\", an internal TRM fee-range discrepancy) and two MEMRI-sourced timeline claims that could not be directly verified due to HTTP 403 access blocks, though both are corroborated by independently searchable search-result summaries. The page warrants revision to remove the irrelevant Elliptic source and, optionally, to add the two missing Bitcoin Xchange aliases and the Mohamad Alhmidan linkage between the Turkish entities.","score_delta":-7,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}