Skip to main content
AVOID.NET
Sign in
← 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 · WEMIX / WEMIX$ Stablecoin
View on Solana ↗
Sequence
#2
Score
22 → 22 (0)
Cluster
mainnet-beta
Slot
443520615
Off-chain at
2026-08-26T11:32:52.838Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
2kN3k1fiPaKSGoufUraomL1AXYhbyxVsooojYh1MA67p
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1326 chars)
{"actor":"reviewer","decided_at":"2026-08-26T11:32:52.731Z","decision":"review","investigation_id":"6a784339-9712-41d2-8a47-0a6059ddf02f","new_score":22,"page_slug":"wemix-wemix-stablecoin","prev_score":22,"reason":"The large majority of the page's discrete factual claims -- hack amounts, dates, court rulings, disclosure quotes, and delisting mechanics -- were independently confirmed against the cited or equivalent sources, including several verbatim-quote checks. However, the review found a real factual error in the relisting timeline (major exchanges relisted in December 2023, not by August 2023, and Upbit appears to have never relisted WEMIX), an internally contradictory statement about when compromised keys were exposed before the February 2025 hack, an arithmetic conflation in the summary between the value of minted tokens and total combined losses, a mismatched price-decline percentage relative to the page's own cited pre-incident price, a source citation that describes the wrong incident, and a significant omission of the criminal prosecution and eventual acquittal of Wemade's former CEO tied to the 2022 circulation-misreporting conduct discussed on the page.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}