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 · Raydium Protocol
- Sequence
- #6
- Score
- 47 → 47 (0)
- Cluster
- mainnet-beta
- Slot
- 426514745
- Off-chain at
- 2026-06-14T23:16:12.123Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- FRpk3vasw83L6ax1k4HR2MRkmVT4fxPPNeVzGK3n5bqd
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1782 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:16:12.062Z","decision":"review","investigation_id":"ef74b3d0-4fed-4f79-a9d6-19255b26afae","new_score":47,"page_slug":"raydium","prev_score":47,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. Raydium is a well-established, operational Solana DEX/AMM — the dominant protocol on its chain by volume — that suffered a single external hack in December 2022 resulting in $4.4M stolen via a compromised admin private key (suspected trojan on a team VM). The incident was not caused by protocol fraud, intentional negligence, or design manipulation: Raydium's own post-mortem notes the intrusion vector was unconfirmed but suspected to be external malware. The team responded rapidly (hotfix in ~4 hours), completed four additional security audits, fully compensated victims via a community DAO vote, and has since grown to $2.5B TVL and $24.3M quarterly revenue as of Q3 2025. Under the band semantics, 20-49 WARNING is reserved for \"elevated fraud/loss risk or unresolved severe incident\"; neither condition applies here — the incident is fully resolved, no ongoing risk is elevated above baseline DeFi operational risk, and there is no fraud attribution to the entity. A score of 62 and CAUTIONARY band is appropriate, reflecting the legitimate operation with material historical caveats (one significant past hack, pseudonymous team, presence of third-party impersonation scams in the ecosystem) that an informed user should know about, without misclassifying a hack victim as a fraud risk.","score_delta":0,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}