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 · Cover Protocol
- Sequence
- #4
- Score
- 36 → 36 (0)
- Cluster
- mainnet-beta
- Slot
- 464279374
- Off-chain at
- 2026-11-01T23:36:57.138Z
- Anchored at
- 2026-11-01T23:37:26.000Z
- Block time
- 2026-11-01T23:37:26.000Z
Independent verification
- 1. Database (off-chain)
- BNGpifyDyic1VbCupwjGB671m7SthozchEYuLw47CBHf
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1564 chars)
{"actor":"judge","artifact_identity":"341b5f5ec57634bc5c9dfea5d3f259d1","band_override":null,"blocked_count":1,"decided_at":"2026-11-01T23:36:56.911Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4,"investigation_id":"2ba645fa-983a-424d-9e08-af9a7185f56f","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":36,"page_slug":"cover-protocol","prev_score":36,"reason":"Of 11 claims checked, one was set aside because its source refused the reviewer, and 4 of the remaining 10 (40%) could not be verified: the 1inch cash-out detail (claim_findings[1]), the SAFE price figures (claim_findings[4]), the January 2021 token reissue (claim_findings[8]) and the uncited statement that ZachXBT flagged the entity (claim_findings[10]). None was contradicted, and the core account holds: the December 2020 exploit, the 40 quintillion mint, the Yearn split and the September 2021 shutdown are supported. Wording that overstates its sources also needs correcting: 'returned the extracted funds' (claim_findings[2]), where CoinDesk reports a partial return, and the unconfirmed Binance delisting date (claim_findings[7]). Because the unverified items are mostly unfetched sources rather than refuted claims, the penalty sits at the low end of the significant band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}