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 · Coinbase
- Sequence
- #2
- Score
- 44 → 44 (0)
- Cluster
- mainnet-beta
- Slot
- 426287644
- Off-chain at
- 2026-06-13T22:15:50.461Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5YvpmnWTHUuRNxkFD6v85wvmcWjenFusTNGcBpRKbwiP
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1154 chars)
{"actor":"reviewer","decided_at":"2026-06-13T22:15:50.353Z","decision":"review","investigation_id":"34a1d395-ed34-4277-a8ff-7adb35a32f66","new_score":44,"page_slug":"coinbase","prev_score":44,"reason":"The Coinbase investigation page is substantially accurate on its major factual claims — the CFTC penalty, NYDFS settlement, SEC action filing and dismissal, ZachXBT reports, insider breach timeline, and ransom details are all well-supported. The primary issues are: a citation mismatch on the SEC filing timeline entry (cites the dismissal PR for the original complaint); an inaccurate wash-trading start date (June 2016 listed but CFTC found conduct in August–September 2016); a disputed OP token decline figure (CoinDesk's own article — the cited source — reports 4% not 20–25% on announcement day); and a content coin peak market cap that varies by source. The page's sections are entirely empty, making the summary and timeline bear all evidential weight. No fabricated or fully disputed claims were found.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}