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 · Tiffany Milanovich
- Sequence
- #3
- Score
- 2 → 0 (-10)
- Cluster
- mainnet-beta
- Slot
- 443516148
- Off-chain at
- 2026-08-25T19:07:50.621Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- jvSvt793TXkKLeWLuFsWnHGQVsTNxvznqQSXNqitcvp
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1955 chars)
{"actor":"judge","decided_at":"2026-08-25T19:07:50.326Z","decision":"review_revise","investigation_id":"3456ece0-b6b3-4b34-917f-faee271d0a77","new_score":0,"page_slug":"tiffany-milanovich","prev_score":2,"reason":"The reviewer confirmed 15 of 18 claims, including the central allegation that ZachXBT publicly named Tiffany Milanovich as an alleged 'caller' in a $5M+ crypto support-impersonation operation, and confirmed that the page accurately reports no criminal charges exist against her (claim_findings[3]) — the single most important fact to get right about a named private individual who has not been charged. However, two disputed claims and one partially-supported claim share a common pattern of overstating the scale and independence of the evidence against her. The page states 'bled' and 'harm' are two separate accomplices supplying phishing infrastructure, but its own cited primary source describes them as two aliases of a single person (claim_findings[8]) — inflating the apparent size of the alleged ring. A timeline entry misdates a key Telegram incident to January 2026, when both the cited source and the page's own prose elsewhere correctly place it in January 2025 (claim_findings[16]) — an internal contradiction that could mislead readers about sequencing. And the page describes a Lookonchain post as 'corroborating' ZachXBT's findings when it merely restates them without independent analysis (claim_findings[15]), manufacturing an appearance of multiple sources where there is effectively one. At 11.1% disputed, this falls just inside the minor-issues band, and reviewer confidence (0.75) is solid enough not to warrant further softening. The corrections needed are narrow and factual rather than going to the core of the allegation, which the page hedges appropriately throughout.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}