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 · Wasabi Protocol
- Sequence
- #6
- Score
- 8 → 3 (-5)
- Cluster
- mainnet-beta
- Slot
- 461841578
- Off-chain at
- 2026-10-26T22:57:00.375Z
- Anchored at
- 2026-10-26T22:57:07.000Z
- Block time
- 2026-10-26T22:57:07.000Z
Independent verification
- 1. Database (off-chain)
- EWEdjkKzSp4mvs1ijUJnUPHJhRiqA5fKvHbSMRyH8XhD
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2477 chars)
{"actor":"judge","artifact_identity":"4ff8d61c69898b591e7ade7b5b063c4f","band_override":{"actual_delta":-5,"actual_verdict":"review_revise","disputed_pct":0,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"The core incident facts hold up: of 13 claims checked, 12 count toward the percentage (one was excluded because its source blocked the reviewer) and none were disputed or unverifiable, so the claim-level disputed rate is 0%. The verdict moves off approval only because of the high-priority coverage gap on current status: the page's latest information is from May 2026, and it is now October 2026, so later compensation, relaunch or legal developments are unchecked. Smaller issues are the CertiK $5.5M figure with no supporting citation (claim_findings[3]), a SlowMist affiliation not stated in the cited source (claim_findings[8]), and the May 3 and May 9 status claims resting on a blocked tier-3 aggregator (claim_findings[5]). The one omission (LP-token warning) is minor and no shutdown or sanction contradicts the page."},"blocked_count":1,"decided_at":"2026-10-26T22:56:59.980Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"994d3e0f-b60a-4242-965c-5a18d3a83a5d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":3,"page_slug":"wasabi-protocol","prev_score":8,"reason":"The core incident facts hold up: of 13 claims checked, 12 count toward the percentage (one was excluded because its source blocked the reviewer) and none were disputed or unverifiable, so the claim-level disputed rate is 0%. The verdict moves off approval only because of the high-priority coverage gap on current status: the page's latest information is from May 2026, and it is now October 2026, so later compensation, relaunch or legal developments are unchecked. Smaller issues are the CertiK $5.5M figure with no supporting citation (claim_findings[3]), a SlowMist affiliation not stated in the cited source (claim_findings[8]), and the May 3 and May 9 status claims resting on a blocked tier-3 aggregator (claim_findings[5]). The one omission (LP-token warning) is minor and no shutdown or sanction contradicts the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-5,"scored_claims":12,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}