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
- 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. - 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.
- 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_revise · Uniswap Google Ad Phishing Campaign (May 2026)
- Sequence
- #3
- Score
- 0 → 0 (-8)
- Cluster
- mainnet-beta
- Slot
- 423150266
- Off-chain at
- 2026-05-30T11:47:48.944Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- FvYmK1W2uacbqLLyJxNm5hDwLEWhyDaJGSmkkKwa4Awo
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1410 chars)
{"actor":"judge","decided_at":"2026-05-30T11:47:48.748Z","decision":"review_revise","investigation_id":"58625252-4783-49c8-bbb5-d44243a2b444","new_score":0,"page_slug":"uniswap-google-ad-phishing-campaign-may-2026","prev_score":0,"reason":"The page is substantially accurate and well-sourced, with 23 of 29 claims confirmed and zero outright disputed findings. The Tier 1 SEAL Radar source directly verifies the core technical, financial, and operational claims. However, claim_findings[2] identifies a material attribution conflict: the page names Inferno Drainer and Vanilla Drainer as the tools used in the May 2026 Uniswap campaign, drawing from SEAL's March 2026 report, while Protos and CoinGabbar — both covering the May 2026 incidents specifically — name 'AngelFerno' instead. The page does not acknowledge or reconcile this discrepancy, which affects a core claim in both the summary and sections[3]. The four partially-supported findings are minor (itemized victim loss list not fully enumerated, suspension timing inferred, 1inch omitted from target list, protocol count discrepancy between 352 and 356). A revision to clarify drainer tool attribution across the March and May 2026 campaign windows is required before the page is considered fully accurate.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}