Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · Aban Tether
View on Solana ↗
Sequence
#3
Score
20 (-10)
Cluster
mainnet-beta
Slot
443517790
Off-chain at
2026-08-25T22:38:29.355Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
9jrqLmhLh64qDU89AUyubiD1tZ9xFFpTAaWRgXQyNaqB
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1927 chars)
{"actor":"judge","decided_at":"2026-08-25T22:38:29.166Z","decision":"review_revise","investigation_id":"a1a38396-d677-46f1-8b7a-1db34180ab43","new_score":0,"page_slug":"aban-tether","prev_score":2,"reason":"The page's core factual claims -- the August 7, 2026 OFAC designation of Aban Tether under Executive Order 13902, the alleged transaction-processing role tied to Nobitex, Wallex, Bitpin and Ramzinex, the joint Shelbit action, and the Bessent quote -- are all independently confirmed against primary Treasury sourcing and multiple outlets, and the page's disambiguation of Aban Tether from Tether Ltd. is accurate and implicates no wrongdoing by Tether Ltd. (claim_findings[26]-[28]). However, two findings the reviewer logged as merely 'partially_supported' are more serious than that label suggests. claim_findings[21] shows the page's claim that this is the 'fourth discrete enforcement wave' is attributed to a source that actually describes only three enforcement layers and predates this action -- the citation does not just fall short, it is contradicted by the material it points to. claim_findings[20] shows the page asserting, in its lead summary and in a section it marks 'high' severity, that secondary-sanctions screening obligations now extend to 'any entity in Aban Tether's on-chain transaction graph' -- a plausible legal inference presented as settled fact with no source establishing it specifically for Aban Tether, in language a reader could mistake for compliance guidance. Three timeline entries additionally use an article's publish date rather than the underlying OFAC action date (claim_findings[29]-[31]), a minor precision issue. No claim was found disputed or unverifiable, and no evidence surfaced that the designation has lapsed or been reversed.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}