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 · AscendEX (BitMax)
View on Solana ↗
Sequence
#2
Score
12 → 12 (0)
Cluster
mainnet-beta
Slot
443515298
Off-chain at
2026-08-25T14:25:29.815Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
Ff72HqgM1V5rTMux2R9KURVuFYQMK4LQ3gHTqGHPQGEr
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1159 chars)
{"actor":"reviewer","decided_at":"2026-08-25T14:25:29.078Z","decision":"review","investigation_id":"a2376978-bfce-4a51-9673-406ac00d7f5d","new_score":12,"page_slug":"ascendex-bitmax","prev_score":12,"reason":"Most factual claims on this page — the ZachXBT withdrawal-freeze reporting, the StablR/USDR/EURR incident, the December 2021 hack figures, and the regulatory-status material — are well supported by their cited or independently located sources. However, the page repeats an unsupported Lazarus Group attribution for the 2021 hack that appears in none of its four cited sources and is contradicted by a dedicated incident tracker (rekt.news), miscites the RootData 46% transparency figure to sources that do not contain it, omits that the 2021 reimbursement pledge was in fact fulfilled, and presents a 'no response' current-state description that was overtaken within days by AscendEX's full operational shutdown — a resolution covered on two other avoid.net pages that substantially overlap this one's scope.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}