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
- Sequence
- #2
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 426254019
- Off-chain at
- 2026-06-13T18:33:30.020Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BYN2CmznPSjdRS2sgej54EogRZ9r9DhVWXYZrkkGCRD2
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1302 chars)
{"actor":"reviewer","decided_at":"2026-06-13T18:33:29.901Z","decision":"review","investigation_id":"aa6fdc14-f59a-4b01-b300-fddbf2224685","new_score":2,"page_slug":"solana-blinks-durable-nonce-drainer-kits-2026","prev_score":2,"reason":"The investigation is factually dense and well-sourced, with the most critical claims — the Drift Protocol exploit details, Rublevka Team operation, SlowMist assign-instruction case, and Blowfish Aqua/Vanish disclosure — all confirmed or partially supported by Tier 1 or strong Tier 2 sources. The primary weaknesses are: one commission structure inaccuracy (page says '20-25% for Rublevka affiliates' when affiliates actually receive 75-80%, i.e. the operator takes 20-25%); the DEV Community article (key source for agentic drainer claims and Q1 2026 Blink phishing incident) returned 404 during review; and several financial figures show minor discrepancies across sources (JLP/USDC token amounts, Radiant Capital $53M vs $50M). The 'under one minute' characterization of the Drift drain is slightly imprecise — the full drain took ~12 minutes, though the durable nonce transactions executed within seconds of each other.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}