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 · Tiffany Milanovich
- Sequence
- #2
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 443516115
- Off-chain at
- 2026-08-25T19:07:50.486Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DPhGEcX22sAeMHNrijLosFRJHK3ptPDSc3w5Zo94fC9X
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1035 chars)
{"actor":"reviewer","decided_at":"2026-08-25T19:07:50.326Z","decision":"review","investigation_id":"3456ece0-b6b3-4b34-917f-faee271d0a77","new_score":2,"page_slug":"tiffany-milanovich","prev_score":2,"reason":"The page's core narrative — ZachXBT's August 10, 2026 allegations against Tiffany Milanovich as a 'caller' in a $5M+ crypto support-impersonation ring, and the underlying Daghita/CMDSS $46M theft case — is well supported by its cited sources and consistently corroborated by independent secondary reporting, with allegations properly hedged throughout. Two defects were found: the page's own primary source describes 'bled' and 'harm' as two aliases of one additional threat actor, not two actors as the page states, and the timeline misdates the Daghita Telegram incident to January 2026 when the cited TRM Labs source (and the page's own prose elsewhere) places it in January 2025.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}