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 · Clipper
- Sequence
- #3
- Score
- 48 → 33 (-15)
- Cluster
- mainnet-beta
- Slot
- 423940083
- Off-chain at
- 2026-06-03T02:53:57.091Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AzSLPtiBy5a3U2DX1h9CaT2LBbgkdjCW4armWn28ez3M
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1432 chars)
{"actor":"judge","decided_at":"2026-06-03T02:53:56.953Z","decision":"review_revise","investigation_id":"c275fe15-9424-451f-aec8-4c4a41641a09","new_score":33,"page_slug":"clipper","prev_score":48,"reason":"The page's core exploit narrative is well-documented and confirmed across multiple sources. However, two disputed claims require correction before the page can stand. First, claim_findings[4] identifies a clear misattribution: both sources cited to support the claim that ZachXBT flagged Clipper actually describe ZachXBT's investigation of Tokenlon, an entirely separate DEX — Clipper is not mentioned in either article. This is a named-person claim with no supporting evidence and must be removed or corrected. Second, claim_findings[8] dates the $21 million funding announcement to January 31, 2023, when the actual announcement was July 13, 2021; the page appears to have adopted a re-publication date, producing a timeline in which Three Arrows Capital is listed as a participant more than six months after their collapse. Additionally, a high-priority coverage gap — the Polychain Capital lawsuit against Shipyard Software — is material to the entity's governance risk profile and should be added. The under_investigation flag is applied due to the named-person misattribution.","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}