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 · Cashio
- Sequence
- #3
- Score
- 5 → 0 (-15)
- Cluster
- mainnet-beta
- Slot
- 464357784
- Off-chain at
- 2026-11-02T04:17:00.304Z
- Anchored at
- 2026-11-02T04:17:24.000Z
- Block time
- 2026-11-02T04:17:24.000Z
Independent verification
- 1. Database (off-chain)
- 8xjN4Yh5BNQaCS28cSViApeon6A1ZiQRxMrtJvst5CKx
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1465 chars)
{"actor":"judge","artifact_identity":"137564cb3cdd151ed3a11f5f88c2f64a","band_override":null,"decided_at":"2026-11-02T04:16:59.955Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"2098c3c5-0cdc-4c96-a8bf-cadb693e915a","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"cashio","prev_score":5,"reason":"Of 15 reviewed claims, 2 were disputed and 3 could not be verified, giving a 33% disputed-or-unverifiable rate, which falls in the significant-issues band. The disputed items are the same error repeated twice: $10.8M is labeled USDT where Rekt says UST (claim_findings[4] and [5]). The unverifiable items are the laundering specifics ($15.3M in three transactions, 1,610 ETH to a mixer in 17 transactions) and the June 2022 Medium announcement (claim_findings[2], [3], [14]). The core narrative (the March 2022 exploit, about $52M lost, the CoinDesk pseudonym investigation and the reported DOJ probe) is supported by Tier 1 and Tier 2 sources, so the penalty sits at the low end of the band. The attack time is also given inconsistently as 08:15 and 08:23 UTC (claim_findings[0] and [1]), and no timeline entry has a source.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}