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 · Solana Blinks / Durable-Nonce Drainer Kits (2026)
- Sequence
- #3
- Score
- 2 → 0 (-10)
- Cluster
- mainnet-beta
- Slot
- 426254022
- Off-chain at
- 2026-06-13T18:33:30.154Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9ZM2v8gAx5c48cdt3MbvkS3bphFVTPaLnEvegwBaa5Kj
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1396 chars)
{"actor":"judge","decided_at":"2026-06-13T18:33:29.901Z","decision":"review_revise","investigation_id":"aa6fdc14-f59a-4b01-b300-fddbf2224685","new_score":0,"page_slug":"solana-blinks-durable-nonce-drainer-kits-2026","prev_score":2,"reason":"The review confirmed 19 of 31 claims outright and found zero directly disputed claims, placing this in the 10–30% disputed band (reviewer-stated disputed_pct: 0.16). However, three corrections are warranted before approval. First, claim_findings[28] documents a confirmed factual error: the page states '20–25% for Rublevka Team affiliates' when the Recorded Future Tier 1 source explicitly confirms affiliates receive 75–80%, with the operator retaining 20–25%. Second, claim_findings[25] shows the page's JLP and USDC figures ($155.6M and $60.4M) differ materially from Chainalysis's Tier 1 figures ($159.3M and $71.4M), which are unreconciled on the page. Third, claim_findings[19] characterizes the Drift drain as occurring 'under one minute' while multiple sources report the full drain took approximately 12 minutes, though the durable nonce transactions themselves executed within seconds. A high-priority coverage gap on on-chain verification of the $90M H1 2025 aggregate loss figure also remains open.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}