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 Digital Asset Compliance Portal Phishing Campaign 2026
- Sequence
- #3
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 443516352
- Off-chain at
- 2026-08-25T19:16:36.616Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- B6w6w9xogpXgXQ8fAw4RiXtAVohh2QSe3yCR165ySb2y
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1529 chars)
{"actor":"judge","decided_at":"2026-08-25T19:16:36.273Z","decision":"review_approve","investigation_id":"ceb1d5c4-9dd4-4214-97fb-adc13a573ab8","new_score":0,"page_slug":"irs-digital-asset-compliance-portal-phishing-campaign-2026","prev_score":0,"reason":"Independent fact-checking of all 18 claims on this page found none disputed and none unverifiable, a 0% disputed rate that falls well within the approval range. Fifteen claims were directly confirmed against primary sources including the IRS's own fraud alert and Chainalysis's crime report; three (claim_findings[10], [15], [17]) were only partially supported due to minor framing issues — an unattributed analytical label, a slightly narrowed statistic, and an overstated dating of a follow-up IRS statement — none of which change the underlying facts or misrepresent the IRS's role as the impersonated party. Two apparent link-rot issues (Bloomberg and Coinbase URLs returning HTTP 403) were resolved as bot-blocking, not dead links, and corroborated through independent secondary sources and archive timestamps. The two coverage gaps the reviewer flagged (added context on real IRS tax-reporting rules, and reliance on a single DarkTower/Coinbase investigation for technical detail) are both rated medium priority and represent opportunities to expand the page, not flaws serious enough to require correction before publication.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}