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 · Audius
- Sequence
- #4
- Score
- 58 → 58 (0)
- Cluster
- mainnet-beta
- Slot
- 457480280
- Off-chain at
- 2026-10-16T03:03:18.440Z
- Anchored at
- 2026-10-16T03:03:20.305Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9wdnbbzBzqMfv5XxTnWmd5qkAbTnWr6o4RxojeMPvt25
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1798 chars)
{"actor":"reviewer","artifact_identity":"b17af02f230070065848e9f2e46b25e1","decided_at":"2026-10-16T03:03:18.238Z","decision":"review","disputed_pct":0.5263,"findings_hash":"F8oaTNUVo4d3ouVdPJJ7xoh77f225SN7zDvYKm1Lm5C7","investigation_id":"783e4b94-9c36-46a8-b071-ef7fc56191b5","mode":"findings_only","new_score":58,"page_content_hash":"cd40dcd8d6e8dd69c030b10cff66565b9968a1c901553d3323102d41cc9b89a7","page_slug":"audius","prev_score":58,"reason":"The core incident narrative - the July 23, 2022 governance exploit, its storage-collision root cause, the ~18.56M AUDIO theft, the 704.17 ETH Uniswap swap, and the Tornado Cash laundering and subsequent OFAC/DOJ actions - is well supported by multiple independent sources and matches Audius's own post-mortem closely, including an exact match on the cited transaction hash. However, the page mischaracterizes the address it labels 'Tornado Cash' as actually the attacker's own wallet (and transcribes it one character short of a valid address), misdates the AUDIO/mainnet launch as September 2020 when it was October 2020 (repeated in two sections and the timeline), lumps PeckShield in with pre-exploit auditors when its documented role was post-exploit analysis, and presents a mid-2025-sourced 7.5-8 million MAU figure as current 'as of early 2026' in two places. Founder titles and the Series A lead-investor framing are each slightly off relative to contemporaneous 2018 reporting but are minor. Overall the page is directionally accurate and well-sourced on the headline exploit but contains several fixable factual and dating errors that a careful reader relying on exact figures would be misled by.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}