Skip to main content
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 · Bybit
View on Solana ↗
Sequence
#3
Score
72 → 72 (0)
Cluster
mainnet-beta
Slot
418531328
Off-chain at
2026-05-09T03:28:15.524Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
A29qP5TUyTADPUrs2ZAg7RH7ptoXJhbxTpwErEvxcCo9
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1094 chars)
{"actor":"reviewer","decided_at":"2026-05-09T03:28:15.267Z","decision":"review","investigation_id":"cc5d2629-b918-4554-b41b-cf765ff31285","new_score":72,"page_slug":"bybit","prev_score":72,"reason":"The core hack narrative is well-sourced and accurate: dates, ETH amounts, attribution chain, and exchange response details are confirmed by primary sources including the FBI IC3 PSA and blockchain analytics firms. The two significant issues are (1) the Overview section's present-tense claim that Bybit 'is registered in the British Virgin Islands' — the BVI entity was dissolved July 4, 2023 and the Regulatory section correctly acknowledges this, creating an internal contradiction — and (2) the UK is listed as a restricted jurisdiction despite Bybit relaunching UK services in December 2025. Secondary issues include the Phemex hack amount ($29M stated vs ~$73M actual total), imprecise DPRK cumulative theft sourcing, and an understated user count.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}