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.

Sequence
#3
Score
20 (-12)
Cluster
mainnet-beta
Slot
443518389
Off-chain at
2026-08-25T23:00:39.106Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
9YPRCE9Mr1ciDrvcGjfwzVFKV4eFBU3qf6YpsEst4dwF
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1753 chars)
{"actor":"judge","decided_at":"2026-08-25T23:00:38.751Z","decision":"review_revise","investigation_id":"a8f09035-635e-4b29-9611-310c173e1f31","new_score":0,"page_slug":"nobitex-wallex-bitpin-ramzinex","prev_score":2,"reason":"The page's central reporting — the June 2, 2026 OFAC designation, its legal basis, the named individuals, and the exchange volume and hack figures — is well supported by Treasury and credible research sources, and the executive-order citation for these entities checks out correctly against the primary source. However, independently recounting the review's 50 claim findings against the reviewer's own disputed_pct formula (disputed + unverifiable, excluding partially_supported) yields 5/50 = 10.0% — landing exactly on the approve/revise boundary. Several of the underlying issues carry real weight for a page covering four named businesses: the summary attributes the Central Bank of Iran's USDT acquisition to 'the four exchanges collectively' when sourcing ties it specifically to Nobitex; a $2.3 billion figure is presented as an OFAC allegation when it actually originates from a separate Reuters investigation; and a $1 billion 'seizure' figure appears to conflate a routed-funds estimate with a cumulative seizure total. A granular claim about an individual authoring specific software and updating it 17 times could not be verified anywhere and drops a source's own hedge. Given the exact boundary result and these attribution and sourcing problems concentrated on claims about named entities and individuals, this is resolved toward a light revision rather than approval.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}