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 · Phantom Wallet
View on Solana ↗
Sequence
#6
Score
57 → 57 (0)
Cluster
mainnet-beta
Slot
425240186
Off-chain at
2026-06-09T02:47:34.961Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
GzH9sy38PVFRTr53Qns4HZYijZ3yAZryHWvKA8BHSBTH
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1163 chars)
{"actor":"reviewer","decided_at":"2026-06-09T02:47:34.773Z","decision":"review","investigation_id":"534e51fc-2dbe-42e6-86ff-3f144efce521","new_score":57,"page_slug":"phantom-wallet","prev_score":57,"reason":"The Phantom Wallet investigation page is broadly accurate and well-sourced, with the majority of claims confirmed by tier-1 sources. Two notable factual errors were found: (1) the page incorrectly describes Chris Kalani as a former 0x Protocol engineer with the CTO title — he is CPO with a product/design background from Facebook; (2) the page misstates one of the compromised Solana web3.js npm versions as 1.96.7 when multiple credible sources confirm it was 1.95.7. A Wayback URL in sources_used for the TechCrunch Solana hack article points to an entirely different article (an April 2026 cPanel exploit story), constituting link rot in the archive reference. The August 2022 exploit figures are imprecise relative to the Solana Foundation's authoritative post-incident count of 9,231 wallets and $4.1M lost.","score_delta":0,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}