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 · Wallex
View on Solana ↗
Sequence
#3
Score
2 → 0 (-8)
Cluster
mainnet-beta
Slot
443519222
Off-chain at
2026-08-26T05:04:58.123Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
CAezsYqgdXVrMi3uvtpsLE8ygpAHUqTmyBCAcJm6yEos
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1897 chars)
{"actor":"judge","decided_at":"2026-08-26T05:04:57.651Z","decision":"review_revise","investigation_id":"e4ddd551-a946-4a51-9287-e7992f9d4198","new_score":0,"page_slug":"wallex","prev_score":2,"reason":"The page's central allegations hold up well: the June 2026 OFAC designation, its legal basis under E.O. 13902, the IRGC-linked transaction language, market-share figures, the March 2026 stablecoin freeze, and the 2021 data breach were all independently confirmed against primary or credible secondary sources, and the reviewer specifically confirmed the page correctly cites only E.O. 13902 rather than conflating Wallex with a co-designated exchange's broader legal basis (claim_findings[3]). No claim was found to be disputed. However, the review surfaced two instances where statistics reported for a four-exchange group were presented as if specific to Wallex alone: an on-chain address count (claim_findings[11]) and, more consequentially, compliance guidance naming TRON and BNB Chain as 'primary infrastructure chains' for Wallex, where one of the three cited sources describes the BNB Chain finding for a different exchange and another names Ethereum instead of BNB Chain (claim_findings[26]). The page also states elsewhere, in its main designation section, that foreign institutions 'face' secondary-sanctions exposure, dropping the source's 'may be exposed' hedge — while a later section on the same page correctly preserves that hedge (claim_findings[7]), an internal inconsistency on a legally consequential point. None of these issues contradict the page's core findings, but they affect content a reader could act on (compliance screening, understanding of legal exposure), which is enough to warrant correction rather than a clean pass.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}