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 · IRS Fake Digital Asset Compliance Portal Letter Campaign — 2026
- Sequence
- #3
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 443518208
- Off-chain at
- 2026-08-25T22:57:01.459Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- HNaZyAvRYHuU7PRp1XTZn6vG6xSVeZhSsX6n9KUTihEV
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1806 chars)
{"actor":"judge","decided_at":"2026-08-25T22:57:01.254Z","decision":"review_approve","investigation_id":"7f3566f6-b222-4575-8585-455856068743","new_score":0,"page_slug":"irs-fake-digital-asset-compliance-portal-letter-campaign-2026","prev_score":0,"reason":"Recounting the reviewer's own claim_findings array (34 entries, not the 36 stated in its summary block) gives 31 confirmed, 2 partially_supported, 1 unverifiable, and 0 disputed. Applying the disputed_pct formula correctly (disputed + unverifiable over total, excluding partially_supported) yields 1/34 = 2.9%, well inside the 0-10% approve band. No claim was found to be disputed, mitigation and victim-guidance content was checked line by line and confirmed to match primary-source advice with no inverted instructions, and the IRS is consistently framed as the impersonated party rather than an actor (claim_findings[0]-[27] throughout). The two partially_supported items are minor: claim_findings[16] shows a quote from IRS-CI's Koopman that drops a trailing clause without ellipsis but does not change its meaning, and claim_findings[21] flags a withdrawal-freeze security tip as a reasonable but not explicitly sourced elaboration on confirmed exchange-security guidance. The single unverifiable item, claim_findings[33], is a timeline entry that cites AVOID.NET itself as the source for an August 7 'no arrests reported' claim -- a circular sourcing practice worth correcting, though the underlying fact is corroborated by every other source reviewed. Coverage gaps are all medium or low priority, so none push the page toward revision. Reviewer confidence (0.88) was the highest of this review run.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}