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_approve · CLINKSINK Drainer
- Sequence
- #3
- Score
- 1 → 1 (0)
- Cluster
- mainnet-beta
- Slot
- 461976703
- Off-chain at
- 2026-10-27T06:55:35.702Z
- Anchored at
- 2026-10-27T06:55:51.000Z
- Block time
- 2026-10-27T06:55:51.000Z
Independent verification
- 1. Database (off-chain)
- AyZJZRKszLBa7ALpbiWXWGZxWMmjvkVgT9DmR9pNzaRh
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1412 chars)
{"actor":"judge","artifact_identity":"192517c6a6604e8cdeeff2d07bc0f9af","band_override":null,"decided_at":"2026-10-27T06:55:35.318Z","decision":"review_approve","delist_requested":false,"disputed_pct":0.0909,"investigation_id":"43b5c8f2-cf48-4c67-a520-c4a1545c94df","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":1,"page_slug":"clinksink-drainer","prev_score":1,"reason":"None of the 10 checked claims was disputed. One claim (claim_findings[9], the 2026 CleanSky blog) could not be checked because the reviewer did not fetch it, which puts the disputed share at 10%, the top of the approve band. Three claims were only partly supported: the $900,000 figure is an estimate (claim_findings[0]), 'each tied to its own payout address' conflicts with Mandiant's 42 wallets for 35 IDs (claim_findings[1]), and the 123,500 follower count was not found in the fetched sources (claim_findings[6]). These are wording and precision issues on secondary details, not errors in the core allegations, which match the Tier 1 Mandiant report. The review found no sign of a shutdown or sanction and no material omission, so the percentage band stands.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}