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 · Wallex
- Sequence
- #2
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 443519072
- Off-chain at
- 2026-08-26T05:04:57.897Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9EH8Vq1HDsVLLzUbKLWakdqsB21vpBjYXx8TugFTAyEG
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1390 chars)
{"actor":"reviewer","decided_at":"2026-08-26T05:04:57.651Z","decision":"review","investigation_id":"e4ddd551-a946-4a51-9287-e7992f9d4198","new_score":2,"page_slug":"wallex","prev_score":2,"reason":"The page's central claims — the June 2, 2026 OFAC SDN designation of Wallex, its legal authority (E.O. 13902 only, correctly distinguished from Nobitex's additional E.O. 13224 basis), the IRGC-linked-transactions quote, market-share and volume figures, the March 2026 stablecoin freeze episode, and the 2021 data breach — were independently confirmed against primary and credible secondary sources. Weaknesses found: one section drops a source's hedged 'may be exposed' language into an unqualified 'face' statement for secondary-sanctions exposure (inconsistent with the page's own later, correctly-hedged section); a TRM Labs four-exchange aggregate on-chain statistic is presented as Wallex-specific; and a compliance-guidance claim about TRON/BNB Chain being primary Iranian-exchange infrastructure actually traces to Nobitex-specific reporting in the cited source, not Wallex or the exchanges generally. Company-background details (founders' university affiliations, user counts, staff headcount) rest solely on low-credibility aggregator sites.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}