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 · AudiA6 Crypto Laundering Network
- Sequence
- #3
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 443561128
- Off-chain at
- 2026-09-02T00:35:54.128Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DX8gZNrf6uwXGMMcRfFkwtw8ZQX7JhKRTFU553sx8HUy
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1199 chars)
{"actor":"judge","artifact_identity":"6b60992870eb4d3c372460e6243a671b","band_override":null,"decided_at":"2026-09-02T00:35:53.960Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"255371db-55cc-4c52-9538-13b49927f4ef","new_score":0,"page_slug":"audia6-crypto-laundering-network","prev_score":0,"reason":"Of 16 claims checked, 14 were fully confirmed against primary sources (DOJ, US Secret Service, Europol) and independent secondary reporting, with disputed_pct at 0%. The two remaining claim_findings[9] items were marked only partially_supported over a minor internal date/intermediary inconsistency in the LastPass-to-Wasabi Wallet tracing detail, not a factual dispute about the underlying $7 million figure. No claims were disputed, no sources showed link rot or staleness, and the only coverage gaps flagged were medium/low priority (defense response, minor victim linkages, on-chain evidence, ongoing case developments) — none rise to high priority. This pattern supports approval with the page left as-is.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}