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 · CLINKSINK Drainer
- Sequence
- #4
- Score
- 1 → 1 (0)
- Cluster
- mainnet-beta
- Slot
- 462364802
- Off-chain at
- 2026-10-28T05:52:11.439Z
- Anchored at
- 2026-10-28T05:52:34.000Z
- Block time
- 2026-10-28T05:52:34.000Z
Independent verification
- 1. Database (off-chain)
- 3Uq5XpcMK131SdP4eWpCLkhicyveLuQSseLqsZc7vvF4
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2113 chars)
{"actor":"reviewer","artifact_identity":"88e0c717752fe4508d50ac6be1cd3c0d","decided_at":"2026-10-28T05:52:11.265Z","decision":"review","disputed_pct":0.0556,"findings_hash":"314R2y6xo68xJGe6LgjRfFPB3eEj2MomUByQYbMGrUWB","investigation_id":"43b5c8f2-cf48-4c67-a520-c4a1545c94df","mode":"findings_only","new_score":1,"omissions":{"material":0,"total":2},"page_content_hash":"56c2d5363a63003ae6860c4d7d6cfd583962d790a17fa97faa132cba3a336cfa","page_slug":"clinksink-drainer","prev_score":1,"reason":"This page is well-sourced and unusually well-hedged. Every major factual claim -- the DaaS model and ~20/80 split, the 35 affiliate IDs, the Phantom/DappRadar/BONK-themed airdrop lures, the $900,000 estimate and its 1,491 SOL/$180,000 on-chain basis, the Chick Drainer/Rainbow Drainer lineage, and the Mandiant X-account hijack details (brute-force, 2FA lapse, ~123,000+ followers, no systems compromised) -- is directly corroborated by Mandiant's original January 2024 blog post and independently corroborated by multiple security-journalism outlets (BleepingComputer, SecurityWeek, The Hacker News, Coinlive). The one overstated claim is the 'browser blacklists' addition to a secondary source's domain-rotation detail, which only discusses wallet blacklists. A second claim -- that hijacking high-follower accounts is a 'broader pattern' specific to CLINKSINK operators -- is not supported by any cited source and could not be independently confirmed. The page's own hedging about an unconfirmed 2026 CLINKSINK wave is accurate: no CLINKSINK-specific reporting for 2025-2026 could be found. Coverage gaps are mostly reasonable given the subject (a malware kit, not an ongoing company) -- no independent on-chain follow-up, no victim case studies, and no law-enforcement outcome to report because none appears to exist.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}