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
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 426522771
- Off-chain at
- 2026-06-15T00:11:58.825Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- GEZiFu2hYT5H2bMyqEybZX47b8eorpHH8NSBXEkrLCVh
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1114 chars)
{"actor":"reviewer","decided_at":"2026-06-15T00:11:58.719Z","decision":"review","investigation_id":"69ff48ea-7855-4146-b98b-3e2d4bcf06c8","new_score":0,"page_slug":"unk-deaddrop-north-korea-developer-phishing-campaign","prev_score":0,"reason":"The investigation page is well-sourced and highly accurate. All core claims — campaign scope, dates, attribution framing, malware components, delivery mechanism, and theft capabilities — are confirmed by the primary Proofpoint report and multiple independent secondary outlets. Two minor partial-support findings involve an incomplete sector label ('finance' vs. 'financial services / business services') and the omission of fictitious company personas (Pulsynk, Trixauvex) from the lure taxonomy alongside the confirmed legitimate-company impersonations. One claim (approximate campaign start date of April 1) is an investigator inference not directly traceable to the cited source. No disputed or fabricated claims were found.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}