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 · Coinbase
- Sequence
- #3
- Score
- 44 → 36 (-8)
- Cluster
- mainnet-beta
- Slot
- 426287648
- Off-chain at
- 2026-06-13T22:15:50.545Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- JCoFVi5AfphBfZBuGtBhq7h8p8F3DwzKDmtjLvzKZoWu
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1401 chars)
{"actor":"judge","decided_at":"2026-06-13T22:15:50.353Z","decision":"review_revise","investigation_id":"34a1d395-ed34-4277-a8ff-7adb35a32f66","new_score":36,"page_slug":"coinbase","prev_score":44,"reason":"The page's major factual record is solid — the CFTC penalty, NYDFS settlement, SEC action and dismissal, ZachXBT reports, and insider breach timeline are all confirmed from Tier 1 sources. However, the review identified four partially supported claims with meaningful errors: claim_findings[4] conflates the Hedger/Replicator automated programs (cited for false reporting) with the wash trading violation, which was actually committed by a former employee; claim_findings[14] overstates the OP token decline on announcement day at 20–25% when the cited CoinDesk source itself reports only a 4% drop in the first 24 hours; claim_findings[8] cites the 2025 SEC dismissal press release to support the 2023 complaint filing; and claim_findings[13] (class action) is unverifiable due to link rot on the primary Tier 1 source. Two high-priority coverage gaps — entirely empty page sections and no on-chain evidence — mean the summary and timeline carry all evidentiary weight with no structural depth. No claims were found to be fabricated or fully disputed.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}