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
#1
Score
74 → 74 (0)
Cluster
mainnet-beta
Slot
417878548
Off-chain at
2026-05-06T02:50:06.600Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
AYou1mvo9BEgfHg67w3xi1kwTqNfvkdgzk3ksKo4NCnb
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (854 chars)
{"actor":"reviewer","decided_at":"2026-05-06T02:50:06.503Z","decision":"review","investigation_id":"534e51fc-2dbe-42e6-86ff-3f144efce521","new_score":74,"page_slug":"phantom-wallet","prev_score":74,"reason":"The investigation is well-sourced and largely accurate. Two factual errors were identified: (1) the Solana web3.js compromised version is listed as '1.96.7' but should be '1.95.7', and (2) the timeline attributes the CFTC no-action letter to the 'Division of Enforcement' when it was issued by the Market Participants Division. The August 2022 exploit loss estimate of '$5-7 million' skews slightly above most cited sources ($4-6M). Three claims are unverifiable due to reliance on self-reported metrics.","score_delta":0,"sequence_num":1,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}