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 · Dunamu / Upbit
View on Solana ↗
Sequence
#2
Score
38 → 38 (0)
Cluster
mainnet-beta
Slot
443522182
Off-chain at
2026-08-26T22:07:23.186Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
AsBaXkmic9C7xbtk2TitMHFM5MZu9gy18jG6nBQ25kHS
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1455 chars)
{"actor":"reviewer","decided_at":"2026-08-26T22:07:22.943Z","decision":"review","investigation_id":"f4b7d1d8-e03d-4c79-be28-f2db3d0ce5f5","new_score":38,"page_slug":"dunamu-upbit","prev_score":38,"reason":"The page's core narrative -- the November 2025 Solana hot-wallet breach, the suspected (not confirmed) Lazarus Group attribution, the confirmed 2019 Lazarus/Andariel attribution, the FIU's 2025 AML/KYC sanctions, and the July 2026 FSS sanction proceedings -- is well supported by independent reporting and correctly distinguishes suspicion from confirmation where the underlying sources do. The most material issues found are: an overstated market-share/volume figure not matched by current third-party data, a mischaracterization of the Naver Financial transaction as consolidating Dunamu's position rather than an acquisition of it, a first-of-month date-placeholder error on the Virtual Asset User Protection Act's effective date (stated July 1, actually July 19, 2024), understatement of the scope of an April 2026 court ruling that fully (not partially) overturned a suspension now under appeal, and a one-day discrepancy in the BonkDAO attack date. No claims were found to be outright disputed by more credible sources, and Upbit/Dunamu is correctly treated throughout as a currently operating entity.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}