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 · Nobitex / Wallex / Bitpin / Ramzinex
View on Solana ↗
Sequence
#5
Score
26 → 26 (0)
Cluster
mainnet-beta
Slot
457556592
Off-chain at
2026-10-16T07:37:21.156Z
Anchored at
2026-10-16T07:37:45.156Z
Block time
—

Independent verification

1. Database (off-chain)
Am6MCxfVF3caeFsJZKvaM9wsM28SuATpSLeg4ytyjQM1
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1908 chars)
{"actor":"reviewer","artifact_identity":"1d78b358bc70fb1459584cbba1f4d746","decided_at":"2026-10-16T07:37:20.915Z","decision":"review","disputed_pct":0.2,"findings_hash":"53XkVySSMZLnvHk4btk25kBc9A7usz1xfJrJEK1Raaja","investigation_id":"a8f09035-635e-4b29-9611-310c173e1f31","mode":"findings_only","new_score":26,"page_content_hash":"521e67563060f34396d0b344829923458d2cca265c12219b0bfecd2b2ab6b45a","page_slug":"nobitex-wallex-bitpin-ramzinex","prev_score":26,"reason":"The page's core narrative -- the June 2, 2026 OFAC designation of Nobitex, Wallex, Bitpin, and Ramzinex, the named individuals, the per-exchange and combined volume figures, the Kharrazi family ownership reporting, the Central Bank of Iran USDT figures, the Economic Fury campaign timeline (Zedcex/Zedxion, CBI wallet freeze, Tether freeze), and the June 2025 Predatory Sparrow hack and source-code leak -- is accurately and specifically sourced to the primary Treasury release, TRM Labs, Elliptic, and contemporaneous news coverage, and checks out against those sources. Several discrete defects were found: a misquoted/composite Bessent quotation that adds words not found in the Treasury release; an unsupported extension of Nobitex's confirmed Garantex exposure to an apparently unrelated Russia-focused Grinex/Kyrgyzstan sanctions-evasion story; an off-by-one-day error in the Predatory Sparrow hack date (page says June 17, 2025; independently corroborated reporting says June 18), which also skews the page's 'two days after the breach' framing of the source-code leak; and an overstated characterization of a speculative $55 million USDT recovery estimate as settled fact. The page is largely silent on anything after the June 2 designation despite being reviewed over four months later.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}