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 · Raydium Protocol
- Sequence
- #7
- Score
- 47 → 62 (+15)
- Cluster
- mainnet-beta
- Slot
- 426514748
- Off-chain at
- 2026-06-14T23:16:12.179Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 3bHYo4rbALT43uoGJfo5iQGxuicyizFnsWtQPzcoeM4M
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1334 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:12.062Z","decision":"review_approve","investigation_id":"ef74b3d0-4fed-4f79-a9d6-19255b26afae","new_score":62,"page_slug":"raydium","prev_score":47,"reason":"All six claim findings (claim_findings[0]–[5]) are supported with no disputed claims across the review (disputed_pct = 0%). The reviewer's calibration assessment is well-grounded: Raydium suffered a single external admin key compromise in December 2022 (claim_findings[0]), responded within four hours, fully compensated victims via a community DAO vote (claim_findings[1]), completed multiple post-exploit security audits (claim_findings[2]), and has since grown to $2.5B TVL with $24.3M quarterly revenue (claim_findings[3]). No fraud, regulatory action, or unresolved risk is attributable to the entity itself (claim_findings[4]). The current WARNING band (score 47) misclassifies a remediated hack victim as an elevated ongoing risk; a CAUTIONARY band (score 62) accurately reflects a legitimate, operational protocol with material but resolved historical caveats. A positive score_modifier_delta of +15 is warranted to correct the miscalibration. Page content stands as published.","score_delta":15,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}