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_approve · Wasabi Protocol
- Sequence
- #15
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 464249845
- Off-chain at
- 2026-11-01T21:51:34.687Z
- Anchored at
- 2026-11-01T21:51:57.000Z
- Block time
- 2026-11-01T21:51:57.000Z
Independent verification
- 1. Database (off-chain)
- Hrq2QnnZzKCM719xFFe828MKjFLBjFYwKjvjUE56jjgz
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1462 chars)
{"actor":"judge","artifact_identity":"9a97725cb2e06ec077c3d3d292a4f0e9","band_override":null,"blocked_count":1,"decided_at":"2026-11-01T21:51:34.171Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"994d3e0f-b60a-4242-965c-5a18d3a83a5d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":52,"page_slug":"wasabi-protocol","prev_score":52,"reason":"Of 14 claim findings, 13 were counted after leaving out claim_findings[13] (DefiLlama TVL), which the reviewer could not fetch because the source was blocked; none of the 13 were disputed or unverifiable, so the disputed share is 0%. Two findings were only partly supported (claim_findings[2], a vault name not found in the fetched source, and claim_findings[3], a Blockaid revoke-approvals detail missing from the cited article), but both are minor details and not the core allegations. The core account of the exploit, the root cause, fund movement and the 2024 funding round matched Tier 1 and Tier 2 sources. No shutdown, sanction or rebrand was found, and the only omission (compensation status) is minor. The blocked TVL check is a coverage limit, not a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":13,"sequence_num":15,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}